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.

Analytics and advertising

ChapterDock uses Google Analytics 4 and Meta (Pixel and Conversions API) to measure visits, traffic sources and the results of Facebook, Instagram and Google campaigns. Measurement runs automatically on every page of the website and the studio, with no banner or preferences to set.

For each page we send the type of route visited, without project, invitation or customer identifiers, the campaign parameters (utm, fbclid, gclid) and, on studio pages, a generic title instead of the story title. Other address parameters, such as verification codes or emails, are not sent. The connection also makes your IP address and technical browser information available to Google and Meta.

We measure registration, email verification, the first personal project, first saved text and first scene reaching 100 words, Studio trial activation, checkout initiation, the first actual subscription payment and Stripe-confirmed token purchases. Events include type, date and ID and, for payments, amount and currency. Google Analytics receives in-page events from the browser and confirmed payments from the server, with a hashed account ID. Meta receives them from the server through Conversions API with SHA-256 hashed email and account ID and, for website events, browser information: hashes remain personal data and allow Meta to match the event to an account.

We do not send Google or Meta manuscripts, story titles, MUSA requests, conversations, passwords or card details.

Cookies used: Google Analytics _ga and _ga_* to recognise the browser and session (up to 2 years); _fbp, a random browser identifier, and _fbc, saved when the address contains a Meta click ID, both for 90 days and shared between chapterdock.com and app.chapterdock.com; technical chapterdock-ga4-* cookies that carry a studio event for up to 24 hours until it is sent. Checkout context, including browser identifiers, remains available for payment for 24 hours.

For new accounts, we internally retain the dates of the first project, email verification and start of writing, linked to the account ID. These markers count each author once: they contain no text and are retained for the life of the account. Events awaiting delivery are removed from the queue on completion or by periodic cleanup after a maximum 24-hour retry window; events already received remain with Google and Meta under their retention rules.

Google processes the data it receives according to its privacy policy; for how it uses data from partner sites, see this page.

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.

Export

You can export your texts using the project tools even after your trial or subscription ends. Versions and notes are stored separately from the manuscript backup. Versions expire after 7 days on Free, 90 days on Studio and 365 days on MUSA, including following a downgrade. Export any checkpoints you want to keep longer.