Sage stores the minimum it needs to do what you signed up for. Your Discord-linked profile (id, username, avatar), your follow list, your position history, any signals you authored if you're a caller, and the audit-log entries associated with your user id.

We do NOT store payment cards (Stripe holds those when billing wires in), we do NOT scrape your Discord DMs, and we do NOT track activity off the dashboard.

Aggregate counts (e.g. how many users opened a given signal) are pseudonymized — they survive deletion as un-identifiable totals.

From /account, click the 'download my data ↓' chip. The browser saves a JSON file with your profile + positions + the export's metadata.

The export endpoint is rate-limited to one per minute per user (polite limit; not abuse-prevention). It returns Cache-Control: no-store so no intermediary caches your personal data.

Important — the export covers the server-side state. Client-only state (recently-viewed list, pinned markets, signal reactions, unread count, persona) lives in your browser's localStorage. You can read those directly via dev-tools; they're not in the export because you already have them.

From /account, click 'delete account →'. The /account/delete page makes you type your username verbatim before the submit button unlocks — protects against accidental clicks.

The request is recorded to the structured log stream. An operator reviews within 30 days (GDPR Article 12(3) timeline). If you have open positions, they're closed out first; you'll get a DM on Discord with the close confirmations before the purge runs.

Once the purge completes, you'll get a final DM. Re-signing in after that creates a fresh account — there's no link back to the previous state.

Aggregate analytics (pseudonymized counts) — these survive because they're already de-identified. Your individual activity is gone; the totals remain.

Legally required retention — closed-position financial records may be retained for the period required by tax or regulatory rules (typically 7 years for trading records). If we keep anything for this reason, the purge confirmation DM names it explicitly.

Public artifacts you posted — if you were a caller and your signals went into the public feed, the signals themselves stay (associated to a deleted-user marker). You're welcome to ask ops for individual signal removals via the support flow.

If something's unclear, DM ops on Discord with your request id (returned in the receipt panel on /account/delete) or the URL of the export you have a question about. We aim to reply within 48 hours.

If you believe Sage has data we shouldn't, or we missed something on a delete request, you can also email the project's data-protection contact listed in the public site footer. We treat those as priority queue items.