How long we keep your data
This page documents the product's current public beta behavior. It is not a promise of a jurisdiction-specific statutory period or a substitute for a negotiated data processing agreement. We minimize active data, provide account export and deletion, protect conference deletion with a 30-day recovery window, and track backup and restore evidence in the production readiness gate.
Trust Center · Data Retention · Last updated: July 25, 2026
Current handling
- Account data
- Name, email, organization, authentication metadata.
- Retention period: Kept while the account is active. Self-service deletion immediately revokes sessions and tokens and scrubs direct identifiers from active application records.
- Conference workspaces
- Conference setup, memberships, schedules, registrations, submissions, and reviews.
- Retention period: Kept while the workspace is active. Owner deletion makes it private immediately and keeps it recoverable for 30 days. Permanent purge is allowed only after that window.
- Orders, receipts & payment records
- Transaction records, invoices, and receipts. Card numbers are never stored — Stripe handles card data.
- Retention period: Transaction records are retained only as needed for support, fraud prevention, and applicable accounting or legal obligations. Account deletion removes or replaces linked attendee identifiers where the record can be preserved without them.
- Submissions & reviews
- Papers, abstracts, review forms, scores, and decision records for a conference.
- Retention period: Kept with the conference workspace. Deleting an author or reviewer account scrubs direct identifiers but does not silently remove the conference's academic record.
- Uploaded files
- Manuscripts, camera-ready files, and other documents in object storage.
- Retention period: Retained while referenced by an active or recoverable record. Files become eligible for storage cleanup after the parent record is permanently purged and then age out of backup snapshots.
- Application & audit logs
- Security and audit logs of sensitive actions, plus operational error logs.
- Retention period: Kept for operational security, debugging, abuse investigation, and accountability. Provider log windows and application audit records can differ; contractual fixed windows are not offered in free public beta.
- Analytics
- Consent-backed, pseudonymous first-party product events. No third-party ad trackers.
- Retention period: Retained for beta product measurement and aggregate reporting. Events use hashed visitor and session identifiers rather than account email addresses.
Fixed contractual retention or residency terms are not included in free public beta. Organizations with those requirements should contact us before placing regulated data on the platform.
How deletion and export work
Self-service export
Download your personal data at any time via GET /users/me/export in a structured, portable format — useful before you close your account.
Account deletion scrubs PII
Deleting your account removes or scrubs your personal data from active systems. This is a self-service action you control.
Transaction records are minimized
Order and receipt records may remain for support, fraud prevention, or applicable obligations, while linked personal identifiers are removed or replaced where possible.
Backups are evidenced and rotated
Database dumps and object snapshots produce timestamped production evidence. Deleted records drop out as rolling copies rotate and are not restored individually.
Frequently asked questions
How do I delete my data?
You can delete your account from your account settings. Deletion scrubs your personal data from active systems. Some financial records (orders, receipts, invoices) are retained where required by tax and accounting law.
Can I export my data before deleting?
Yes. Use the self-service export endpoint (GET /users/me/export) to download your personal data in a structured, portable format before you delete your account.
How long do deleted items stay in backups?
Deleted data may remain in protected database dumps or object snapshots until those copies rotate out. Backups are used for disaster recovery, not to reintroduce an individually deleted account into the live service.
Related: Privacy Policy · Subprocessors · Security