Legalaup-2026-10-27
Acceptable use policy
socially reads public pages so that developers can build honest products on public data. This says what that does and does not allow.
Last updated October 27, 2026
This policy is part of the terms of service. This revision is aup-2026-10-27, the one your account must have accepted before an email lookup will run. An email lookup needs a paid plan and your explicit acceptance of this policy, recorded on your account. Until then the API answers 403 AUP_REQUIRED.
What you may do
- Look up public profiles, posts and websites to enrich records you already hold lawfully (leads, customers, creators, vendors), to watch your own brand, to research public figures and organizations, and to check that a handle or an address you were given is what it claims to be.
- Run username searches to find where a handle exists: for your own accounts, for brand protection, or for research with a legitimate interest.
- Run email lookups to verify or de-duplicate contacts you already hold lawfully, or to investigate accounts on your own platform.
- Build products on the API and show results with their source, confidence and original read time. Keep only what you have a lawful basis to store, set a retention period for your use and honor removal requests. Our storage period does not give you a legal basis to keep the data.
What you may not do
- Target a private individual for harm: stalking, harassment, intimidation, doxxing, blackmail, or locating somebody who does not want to be found.
- Profile people on protected characteristics, or make a decision with legal or similarly significant effects (employment, credit, housing, insurance, policing) based only on our results.
- Re-identify or contact somebody who opted out, or route around a suppression.
- Resell raw results as a people-search or background-check product, or scrape our API to build one.
- Run email lookups on lists you did not obtain lawfully, on bought lists, or to build a marketing audience without a lawful basis.
- Work around rate limits, quotas, suppressions, or the three-way outcome, by presenting a lookup we could not check as a fact.
- Use the results to attack accounts: credential stuffing, account takeover, phishing.
- Anything unlawful where you are, or where the person is.
What we do on our side
- We provide public data without asking for or using customers' social-network passwords or session cookies. Some data comes from paid providers, whose collection methods we do not control.
- Email lookups run with password-recovery flows disabled. No site is asked to send anything to the person.
- Anyone can ask to exclude a handle, email address or domain through the opt-out form. We confirm the contact email and review the request. Approval blocks matching new lookups, including cached profile answers, at no charge. Some links must be read before we can identify an excluded profile or domain; we then withhold the answer. Cleanup removes matching profile, post-by-link and website copies, including their saved versions, but not every mention in past job or search results. For broader removal, write to privacy@socially.run. Site operators can use the same address to leave the username-search database.
- We keep public results and their versions indefinitely for cached and fallback answers, subject to approved removal requests. Jobs, results, events and lookup history stay while the account exists. Account deletion still applies. Stored answers keep their original read time; we do not keep the original page HTML or media files.
- We suspend accounts that breach this policy, and we cooperate with lawful requests from authorities and from the people affected.
Reporting
Misuse of the service, or a result about you that you want removed: write to privacy@socially.run, or use the opt-out form. We answer within 15 days.