Skip to content

Privacy Policy

Version and last updated 2026-11-10

1. Controller

SuperPost is the controller for account and workspace data. Privacy requests: privacy@superpost.io.

2. What we collect

Account: email, name, password hash or federated identity, and the time you accepted these terms. Workspace: timezone, mix, kill switch, Product Brain, drafts, posts, inbox, post metric snapshots, the Brain's lessons about what worked for your posts, research items. Repository: the repo map, the facts SuperPost found with the few lines that prove each one (and their git blob SHAs), and the list of files read. We don't keep your code: SuperPost stores the facts it found with the few lines that prove them, never your files. Secrets are redacted before any text is stored or sent to a model. A zip you upload is read in memory and not kept. Connections: network and GitHub tokens sealed with AES-256-GCM (sp2: envelope with a key id and per-row additional data). Export never includes tokens. Media: stills and motion files in the object store you configure. We do not use your repository, drafts or results to train models. See /ai. Network memory: aggregate effects only, never your posts or text; see §18 for what it holds and how to opt out.

4. Sub-processors

When configured we use the vendors listed at /sub-processors. That page names the legal entity, the data processed and the country of processing.

5. Cookies

SuperPost sets only strictly necessary cookies and storage. The measured list, lifetimes and the reason no consent banner is shown are at /cookies.

6. Retention

Account: Until account deletion, then 30 days Workspace content: Until workspace or account deletion Evidence spans: Until the product is deleted Research items: 180 days Metrics: While subscribed, plus 90 days in archive Deleted workspaces: Purged within 30 days; backups expire within 35 Network tokens: Until you disconnect; revoked at the provider jobs: 30 days (dead jobs until retry or delete) mail_log: 30 days; recipient stored as a hash only audit: 24 months, then pruned Media objects: Until workspace deletion Stripe / billing records: 10 years (tax retention) Backups: Neon PITR window of the deployed project; not a separate SuperPost copy

7. Your rights

You have the rights of access, rectification, erasure, restriction, portability, objection and withdrawal of consent. Self-service: Settings → Data (export and delete). Email: privacy@superpost.io. We respond within 30 days.

8. Complaints

You have the right to lodge a complaint with a supervisory authority in your country of residence or work, or with the authority of the operator identified at /imprint.

9. International transfers

Data may be processed in the United States and other regions where sub-processors operate. Transfers rely on Standard Contractual Clauses (Module Two, controller to processor) or an adequacy decision. A copy of the clauses is available from legal@superpost.io. For questions about where your data is stored, contact legal@superpost.io.

10. Automated decision-making

We do not make decisions producing legal effects about you by automated means. The Brain learns from your own posts' results to plan and rank drafts for your workspace only. Not unless you switch Autopilot on. Every post waits for your approval. Once a network has earned it (40 decisions across your workspace, at least 10 on that network, at least 90 percent approved and no "not true"), you can switch Autopilot on for it; on X you also set X's Automated label first. Then a post sends at its time unless you veto it in the 12 hours before. A "not true", a "not me" on an Autopilot post, a failed send or Pause switches Autopilot off, and only you switch it back on.

11. Children

The service is not for under-18s and is not directed at children. We do not knowingly collect children's data.

12. CCPA / CPRA

We do not sell or share personal information as those terms are defined in the CPRA. California residents may request access, deletion and correction at privacy@superpost.io or Settings → Data. We do not use sensitive personal information to infer characteristics.

13. Security and breaches

Measures are listed on /security and in DPA Annex II. Personal-data breaches are notified without undue delay as described in the DPA.

14. Data protection officer

A DPO is not appointed; Art. 37 does not require one for this operator's core activities as currently scoped. Privacy contact remains privacy@superpost.io.

15. Changes

This notice is versioned. Material changes re-prompt acceptance via the Terms gate.

16. Live URL ingest

Live URL ingest fetches the page you name, with private IPs refused. Do not point it at a host you do not control.

17. Legitimate Interests Assessment (LIA)

This is the assessment behind the Art. 6(1)(f) processing in §3. It covers only processing that this product actually performs; nothing here is marketing analytics, profiling or resale. (a) Security of accounts and the host. Purpose — keep credentials, sessions and connected-network tokens from being abused. Necessity — sign-in, sign-up, reset and the public forms are rate-limited by IP address in a database table with a rolling window (the rate_limits table, about one hour); each session row stores the IP address and browser user agent so you can review and revoke devices in Settings → Account, and so we can email you about a sign-in from a new device; an audit log records who did what in a workspace (connect, approve, publish, delete). We found no less intrusive way to stop credential stuffing, form spam and the Pull Test being used as a free proxy. Balancing — the data is limited to what the request already carries (IP, user agent), is not combined with other sources, and is expected by anyone using a signed-in product. Safeguards — rate-limit rows expire with their window; session rows are deleted on sign-out, password reset and revoke; the IP shown in the desk is truncated; audit rows are pruned after 24 months (§6). (b) Abuse prevention on public forms and the Pull Test. Purpose — stop bulk submissions to /contact and /try. Necessity — a per-IP counter (for example five Pull Tests per hour per IP, one contact message per ten seconds) is the minimum needed and blocks nothing for ordinary use. Balancing — a counter keyed by IP for a short window has negligible impact and no secondary use. Safeguards — counters are not linked to accounts and fall out of the window automatically. (c) Service reliability and delivery. Purpose — know whether background jobs, publishes and emails succeeded. Necessity — job rows keep their payload for 30 days so failed work can be retried; mail_log records the kind, status and any provider error for each message with the recipient stored only as a hash; when SENTRY_DSN is set, exceptions are reported with stack traces and truncated URLs. Balancing — these records are operational, viewed only to fix a fault, and hold no message body or token. Safeguards — mail_log and jobs are purged after 30 days (§6); tokens are sealed before they reach any log; error reporting is off unless the operator configures it and is listed at /sub-processors. (d) Public replies pulled into your Inbox. Purpose — show you public comments on posts you published so you can answer them from the desk. Necessity — the handle, display name and text of a public reply are what the network returns for a reply to your post; SuperPost reads only replies to your own posts, never strangers' timelines. Balancing — the author chose to reply publicly to your account and reasonably expects the account owner to read and answer; SuperPost does not use the author's handle as a targeting or model-training signal (see /ai). Safeguards — Inbox items live inside your workspace, are deleted with it, and are never used for advertising or enrichment. Outcome — for (a) to (d) the interest is real, the processing is necessary for it, and the impact on the person is small and expected. You may object at privacy@superpost.io; we will stop unless we can show compelling grounds (Art. 21). This assessment is reviewed when a new processing purpose is added and is dated with this notice's version.

18. Network memory

The network memory is the one place SuperPost learns across workspaces. It holds only aggregate effects per account, for example how number-led opening lines did against each account's own baseline, grouped by network and, once a group holds at least twenty accounts, by product category and size. It never holds your posts, drafts, claims, names or handles, and no customer's content ever appears in another customer's prompt. It is on by default; the legal basis is our legitimate interest in better drafts for every customer (Art. 6(1)(f)), and you can object at any time. To opt out, turn off "Include this workspace" under Settings → Data (Learning pool), or email privacy@superpost.io with the subject "network memory"; your workspace is left out of the next nightly build and every build after it. Deleting a workspace removes it from the network memory that night. The network memory is rebuilt every night from the workspaces that have not opted out. More at /ai §9.