← Scriptum
Scriptum logoScriptum

Privacy Policy — Scriptum

Effective date: 2026-10-27 Last updated: 2026-11-14

This Privacy Policy explains what data the Scriptum app and its backend services (api-bible, api-bible-users; collectively the "Service") collect, why, and what rights you have. It is written to satisfy the GDPR (the operator is established in Poland) and Google Play's data-safety requirements.


1. Data controller

CODEZAUR Dominik Lipinski Contact: codezaur [at] gmail [dot] com

We are a small independent operation and are not required to appoint a Data Protection Officer; the contact above reaches the person responsible.

2. The short version

3. Data on your device

Preferences live locally (Android DataStore / app internal storage). One distinction matters:

Stored locally and echoed to the API as request parameters:

Never leaves your device at all:

Daily notifications are scheduled on-device (WorkManager); we do not operate a push-messaging service and never receive a device push token.

4. Data we process

4.1 Content-API use (anonymous and logged-in)

Requests to api-bible carry the parameters you chose (language, topics; API clients may also send an edition key). Anonymous use is authorized by a shared app token that identifies the app build, not you. When you are logged in, requests carry your account access token instead, so they are technically linkable to your account — we do not use this to profile your reading. Our infrastructure necessarily processes:

DataPurpose
IP addressserving responses; Cloudflare rate limiting and abuse protection
Request parameters (lang, topics, optional edition), timestampsserving content; aggregate reliability monitoring

We do not build per-device or per-account profiles from this data.

4.2 Account data (if you register)

DataSourcePurpose
Email addressyoulogin, account identification
Passwordyoustored only as a one-way cryptographic hash (argon2id) — never plaintext
Display nameyou (optional)profile display
Timezone; locale (optional)you / devicestreak day boundaries, localization
Google account sub and emailGoogle Sign-InOAuth login link (ID token verified against Google's keys; we never see your Google password)
Device label (e.g. "Pixel 8")your devicesession list / audit of refresh tokens
Refresh tokensissued by usstored only as SHA-256 hashes; rotate on every use

Profile photos are picked and stored on your device only — they are never uploaded to us. If you sign in with Google, the app may fetch your public Google profile image directly from Google to display it locally.

4.3 Activity and streaks

4.4 Purchases and entitlements (when shipped)

4.5 Paid-feature usage (semantic verse search — when shipped)

4.6 Analytics and attribution

While the Settings → Privacy → Analytics toggle is on (it is on by default), the app reports product events to Firebase Analytics and Meta AppEvents:

4.7 Technical logs

Standard web logs (nginx/Cloudflare: IP, path, status, timestamp) kept for security and debugging. Access and refresh tokens are never logged.

5. Legal bases (GDPR)

ProcessingBasis
Serving verses, corpus downloadsLegitimate interest (Art. 6(1)(f)) — running a public content API
Account creation, login, tokensContract (Art. 6(1)(b))
Streaks, activity daysContract (Art. 6(1)(b)) — the feature you enabled
Subscription verification, purchase audit (when shipped)Contract + legal obligation (Art. 6(1)(b), (c)) — consumer/accounting law
Security logs, rate limiting, abuse preventionLegitimate interest (Art. 6(1)(f))
Semantic-search queries to the embedding provider (when shipped)Contract (Art. 6(1)(b)) — the feature you invoked
Product analytics, crash reports, install attributionConsent (Art. 6(1)(a)) — withdrawable anytime via Settings → Privacy → Analytics

(b) = needed to provide the feature you asked for; (c) = the law requires it (consumer/accounting rules); (f) = our justified operational interest — you may object to (f) (see §9).

6. Who we share data with (processors)

Third partyRoleWhat they receive
Google (Sign-In, Play Billing; currently also the embedding API)auth, payments, search rankingGoogle ID tokens (verified server-side); purchase tokens; your search query text
Google Firebase (Analytics, Crashlytics)product analytics, crash reportingusage events listed in §4.6, app-instance identifier, crash diagnostics
Meta Platforms (AppEvents)install attribution, ad-campaign measurementthe app events listed in §4.6; advertising ID while the toggle is on
CloudflareCDN/WAF, TLS termination, rate limitingall public-API traffic metadata (IP, request line)
Hetznerhosting (VPS in the EU)the whole database and logs — as our hosting sub-processor

No data is sold, rented, or shared for advertising. There are no other recipients today; any future processor will be listed here before it receives data.

7. International transfers

Google, Cloudflare, and Meta process data globally, including in the United States, under their own data-processing terms incorporating EU Standard Contractual Clauses (or equivalent mechanisms under GDPR Art. 46). Hosting and our database remain in the EU.

8. Retention

DataRetention
Account record (email, name, tz, locale)until you delete the account
Refresh-token hasheseach token is valid max 30 days; rotated on every use, revoked on logout or password change; deleted with the account
Activity daysdeleted with the account
Entitlementsdeleted with the account — Google Play retains the underlying purchase record independently (when subscriptions ship)
Server logs (IP)~30 days
Deleted accountsthe account record is kept only in anonymized form (the email is rewritten to a generated placeholder); all data linked to it — OAuth identities, refresh tokens, activity days, entitlements — is deleted

Deleting the app without an account deletes all local data with it — there is nothing else to remove.

9. Your rights

As an EU/EEA user you may:

We make no automated decisions about you and do not build profiles (GDPR Art. 22).

To exercise any right, email codezaur [at] gmail [dot] com. We respond within one month.

10. Security measures

No system is perfectly secure; if a breach affects your data, we will notify you and the supervisory authority as required by GDPR Art. 33–34.

11. Children

Accounts require age 16+ (or your jurisdiction's digital-consent age). Anonymous reading features collect no personal data and may be used by younger users under parental supervision. We do not knowingly collect children's personal data; contact us to remove any such account.

12. Changes

We may update this policy; material changes are announced in-app before taking effect. The "last updated" date always reflects the current version. Continued use after the effective date means acceptance.

13. Contact

Privacy questions, data requests, complaints: