How it works
Ending a project, step by step
Every key is named in full
Not a wildcard. A list, in one file, that a test walks the entire store to verify — it fails if a single key of that project survives.
The files go too
Everything under the project's storage prefix: the recordings, the photographs, the screenshots.
The owner's link is the only one that may ask
A seat runs a project; only the person whose business it is may end it.
Safe by design
The rule that makes it safe to have
Clear boundaries
What it will not do
Every capability page ends with this list. It is the part that says what you are actually buying.
- It will not cancel your subscription — that lives with the payment provider, and the answer says so rather than letting you find out from a bank statement.
- It will not keep a copy for analytics.
- It cannot be undone.
Where it lives in the code: lib/destroy.ts · components/DeleteProject.tsx
Questions
Asked about this
From Help, where every answer is written from the product as it runs.
Can you read my testimonials?
An operator can open a dashboard, and the privacy page says so in plain words: we can, we do it to answer a request you made or a fault you reported, and not otherwise.
Is my customer's email address ever public?
No. An author's email address is in no public answer, from any endpoint, on any plan.
Can I give somebody access without giving them my link?
Yes — a seat has its own link and its own permissions, and revoking it revokes only that one. A seat cannot delete the project or add a paid extra to your subscription.
Does the widget track my visitors?
It counts views, plays and clicks per widget so you can tell whether anybody is reading them. There is no visitor profile and no cross-site identifier. Your page's visitors are not our product.
This is running now
Open a project and use it. Nothing on this page is a roadmap.