In short
EnigmaBox has no account, no login, and no content-storage backend of our own. It never automatically uploads your files, messages, passwords, or encryption keys — encrypted content leaves your device only when you explicitly export or share it. Two Google-provided components can still touch the network on their own terms: an off-by-default crash report (Firebase Crashlytics, which you control in Settings) and the QR code scanner used to add a trusted contact (Google Play Services, used only when you choose to scan a QR code — you can add a contact from a file instead). Neither is designed to see your file contents, messages, passwords, or encryption keys.
EnigmaBox is a local encryption tool for text and files. It has no user accounts, no sign-in, and no developer-operated backend for storing your encrypted content or keys. Encryption, decryption, and key storage all happen on your device, using your device's own storage and processing power.
EnigmaBox does not use advertising SDKs or analytics trackers, and we ourselves never collect or receive any of your content, files, or credentials — nothing about what you encrypt reaches us. Two Google-operated components are still part of the app and are covered in detail below: Firebase Crashlytics (off by default, and yours to enable) and Google's ML Kit QR code scanner (used only if you choose to add a trusted contact by scanning their QR code — importing a contact from a file doesn't use it). Both send data to Google over HTTPS, processed on Google's own global infrastructure.
EnigmaBox includes an optional crash-reporting feature, built on Firebase Crashlytics, that is off by default. You can turn it on or off at any time from Settings.
When enabled, a report may include:
The app is designed not to send file names, file paths, file contents, message contents, passwords, or encryption keys. Known, expected failures (wrong password, corrupted file, and similar) are handled entirely in the app's own interface and are never sent to Crashlytics — only genuinely unexpected errors are, and we can't fully rule out that an unexpected system-level error occasionally carries a file name or path as part of its own error text.
Crash reports and their associated identifiers are retained by Google for approximately 90 days. Turning crash reporting off in Settings stops future reports from being sent, but does not retroactively delete reports already submitted.
EnigmaBox uses Google Play Services' ML Kit code scanner to read QR codes when you add a trusted contact. QR scanning is user-initiated and happens only when you choose to scan a QR code — you can add a trusted contact from a file instead, which doesn't use this component. There's no Settings toggle for the scanner itself, but using it is your choice each time. The scanner module may be downloaded or updated by Google Play Services independently of EnigmaBox.
The QR image itself, and whatever it decodes to, are processed entirely on your device and are never sent to Google or to us. Using this component does, however, involve Google's own data collection, independent of EnigmaBox: device and app information, installation identifiers, performance metrics, and scan events, plus — because auto-zoom is enabled — a session identifier and the zoom and viewport adjustments made while scanning. This is documented directly by Google in its ML Kit data disclosure. We do not control or receive this data ourselves.
Your encryption spaces, trusted contacts, and cryptographic keys are stored locally on your device, protected by the Android Keystore and, where applicable, your own password. None of it is transmitted to us, and none of it leaves your device automatically — it moves only when you explicitly export or share it (see §07).
This data stays on your device for as long as you keep your profile. It is removed only when you wipe your local profile or uninstall the app — both of which delete it permanently and irrecoverably, with no copy kept anywhere by us.
If you create an encrypted backup, it is saved directly to your own device storage, or to a destination you choose yourself through the system file picker. EnigmaBox never uploads a backup anywhere on your behalf.
Trusted contacts and shared encryption spaces are exchanged directly between devices, through QR codes or files you choose to share, never through a server we operate. See §04 for what the QR scanning component itself sends to Google while it's active.
EnigmaBox requests only what it needs to function:
EnigmaBox is not directed at children and does not knowingly collect information from children.
This policy may be updated as the app evolves. We'll reflect any change on this page and update the date at the top. We encourage you to check back periodically.
If you're in the EU/EEA: our own legal basis for processing is limited to begin with, since we don't collect your content or credentials ourselves (see §02). Firebase Crashlytics runs only after you actively turn it on in Settings — that's your consent, and you can withdraw it at any time by turning it back off. The QR code scanner runs only when you actively choose to scan a code — that data collection is a direct, necessary consequence of using a feature you specifically invoked, not something done in the background.
Because EnigmaBox stores your data only on your own device, most rights you'd otherwise have to request from us (access, rectification, erasure, portability) are already in your hands: you can view, back up, or permanently delete your profile at any time from Settings, with no request to us required. You also have the right to lodge a complaint with your local data protection authority.
For Firebase Crashlytics, Google generally processes the submitted crash data on our behalf as a data processor — we remain the controller for that data. To exercise your rights regarding a crash report (access, deletion, objection), contact us at dataforgemobile@gmail.com. Because EnigmaBox has no accounts and crash reports use pseudonymous installation identifiers, we may need additional technical information and may not always be able to associate a report with a particular person.
Google Play Services and ML Kit separately process service and telemetry data as described in §04 and Google's Privacy Policy. We do not receive that data.
Questions about this policy can be sent to dataforgemobile@gmail.com.
This page is itself hosted on Firebase Hosting. Loading it causes Google to log your IP address, for standard web-server purposes like traffic monitoring and abuse prevention, retained by Google for a few months according to Firebase's current documentation — this is separate from anything the EnigmaBox app does.