What we see. What we don't.

LumaDocs is built on a simple rule: your documents never leave your device unencrypted. This page explains, in plain English, exactly what data we (the operator of LumaDocs) and the third-party services we integrate with can and cannot see.

TL;DR

• Your documents are encrypted on your device using AES-256-GCM before they are stored locally or synced to your cloud. We never hold the decryption key.
• Guest mode sends nothing to any server. The entire vault lives in your browser's local storage.
• When you sign in with Google, we receive your email, name, profile photo, and a Google ID so we know which account you are. That's it.
• When you enable Drive sync, encrypted blobs are uploaded to your own Google Drive using a scoped token that only sees files this app created.
• We do not run analytics, ad tracking, or behavioural telemetry.

1. Who is responsible for this data

The operator of LumaDocs ("we", "us") is responsible for processing of personal data described here. For questions, corrections, or deletion requests, contact privacy@lumadocs.app.

2. What data we collect

2.1 Account identifiers (only if you sign in)

When you sign in with Google, we receive from Google:

• Your Google account ID (a stable numeric identifier)
• Your email address
• Your display name
• Your profile picture URL

We use these to authenticate you and to derive a session. We do not sell, share, or augment this data with third-party sources.

2.2 Your documents

Everything you add to LumaDocs — the files themselves, their names, categories, tags, expiry dates, and notes — is stored in your browser's local database (IndexedDB). Before anything is written to disk (locally or remotely), it is encrypted on your device with AES-256-GCM using a key that is derived from your account and never transmitted.

We cannot see your documents. Neither can Google, and neither can anyone who gains access to our server infrastructure, because we do not hold the decryption key.

2.3 Drive sync (optional, and off by default in guest mode)

If you enable Google Drive sync, encrypted blobs (not plaintext) are uploaded to a dedicated folder in your own Google Drive. We request the drive.file scope, which means our app can only see files it has created. We cannot read the rest of your Drive.

2.4 Minimal server-side state

LumaDocs does not keep a database of user records. Authentication tokens are stored in a signed browser cookie. If you enable experimental features (for example a future Telegram integration), we may need to store a small record linking your account to an external identifier; that will be disclosed here before launch.

2.5 Technical logs

Our hosting provider may keep short-lived access logs (request timestamps, IP addresses, response codes) for operational and abuse-prevention purposes. These logs are not used for profiling and are retained only as long as needed to debug or defend the service.

3. Cookies

LumaDocs uses a small, strictly necessary set of cookies:

• authjs.session-token — signed session cookie set by NextAuth when you sign in. Required for authentication.
• luma_guest — set when you choose "Continue as Guest" so the app knows to keep you local-only. Cleared when you sign out of guest mode.
• lang — remembers your language preference.

We do not set third-party advertising or analytics cookies.

4. Third parties we share data with

• Google — only if you sign in with Google (for authentication) and/or enable Drive sync (for encrypted backups). Google's privacy policy.
• Our hosting provider — receives standard HTTP request metadata while serving the app.

We do not sell personal data. We do not share data for advertising. We do not join the data we hold with data from other sources.

5. Your rights

Depending on where you live, you may have the right to:

• Access the personal data we hold about you — which in our case is limited to the account identifiers in §2.1.
• Export your vault. Settings → Export Vault produces an encrypted .lumavault archive you can keep or move elsewhere.
• Delete your account. You can sign out and revoke our access from your Google account settings, and clear local data from your browser. We will also delete any server-side record on request to privacy@lumadocs.app.
• Object or restrict processing — write to us and we will respond within a reasonable timeframe.

6. Data retention

• Documents you delete are moved to Trash and kept for 30 days before permanent purge.
• Account identifiers persist as long as you have an active session. On sign-out we keep the cookie-based session until it expires; the session is invalidated on the server immediately.
• Hosting access logs are rotated on a short schedule by our provider (typically 7–30 days).

7. Security

LumaDocs is designed so that a breach of our servers does not expose your documents. Every document is encrypted on your device with AES-256-GCM. The key is derived with PBKDF2-SHA-256 (210,000 iterations) from a per-account seed that never leaves your device in plaintext. Guest users get a randomly generated seed stored only in their browser's IndexedDB.

One important consequence: if you lose access to the account you used to sign in, you also lose access to the encrypted vault. Use the Export Vault option regularly if your documents are irreplaceable.

8. Children

LumaDocs is not directed to children under 13 (or under 16 where required by local law). We do not knowingly collect data from children.

9. International transfers

Because we rely on Google services and common hosting providers, your authentication data may be processed in the United States and other jurisdictions where those providers operate. Standard contractual clauses and equivalent safeguards apply where required.

10. Changes to this policy

If we change this policy in a way that materially affects what we collect or how we use it, we will update the "Last updated" date at the top of this page and announce the change in-app or by email to signed-in users before the change takes effect.

11. Contact

Privacy questions, complaints, or deletion requests: privacy@lumadocs.app.

← Back to home · Terms of Service