Last Updated: October 30, 2026
This policy covers the ClaraNarratio website and apps. We use Clerk for account authentication. When you sign in, we process account identifiers, email addresses, profile names when provided, and session information to authenticate you, maintain your account, and check access to features. Sign in with Apple may provide a private relay email address. Cloudflare hosts our website, API, and application data. Authentication and hosting providers also process network and device information needed to operate and secure their services.
Apple, Google Play, or our website checkout provider processes payments for the corresponding purchase method. For App Store purchases, ClaraNarratio receives transaction and product identifiers, subscription status, billing-period dates, signed transaction information, and an identifier binding the purchase to your Clara account. We use these records to activate and restore access, reconcile renewals, prevent misuse, and handle billing support. Apple does not send us your payment-card details through this purchase flow. Other checkout providers process payment information under their own terms and privacy policies.
The apps use on-device storage for downloaded audio and text, bookshelf items, bookmarks, playback progress, preferences, and authentication state. These local records support offline listening and resuming playback. Requests to stream or download content, verify an account, or use an online feature reach our service providers and may create operational records. Removing local downloads or signing out does not by itself delete your server account or purchase records.
Online catalogue searches may send your search terms through our backend to services such as Standard Ebooks, LibriVox, or Gutendex. Search terms and requested content URLs may appear in server request logs. Where you choose to submit a story or source for editorial consideration, we process the name and email address you provide, the submitted link, title, text, and notes, and any account information associated with the submission. These records support reviewing and following up on your submission; an on-device draft is separate from a submitted record.
Ask Clara uses OpenAI's API to generate answers. We send your question, relevant recent conversation history, and supporting episode or book context through our backend to OpenAI. If you request further research, we may store the question, account identifier, context, and processing status for that follow-up. Questions and related diagnostic information may also appear in operational logs. Authorized administrators may review these records to fulfill follow-up requests, provide support, and investigate errors or misuse. Where a voice feature is enabled and you choose to use it, microphone audio is transmitted to OpenAI for live responses, and we record session and usage information.
OpenAI's published API policy states that API content is not used to train its models by default; model-improvement sharing requires an explicit opt-in. This does not mean API content is never retained. OpenAI may retain content for abuse monitoring, legal and safety obligations, and application state, depending on the endpoint and applicable account controls. Its published defaults include abuse-monitoring retention generally up to 30 days, with exceptions, and retention of stored Responses API state. We do not promise zero retention or immediate removal from provider safety records. See OpenAI's API data controls for its current practices.
Our website and supported client surfaces use first-party usage measurement to understand reliability and how features are used. Events may include a randomly generated browser/session identifier, page or content identifiers, listening and download milestones, sign-in or subscription events, error details, referrer and campaign parameters, and general device/browser information. Servers may add IP-derived country or region and record IP addresses and user-agent information in operational logs. Collection varies by platform and feature. We use these records for service operation, troubleshooting, security, and product measurement. We do not use advertising networks or sell listening data. Website pages may request externally hosted fonts, whose providers receive the network information needed to serve those requests.
We retain account and entitlement records to operate your account and subscription, research, editorial-submission, and support records to handle requests, release-notification records to administer the notifications you requested, and operational records to maintain and secure the service. These record types do not share a single automatic expiry date. Payment, security, and deletion-request audit records may need to be retained for accounting, disputes, fraud prevention, or legal obligations. Provider-held data is also subject to the provider's applicable retention and deletion processes.
You can initiate account deletion in the app under Settings > Account & Data Privacy, use our Account Deletion Request Page, or email support@claranarratio.com. An accepted in-app request is recorded with a request ID and remains pending until an administrator completes fulfillment. Submission or sign-out is not confirmation that cloud records have already been deleted. Our account-deletion process provides for fulfillment within 30 calendar days following verification, subject to the retained records described above. Store subscriptions must be managed or cancelled separately through the App Store or Google Play. We also handle applicable requests for access or correction through the same support address.
If you apply for or participate in the Android closed beta, we process your Google Play email for allowlisting and transactional notices, participation dates, app/build version and general device model, and feedback you submit. If your Play email differs from your Clara sign-in email, we verify ownership through an email link. Participation records support beta administration and testing evidence; a complimentary membership's 90-day duration is not an automatic data-deletion timer. You can withdraw or request deletion through the beta dashboard or support@claranarratio.com, with account, billing, audit, and provider records handled as described above. The beta heartbeat does not request GPS location or an advertising ID.
If you confirm that you want to join a book-release waitlist, we record your account identifier, account email address, selected book, sign-up source, referring page, general device/browser information, IP-derived country, and registration dates. We use the email address and selected book to administer the waitlist and send the release updates you requested. Joining a waitlist is optional and is separate from signing in or buying a subscription. To withdraw from a release-notification list or request deletion of its records, contact support@claranarratio.com.