Public data notice

• —Read public accounts and public posts. Profiles, posts, comments, and the numbers shown on them, from accounts that are set to public.
• —Only when asked. A customer requests a profile or a post, we read it and answer. We do not crawl the platforms on our own.
• —Return it in one shape. We normalize what the platform shows into one response shape. Nothing is added that the platform did not show. If a source hands us something sensitive that is not visible on the public page, we drop it. Only what anyone can find by looking is returned.

• —No account actions. Openhandle is read-only. We never like, follow, comment, post, message, or take any action on any account, on anyone’s behalf. There is no endpoint for it and there will not be one.
• —No private accounts. A private profile returns a clear error. We do not try to get around it.
• —No private content. Direct messages, close-friends posts, drafts, and anything else that is not public are out of scope.
• —No made-up data. If a platform hides a number, we say it is hidden. We never fill in a zero, an estimate, or a guess.
• —Public data only. Anything private stays private. We only return information anyone can view publicly. We do not enrich it with (identifiable) personal data.

• —Answers. Cached for up to 31 days so repeat reads are faster and cost less. Then they expire.
• —Identity history. We remember which handle belongs to which platform ID for one year after we last saw it, so a rename does not break a customer’s reference. That record is an ID and a handle, nothing else.
• —Request logs. Operational metadata about each request, such as the endpoint, timing, result, and charge, for 90 days. Not the content.
• —Media. Openhandle serves requested media through its own cache and CDN. Your Openhandle link stays the same when platform links expire.

If you own an account and do not want it to be readable through Openhandle, send us one email. This link opens it with the subject and the text filled in. Add the profile link and send: Email a block request.

• —What happens. The profile goes on a block list. New requests for it return a clear error and are not billed. Cached answers for it are removed.
• —How long it takes. We confirm by email. Cached answers expire within 31 days at most, and we remove them sooner when we process the request.
• —Logs. Operational logs that mention the profile age out within 90 days.

Openhandle processes public data on a legitimate-interest basis, as described in the privacy policy. Customers who read data through the API are responsible for how they use it and for their own obligations to the people in that data.