FounderReply
Products
All productsSocial agentApproval queueCold emailVoice callingSEO engineBlog autopilot
Platforms
All platformsRedditXBlueskyLemmyDiscourseLinkedInsoonInstagramsoonFacebooksoonYouTubesoonStack Exchangesoon
Solutions
All solutionsSaaSEcommerceAgenciesReal estateStartupsSolopreneursSmall businessFor agencies
Resources
All resourcesGuidesBlogCompareAlternativesSecurity
DevelopersPricing
Log inStart free

LEGAL

Your data, and how to delete it

FounderReply stores your account, the platform accounts you connect and their OAuth tokens, and the posts, drafts and messages your workspace works on. You can revoke a single platform connection from Settings → Connections, or erase everything by deleting your account in Settings → Account. Both take effect immediately.

Last updated: 2 September 2026

In short

  • Remove one platform:Settings → Connections → Disconnect. We ask the platform to revoke the token, then delete our copy.
  • Remove everything:Settings → Account → Danger Zone. Type delete my account and confirm. Immediate and irreversible.
  • Locked out: email privacy@founderreply.com from your account address and we will verify and delete within 30 days.
  • One exception: the security audit log is append-only and is not erased by self-serve deletion. Ask us and we will erase it.

What we store

Everything below is scoped to a workspace or to your user record. “Deleted with your account” means the row is removed by a database cascade when the workspace or the auth user is deleted, not that we mark it hidden. Table names are the real Postgres tables so an auditor can check the claim rather than take it.

Data FounderReply stores, why it is stored, and when it is deleted
What we storeWhyRetention
Account identityYour email address and sign-in credentials, held by Supabase Auth in auth.users, plus a profile row (public.users) holding your id, email and signup date.To authenticate you and to attach you to a workspace.Deleted when you delete your account.
Workspace & brand voiceworkspaces (name, slug, brand-voice guide) and workspace_settings, which holds per-workspace configuration including a bring-your-own X app secret — encrypted with AES-256-GCM before it is written.Configuration, and the voice the drafting model is told to write in.Deleted when you delete your account.
Connected platform accountsbrand_accounts: handle, display name, platform identity, granted scopes, and the OAuth access and refresh tokens — encrypted at rest with AES-256-GCM.To read and publish on the platform on your behalf.Deleted the moment you disconnect that account, or when you delete your account.
Drafts & the approval queueapproval_queue (every outbound draft, its status and its context) and edit_events(the model’s draft alongside the text you actually sent).Human-in-the-loop review; the edit deltas are used to improve drafting.Deleted with the connected account or with your account.
Published & scheduled postspublications, scheduled_posts, content_plans, personas and autonomy_settings — post bodies, permalinks, the content calendar and your per-action autonomy dial.To run the calendar, link comments back to a post, and honour your autonomy settings.Deleted with the connected account or with your account.
Inbound mentions & DMsmentions, dm_threads and dm_messages: author handle, author platform id, message text and the raw platform payload.So the agent can draft a reply in context and de-duplicate deliveries.Deleted with the connected account or with your account.
Engagement analyticspost_metrics, audience_snapshots and engagement_opportunities — impression, like, comment and follower counts over time.Reporting, and to decide what the agent should engage with next.Deleted with the connected account or with your account.
AI recall indexmemory_embeddings: the text of your posts, mentions, DMs and brand-voice corrections, stored alongside a vector so the drafting model can recall prior contact.Consistent voice across platforms and continuity with people you have replied to.Deleted when you delete your account.
Outreach contactsleads, lead_identities, outreach_conversations, outreach_messages, outreach_sequences, outreach_enrollments, outreach_signals, outreach_scheduled_calls, outreach_approvals and outreach_aup_acceptances — names, companies, email addresses, phone numbers and message bodies that you upload or ingest.To run outreach sequences you configured. You are the controller for this data.Deleted when you delete your account.
Do-not-contact listoutreach_suppressions: addresses that unsubscribed, bounced or complained, held per workspace so one tenant’s opt-out does not bind another.To stop us contacting someone who asked not to be contacted.Deleted when you delete your workspace or your account.
Browser-session accountsbot_accounts, bot_posts, bot_post_metrics, bot_post_comments and twin_connections: a handle and a server-derived session label. No passwords, cookies or session material are stored here — those live with the browser provider.To map a workspace to its browser sessions and show connection status.Deleted when you delete your account.
Site & keyword dataseo_sites, seo_pages, seo_page_audits, seo_issues, seo_page_reviews, seo_keywords and seo_rankings — the URLs and keywords you asked us to track.To audit the pages and keywords you added to the workspace.Deleted when you delete your account.
API keysapi_keys: a hash of each key, its label and its last-used timestamp. The key itself is shown once at creation and never stored.To authenticate MCP and API calls without holding a usable secret.Deleted when you revoke the key, or when you delete your account.
Billing & usagesubscriptions (Stripe customer and subscription ids, tier, status), credit_ledger, usage_counters and usage_reconcile_snapshots. Card details never reach our servers — Stripe holds them.Entitlements, credit balance and usage caps.Our rows are deleted with your account. Stripe keeps its own invoice records for as long as accounting and tax law requires, typically seven years.
OAuth handshake stateoauth_states: a single-use PKCE verifier bound to one connection attempt.To complete an OAuth exchange without sending the verifier to the platform.Deleted on first read; abandoned rows are swept periodically.
Delivery ledgerprocessed_events: a platform name and an event id. No message content and no link to your account.So a re-delivered webhook is not processed twice.Retained; carries nothing that identifies you.
Security audit logaudit_log: an append-only record of sign-ins, sign-up attempts, password changes, platform connections, publishes and account deletions. Entries include your email address and IP address.Abuse investigation and proof of what was done on an account, and when.Not removed by self-serve deletion — see what deletion does not remove.
Request logsStandard server-side logs held by our hosting provider: request paths, status codes and error messages. Request bodies containing personal data are not logged.Debugging and abuse detection.Up to 30 days, then automatically deleted.

Disconnecting one platform account

Disconnecting revokes a single platform connection and leaves the rest of your account intact. Open Dashboard → Settings → Connections, find the account, and click Disconnect. You are asked to confirm, because it cannot be undone.

The request goes to DELETE /api/v1/accounts/:id. We first ask the platform to revoke the token on its side — best effort, so a platform outage can never block the deletion that follows — and then delete the brand_accounts row. That cascade removes everything hanging off that connection: its published posts, its scheduled posts, its inbound mentions and DM threads, its approval-queue items and its analytics snapshots. We keep no copy of the access or refresh token.

Facebook and Instagram

Disconnecting deletes our stored tokens. To also withdraw the app permission on Meta’s side, open your Facebook or Instagram settings and remove “FounderReply” from your connected apps — that part happens on Meta, not here, so we cannot do it for you.

Deleting your account

In the dashboard

  1. Sign in and open Dashboard → Settings → Account.
  2. Scroll to the Danger Zone card at the bottom of the page.
  3. Type delete my account in the confirmation field. The delete button stays disabled until the phrase matches exactly.
  4. Click Delete my account. You are signed out and returned to the homepage.

The button calls POST /api/v1/auth/delete-account, which runs in one pass: it asks each connected platform to revoke its token, deletes every workspace you own — cascading the connected accounts, publications, mentions, DM threads, approval queue, workspace settings, subscriptions, credit ledger, usage counters, edit events and OAuth state with them — removes your membership of any workspace you joined but do not own, deletes your Supabase Auth user, and clears your session cookies. Deletion is immediate and cannot be undone.

What deletion does not remove

Two things survive, and we would rather say so than let you find out later.

The security audit log. audit_log is append-only and carries no foreign key to your user or your workspace, so the cascade above does not reach it. Entries recording your sign-ins, sign-up, password changes and the deletion itself include your email address and IP address, and they remain after the rest of your data is gone. If you want them erased as well, email privacy@founderreply.com and ask; we will delete them.

Stripe’s billing records.Our subscription, credit and usage rows go with your workspace, but Stripe holds its own customer and invoice records for as long as accounting and tax law requires — typically seven years. That retention is Stripe’s and the law’s, not a copy we keep.

If you cannot sign in

If you have lost access to your account and cannot reset your password, email privacy@founderreply.comfrom the address associated with the account, with “Account deletion request” in the subject line. We verify your identity against the account email and complete the deletion within 30 days.

Getting a copy of your data

There is no one-click export in the dashboard yet. Email privacy@founderreply.com from the address associated with your account and we will respond within 30 days with a machine-readable JSON export of your account, workspace and content data. OAuth tokens are not included: they are credentials rather than records, and they stop being valid the moment the connection is removed.

Contact and related pages