ScriptumEffective 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.
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.
Preferences live locally (Android DataStore / app internal storage). One distinction matters:
Stored locally and echoed to the API as request parameters:
edition parameter.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.
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:
| Data | Purpose |
|---|---|
| IP address | serving responses; Cloudflare rate limiting and abuse protection |
| Request parameters (lang, topics, optional edition), timestamps | serving content; aggregate reliability monitoring |
We do not build per-device or per-account profiles from this data.
| Data | Source | Purpose |
|---|---|---|
| Email address | you | login, account identification |
| Password | you | stored only as a one-way cryptographic hash (argon2id) — never plaintext |
| Display name | you (optional) | profile display |
| Timezone; locale (optional) | you / device | streak day boundaries, localization |
Google account sub and email | Google Sign-In | OAuth login link (ID token verified against Google's keys; we never see your Google password) |
| Device label (e.g. "Pixel 8") | your device | session list / audit of refresh tokens |
| Refresh tokens | issued by us | stored 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.
activity_days: the calendar dates (in your timezone) on which the app reported an open — used solely to compute and display streaks.entitlements: your plan key, status, expiry, source (play_billing), and the Play purchase token — used to verify and honor your subscription via the Google Play Developer API.While the Settings → Privacy → Analytics toggle is on (it is on by default), the app reports product events to Firebase Analytics and Meta AppEvents:
install_attribution event carrying any utm_* parameters the Play Store recorded at install;utm_source/medium/campaign/content values are reported;Standard web logs (nginx/Cloudflare: IP, path, status, timestamp) kept for security and debugging. Access and refresh tokens are never logged.
| Processing | Basis |
|---|---|
| Serving verses, corpus downloads | Legitimate interest (Art. 6(1)(f)) — running a public content API |
| Account creation, login, tokens | Contract (Art. 6(1)(b)) |
| Streaks, activity days | Contract (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 prevention | Legitimate 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 attribution | Consent (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).
| Third party | Role | What they receive |
|---|---|---|
| Google (Sign-In, Play Billing; currently also the embedding API) | auth, payments, search ranking | Google ID tokens (verified server-side); purchase tokens; your search query text |
| Google Firebase (Analytics, Crashlytics) | product analytics, crash reporting | usage events listed in §4.6, app-instance identifier, crash diagnostics |
| Meta Platforms (AppEvents) | install attribution, ad-campaign measurement | the app events listed in §4.6; advertising ID while the toggle is on |
| Cloudflare | CDN/WAF, TLS termination, rate limiting | all public-API traffic metadata (IP, request line) |
| Hetzner | hosting (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.
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.
| Data | Retention |
|---|---|
| Account record (email, name, tz, locale) | until you delete the account |
| Refresh-token hashes | each token is valid max 30 days; rotated on every use, revoked on logout or password change; deleted with the account |
| Activity days | deleted with the account |
| Entitlements | deleted with the account — Google Play retains the underlying purchase record independently (when subscriptions ship) |
| Server logs (IP) | ~30 days |
| Deleted accounts | the 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.
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.
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.
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.
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.
Privacy questions, data requests, complaints: