Your data, clearly explained.

This page describes how ChapterDock processes website and studio data. To request access, correction, export or deletion of your data, email support@chapterdock.com.

Your studio

Your name, email, profile and subscription status are associated with your account. Projects contain manuscripts, characters, locations, notes and versions. Firebase handles authentication and project storage; access is restricted to the owner and authorised collaborators.

The demo and drafts

The demo saves projects in your browser’s local storage. The editor also keeps a local draft of text that has not yet been saved. Anyone using the same browser profile can access this data: export your work and clear site data when using a shared computer.

Musa AI

Suggestions send the current passage, request and selected context to OpenAI. When the owner enables MUSA memory, the manuscript is also analysed in the background after edits. The owner can pause memory at any time. Excerpts, summaries, sources, embeddings, decisions and results are stored in the project. Private conversations are visible to their author; shared conversations and approved decisions are accessible to project members. Requests use store: false; this setting is not a guarantee of zero retention by the provider. ChapterDock stores output and usage counters to manage the service and quotas. You can export memory, reports and individual results, and delete conversations you created. Deleting a project also deletes its MUSA data through a resumable process. Aggregate cost and usage counters do not contain the manuscript.

Service emails

Brevo sends transactional emails from noreply@chapterdock.com: address verification, password recovery, invitations, plan and payment updates, and project notifications. The provider receives the address, name and information needed for each message. Manuscripts and the contents of MUSA analyses are not included in emails. Messages relate to operations on your account, not a newsletter.

Payments and cookies

Stripe handles payment details, top-ups and subscriptions. ChapterDock does not store full card numbers. Token balances and transactions record the amount, date, status and references to the payment or operation, without manuscript text. Balance history is restricted to the account owner. A necessary session cookie keeps you signed in. Internal counters record registration, writing, trials, invitations, exports and encounters with limits, using the account ID, plan and day, without text, name or email in the event. They are kept for 90 days to assess the service’s usefulness and costs.

Advertising and consent

ChapterDock measures public website visits with Meta Pixel, which runs automatically without a prior acceptance banner. You can separately choose whether to allow conversions associated with your account through Conversions API. This choice does not restrict access to the service, is separate from the terms and does not subscribe you to a newsletter.

The Pixel automatically reports public website page visits to Meta. It sends the page address without search parameters; the connection also makes your IP address and technical information sent by the browser available to Meta. The Pixel does not run in the editor, studio, admin area or authentication pages.

Only with consent, Conversions API reports registration, checkout initiation, the first actual subscription payment and Stripe-confirmed token purchases from the server. Data includes the event type, date and ID and, for payments, amount and currency, together with browser information for website events. Email and account IDs are hashed with SHA-256 before sending: they remain personal data and Meta may use them to match an event to an account. We do not send Meta manuscripts, story titles, MUSA requests, conversations, passwords or card details.

Your preference is stored for 180 days in a dedicated cookie and, when you log in, associated with your account so it also applies to server events. You can change or withdraw it at any time through Advertising preferences on the website and in your account settings. Withdrawal stops new account conversions and cancels pending ones; it does not disable the Pixel on public pages or retract events Meta has already received. Data awaiting delivery is removed from the queue on completion or by periodic cleanup after a maximum retry window of 24 hours.

Meta processes the data it receives according to its privacy policy and its cookie policy. These pages also describe retention, transfers and the controls available for Meta services.