Privacy Policy

Effective Date: [EFFECTIVE_DATE] · Last Updated: [LAST_UPDATED_DATE] · Version: 1.3

DRAFT — LEGAL REVIEW REQUIRED. Bracketed values must be completed and this document reviewed by qualified counsel in each distribution territory before publication. The disclosures here must match the app's actual behaviour, the Apple App Privacy label, and the Google Play Data safety form at all times.

v1.3 changes (2026-11-13) — Google Analytics for Firebase is introduced to measure a fixed list of usage events (§1.3, §1.5). In the EEA, the United Kingdom and Switzerland it runs only if you consent; elsewhere it runs without a prompt. The "screen-reached and screen-exit events" row is removed from §1.3 because the app never sent them. Retention (§7), recipients (§5), transfers (§6), withdrawal (§8) and advertising (§10) are updated to match. When analytics is on, Crashlytics crash reports may also carry the names of app events (§1.3). 2026-11-13 correction: the Google Analytics contracting entity is Google LLC, Google Cloud Korea LLC is added as a recipient, and review notes are removed from this document.

v1.2 changes (2026-08-17) — Google contracting entities identified and Crashlytics retention set to 90 days.

v1.1 changes (2026-08-17) — Third-party SDKs confirmed: Google AdMob (advertising, non-personalized) and Google Firebase Crashlytics (crash reporting). §1.3 distinguishes data used by SDKs on your device from data our servers receive. §10 states non-personalized advertising as the default.

[COMPANY_LEGAL_NAME] ("Lectorium", "we") operates the Lectorium reading application. This Policy explains what personal data we collect, why, how long we keep it, and the choices you have.

We collect only what a feature actually needs. You can read public-domain books without an account at all.


1. Data We Collect

1.1 Data you provide

Data Purpose When collected
Account identifier, email address, or sign-in provider ID Account creation, purchase restoration, community operation When you create an account
Display name (nickname) and profile settings Community identity When you set them
Ratings, reviews, posts, comments Providing Readers' Circle When you submit them
Reports and block lists Safety and moderation When you report or block
Support correspondence Answering your enquiry When you contact us

1.2 Data generated by your use

Data Purpose Notes
Reading position, bookmarks, highlights, notes Restoring where you were; cloud sync Free tier: stored on your device. Subscribers: synced to our servers. Guests: memory only, erased on app close
Completion eligibility events Determining Readers' Circle access and achievements Minimal event data stored on our servers even for free-tier users
Reading statistics Your own statistics display Free tier local; subscribers synced
Achievement records Profile and badges Stored on our servers for account holders
Language and display settings Serving the correct UI and translation language ko, ja, zh_Hans, zh_Hant, en

We do not record your reading sessions. We do not store the time of day you read, how long each session lasted, or how many consecutive days you have read. Features that would have required this data were removed from the Service rather than collected for.

1.3 Data collected automatically

By our servers

Data Purpose
Device model, OS version, app version, language, region Compatibility, security
IP address and access timestamps Security, abuse prevention, fraud detection

By third-party SDKs on your device

Three Google SDKs operate inside the app. The data they process is described below and in §5. Where the data does not reach our servers, we say so.

SDK Data Reaches our servers?
Google Firebase Crashlytics Crash stack traces and exception details, app version, device model and OS version, device state at the time of the crash (memory, storage, orientation), and a Crashlytics installation identifier No. We read aggregated crash reports in the Firebase console. We do not attach your account ID to crash reports When analytics is on, Crashlytics may also attach the names and parameters of the app events listed in the Analytics row (a fixed list, no personal data) to crash reports
Google Analytics for Firebase An app-instance identifier; a fixed list of usage events (onboarding steps, sign-in method and outcome, a result-count range for searches, opening a preview or a book with its language only, opening a store or purchase screen and starting a purchase with the product type only, switching editions with the language pair, opening a notification with its type); automatic events such as first open, session start, engagement time and app update; device model, OS version, app version, language, and country- or region-level location derived from the IP address No. Events go to Google, not to our servers. We do not attach your account ID or email address, we do not send book or edition identifiers or search terms, and we do not collect the advertising identifier. In the EEA, the UK and Switzerland it runs only if you consent (§2) Where analytics is on, Crashlytics may attach the names of these app events to crash reports, and records an app_exception event in Analytics
Google AdMob An advertising identifier and standard ad-request signals, used to serve non-personalized advertisements to free-tier users (§10) No. Ad serving is handled entirely by Google. We do not receive or store advertising identifiers

We disclose these SDKs in the Apple App Privacy label and the Google Play Data safety form.

1.4 Purchase data

Purchase receipts and transaction identifiers are received from Apple or Google and verified on our servers, so that we can grant and restore Subscriptions, Coins, and Translation Licenses, and prevent fraudulent purchases.

We never receive or store your payment card number, bank details, or billing address. Those are handled entirely by Apple and Google.

1.5 What we do not collect

We do not request or collect your contacts, photo library, precise location, microphone, camera, health data, or biometric data. These are not required for any feature of the Service.

We use Google Analytics for Firebase only for a limited, fixed list of usage events (§1.3). We do not send your account ID, email address, the books you read, your search terms, or anything you write. We do not use this data for advertising, and we have turned off advertising personalization signals and advertising-identifier collection for it. Beyond this we use no third-party product-analytics or user-tracking SDK; our other operating metrics are calculated from our own database. Crashlytics is used for crash diagnostics only.


2. Legal Bases for Processing

Where the EU/UK GDPR applies, we rely on the following bases:

Processing Legal basis
Providing the Service and your account Performance of a contract (Art. 6(1)(b))
Purchases, entitlement verification, restoration Performance of a contract
Security, fraud prevention, abuse detection Legitimate interests (Art. 6(1)(f))
Crash diagnostics and service improvement Legitimate interests
Usage analytics (Google Analytics for Firebase) In the EEA, the UK and Switzerland: consent (Art. 6(1)(a)), requested on first launch and withdrawable in Settings. Elsewhere: legitimate interests, or the basis permitted by local law
Serving non-personalized advertising Consent where required by the ePrivacy Directive for storing or accessing information on your device (Art. 6(1)(a)); otherwise legitimate interests
Personalized advertising Consent (Art. 6(1)(a)) — not currently used (§10)
Marketing notifications Consent (Art. 6(1)(a))
Retaining transaction records Legal obligation (Art. 6(1)(c))

Where Korean law applies, we obtain the consents required by the Personal Information Protection Act and distinguish clearly between required and optional items. Declining an optional consent does not prevent you from using the core Service.


3. How We Use Data

We use personal data to operate the reading experience, deliver and restore purchases, generate and deliver Translation Editions, determine reading completion, run Readers' Circle safely, award achievements, respond to support requests, detect and prevent fraud and abuse, comply with legal obligations, and improve the Service.

We do not sell personal data. We do not use the content of your private notes or highlights to train machine-learning models.


4. AI Translation and Your Data

Translation Editions are generated from public-domain book text only. Your personal data, reading history, notes, and highlights are never sent to a translation model.

Translation processing is performed using [AI_PROVIDER_NAME] under a contract that prohibits use of the submitted text for model training. Because only public-domain literary text is submitted, no personal data is transferred for this purpose.


5. Sharing and Disclosure

We share personal data only with the following categories of recipient, and only to the extent needed:

Recipient Purpose Data Country
[CLOUD_PROVIDER] Hosting, storage, database Account, sync, community data [SERVER_REGION]
Apple Inc. / Google Payment processing and receipt verification Transaction identifiers, receipts United States and others
Google Asia Pacific Pte. Ltd.
8 Marina View, Asia Square Tower 1, #30-01, Singapore 018960
Crash reporting and diagnostics (Firebase Crashlytics) Crash reports, device and app state, Crashlytics installation identifier Singapore; processed globally, including the United States
Google Asia Pacific Pte. Ltd.
(address as above)
Serving non-personalized advertisements to free-tier users (AdMob) Advertising identifier and ad-request signals Singapore; processed globally, including the United States
Google LLC
1600 Amphitheatre Parkway, Mountain View, CA 94043, United States
Usage analytics (Google Analytics for Firebase) App-instance identifier, fixed-list usage events, automatic events, device and app information, country-level location; not linked to your account United States; processed globally
Google Cloud Korea LLC
20F Gangnam Finance Center, 152 Teheran-ro, Gangnam-gu, Seoul
Firebase backend services used by the app Data processed by the Firebase services described in §1.3 Republic of Korea; processed globally, including the United States
[AI_PROVIDER_NAME] Translation generation Public-domain book text only [AI_PROVIDER_REGION]
Legal and regulatory authorities Compliance with binding legal process As legally required —

Basis for the Google entities named above. The Firebase Crashlytics and App Distribution Terms of Service designate Google Asia Pacific Pte. Ltd. as the contracting entity where the customer's principal place of business is in the Asia Pacific region, which includes the Republic of Korea. For AdMob, Google Asia Pacific Pte. Ltd. is the contracting entity because the billing-address country of our account is the Republic of Korea. For Google Analytics, Google LLC is the contracting entity because the country registered on our Analytics account is the United States. Google Cloud Korea LLC is named because our Firebase project is on a paid (Blaze) plan.

Google's handling of data collected through Crashlytics, Google Analytics for Firebase and AdMob is governed by Google's own privacy policy, available at https://policies.google.com/privacy, and by the applicable Google data-processing terms.

An up-to-date list of sub-processors is maintained at [SUBPROCESSOR_URL].

We may also disclose data in connection with a merger, acquisition, or asset sale, subject to notice to you and continuity of protection.


6. International Transfers

Our servers are located in [SERVER_REGION]. Your data may be transferred to and processed in countries other than your own. Data processed by Google Firebase Crashlytics and Google AdMob is transferred to Google Asia Pacific Pte. Ltd. in Singapore, data processed by Google Analytics for Firebase is transferred to Google LLC in the United States, and such data may be processed on Google infrastructure in other countries, including the United States.


7. Retention

Data Retention
Account data Until you delete your account
Reading sync data (subscribers) Until deleted by you, or account deletion
Completion eligibility and achievements Until account deletion
Community content Until you delete it, or account deletion
Reports and enforcement records [ENFORCEMENT_RETENTION, e.g. 3 years] after resolution, for safety and appeal purposes
Transaction and settlement records 5 years where required by the Republic of Korea's Act on the Consumer Protection in Electronic Commerce; equivalent periods where other laws apply
Access and security logs [LOG_RETENTION, e.g. 3 months]
Crash diagnostics 90 days, under Google Firebase Crashlytics' retention schedule
Usage analytics 2 months for event-level data, under our Google Analytics data-retention setting
Advertising identifiers Not retained by us. Retention is governed by Google's policies and your device settings

After the retention period we delete or irreversibly anonymize the data.


8. Your Rights

Subject to your jurisdiction, you may:

Withdrawing analytics consent. Where the app asks for your consent (devices whose region setting is in the EEA, the UK or Switzerland), open Settings → Privacy & data and turn off "Send usage analytics". Events after that are no longer collected. If you declined, the switch stays off and remains available to you.

To exercise any right, contact [PRIVACY_EMAIL]. We respond within 30 days, or sooner where local law requires — including the 10-day period applicable to certain requests under Korean law.

We may ask you to verify your identity before acting on a request, in order to protect your account.

California residents additionally have the rights described in the CCPA/CPRA, including the right to know, delete, correct, and opt out of "sharing" for cross-context behavioural advertising. We do not sell personal information, and because we serve only non-personalized advertising we do not engage in "sharing" for cross-context behavioural advertising.


9. Children's Privacy

The Service is not directed to children under [MINIMUM_AGE]. We do not knowingly collect personal data from children below the applicable age of consent without verifiable parental consent.

If we learn that we have collected data from a child without the required consent, we delete it promptly. See our [Child Safety Standards](/en/child-safety-standards).


10. Advertising

Advertisements are shown to free-tier users and guests only. Subscribers see no advertisements. We do not place advertisements inside the reading screen.

We serve non-personalized advertising only. Non-personalized advertisements are based on general context — such as the app content and approximate coarse location — rather than on a profile of your past behaviour or interests. We do not build advertising profiles, and we do not combine your reading activity with advertising data.

Where your jurisdiction requires consent before information is stored on or accessed from your device for advertising, we request it through Google's User Messaging Platform before any advertisement is shown. You can decline, and you can withdraw consent at any time from the app's Settings. Declining does not restrict any reading, purchasing, or community feature.

We do not serve personalized advertising. Should we introduce it in the future, we will request the consent required in your jurisdiction — including App Tracking Transparency authorization on iOS and consent under the ePrivacy Directive and GDPR in the EEA/UK — and update this Policy with advance notice under §13 before doing so.

We do not serve personalized advertising to users we know to be minors.

Data collected by Google Analytics for Firebase is not used for advertising. We have turned off advertising personalization signals and advertising-identifier collection for it.


11. Security

No system is perfectly secure. If a breach occurs that is likely to affect your rights, we will notify you and the relevant authority within the period required by applicable law — including the 72-hour notification requirement under the GDPR and the notification duties under Korean and Japanese law.


12. Cookies and Similar Technologies

The mobile app does not use browser cookies. Advertising, analytics and crash-reporting SDKs may store identifiers on your device as described in §1.3 and §10. Our websites use only essential cookies required for operation and security. If we introduce analytics or advertising cookies on the web, we will request consent first where required.


13. Changes to This Policy

We may update this Policy. Material changes will be announced in the app or by email at least [NOTICE_PERIOD, e.g. 30] days before they take effect, and where the law requires your consent for a change, we will request it.


14. Contact

Purpose Contact
Privacy enquiries and rights requests [PRIVACY_EMAIL]
Data Protection Officer / Privacy Officer [PRIVACY_OFFICER_NAME], [PRIVACY_OFFICER_CONTACT]
EU representative (Art. 27), if applicable [EU_REPRESENTATIVE]
Postal address [COMPANY_ADDRESS]

Korean users may also contact the Personal Information Dispute Mediation Committee (kopico.go.kr, 1833-6972) or the Korea Internet & Security Agency Privacy Complaint Centre (privacy.kisa.or.kr, 118).