Privacy Policy
What we collect, why we collect it, and how to control it.
Last updated
⟩ What we collect
Account data: email, name, billing address, payment method (held by Stripe).
Repository data: contents of repos you connect via OAuth, including commits, issues, and pull requests.
Generated content: posts, video, audio, and replies the service produces from your data.
Usage data: events from the dashboard, CLI, and API for product analytics.
⟩ How we use it
We use your data to operate the service: to generate content, publish it to the platforms you connect, charge for subscriptions, support you, and improve the product.
We do not sell your data. We do not train third-party models on your data.
⟩ How we use your voice
If you opt in to voice cloning, your voice samples and the resulting clone are sent to ElevenLabs (our voice-synthesis subprocessor) and used to (1) generate audio for short-form video renders and any other outbound voice content you ask us to publish, and (2) — separately, only if you opt in a second time during onboarding — synthesize your cloned voice on every generated draft as part of an internal quality check that scores whether the draft sounds like you. The internal critic audio is never published; it is compared to your voice samples by an automated voice-drift score and is deleted within 24 hours unless you explicitly enable retention. You can withdraw either consent at any time from Settings → Voice; withdrawal takes effect immediately for new processing.
⟩ How we use your edits
When you edit a generated draft before publishing, we store the original and edited text in a per-workspace edit ledger and feed it into an automated learning loop that updates the prompt context, bandit weights, and persona-drift score for future drafts in your workspace. Edits never leave your workspace; they are not shared with other customers, sold, or used to train third-party foundation models. You can disable edit capture from Settings → Privacy and request deletion of your edit ledger at any time from Settings → Data.
⟩ How we measure post outcomes
After we publish a post on your behalf to a platform you have connected — X, TikTok, or YouTube — we poll that platform's public API at fixed intervals (1 hour, 6 hours, 24 hours, 7 days) to collect public engagement metrics (views, likes, reactions, comments, reshares, and watch-time where the platform exposes it) and store them per post. We only poll posts the engine published; we do not crawl your accounts or scrape historical content. If you have connected a GitHub repository, we also record an hourly snapshot of your repository's public star count so that we can attribute new stars to recent posts on a best-effort time-window basis. These outcomes feed an automated per-workspace learning loop that selects future hooks, formats, and post times. None of this is shared with other workspaces unless you opt in to the cross-workspace leaderboard described below.
⟩ Cross-workspace leaderboard (opt-in)
If you flip the public-leaderboard switch in workspace settings (off by default; the workspaces.public_leaderboard_opt_in flag is the source of truth), we include this workspace's high-performing posts in an anonymized cross-workspace winner library that bootstraps good defaults for new workspaces and powers the public leaderboard at superpost.io/leaderboard. Before a winner enters the shared pool we strip the workspace identifier, owner name, repository URL, and any text features we cannot guarantee are non-attributing. Turning the switch off removes existing contributions from the shared pool within 24 hours. The shared pool is never used to identify or contact other workspaces.
⟩ Folder uploads (R2 + workspace scope)
If you upload a zipped folder as an alternative to connecting a GitHub repository, we extract it to Cloudflare R2 object storage under a workspace-scoped prefix (workspaces/{workspace_id}/projects/{project_id}/). The R2 bucket policy denies cross-workspace reads; only members of the uploading workspace can access those objects, and access goes through a signed-URL exchange that is bound to the workspace. Uploads are retained while the workspace is active and deleted within 30 days of workspace deletion. You can remove a specific upload from Settings → Sources at any time.
⟩ Your rights
You can export or delete your data from the dashboard at any time. EU/UK/Swiss residents have additional rights under GDPR/UK-GDPR; California residents have additional rights under the CCPA/CPRA. Contact privacy@superpost.io to exercise these rights.
⟩ Retention
Active account: data is retained for the lifetime of the account. Cancelled account: data is deleted within 30 days, except where we are required by law to retain it.
⟩ Contact
Questions about this policy: privacy@superpost.io. Data Protection Officer: dpo@superpost.io.