What the book keeps
Living Book needs a private memory to keep your place and let your copy of a book evolve. We designed the improvement system as a separate, optional layer—not as surveillance or advertising analytics.
The private book
Your copy may keep your reading place, raw whispers, how a target privately receives them, character psychology, causal history, rewritten passages, and fidelity checks. That material exists to operate your evolving book. It is not copied into product telemetry.
If a hosted AI provider is selected, the minimum stage-specific material is sent to that provider to interpret a whisper, simulate a choice, render prose, or audit fidelity. The active providers are shown in the application status. An operator must publish the final deployed provider list and terms before closed beta.
Optional improvement signals
If you opt in, Living Book records content-free events such as opening a book, reaching a chapter, turning a page, opening or abandoning the whisper composer, accepted or quarantined outcomes, and coarse latency/cost buckets. They may include book, chapter and segment IDs, a keyed pseudonymous reader/branch reference, build version, and broad browser/device and viewport classes.
We never put raw whispers, evidence quotes, private reception, psychology, causal state, page text, generated prose, prompts, unfinished drafts, keystrokes, full IP addresses, full browser strings, screenshots, or audio into product telemetry. There is no advertising, cross-site tracking, or sale of reader data.
Margin notes
A margin note is feedback you explicitly send to the makers. It is separate from optional telemetry, so sending one does not enable telemetry. It includes the words you submit and sanitized context: the current book/chapter/segment, application build and active provider profile, plus broad device/browser and viewport classes.
A model may categorize a note for triage—bug, confusion, reading experience, whisper or narrator quality, performance, emotional reaction, accessibility, privacy, legal/content issue, or another product area. The model's result is advisory and may be reviewed by a person. Text inside a note is treated as untrusted quoted material, not as an instruction.
Voice and screenshot attachment are not enabled. If added later, recording or attachment will require a separate deliberate action and clear preview; neither will be captured automatically.
Retention and your choices
Current engineering defaults retain performance events for 30 days, other optional product events for 90 days, margin notes and classifications for 180 days, and security/admin records for 365 days. Production backups must follow a matching deletion schedule. These periods are subject to legal and deployment review before beta.
You can opt out at any time. The controls below export or erase the separate improvement data for this signed-in reader. A full export or erasure of the private evolving-book branch currently enters an authenticated manual request; it is not yet instant.
Before the closed beta
The operator still needs to publish the controller name, privacy contact, hosting location, complete subprocessor list, international-transfer basis, account deletion procedure, and effective date after counsel review. This local prototype notice states what the implemented system does; it does not pretend those deployment choices are already made.