About AnonSight
Revised on
Operator
Operator: AnonSight. Team: small, independent. Personal names and a registered address: not published. Published instead: the request path, the data scope, and the refusals listed below. Those are the facts that decide what happens to a lookup. There is one operator and one inbox, and no cluster of sister domains sits behind this one. Anything outdated on this page can be reported to the address below.
Design goal
Content an owner made public should be readable at zero cost, without registering, installing an app or handing over personal data. The typical case is a single check ahead of buying something, a job call, a first date, or answering a message from someone unknown. Creating a platform account for that is overhead. Typing credentials into a third-party login proxy is an actual security risk. AnonSight takes both out of the picture. It requests what the account has already exposed, renders it in the browser, and does nothing beyond that.
Declined on principle
- Private profiles. They are closed at the source, and we make no claim to the contrary.
- Credentials. No screen here requests an Instagram login, and none ever will.
- Search history. Handles typed into the lookup box are not stored server side.
- Username pages. Nobody who was looked up gets an indexable page generated about them.
- Data sales. Zero collection means zero inventory to sell.
Every lookup is relayed by an upstream data provider. Field-by-field detail of what it receives: privacy page.
Independence
There is no business relationship between AnonSight and Meta or its Instagram product. Both names are Meta’s marks.
Reaching us
hello@anonsight.com. Replies take up to two business days. Copyright notices: see the removal page.