Privacy Policy
Effective date: 23 June 2026
The short version
Docrux is a mobile-first app for your documents, checklists, and essentials. Your files stay on your phone (and optionally in your own iCloud or Google Drive). We do not store, read, or host your documents on Docrux servers.
The docrux.app website provides the marketing landing page, legal policies, support contact, and the backend APIs that power optional mobile AI features. The public web document vault was retired in May 2026.
The mobile app requires no sign-in. We do not collect your name, email, or a hardware device identifier. Support uses an anonymous app-generated code only.
Who we are
Docrux is a document organisation tool operated as an independent project. If you have privacy questions, contact us at [email protected].
What we do not collect
- We do not store your documents or their contents on our servers
- We do not collect your name, email, or real device identifier from the mobile app
- We do not use advertising trackers or analytics cookies
- We do not sell or share your data with third parties for commercial purposes
- We do not build behavioural profiles
- We do not use your data to train AI or machine-learning models, and our AI provider (Google Gemini API) is contractually bound by the same restriction
Mobile app (iOS and Android)
The Docrux mobile app is designed as a local-firstapplication. Your document metadata and Essentials are encrypted on device. Document files are encrypted at rest on Android; on iOS they are protected by Apple’s sandbox (see On-device storage). No sign-in is required, and no files are uploaded to Docrux servers.
On-device storage
Android:documents and your Essentials metadata are stored in the app’s private sandbox. Document files and the encrypted index are encrypted at rest with AES-256-GCM. The encryption key is stored in the Android Keystore and never leaves your device.
iOS:document metadata and Essentials are encrypted with AES-256-GCM. Document files are stored in the app’s sandbox (and, when iCloud sync is on, in your personal iCloud Drive under “Docrux” so they appear in the Files app). iOS protects those files with its sandbox and Data Protection; Docrux does not double-encrypt individual document files on iOS.
Identity and support
We never collect your real device identifier, name, or email address. The app generates a random anonymous ID (a UUID) used only for aggregate analytics counts. Support requests use an app-generated code (e.g. DRX-a1b2c3d4) with no link to your real identity. These codes are random strings stored on your device. We cannot trace them back to you.
Camera and photo library
The app may request access to your camera or photo library to scan documents. Images are processed entirely on-device using Apple Vision (iOS) or ML Kit (Android). Image data is not transmitted to Docrux servers. Raw images are discarded once OCR extraction is complete; only the extracted text and the resulting document file are saved locally.
App lock and biometrics
Docrux can lock when you leave the app. Unlock uses Face ID, Touch ID, fingerprint, your device passcode, or an optional app PIN you set in Settings. The biometric check is performed by the operating system; Docrux never receives or stores biometric data.
Sensitive Essentials fields (passport numbers, licence details, etc.) stay masked until you unlock the app or tap to reveal a field temporarily.
Optional cloud sync
iOS: iCloud sync is opt-in (off by default). When enabled, your encrypted metadata and document files sync to your personal iCloud account (container iCloud.app.docrux.docrux). Documents appear in the Files app under iCloud Drive > Docrux. You can also place your own files in that folder; Docrux will not delete files it did not create.
Android:Google Drive sync is opt-in. Your encrypted metadata, Essentials, and document files are stored in a “Docrux” folder in your own Google Drive. The app works fully without Drive.
AI features (optional)
Several optional features use AI to improve accuracy: automatic document naming, essentials field extraction, and checklist matching. When you use these features, the app sends a portion of the OCR text already extracted on your device to the Docrux backend, which forwards it to Google Gemini. This processing is transient. Document text is processed in memory and immediately discarded. Nothing is logged or stored on our servers. No document files are ever sent. Only plain text.
AI features are opt-in and can be set to on-device only or fully manual in Settings. On-device AI (Apple Intelligence on supported devices) never sends data off your phone.
AI training: Docrux uses the Google Gemini API under terms that prohibit Google from using submitted content to train or improve its AI models. Your document text is not used to train any AI model.
Analytics and crash reporting
The app uses PostHog for anonymous usage analytics (screen views and feature usage counts, never names, emails, or document content) and Sentry for crash reporting (stack traces, device model, OS version). A PII scrubber strips document names, extracted text, notes, and file paths from all crash reports before they leave your device. Both services are fire-and-forget; no personally identifiable information is included in any event.
In-app purchases
Docrux offers optional Pro subscriptions (monthly and annual) via Apple’s App Store and Google Play. Purchase transactions are processed entirely by Apple or Google. We receive only an anonymous receipt to verify subscription status. We do not receive or store your payment method, billing address, or store account ID.
Deleting your mobile data
Uninstalling the app removes all local data. If iCloud sync was enabled, your files remain in your iCloud Drive until you delete them. If Drive sync was enabled, delete the “Docrux” folder from your Google Drive and revoke access in Google account permissions. No further action is needed.
Website (docrux.app)
The public website hosts our landing page, Privacy Policy, Terms of Service, and Support page. It does not store your documents. The browser-based document vault that previously used Google Drive was retired in May 2026; those routes now show a placeholder.
Mobile backend APIs
When you use optional AI features in the mobile app, extracted text is sent over HTTPS to our backend on Vercel, processed in memory, and discarded. These endpoints are HMAC-authenticated and rate-limited. No document files are accepted.
Founder admin dashboard
A private admin area uses Google Sign-In to authenticate the operator only. It shows aggregate install and usage counters, not user documents or profile data.
Server logs
Our hosting provider (Vercel) automatically records standard web server logs (IP address, request path, response code, timestamp) for a limited retention period. These logs are used only for debugging and security. We do not use them to build profiles or track behaviour.
Third-party services
Docrux relies on the following third-party services. Their own privacy policies govern how they handle data:
- Google OAuth & Google Drive API: authentication and file storage (web app and Android sync). Google Privacy Policy
- Apple iCloud: optional document sync for iOS users. Data is stored in your personal iCloud account. Apple Privacy Policy
- Google Gemini API:AI-powered features (auto-name, essentials field extraction, checklist matching). OCR text only is sent; no files. Processing is transient. Google’s API terms prohibit using submitted content to train models. Google Privacy Policy
- PostHog: anonymous usage analytics (event counts only, no PII). PostHog Privacy Policy
- Sentry: crash reporting (PII scrubbed before transmission). Sentry Privacy Policy
- Vercel: hosting and edge infrastructure. Vercel Privacy Policy
Cookies and session storage
The public website does not set advertising or tracking cookies. The founder admin area may use an encrypted HTTP-only session cookie for operator sign-in. The mobile app does not use cookies.
Security
All communication between your device and Docrux is encrypted via HTTPS. On Android, documents and their metadata are encrypted at rest with AES-256-GCM; the key stays in the Android Keystore. On iOS, document metadata is encrypted at rest; document files rely on Apple’s sandbox and Data Protection (and your device passcode/biometrics). Optional app lock (biometrics, device passcode, or app PIN) protects access when you return to the app. We apply Content Security Policy headers on the website.
Data retention and deletion
Because we do not store your personal data on our servers, there is nothing for us to delete on your behalf.
Mobile: Uninstalling the app removes all local data. If cloud sync was enabled, delete the synced data from your iCloud Drive or Google Drive as described above.
Web:The public document vault was retired. If you previously used Docrux in a browser, delete the “Docrux” folder from your Google Drive and revoke app access in your Google account permissions.
Children
Docrux is not directed at children under 13. We do not knowingly collect data from children.
Changes to this policy
If we make material changes we will update the effective date above. Continued use of Docrux after a change constitutes acceptance of the updated policy.
Contact
For any privacy-related questions, email us at [email protected].