Privacy

Website notice effective 2 November 2026

CaraLore is a private reading companion operated by Wade Norman, based in New Zealand. Wade is also the privacy contact, reachable at support@caralore.com.

The public app is not open yet. This notice applies now to this website and support email. The app sections explain the planned service; they will be reviewed before public accounts open. Browsing this site does not create an account or send book content to an AI provider.

CaraLore is intended for a general audience and does not target children under 13. The app does not collect birth dates or use an 18+ checkbox solely for launch. This is not a claim that users’ ages are verified.

This website

The landing, privacy and terms pages contain no forms, analytics scripts, advertising trackers or application cookies. Cloudflare serves these pages and processes connection information, such as IP addresses and request details, to deliver and protect the website. This technical information is needed to serve a request.

This static site has no application database or Worker execution logs, traces or error records. Cloudflare separately processes network and security information under its own policies; this notice does not promise a fixed deletion period for those records. See Cloudflare’s privacy policy.

Contacting support is voluntary. We use the address, message and attachments you send to respond and handle your request. Without enough information we may not be able to help or verify a privacy request. You do not need to email us to browse the website.

Information in the planned app

• Account information: the identifier and basic profile information supplied by your sign-in provider, such as your name and email address. CaraLore does not receive your Google or GitHub password.
• Your library: files or links you import, book metadata, collections, reading positions and saved results.
• Your conversations: messages, attachments, responses and feedback you choose to send.
• Connections: information and credentials needed for integrations you enable, including a connected OpenRouter key.
• Operational records: request, error, processing and usage information needed to keep the service working and enforce limits.
• Support: messages you send for help, including any account details or attachments you choose to include.

The app uses session cookies to keep you signed in and browser storage to remember interface preferences and drafts. Those are separate from this static website.

Why information is used

CaraLore uses this information to operate your account, store and organize your library, track progress, answer your requests, provide the integrations you enable, investigate failures and prevent abuse. Your reading content is not sold to advertisers or used for advertising profiles.

AI and connected services

When you request AI features or enable background AI processing, relevant messages, attachments and book evidence are sent to the services needed for that work. Importing a book alone does not enable story-memory processing.

Book-grounded answers and visible story memory use your saved reading position as their evidence boundary. Authorized audiobook lookahead can process transcript ahead of that position in the background; derived story facts stay hidden until you reach their reveal point. A visibility boundary is not a promise that no future transcript is processed.

For reader-funded AI, OpenRouter routes requests to model providers. Their own privacy and retention policies apply to the data they receive. Review OpenRouter’s privacy policy and the policies of the models you use. Do not submit sensitive information you do not want those services to process.

Cloudflare provides hosting and storage. Google or GitHub handles sign-in when you choose that provider. Other reading services are contacted through the connections you enable or links you ask CaraLore to retrieve. If you grant an external assistant access, it can receive the information covered by those permissions; its own policies also apply.

Your library is private to your account, but it is not end-to-end encrypted. Authorized operators and service providers may process information to deliver the service, investigate a problem or meet legal obligations. Providers may process information outside your country; CaraLore does not promise storage in a particular country.

Diagnostics and saved processing records

Cloudflare-native operational diagnostics help detect errors, abuse and capacity problems. Application logging is designed to exclude book text, prompts, responses, credentials and private attachments. There is no external operational-log archive. Cloudflare may also record connection and request metadata to deliver and secure the service.

Aggregate operational measurements contain event counts, timings and usage totals, not reader or book identifiers or story content. Cloudflare Analytics Engine retains these measurements for three months. Logs, traces and error records have separate platform retention periods; they are not a permanent library archive.

Saved conversations, feedback reports, private conversation traces and background-processing checkpoints are different: they can contain your content and are stored as application data. They are included in account-erasure processing, rather than treated as anonymous diagnostics.

Storage, deletion and your choices

CaraLore generally keeps saved library content, conversations and results while your account remains active, until you remove them or delete your account. This is not a backup or availability guarantee. You can export supported book data, remove books and disconnect integrations in the app. Removing a book is not the same as deleting your account and does not promise to erase every conversation or record that mentioned it.

Account deletion first restricts account activity, then removes the account’s data from active application stores. It can require retries while existing work finishes or an uncertain write is investigated. If erasure cannot be confirmed, deletion remains incomplete and the account stays restricted; the app does not report completion. Use Resume deletion or contact support if it remains blocked.

Cloudflare recovery systems can retain earlier database states for up to 30 days. Operational records follow their separate retention periods, and independent providers control information already sent to them. Completing deletion from active application stores does not mean those recovery copies or provider records have been immediately erased.

Disconnecting an integration does not delete material already imported, cancel completed charges or erase copies held by that provider. Removing the OpenRouter connection does not guarantee revocation of the provider-side key; manage access in OpenRouter too. Browser-held drafts and preferences may remain on your device until you clear site data.

Questions and requests

For privacy, access, correction, export or deletion requests, contact support@caralore.com. We may need to verify account ownership before acting. Rights and available remedies depend on applicable law; you may also contact your local privacy regulator. Do not send passwords or provider keys, or post book files or private conversations in public GitHub issues.

Cloudflare forwards support email to the operator’s Gmail inbox, where Google processes and stores the correspondence. Replies come from the operator’s personal Gmail address. See Google’s privacy policy for its data practices.

Support conversations are deleted from the support mailbox 90 days after resolution. Unresolved cases are kept until resolved; records are retained longer only where legally required. This mailbox policy does not erase copies held by correspondents or promise immediate deletion from provider recovery systems.

Support correspondence is handled separately from in-app account deletion. Ask us about removing it when making a privacy request.

Changes to this notice

This page will be updated when practices change. The date above identifies the current version.