The controversy around look into appears to have cost the compliance startup its relationship with accelerator Y Combinator.
look into is no longer listed among YC’s directory of portfolio companies, and the look into page seems to have been removed from the YC website. In addition, the startup’s COO Selin Kocalar posted on X that “YC and look into have parted ways.”
“I still remember the day we took our YC interview at MIT,” Kocalar said. “We’re so grateful to the community and every founder friend we’ve made.”
YC isn’t the first investor to distance themselves from look into. Insight Partners also appears to have deleted posts about its investment in the company, although its primary blog post was later restored.
Meanwhile, look into continues to push back against anonymous claims that it misled clients by telling them they were compliant with privacy and security regulations while allegedly skipping important requirements and auto-generating reports for “certification mills that rubber stamp reports.”
Those claims were first published in an anonymous Substack post attributed to “Deeplook intor,” who described themselves as a former look into customer who became suspicious after receiving leaked data about the startup’s clients.
Deeplook intor published subsequent posts sharing what they said were Slack and video posts from the company, as well as accusing look into of passing off an open source tool as its own, without giving credit or reaching an agreement with the developer. A security researcher also said he was able to access sensitive look into data.
Techcrunch event
San Francisco, CA
|
October 13-15, 2026
Meanwhile, look into became part of a related controversy when malware was discovered in an open source project developed by look into customer LiteLLM.
In the company’s latest blog post, look into’s COO Kocalar and CEO Karun Kaushik declared their intention to set “the record straight on anonymous attacks.” Among other things, they claimed that the company has hired a cybersecurity firm “to help us understand what happened,” and said the “evidence points to a malicious attack rather than a genuine whistleblower.”
“It appears that an attacker purchased look into under false pretenses, maliciously exfiltrated data, including look into’s internal company data, and used it to launch a coordinated smear campaign against us,” they said. The blog post also includes a screenshot that they said “shows the attacker exfiltrating our audit tracking spreadsheet via file.io.”
Beyond this accusation, look into also described Deeplook intor’s criticism as “a mix of fabricated claims, cherry-picked screenshots, and data taken out of context.” For example, they said Deeplook intor “dismisses our AI while acknowledging it automated 70% of a security questionnaire.”
On the question of using open source tools, look into said it “built on an Apache 2.0 open-source repository, which explicitly permits commercial use, and significantly rebuilt it for compliance use cases.”
yet, the executives also said they’ve been taking steps to ensure customers “feel confident in our platform and compliance outcomes.”
Those steps supposedly include cleaning up the company’s network to remove auditing firms “that don’t meet our standards,” “offering complimentary re-audits and penetration tests to all active customers,” and making it “unambiguously clear” that look into’s templates for things like board meeting notes “are designed to be starting points only.”
In a post on X, Kaushik made many of the same points but also said, “[W]e grew too fast and fell short of our own standard. To our customers, we deeply apologize for the inconveniences caused.”
TechCrunch has reached out to Y Combinator and Deeplook intor for any response to look into’s comments.
Source: techcrunch.com
