LIBELL.US
FeaturesPricingAbout
English
Open Studio

Privacy Notice v2.0

Pre-launch draft — not yet effective.

Draft updated: October 18, 2026

1. Scope

LIBELL US PUBLISHING LLC ("libell.us," "we," "us" or "our") provides the libell.us website, Creator Studio and reader applications (the "Services"). This notice explains the personal information we collect, why we use it, who receives it, and your choices. It covers early access as well as general availability.

The Services are offered to users in the United States aged 13 or older. Users aged 13–17 need parent or guardian permission, and an adult must be responsible for any paid Creator Studio subscription, as explained in our Terms of Service. This notice describes our practices; it is not a request for blanket consent to every use of information.

2. Information we collect

Account and access information

Creator Studio supports sign-in through Google, Apple and Microsoft. The reader apps support Google and Apple sign-in and anonymous accounts. Firebase Authentication processes provider identifiers, an internal user identifier, display name, email address and verification status when supplied by the provider. A provider profile-photo URL may also be available and used to display your photo in the reader app; loading it can send a request to the photo host. We do not receive your sign-in provider's password.

Creator and reader identities are separate, even when the same provider and email are used. We also process creator pen names and their publication confirmation, membership and account status, and early-access signup or access-list records such as name, email, user identifier and signup date.

Creative work and publishing

We process manuscripts, prompts, story structures, characters, settings, uploaded images, generated text, images and narration, translations, book metadata and the content you submit for publication or sharing. Publication creates separate copies and moderation records, including author credit and identifiers. Where an import feature is available, we also process the source text, source references, original-author attribution and import progress or errors.

Reader activity and feedback

We process libraries, bookmarks, reading and listening progress, ratings and written comments, content reports, and support messages. Interactive adventures also use fictional character profiles, choices, inventory, game state, outcomes and Hall of Fame records. A fictional character's age or attributes are story information, not a verified statement of the reader's age or identity.

Billing information

Stripe handles Creator Studio payments and its billing portal. We send relevant account identifiers, name, email and selected plan information and receive customer, subscription, payment and invoice records. Those records can include billing contact details, address, tax details and limited payment-method information. We store invoice and order records and use Stripe records to display billing history. Our application servers do not receive or store full card numbers or card security codes. Stripe processes payment details entered into its payment forms.

Usage, device and diagnostic information

The website and apps collect operational and analytics information, such as page or screen visits, app opens, feature interactions, search text, book identifiers, reading events, API results, timestamps and error details. We use Google Analytics, Firebase Crashlytics and Firebase Performance Monitoring, together with server logs, to understand use and diagnose failures.

These records can contain or be associated with account, installation, session or device identifiers, IP addresses, app and operating-system versions, device model or name, language settings, performance measurements, crash stacks and diagnostic context. Mobile API requests include device and application information. Support reports can contain detailed device data and whatever you type. Logs can include account and payment-reference identifiers; diagnostic output can also contain prompts or other content included in an error. Do not assume analytics, crash reports or free-text reports are anonymous.

Firebase App Check and related security services process tokens and device or browser signals to help detect illegitimate requests and abuse.

Cookies, browser storage and device storage

We and the providers described below use cookies, browser storage, application storage and similar technologies for authentication, security, analytics and preferences. Browser and app storage also hold settings, cached books and media, and local reader or adventure state. Some preferences, such as font size and theme, stay on the device; language and content-language choices can be transmitted for service operation. Clearing local storage or reinstalling an app can remove locally stored data, including access to an anonymous account.

3. How we use information

We use the information above to:

  • Authenticate accounts, manage early access and enforce memberships and usage limits.
  • Save creative work, deliver reading and adventure functions, and process the AI, translation, import, sharing and publication operations you request.
  • Process subscriptions, invoices, cancellation, usage accounting, refunds and payment disputes.
  • Review content, investigate reports, prevent abuse and secure the Services.
  • Diagnose failures, measure service performance and understand how features are used so we can improve them.
  • Respond to requests and communicate about accounts, service changes or legal obligations.
  • Comply with law, maintain necessary records and establish or defend legal claims.

AI processing

AI features send the content needed for the operation to external providers, which can include prompts, manuscript passages, story structures, character or setting details, reference images and text for narration. Publication and private sharing can also involve AI processing, for example to generate metadata or classify a book, even if you did not use a separate generation button. Some operations can process extensive manuscript content.

We do not use private manuscripts to train our own foundational AI models. We use third-party services under their applicable service terms and our arrangements with them. Their processing and retention depend on the provider, model, feature and configuration. We do not promise that every provider stores no data or that every model has identical data-use terms. Avoid including unnecessary sensitive information or another person's private information in prompts and uploads.

4. Who receives information

Service providers and integrations

Providers receive information relevant to the functions they perform. The provider used can vary by platform and selected feature:

  • Google Cloud and Firebase: hosting, databases and storage, authentication, App Check, analytics, crash reporting, performance monitoring and other operational services. App protection can use reCAPTCHA Enterprise or Play Integrity. See Google's Privacy Policy.
  • Sign-in and device-platform providers: Google, Apple and, on the website, Microsoft handle sign-in requests. Apple also supports app-integrity checks and account-related notifications. They receive information through those interactions and handle it under their own terms and privacy notices.
  • Stripe: payment collection, customer and subscription administration, billing records, fraud prevention and financial compliance. Stripe also processes some information for its own purposes, described in Stripe's Privacy Policy.
  • AI providers: Google Vertex AI and Text-to-Speech, models available through Vertex AI including Anthropic where configured, AWS Bedrock, Microsoft Azure OpenAI and OpenAI can process relevant inputs and outputs. This list describes supported integrations, not a statement that every request goes to every provider.
  • Optional content integrations: a dictionary lookup sends the selected word and language to dictionaryapi.dev, whose server also receives normal network information such as your IP address. Loading embedded YouTube content connects to YouTube's privacy-enhanced player. Import tools can retrieve text or references from sources such as Open Library, Project Gutenberg and Wikisource. Visiting a source or other external link also discloses ordinary browser/network information to that site.

Independent websites and providers may process information under their own privacy notices. Their presence here does not mean they receive your entire account or manuscript.

Readers, the public and authors

Public books: publication makes book content available to readers and makes metadata, covers and author credits available through app and web catalogs. Search engines and others may index, copy or share public material. A pen name or content you choose can identify you. Updating a profile pen name does not automatically change credits on earlier editions.

Private shares: an unlisted share is not restricted to named recipients. Someone with the share identifier and reader-app access, including anonymous access, may read the copy. Temporary cleanup is not a guarantee of immediate removal at a specific time.

Feedback to authors: for a rating, the author can see the stars, written comment, date and whether the reader had started the book. We do not attach the reader's name, email or account identifier to that author-facing feedback. However, a comment can identify you if you include identifying details. For a content report, the author sees report reasons and counts, not the reporter's identity or the detailed report text. Support and authorized review personnel may access the underlying records to handle the issue.

Legal and protective disclosures

We may disclose relevant information to respond to lawful requests, meet legal obligations, investigate abuse, protect rights or safety, or resolve disputes. Copyright notices and counter-notices may be shared with the other party, including the contact details needed for that process.

We do not sell personal information or share it for cross-context behavioral advertising. Google signals and advertising-personalization signals are disabled in our website analytics configuration. We still use analytics for the operational purposes described above.

5. Storage, retention and deletion

Our primary infrastructure is in the United States. Provider processing or support may take place in other locations, including through globally routed AI services; we do not promise that all processing remains in a particular US region.

We retain information according to its purpose, account status, reader access, security needs and applicable financial or legal requirements. Ending a subscription does not by itself delete an account. There is no automatic six-month deletion guarantee for inactive creator accounts.

  • Active accounts and work: account information, drafts and associated media generally remain while needed to provide the account and features you use, unless you delete them or request deletion.
  • Creator deletion: the process stops associated billing, removes creator account records, private drafts, private shared copies and associated support and moderation records, and withdraws current public editions. It does not automatically delete a separate reader account.
  • Published editions: withdrawn editions can remain stored and accessible, including to support reader libraries, together with author credit and publication identifiers. Retired public editions have a minimum cleanup period of 30 days; library holds and other publication references can extend retention. This is not a maximum retention period or an immediate recall of copies already obtained by readers. Contact us about privacy or unlawful-content concerns involving a retained edition.
  • Reader deletion: the process removes the reader profile, library, bookmarks, adventure records, individual ratings/comments and reports. Aggregate statistics, including counts and ratings, may remain. Current account-linked issue reports and their free text and diagnostic details are erased. Historical backups and independently held provider diagnostics follow their separate retention requirements.
  • Usage and temporary records: creator AI charge records are scheduled to expire after 13 months and are also removed with creator account data. Short-lived request-deduplication records can remain for about 7 days after a reader request. Scheduled expiration and cleanup can take additional processing time.
  • Other separate records: early-access signup/access lists, import-operation records, correspondence, and provider-side payment records have their own purposes and lifecycles. They are not all removed automatically by deleting an application account. Include them in a deletion request when relevant.
  • Backups and logs: copies may remain until backup, recovery, log and storage-retention periods expire. We may retain records required for security, tax, accounting, disputes or other legal obligations. Deletion is not instantaneous across every system, and failures may require follow-up.

We do not use retained backup or legally preserved information to restore ordinary account access after an approved deletion. Copies saved by other people and records independently held by payment or sign-in providers may require separate requests to those parties.

6. Your choices and privacy requests

See Delete account / Privacy requests for email instructions, verification, handling targets and retention details. No sign-in or app installation is required.

For a waitlist-only account, use Leave waitlist & delete account on the Beta page. This removes your waitlist signup and the Libell.us sign-in account created for it; it does not delete your Google, Apple or Microsoft account. The page confirms completion only after server verification and local sign-out. If removal cannot be confirmed, retry or contact contact@libell.us for recovery. A new login during beta automatically joins the waitlist again. Old sessions and background retries do not re-enroll a removed account. Minimal deletion and recovery records remain for at least 90 days after completion and until seven days after the verified expiry of the last restorable pre-deletion copy, whichever is later. Unresolved cases are retained until resolved; backups and logs follow their stated retention. Approved beta or creator accounts need the separate deletion request described below.

Use the available profile and content controls to manage your pen name, books and preferences. Some identity details come from your sign-in provider and must be changed there. Reader account settings include deletion; to request creator account deletion, or assistance with either account, email contact@libell.us. Tell us whether your request concerns Creator Studio, the reader app, early-access records or more than one of these. Do not send passwords or full payment-card details.

Depending on the law applicable to you, you may have rights to access or obtain a copy of personal information, correct it, delete it, or appeal a refusal. Send requests, authorized-agent requests or appeals to the same email address. We may need information to verify the request and an agent's authority. We will explain applicable exceptions or a refusal and provide the response or appeal information required by law. We do not discriminate against you for exercising applicable privacy rights, though deleting information needed for a feature can prevent its use.

Signing out, uninstalling the app or revoking Google, Apple or Microsoft access does not by itself complete a libell.us deletion request. If you have lost access to the account, contact us. Cancel a paid subscription through its membership controls if you want renewal stopped while a separate request is being handled.

Browser settings can restrict cookies or clear storage, but this may affect sign-in and preferences. Google's Analytics Opt-out Browser Add-on can limit supported browser analytics; it does not disable mobile analytics, crash reporting or server security logs. The Services do not currently provide an in-product switch for all telemetry. We do not respond to browser Do Not Track signals. Because we do not sell information or share it for cross-context behavioral advertising, we do not offer an opt-out from those activities; this does not limit any control or response required by applicable law.

7. Children and teenagers

Children under 13 may not use the Services. We do not knowingly collect personal information from them. If you believe a child under 13 has provided information, contact contact@libell.us so we can investigate and delete it as required. Do not place a child's private information in manuscripts, prompts or reports unnecessarily.

Users aged 13–17 require parent or guardian permission. An adult must be the responsible paid subscriber for any Creator Studio subscription they use. A parent or guardian can contact us about a minor's information; we may need to verify identity, authority and the relevant account before acting. Public publication and unlisted sharing have the visibility described in Section 4, including for teen users.

8. Security

We use reasonable technical and organizational safeguards designed to protect information. No internet transmission or storage system is completely secure. Protect your sign-in provider account and share identifiers, and avoid including unnecessary sensitive information in public content or support reports.

9. Updates to this notice

We will post updates here with a new effective date. For material changes, we will provide additional notice through the Services or available account contact details as appropriate or required by law. Where a change requires consent, we will obtain it before using information in that way.

10. Contact

Email: contact@libell.us

Mail: LIBELL US PUBLISHING LLC, 1032 E BRANDON BLVD #9564, BRANDON, FL 33511, UNITED STATES.

Libell.us
FeaturesGuidesAboutContact UsDelete account / Privacy requestsPrivacyTerms

©2025 Libell.us Publishing LLC. All Rights Reserved.