Public data notice

TrueScrape, operated by Omit System, trading as TrueScrape, a sole proprietorship operating from India, provides an API that returns publicly accessible data from social, commerce and property websites in a consistent shape. Customers use it for analytics, market research, brand monitoring and academic work.

Only what a browser shows without logging in. Public profile details, public posts and their engagement counts, public comments, public advertising records, and captions or transcripts a platform publishes publicly.

What is not involved, and this is enforced in the code rather than promised:

• Private or restricted accounts. We hold no credentials that could reach one.
• Anything behind a login or a paywall.
• Personal profiles on platforms that distinguish them from public pages — on Facebook, for example, we read public Pages.
• Special-category inferences presented as fact. Where a value is derived rather than published, it is labelled as derived.

We fetch it ourselves, from public pages and public platform APIs, using commercial proxy infrastructure. We say this plainly because some providers in this market describe their data as arriving only through third parties, and that is not what happens here.

Always logged out. No account pool, no session belonging to a person, no credentials. The only cookies retained are the anonymous device cookies a platform hands any first-time visitor; they identify a browser, not a person. A change that would require signing in is refused, and that is a constraint on the architecture rather than a preference.

Demand-driven. A fetch happens because a customer asked for that specific target. There is no background harvest of platforms at large, and no attempt to build a profile of anyone. Where a customer subscribes to a target for change notifications, the polling interval and the target are theirs.

We rely on legitimate interests: providing an analytics and research tool over information the publisher has already made public to the world. In weighing that against your interests we take into account that the data was published publicly by the account holder, that we do not assemble a persistent profile of any individual, that retrieval happens per request rather than in bulk, that our acceptable use policy contractually forbids customers from using it for biometric identification, surveillance, profiling or re-identification, and that you can object under §6.

Because we hold no contact details for the people in this data, individual notification is not possible — this public notice is how that duty is discharged.

No persistent per-person profile is assembled. There is no store keyed on an individual. Responses are cached only so that a repeated request does not re-fetch the source, and each cache entry expires on the lifetime published for that endpoint in /openapi.json.

Once a response reaches a customer, what they retain is governed by their own obligations and by our terms, not by us.

Write to privacy@truescrape.com with a link to the profile or post concerned. We will review the request and respond within 30 days.

To be straight about the current mechanism: requests are handled manually. We are building an automated suppression list that will prevent a named account from being served through the API at all; until it ships, an objection is actioned by hand rather than by a switch. We would rather tell you that than describe a button that does not exist.

You can also ask what we hold about you, ask for it to be corrected, or complain to a data protection authority — the Data Protection Board in India, or your national authority in the EU or UK.

The date at the top changes when this notice does, and material changes are noted in the changelog.