Founder view
Your data
This screen performs no deletion
Scheduled deletion
A founder sees an exact timestamp here, for example “your uploaded materials and session data are scheduled for deletion on 4 October 2026 at 16:40 — in 6 days”.
That deadline is set when they first create something and never moves. Returning to the app, adding a deck, or running a second session does not extend it — the database refuses to change the value once written.
What would be held for this founder
- Company briefKettlefish
- Uploaded deckkettlefish-seed-deck.pdf
- Extracted deck textHeld
- Session records (when, which focus, which AI model, status)1
- Reports, including the figures the browser measured (turn lengths, pauses, delays, interruptions, and how far pitch moved and loudness varied, as numbers only, never audio or absolute pitch), and their theme tags1
- Audio recordingsNone — none are made
- TranscriptsNone — none are made
- Consent and deletion records (dates, versions and statuses, none of the founder’s material)Kept
Deletion history
A job record outlives the content it removed, so a founder can see what happened.
- QueuedScheduled expiryDue 4 October 2026 at 16:40rows pending · file pending
The record holds an identifier, a status and an attempt count. It never holds any of the founder’s material, and the logs behind it carry the same fields and nothing more.
In the real product this position is a red “Delete everything now” button with a typed confirmation. Here it takes you to the privacy notice instead, since there is nothing to delete.
The caveat we do not hide
Deleting removes content from the live service. It does not reach into the hosting provider’s database backups, which expire on their own rolling window — so a copy taken before the deletion persists until that window passes.
Nor does it reach the live-voice provider (OpenAI), which receives the founder’s microphone audio, brief, deck text, meeting focus and firm context during a real meeting, a pseudonymous account identifier (no name or email), and the figures the browser measured for the report, and handles them under its own terms. It may keep abuse-monitoring logs, which can include content, for up to 30 days, and nothing here can delete them.
Otherwise, a founder’s content is scheduled for deletion 7 days after it was first created, and removed when the operator’s scheduled cleanup job runs. The full notice spells this out rather than claiming more than the implementation delivers.