Privacy Notice
Last Updated: September 5, 2026
Easy eBooks is committed to protecting your privacy. This Privacy Notice describes how we collect, use, and share your personal information when you use our services.
1. Information We Collect
- Account Information: When you sign in (e.g. using Google Sign-In), we receive your email address, name, and profile picture URL.
- User-Generated Content: We store the parameters and text of the stories you generate, as well as review glossaries and vocabulary terms added to your practices collection. All generated stories are added to our public shared library catalog.
- Reading History and Progress: We store your active reading placements (such as the last read chapter index) and the completion status of stories you read. If you are signed in, this data is saved to your account profile to sync your progress across devices; otherwise, it is stored locally on your browser's local storage.
- Technical Diagnostics: To help us identify and troubleshoot issues, we log diagnostic metadata (such as model identifiers, action names, request duration, and technical error descriptions) exclusively when AI generation or translation requests fail. Any user email addresses linked to these logs are automatically and permanently masked (e.g. u***@domain.com) on our servers before storage.
2. Data Ownership and Deletion
We respect your ownership rights over your creative output:
- Public Catalog: Stories created on Easy eBooks are public and published to the community catalog for language learners.
- Story Deletion Requests: Users and community members can flag stories for deletion. Flagged stories are reviewed by administrators, who evaluate and execute permanent deletion from our databases in accordance with community guidelines.
3. How We Use Your Information
We use your information to:
- Deliver the language learning story generator service.
- Support dictionary lookup operations and count API key transactions.
- Enhance pedagogical grading configurations (using public stories or aggregates).
4. AI Integration (API Data Sharing and Prompt Handling)
When you generate a story outline, chapter, or vocabulary glossary, configuration prompts (such as target language, CEFR difficulty level, genre, and custom user notes) are sent to third-party AI inference providers and routing gateways (including OpenRouter, Meta, Google, Z-AI, and DeepSeek) to fulfill the generation request.
Identity and Anonymity: We do not attach your user name, email address, or user account ID to prompts or metadata transmitted to these third-party AI providers. For standard platform generations (including the free tier), requests are proxied through our servers and appear to AI providers as originating generically from our platform infrastructure.
Provider Routing, Prompt Retention & Model Training: OpenRouter and AI model gateways dynamically route inference requests across a diverse network of independent hosting providers and data centers. As a result, data retention and model training practices vary:
- Provider Diversity & Operational Logging: OpenRouter routes requests across multiple hosting providers. While standard commercial API endpoints typically do not use customer API inputs to train foundation models by default, individual third-party hosting providers may temporarily retain or log prompt text and completions for operational monitoring, caching, or abuse prevention (typically up to 30 days) according to their own data policies.
- Contributor & Free Tiers: Certain free or contributor-tier model endpoints (such as
meta/muse-spark-1.3-contributorvia OpenRouter) explicitly permit providers to retain, log, and analyze prompts and generated outputs to train and improve future AI models. - No Guarantee of Zero-Retention: Because inference is distributed across multiple third-party hosting partners outside our direct infrastructure, we cannot guarantee zero-retention or that underlying providers will not temporarily log requests. Users are strongly advised never to submit confidential data, sensitive personal information, or proprietary secrets within story notes or generation prompts.
Bring Your Own Key (BYOK): If you configure a custom OpenRouter API key in Settings, generation requests are authenticated using your personal OpenRouter credentials. In this mode, usage and billing are associated directly with your OpenRouter account, and data handling is governed by OpenRouter's privacy policy and the specific provider routing, model endpoints, and data collection preferences configured on your OpenRouter account.
5. Google Advertising and Third-Party Cookies
We may display Google AdSense advertisements on our platform in the future to support free access. Google uses cookies to serve ads based on your prior visits to our website or other websites on the internet. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to our site and/or other sites on the Internet. You may opt out of personalized advertising by visiting Google Ads Settings. Alternatively, you can manage your advertising cookie choices directly using our Cookie Consent manager banner on our website.
6. Contact Us
If you have any questions regarding your data privacy or request data extraction/removal, please feel free to reach out to us at [email protected].