Privacy policy

1. What socially does

socially returns public social-media data, web page content and checks of whether a username or email is registered, on behalf of its customers. We read some data ourselves and buy some from data providers (section 8). We do not ask for or use customers' social-network passwords or session cookies. Providers control their own collection methods; we do not claim that they work without signing in.

2. Two kinds of people

Customers are the people who open an account and call the API or use the console. People who appear in results are the owners of the public profiles our customers look up. This policy covers both.

3. What we collect about customers

• Account: email address, display name, the sign-in provider (email, Google or GitHub), the interface language and time zone you pick, and whether you accepted the acceptable use policy and when.
• Usage: the kind, target platform, credits charged or refunded, cache status, request id and timestamp of every request; the hashed API keys you mint; the jobs you start and their results; your webhook endpoint and its delivery log.
• Billing: your plan, your credit balance, and the Stripe customer and payment references. Card numbers never touch our systems; Stripe holds them.
• Technical: the IP address and user agent of each request, in the request logs.

We use it to run the service, meter it, bill it, keep it secure and support you. We do not sell it, and we do not train models on it.

4. Signing in with Google or GitHub

You can open an account with an email address and a password, or with Google or GitHub. If you use one of those, all we receive from them is what their consent screen shows: your name, your email address and your profile picture. We use them to create your account and to recognise you when you come back.

We ask them for nothing else. Not your Gmail, your Drive, your calendar, your contacts or your repositories. We do not sell what they give us, we do not use it for advertising, and we do not train anything on it.

To disconnect, remove socially at myaccount.google.com/permissions or at github.com/settings/applications. That ends their part in signing you in; it does not delete your account, which you do in the console, under Account.

socially’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

5. What we collect about people who appear in results

Whatever the public page showed at the moment we read it: display name, handle, bio, avatar URL, follower and post counts, recent public posts, links. For a username search, whether a site answered that the handle exists. For an email lookup, whether a site answered that the address is already registered, never the account itself, and never a recovery flow, because the tool runs with password recovery disabled.

Legal basis. We rely on legitimate interest in public information (LGPD art. 7, IX; GDPR art. 6(1)(f)), with the safeguards below: public data only, reviewed opt-out requests and an acceptable use policy before email lookups. This requires a valid purpose, necessary processing and a balance with the person's rights. A public page or this policy does not make every use or storage period lawful.

6. How long we keep things

• Profile, post, web and search results: we keep the public data we read and its earlier versions indefinitely in our database for cached and fallback answers, subject to removal requests and the rights below. We do not keep the original page HTML or image and video files. Stored media links may expire. The short-lived cache expires separately.
• Jobs, results and events (username searches, email lookups, dossiers) are kept while the account exists. Account deletion and approved removal requests still apply. Webhook delivery logs are kept 7 days.
• Accounts: deleting yours blocks access right away. We revoke its keys and stop open jobs, then hold the account for 14 days so you can undo it. After that we delete the account you sign in with and all data it owns from the live system. Payment records we must keep for tax and accounting remain without your socially user id. Their transaction details and Stripe reference remain.
• Lookup history (what you called, never the page content): kept for the life of the account.
• Request logs: 180 days. Backups run every night: they stay 7 days on our servers and 30 days in encrypted offsite storage.

7. Your rights (LGPD and GDPR)

Customer or not, you can ask us to confirm whether we hold data about you, to show it to you, to correct it, to delete or anonymize it, to hand it over in a portable form, and to stop processing it where our basis is legitimate interest. You can withdraw a consent you gave us at any time, and you can complain to the data protection authority where you live (in Brazil, the ANPD).

In the console, under Account, customers can download their account details, API key details, usage summary and payment records. The file excludes job results and request history; for a broader access copy, email hello@socially.run. Customers can also delete their account there. Anyone else, and customers too, 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. It does not automatically remove every mention in old job or search results. For broader removal, write to privacy@socially.run. We answer within 15 days.

8. Who else touches the data

• Stripe: payments. Card data never reaches us.
• Amazon SES (Amazon Web Services, United States): delivers our email, such as sign-in links, password resets, notices about your account and our answers to an opt-out request. It receives your address, your name and the message itself. It runs in AWS's us-east-1 region, in the United States. AWS may store and scan each message to block spam, phishing and viruses. If our email to you bounces for good, or you mark it as spam, Amazon SES keeps your address on our account's list of addresses it sends nothing to, until we take it off.
• Supabase: authentication and the database, self-hosted on our own server. Nothing leaves it for this.
• Our egress proxy vendor: public pages are fetched through rented IP addresses. The vendor sees which URLs we fetch, not who asked for them.
• scrapa: rendering of JavaScript-heavy public pages, under a metered budget. It sees which URLs we render, not who asked for them.
• ScrapeCreators and HikerAPI: paid data providers for public profiles, posts, hashtags and searches. EnsembleData or an X data provider (TwitterAPI.io or SocialData) may also be used when configured. We send the profile, post, hashtag or search requested, not the identity of the customer who asked.
• Cloudflare: DNS and the hosting of our web front-ends.
• maigret and holehe: open-source tools we run in containers on our own server, never as a service.

Our servers are in São Paulo, Brazil. Transfers outside Brazil and the EEA rely on the processors' standard contractual clauses.

9. Security

API keys are stored as hashes, sessions expire, and public traffic uses TLS. From outside its server, Postgres accepts only TLS connections with a password. Only the root administrator can read local backups; offsite copies are encrypted at rest. Operator access is restricted. No system is perfect: if a breach affects you, we will tell you and the authority as the law requires.

10. Children

socially is not for people under 18, and we do not knowingly hold accounts for them.

11. Emails we send

About your account. Sign-up confirmation, password resets, receipts, failed payments, deletion notices, quota warnings, and a warning when we switch off a webhook endpoint that kept failing. You can switch quota warnings off in the console, under Account. The rest are part of the service and keep coming while the account exists.

News and tips. We send none and ask for no marketing-email consent today. If that changes, we will ask separately, with the choice off by default, and let you withdraw it.

We don't sell your email address.

12. Connecting an AI app or agent

When you connect Claude, ChatGPT or another app to socially.run, or approve an agent with a short code, we create an ordinary API key in your account, named after the app, and give it to that app. As with every key, we store only its hash. The app can do anything your keys can, and its lookups spend your credits.

While a sign-in is in progress we keep a short record: a hash of the one-time code, the app's name and the address it returns to, and which account said yes. The code expires 5 minutes after you say yes (10 minutes after an agent asks for a short code), and the record is deleted 24 hours after it expires. We keep nothing else about the app.

The app's calls are recorded like any key's: in your usage and history, and in our request logs, for the periods in section 6. What the app keeps of the answers it gets is up to that app's own privacy policy.

To disconnect an app, revoke its key under API keys in the console. It stops working at once.

13. Changes

A material change is announced by email to customers, and by a dated note at the top of this page.