Privacy notice
1. Controller and contact
David Albrecht, Mindoro Evolution, Jüchener Weg 49, 40547 Düsseldorf, Germany. Email: services@mindoroevolution.com; telephone: +49 1520 8947277. This notice covers books.mindoroevolution.com, including the Reader, editor, accounts and export service.
2. Access and hosting
When you access the service, technically necessary connection data is processed, particularly IP address, time, requested URL, browser and device information, and technical status data. The purposes are delivering, securing and troubleshooting the service. The legal basis is Article 6(1)(f) GDPR, our legitimate interest in secure operation, and Article 6(1)(b) for requested contractual services. We use Google Firebase Hosting and Google Cloud. Firestore, functions and our export bucket are configured in Frankfurt; Hosting is a global service, and this configuration does not restrict Firebase Authentication or support and security processing to Frankfurt. We do not promise processing exclusively in Germany.
3. Reader and browser storage
No account is required for reading. Imported books, progress and selected preferences are stored in IndexedDB or Local Storage on your device. Using the Reader does not automatically upload their book contents to our server. Storage on your device necessary for expressly requested functions, such as book import, saving and login, is provided under section 25(2), no. 2 TDDDG. An optional offline copy of the application is enabled only after you select it. Details and controls are under Browser storage. There are currently no embedded advertising or analytics services and no newsletter tracking.
Underlines, comments and progress through interactive story sequences are also stored locally. Story sequence progress and tasks solved within those sequences are currently not synchronised between devices. Speech bubbles, animations, click actions and embedded recordings belong to the digital book edition; a static PDF does not reproduce these interactive functions. The standalone asset workshop and private game templates initially also store their working data in this browser.
4. Regular accounts and login
For a regular account we process your email address, Firebase user ID, authentication data, verification status and necessary technical security data. Firebase Authentication manages your password; we do not see it in plain text. Browser persistence enables the signed-in session you request. The purposes are creating and securely using the account, based on Article 6(1)(b) GDPR and, for abuse prevention, Article 6(1)(f). Accepted terms, their version and the time of acceptance are stored to document the contract. Acknowledging this privacy notice is not blanket consent to arbitrary data processing.
5. Child accounts and parental approval
Children can use the Reader without an account. A separate child account is created only through a verified adult parent account. This involves processing a chosen display name, random login identifier, age group of under 16 or 16–17, the link to the parent account and documented approval. We do not require the child's own email address or exact date of birth. Technical login uses an internal, non-deliverable identifier, not communication with the child. Parents confirm their parental responsibility and receive information about purposes, data and withdrawal before approval. An additional one-time email link must be expressly confirmed in the associated parent account within 24 hours. Only a token hash is stored, not the confirmation link. The version of the parental information and the confirmation are recorded. Young people aged 16 and over additionally confirm their own consent before account-based Reader access; each child account receives understandable information and a way to withdraw approval itself. Where consent is required, it is obtained separately and can be withdrawn in the parent account (Articles 6(1)(a) and 8 GDPR). Access requested by parents is provided on the basis of the contract with them; protection and abuse prevention rely on Article 6(1)(f). Child accounts cannot make purchases or sales. We do not require an identity document copy or officially verify parental responsibility. The scope of protection and approval process are described under Parents and child accounts.
6. Projects, private cloud library and server exports
Editor drafts are initially stored locally and separated by signed-in account. Verified regular accounts can additionally enable a private cloud library at their express request. Only selected book files or files expressly saved from the editor are uploaded. We process the account ID, optional display name, filename, book or project title, file contents including embedded images, size, checksum and time, plus reading progress, the last reading position and your private underlines and comments for cloud books. The legal basis is the requested cloud service under Article 6(1)(b) GDPR. This is neither public publication nor a general automatic backup of all local files.
Original files are kept in the private Google Cloud/Firebase storage area mindoro-reader-private-library in Frankfurt; metadata and progress are kept in Firestore. Access is assigned to the respective account on the server. Download links are created only after login and are valid for one minute; anyone receiving such a link can use it until it expires. There are no permanent public book links. Data is not automatically made available to other users, search engines or a marketplace. Current limits are five files and 50 MB in total (Free) or 100 files and 500 MB in total (Creator), with a maximum of 50 MB per file. Where progress changes concurrently on several devices, an outdated write is rejected; progress not yet transferred remains on the device and can be reconciled with the cloud version. Child accounts do not upload to this cloud library themselves; it is managed in the parent account.
Files and their associated cloud progress can be deleted individually. Account deletion removes active private files, upload remnants, account and library data, progress and associated child accounts. The new private library storage area uses neither object versioning nor additional soft-delete retention. Technically delayed uploads are also removed based on their deleted account association. Abandoned upload parts are additionally scheduled for deletion after approximately one day. General provider, log and backup retention periods are separate. Local files on other devices or emails already delivered cannot be guaranteed to be deleted remotely.
For a requested paid server export, the selected book version, embedded images and contents, export options and account ID are transmitted to our export service, processed and provided as a private file. The legal basis is Article 6(1)(b) GDPR. Export downloads use short-lived signed URLs. These temporary export files are scheduled for deletion after approximately one day; any technical recovery or backup retention periods for the separate export area must be taken into account. Payment authorisations, export checksums and necessary contract records are separate.
6a. Optional AI narration and your own recordings
Updated 6 November 2026. AI narration requires an active Creator subscription, a verified adult account and your own Google Gemini API key. When you expressly request a recording, our server forwards the selected script, speaking style, language and voice to the Google Gemini API using your key. We do not automatically send the entire book, pictures or payment details. The key stays in memory for the current editor session and is transmitted over HTTPS for key validation and generation; we do not save it in your book, browser storage, account or generation records. Closing or reloading the editor ends this session. Google may charge API usage directly to your Google project; Creator does not include these charges. Your Google API agreement and applicable Google data processing terms apply to your project. The Gemini API does not assure exclusively EU processing; transfers outside the EU/EEA may occur. Review Google's Gemini API terms before enabling it. Child accounts cannot request AI generation directly.
Completed audio is stored privately in Google Cloud Storage under your account and included in your authored book for Reader and offline playback. Matching recordings can be reused. Account-linked records hold a request hash, voice and language settings, duration, processing status and quota usage; the script and style prompt are not stored separately in those job records. The script may remain part of your local project or a book you explicitly save to your private cloud library. This processing serves the requested contract feature and abuse protection described above. Account deletion removes private narration files and related account records. Copies already downloaded to devices cannot be erased remotely. You can request deletion of individual cached recordings.
For your own microphone recordings, your browser asks for microphone permission only after you start recording. Recording and preview happen on your device. Adding the recording includes it in your book; uploading the book to your private cloud library or requesting a server export also uploads its audio. Imported audio follows the same book storage and export rules. Microphone recordings and imports do not use Google AI and do not require Creator or an API key.
The 18+ declaration is separate from ordinary editor access. We store the declared 18+ status, its version and time under the account to enforce Gemini access. No date of birth or identity document is collected and this is not official age verification. Earlier expressly recorded adult declarations can be retained. Child accounts cannot enable Gemini; Creator alone does not override the age check. This account data is deleted with the account.
7. Emails and contact
For verification, password resets, parental approvals, necessary account and contract messages, invoices and replies, we process the recipient address, necessary message content, technical delivery data and relevant attachments. Depending on the purpose, the legal bases are Article 6(1)(b), (c) and (f) GDPR. Registration alone does not result in advertising emails. Service messages are sent through our mailbox services@mindoroevolution.com using authenticated, encrypted SMTP with united-domains GmbH, Gautinger Straße 10, 82319 Starnberg, Germany. A data processing agreement has been concluded for this service. See the provider's privacy information. Delivered messages can remain in recipients' mailboxes; account deletion cannot recall them. Please do not send particularly sensitive information in unencrypted email.
Messages previously sent or received through mindoro.evolution@gmail.com may remain in that mailbox for the applicable correspondence or statutory retention periods. Gmail is no longer the automatic sending route. The Google privacy policy applies to that legacy mailbox. The new mail service does not imply exclusively European processing by all other services used by Books.
8. Stripe payments, invoices and subscriptions
Paid purchases are processed through Stripe and are currently limited to the EU VAT territory. When you deliberately start checkout, we process and transmit your account ID, email, plan, invoice name and address, any company and tax information you provide, and necessary transaction data to Stripe. For international sales, billing location and configured tax registrations are used to determine the tax details. Payment instrument details are entered with Stripe; we do not receive full card details. We process payment, subscription and invoice IDs, status, amounts, tax details, billing periods and cancellation dates for contract performance and billing. Invoices and invoice corrections are provided as PDFs in your account and, with the electronic delivery agreed at checkout, by service email. PDFs are kept separately and privately with Google Cloud Storage in Frankfurt. The legal bases are Articles 6(1)(b) and (c) GDPR and, for fraud prevention and necessary records, Article 6(1)(f). Stripe Payments Europe Limited in Ireland is generally involved for European customers. Stripe acts as a controller or processor depending on purpose; see Stripe privacy and Stripe data processing terms. Additional optional features may require separate assessment.
9. Termination, withdrawal and records
When you use the online forms, we process the names, email addresses, contract references, declarations and receipt time you provide so that we can receive, acknowledge and implement the declaration. Login is not required. The legal bases are Article 6(1)(b) and (c) GDPR and, where necessary, Article 6(1)(f) for legal records. Providing any other person's email address does not by itself automatically change their account. We check the association and handle the declaration at the legally relevant time.
10. Recipients and transfers
Necessary recipients are the Google hosting, authentication and storage providers we use, united-domains for service emails and Google for any legacy Gmail correspondence, Stripe for payment processing, and bodies legally entitled to receive the data where applicable. Google describes processing for Firebase services in its Firebase Data Processing and Security Terms; services governed by the Google Cloud contract are covered by its Cloud Data Processing Addendum. These terms do not automatically cover a consumer Gmail account. The mail services are covered by the provider information linked in section 7; Stripe terms are linked in section 8. Providers may process data outside the EU/EEA, particularly in the USA. Google describes transfers to the appropriately certified Google LLC under the EU-US Data Privacy Framework and contractual safeguards in its Firebase privacy information. Other recipients and transfers are subject to the respective adequacy decisions or standard contractual clauses with necessary supplementary measures under the linked provider terms. Processing exclusively in Europe is not assured. You can request information and copies of the relevant safeguards from us.
Real invoices, invoice corrections and necessary accounting records are retained separately from the private book library, generally for eight years from the end of the calendar year of issue, subject to longer statutory or legal hold requirements. Account deletion removes private books and account access; it does not prematurely erase these legally required records. Test documents are marked as tests and scheduled for removal after 30 days or removed with the test account. For deleted export and billing files, Google Cloud Storage may retain separate recovery copies for up to seven additional days. These are no longer accessible through the account or its download links and are used only for recovery following data loss. Delivered emails and downloaded files cannot be recalled from recipients.
11. Retention and deletion
Local books and projects remain until you or your browser delete them. The offline copy can be removed in storage preferences without deliberately deleting your book databases. We process account data until account deletion unless statutory retention or necessary legal defence requires otherwise. You can trigger account deletion yourself in the account after confirming your password again, or request it by email. Contract records subject to statutory retention may be kept separately and only to the extent necessary. Parents can suspend and delete child accounts in their account.
Temporary parental approval requests, authentication email requests and associated rate limits are scheduled for TTL deletion after approximately one day; verification and reset jobs are no longer executed after one hour. After successful or skipped delivery, the recipient address is removed from the job. Necessary delivery markers, approvals and contract records are kept only as long as needed and are reviewed and deleted as circumstances require. Server logs follow the configured technical retention periods of the services used; no unverified uniform seven-day period is promised. Statutory tax retention periods apply to accounting records, particularly eight years for accounting vouchers, with different periods potentially applying to other documents. Records necessary for enforcing legal rights may be retained until the relevant periods expire.
12. Your rights
Subject to the respective legal conditions, you have rights of access (Article 15), rectification (16), erasure (17), restriction (18), data portability (20) and objection to processing based on legitimate interests (21 GDPR). You can withdraw consent at any time for the future; this does not affect the lawfulness of earlier processing. Contact: services@mindoroevolution.com. You can complain to a supervisory authority, particularly the North Rhine-Westphalia Commissioner for Data Protection and Freedom of Information, Kavalleriestraße 2–4, 40213 Düsseldorf, Germany, www.ldi.nrw.de. We do not use solely automated decision-making with legal or similarly significant effects, or our own advertising profiling. Necessary account data is required for an account; without it, the Reader remains available without login.
Project slots and plan limits
To enforce active project slots across devices, we store project identifiers, their active status and update times under your account. This does not upload local book contents. The basis is the requested account service under Article 6(1)(b) GDPR. Cloud content is uploaded only when you request cloud storage; paid export transmits the selected book version. Project-slot metadata is removed with account deletion. Local archive status is reconciled online; books already downloaded to other devices cannot be deleted remotely.
Support requests
You can send a question through the support window without an account. We process your reply email, optional name, category, subject, message, language and the application area. Browser family and major version, window size and connection status are included only if you select the optional technical-information field. We do not automatically attach book contents, files, passwords, API keys, complete addresses with URL parameters or error logs.
Requests sent while signed in are additionally associated with your account so that you can view your latest requests. Access to this history is restricted to that account. Child accounts are directed to contact through their parent or guardian, and cannot submit their own account-based requests. Your message is stored in Firebase/Firestore and forwarded through our service mailbox; replies arrive by email. This is not a live chat and does not create a public profile or subscribe you to advertising.
The bases are handling requested pre-contractual or contractual support under Article 6(1)(b) GDPR, or our legitimate interest in answering other inquiries and preventing abuse under Article 6(1)(f). No blanket privacy-consent checkbox is required. For abuse prevention, short-lived hashes of the network address and reply email, request counts and retry identifiers are kept for approximately one day. Form requests in Firebase are automatically scheduled for removal after 180 days; associated account records are removed on account deletion. Emails already delivered cannot be recalled, and mailbox correspondence or legally required evidence can be retained separately as described in the email and retention sections.