Data and local storage
Privacy, made clear.
Updated October 28, 2026. This describes DataLux’s Android and desktop apps, website, browser app, and optional account service, operated by Josh Gessner / Anomalous Interactive.
Your files and camera
DataLux processes camera frames locally and transfers files through the optical patterns you choose to display. Files and camera frames are not uploaded to the account service. The browser keeps selected and received files in local browser storage; native apps read selected files and save received files on your device. DataLux does not provide a file-upload or cloud file-sync endpoint. Unencrypted optical patterns can be read by other cameras that see them; use the native app for encrypted pairing and teams.
The Android app asks for camera access to receive optical transfers. File access is used to select files to send and manage files you receive. Device checks run locally; any diagnostics export is started by you. Basic transfers work without an account or an internet connection. Optional account actions and Google Play purchases use network connections.
Optional accounts
Registration sends your name, email, and password to the DataLux account server over HTTPS. The server stores a password hash. The website uses a private session cookie; native apps keep an account session in private app storage. Android encrypts its cached account information with a device-keystore key. Desktop account files use private operating-system file permissions. Accounts are not required for local file transfers. Signing out ends the account session and leaves your local files in place.
Verification and recovery emails are sent through the account server’s configured email service. The service processes your email address and a temporary action link. These links are single-use and expire. Action tokens are stored as digests; pending email messages are encrypted in the private delivery queue and removed after delivery or expiry. Email links open a dedicated account page without traffic reporting. Verification and password reset require an explicit action; merely opening a link does not change your account.
The official DataLux account service uses Brevo for these transactional emails. Verification does not subscribe you to marketing. Requests are limited to help prevent duplicate emails and abuse.
Purchases and connected devices
If you purchase Android DataLux Pro, Google Play processes the payment. DataLux verifies the purchase with Google and stores the receipt token encrypted, plus its digest and entitlement status, to provide and restore Pro on the Android phones using your DataLux account. DataLux does not receive your payment-card details. Desktop includes all features free and does not require an account or activation. Optional PC account sign-in requires approval of the code shown by the PC app. Signed offline activations contain account and license identifiers, not transferred files.
First-party traffic reports
We operate our own traffic reporting. It counts public page views, browser-app opens, and clicks on recognized download links. It also groups external referring website names and campaign labels from marketing links. These reports use a 90-day retention window.
Traffic reports do not use analytics cookies or visitor IDs, and do not store IP addresses, complete referring URLs, query strings, file names, file contents, camera frames, or transfer history. The site respects your browser’s Do Not Track and Global Privacy Control preferences for page and click events. Ad blockers and offline use may also prevent these events.
The server keeps aggregate request/error counts and response-time buckets to monitor availability. Network addresses are used temporarily to limit abusive requests. Hosting and reverse-proxy logs have separate operator settings and may record network information.
Account administration
Authorized administrators can view account details, suspend or reactivate accounts, and end account sessions. Administrative actions record the operator, affected account, time, action, and reason in an operational audit history, normally retained for one year. Admin access requires a password and authenticator code. Account records and private backups are stored separately from files you transfer.
Delete your account
Use Delete account ↗ to sign in, confirm your password, and permanently delete your account and its linked records from the active account service. This ends connected account sessions and removes synchronized Android Pro access; desktop features remain free. Linked account identifiers, email addresses, and reasons in administrative audit records are scrubbed. Files already saved on your devices are not deleted.
Deleting a DataLux account does not cancel or refund a purchase through Google Play. Existing offline activation files may keep working without reconnecting; they cannot restore the deleted account. Private database backups are kept separately and expire under the server operator’s backup-retention policy. Deletion from the active service does not immediately erase old backups. Contact the operator if you need the backup-retention details for this deployment.
Support and privacy contact
For account help, privacy questions, or data requests, contact fileflowsupport@gmail.com. Include your account email if relevant. Never send your password, verification/reset links, activation file, or payment-card details. Support mail is processed through Gmail; sending a support request does not subscribe you to marketing.
Local storage and your choices
Use Local files in the browser app to delete individual files or the entire local library. Browser settings can clear all site data, including the cached offline interface. Export important files before clearing storage. Manage your account ↗ to verify your email, recover access, or delete the account. Avoid posting passwords, recovery links, or account records in public issues.