Effective and last updated: 9 August 2026
On this page
01 · Private by default
Projects, transcripts, images, manuscripts, and finished editions are associated with your account and are not public. Private media is served through authenticated endpoints rather than public file URLs.
Access is limited to the account owner, authorised support personnel when help or repair is needed, and service providers that perform a required processing step. We use access controls, private storage, transport encryption, protected credentials, and operational logging. No online service can promise absolute security.
02 · Where data is held
- Account, project, transcript, consent, and transaction-reference records are stored in a Cloudflare D1 database configured for the Bookstory service.
- Images, working files, and finished ebook and audiobook files are stored in a private Cloudflare R2 bucket. Bookstory does not retain original interview audio; finalized live speech is saved as answer text.
- Selected data is processed by AssemblyAI, Google Gemini, Stripe, Resend, or GitHub only for the functions described in the Privacy Notice.
- Audiobook preferences may also remain locally in your browser.
03 · Retention by category
| Category | Normal retention approach |
|---|---|
| Account and authentication | While the account is active, then until deletion is completed, except for records that must be retained for law, security, or claims. |
| Active story material and finished editions | While needed to provide the project and continued access to purchased outputs, or until a valid deletion request is completed. |
| Replaced drafts, images, and generated files | Removed when replaced, rejected, refunded, or no longer needed; temporary workflow copies are removed as processing completes. |
| Purchase, consent, refund, dispute, and accounting evidence | For the period required by bookkeeping, tax, consumer, contract, fraud-prevention, and legal-claim rules. |
| Print-order contact and delivery address | Stored with the private print request while needed for the sandbox order, support, and any valid deletion or legal-retention requirements. |
| Security and rate-limit records | For the shortest practical security window; some protected fraud or dispute evidence may be kept longer where justified. |
| Support messages | Until the request is resolved and for a limited follow-up period, or longer if needed for a purchase, complaint, security issue, or legal claim. |
04 · Deletion requests
Contact us from the email address associated with your account to request deletion of an account, project, or image. We will verify the request, explain any effect on paid access, and delete or anonymise data that is no longer required.
Deletion is not always immediate or absolute. We may retain limited transaction, consent, dispute, fraud-prevention, or audit evidence when law or a compelling legal need requires it. Data already included in a file you downloaded, or copies another person made after you shared a file, are outside our control.
05 · Provider copies and generated media
When applicable, we send deletion instructions to processors and remove the Bookstory copy. Provider security logs, billing records, abuse-monitoring records, or backups may age out under that provider’s own contractually controlled schedule.
Previously downloaded audiobooks cannot be recalled after a project is removed.
06 · Backups and recovery
Residual copies can remain temporarily in encrypted backups or provider recovery systems after deletion from the active service. They are isolated from normal use and expire or are overwritten under the applicable recovery schedule unless preservation is legally required.
07 · Exports and your own archive
Download accepted ebook and audiobook files when they are available and keep copies in storage you control. You can also ask for a copy of personal data associated with your account. Bookstory should not be your only archive for irreplaceable original photographs.
08 · Questions
If you want to know whether a particular record still exists, need help removing local browser data, or have a retention question, contact us and identify the relevant account or project.