Data Retention and Deletion

Capsule may store account data such as name, email address, authentication identifiers, plan status, settings, and communication preferences.

Capsule may store uploaded or pasted content, transcripts, URLs, notes, summaries, insights, topic tags, topic history, suggested actions, action statuses, Daily Briefs, Decision Briefs, exports, and related metadata.

Capsule may also store usage data such as feature usage, billing events, error events, product analytics events, device/browser metadata, and security logs. Analytics should not intentionally include full transcripts, secrets, or payment card details.

Capsule retains data to provide the service, save user history, power library and memory features, personalise insights, track topics and actions, maintain account settings, and support billing or email delivery where configured.

Some data may be retained for security, debugging, fraud prevention, abuse prevention, service reliability, legal obligations, tax or accounting requirements, and dispute handling.

Users can request deletion of account data and saved content by contacting privacy@yourdomain.com. Replace this placeholder with the production privacy contact before public launch.

In the current alpha prototype, backend account deletion may not be fully automated. Settings includes a non-production request placeholder and a local/demo data clearing control for browser-stored demo data.

Deletion requests should be reviewed before production launch to define identity verification, response timing, exceptions, and how deletion interacts with billing, security logs, legal holds, and backups.

Users can request an export of their account data, saved content, summaries, insights, topics, and actions by contacting privacy@yourdomain.com.

A production export workflow should define supported formats, verification steps, expected turnaround time, and any limits for security or third-party rights.

Deleted data may remain temporarily in backups, logs, caches, audit trails, or provider systems before being removed under normal retention schedules.

Capsule should avoid restoring deleted user data into active systems except where necessary for security, legal compliance, service recovery, or dispute handling.

Third-party processors such as AI providers, email providers, payment providers, analytics tools, hosting services, and database providers may have separate retention periods and deletion processes.

Capsule should document processor retention and deletion behaviour before public launch and ensure subprocessors match the production privacy commitments.

When Capsule runs without production auth or database configuration, some data may be stored only in the browser using local storage. Clearing local/demo data removes that browser copy but does not affect any production backend data if configured later.