Orakel Books

V1 data notice

Privacy and Reader Data

This notice explains the current OrakelBooks V1 reader companion behavior. It is focused on the live reader experience at app.orakelbooks.com.

Do not enter sensitive personal information in reader questions. OrakelBooks is designed for book discussion, chapter guidance, and companion responses.

What We Collect When You Ask The Book

When a reader asks a question in the companion, OrakelBooks may save the following information:

  • An anonymous or pseudonymous browser session ID stored in the reader's browser. Clearing browser storage resets this ID.
  • The book and chapter connected to the reader route.
  • The question submitted by the reader.
  • The companion response shown to the reader.
  • If the reader chooses to create an account, the email address connected to that Memberstack account and the reader's saved place.
  • Whether broader-context or spoiler mode was requested.
  • The model label used for the response.
  • An approximate token estimate for usage tracking.
  • Speech-generation usage metadata for read-aloud and spoken answers, including voice label, cache hit or miss, character counts, estimated cost, latency, and timestamp.
  • The date and time of the question.

OrakelBooks uses this speech metadata to monitor cost and reliability. The usage ledger is not intended to store the passage text being narrated.

Why We Collect It

Reader questions help authors understand what readers are curious about, where explanations may need improvement, and how the book companion is performing. Questions and responses may be reviewed by the book author or an OrakelBooks administrator for quality, debugging, and basic usage monitoring.

What We Do Not Collect In V1

  • Readers do not need an account to ask the book.
  • OrakelBooks does not collect reader payment information.
  • OrakelBooks does not ask for precise reader location.
  • OrakelBooks does not track Amazon purchase attribution.
  • OrakelBooks does not run a third-party reader analytics SDK.
  • OrakelBooks does not use reader questions to replace the book.

Hosting and infrastructure providers may process ordinary server request information, such as IP address, user agent, and request timestamps, for security, operations, and delivery of the site.

Optional Reader Accounts

A reader account is optional and is handled through Memberstack. It is used to save the reader's latest section in a book and restore recent signed-in chat history for that section. OrakelBooks stores the verified Memberstack member identifier and email needed to connect progress to the reader.

Author Dashboard Visibility

Authors with access to the protected dashboard, and OrakelBooks administrators, may see reader questions, companion responses, chapter names, spoiler status, model labels, token estimates, and timestamps for the relevant book companion.

AI Processing

Reader questions and approved chapter context may be sent to the configured AI provider, currently OpenAI, to generate a companion response. Requests are made server-side and are currently configured with response storage disabled. The provider may still process data as needed to provide the response under its service terms.

Contact

For privacy or reader-data questions during the V1 launch period, contact the project owner at colin@doylezone.com.