Privacy policy
This policy explains what SuperAgent Social collects, why we collect it, where it goes and how to get it deleted. It covers the website and the application prototype. The service is a demo build; the data described here is the data the prototype is designed to handle, not a production dataset.
1. Who we are
SuperAgent Social is the controller of account and website data. For the content you upload and publish, you are the controller and we are the processor; the data processing addendum sets out that relationship. You can reach us at privacy@superagent.social.
2. What we collect
We collect the details you give us when you create a workspace: name, email, password hash, company name and billing country. If you subscribe, our payment processor collects card details and gives us a token, the last four digits, the brand and the expiry month; we never see the full number.
We also collect the content you create or upload, the channels you connect, the profile identifiers and tokens needed to publish, the people you invite, and the settings you choose. When you use the site we record technical data such as IP address, browser, pages viewed and errors.
Usage data is recorded per workspace, not per person, except for security events such as a failed login, which include the account email and IP address. We do not read the body of your private messages for product analytics; the inbox shows them to you, and automated classification runs only when you switch it on.
If you contact support, we keep the conversation, the screenshots you send and any diagnostic bundle you choose to share. A diagnostic bundle can include channel names and error codes, so review it before sending if it contains something you consider confidential.
3. Why we use it
We use account data to provide the service, authenticate you, keep your workspace separate from others, take payment and send service messages. We use content data to draft, schedule and publish what you approve, and to show you the calendar and inbox. We use technical data to keep the service secure, diagnose failures and understand which pages are used.
We do not sell personal data, we do not use your content to train a model for other customers, and we do not send advertising email without a separate opt-in. Product email about the service is part of the contract; you cannot opt out of billing and security messages.
When the agent drafts content, the prompt and the relevant brand context are sent to a model provider for the length of the request. The provider is bound by a data processing agreement that forbids training on that data for its own purposes. Drafts and their versions stay in your workspace until you delete them or close it.
Analytics is aggregate: we look at which pages are opened and which flows fail, not at what an individual account writes. The exception is a security investigation, where we may read logs and account events to stop abuse or respond to a legal request.
4. Legal bases
Where the GDPR applies, we rely on contract for account, content and billing data; on legitimate interests for security, fraud prevention and product improvement; on consent for optional analytics cookies and any marketing email; and on legal obligation for tax and accounting records. You can withdraw consent at any time without affecting the lawfulness of processing before that point.
Our legitimate-interest assessment for security balances the risk of abuse against the limited data we read: login events, IP addresses and error codes. For product improvement we use aggregated usage and, where we need to look at a specific workspace, we ask first unless the account is part of a paid research programme you joined. You can object to legitimate-interest processing; we stop unless we have a compelling reason that the law recognises.
5. Channel connections and tokens
When you connect a network, the network gives us an access token and the profile identifier you authorised. We encrypt tokens at rest, scope access to the workspace and brand that needs it, and use the token only to publish, read replies or refresh the connection. We do not post without an approved item. You can revoke a connection from Settings → Channels, which deletes the token we hold.
A connection is per account, not per person: if two teammates share a workspace, both see the connected profiles unless a role restricts it. A network may tell us when a token is revoked or a password changes, and we then mark the channel as disconnected instead of retrying with a dead token. We never ask for your network password and never store one.
6. Cookies and analytics
We set a session cookie to keep you signed in, a preference cookie for theme and language, and an optional analytics cookie that counts page views without identifying you. We do not use advertising cookies or cross-site tracking pixels. The cookie policy lists each cookie and how to block it.
The analytics cookie records the page path, a random identifier, the referrer and whether the page was opened from a campaign link. It does not record what you type into the workspace. If you refuse it, we still count the visit in an aggregate server log that cannot be tied to a browser.
7. Sharing and sub-processors
We share data with hosting, payment, email delivery and model providers, each bound by a data processing agreement and allowed to use it only for the service. We also share data with the networks you choose to publish to, at your instruction. We may disclose data if the law requires it, if we must protect the rights or safety of a person, or as part of a merger or acquisition, in which case we tell you before your data moves to a new controller.
The categories are: cloud hosting in the EU and the US; a payment processor for card and invoice payments; an email provider for transactional mail; model providers for drafting; and an error-monitoring service that receives stack traces without content. A current list with locations is available on request, and we notify customers who subscribe to updates before a new processor that touches personal data is added.
8. International transfers
Our hosting and providers are in the EU and the United States, and some support staff work from Vietnam. Where data leaves the EEA or the UK, we rely on an adequacy decision or the standard contractual clauses, with additional measures where needed. A copy of the safeguards is available on request, and we review the transfer position at least once a year.
9. Retention
Content stays until you delete it or close the workspace. After closure we delete content within 30 days, apart from backups that expire within 90 days and records we must keep for tax, fraud prevention or legal claims. Support tickets are kept for two years, security logs for twelve months and billing records for the period the law requires.
When you delete a single post, it leaves the calendar and the library at once and disappears from backups within 90 days. Deleting a channel removes the token immediately; the network's own copy of anything already published stays under that network's policy. Drafts that were never published are deleted with the workspace. A restored backup may briefly bring back an item deleted after the backup was taken; we delete it again when the restore is verified.
10. Your rights
You can ask for a copy of your data, correct it, delete it, restrict or object to processing, and export your content. Write to privacy@superagent.social from the account email; we answer within 30 days and may ask for proof of identity before acting. You can also complain to the data protection authority in your country.
11. Security and breach notification
Tokens are encrypted at rest, traffic is encrypted in transit, access is scoped per brand and every write through the API or MCP is logged. No system is perfect; if a breach affects your data we notify you without undue delay, describe what happened and tell you what we are doing about it.
Staff access is limited to the people who need it for support or security, is logged, and is reviewed each quarter. We test backups by restoring them, review dependencies before release and run an independent assessment once a year. You can report a vulnerability to security@superagent.social; we acknowledge reports within two working days and do not pursue good-faith research.
12. Contact us
Privacy questions and requests: privacy@superagent.social. Security reports: security@superagent.social. You can also write to the address on the contact page. We answer privacy requests within 30 days and security reports within two working days. If your request is urgent because an account is at risk, say so in the subject line and we move it to the front of the queue.