LifeLens Privacy Policy
Operator and scope
Axios Technologies provides LifeLens. This document covers the Android app only. It does not describe an iOS app.
The app behavior described below is based on the Android source review dated October 3, 2026. Account deletion is based on a subsequent confirmation from Axios Technologies. Backend operations and third-party provider practices have not been independently verified. This document remains an unapproved draft; no policy effective date has been established.
Account and capture information
LifeLens processes information to authenticate accounts and register devices. When a capture is submitted, the Android app sends extracted text and associated metadata to the LifeLens backend. This information is used to organize captured content into tasks, reminders, events, appointments, orders, and other actionable items.
Captured text can include personal or sensitive information from the content you select. The reviewed client does not redact that text before sending it to the backend. Avoid capturing information that you do not want sent for processing.
Screenshots and device backup
The reviewed Android capture pipeline extracts text on the device. Its capture API sends extracted text and metadata, not screenshot image bytes.
Android backup is enabled in the reviewed app configuration. The review did not establish which local files are included in backup or how backup copies are retained or deleted. Local text extraction therefore does not mean that every screenshot or local record stays exclusively on your phone.
Backend processing and AI providers
Submitted text is sent to the LifeLens backend for processing. The review did not establish which AI providers receive that text, the exact payloads they receive, or whether the backend redacts content before forwarding it.
Provider names, processing countries, sharing arrangements, training use, and provider retention periods are not yet verified. This document does not guarantee that submitted content is excluded from AI training or that providers immediately delete it.
Analytics and advertising identifiers
The Android app includes Firebase Analytics. The reviewed app manifest declares advertising identifier and ad-services permissions. No setting that disables analytics collection was found in the reviewed configuration.
These dependencies and permissions do not establish exactly what is collected during use. Runtime analytics events, identifiers, recipients, and retention were not measured. This document makes no claim that LifeLens operates without analytics or advertising identifiers, and it does not establish that LifeLens displays advertising or sells personal information.
Permissions and controls
Screen capture, notification access, floating overlays, and reminders use Android permission flows. Permissions authorize the corresponding device access; they do not establish how information is retained after submission to the backend. You can manage the permissions exposed by Android through your device settings. Removing a permission does not itself delete previously submitted information.
In the reviewed version, the AI setting saves a local preference but the capture pipeline does not read that preference or explicitly disable processing. Do not rely on that switch to stop backend or AI processing of submitted captures. No control for consenting to correction-sharing was found in the reviewed version.
Acceptance of privacy and terms documents
Before first access to Home, LifeLens requires you to check an acknowledgment box and choose Accept and Continue. Declining or leaving the screen does not record acceptance. If policy loading or saving acceptance fails, Home access remains blocked.
Acceptance is stored locally on the device as a version string. It is not account-specific, is not synchronized with the backend, and does not include a server-side acceptance timestamp. App restarts do not remove acceptance; clearing app data does. The reviewed version does not ask for acceptance again when the policy version changes.
The acceptance screen controls interactive access to Home, including capture entry flows. It does not block all processing before acceptance: authentication occurs earlier, and app startup can restore a session and schedule queued uploads.
Account deletion and retained copies
Axios Technologies has confirmed that you can open Profile and tap Delete account to delete your account and all account data. Follow the account deletion guide. This statement reflects the operator's confirmation, not an independent test of backend deletion.
The effect of account deletion on provider-held copies and backups, any legally required retention, and the time needed to complete deletion have not been verified. Do not interpret account deletion as a verified promise that every backup or third-party copy is removed immediately. Specific retention periods and deletion deadlines have not been established for this draft.
Security
The reviewed production API address uses HTTPS for transport. The review did not establish encryption of stored data, database isolation, backend logging practices, or third-party security measures. HTTPS alone is not evidence of those additional protections.
Contact and privacy requests
Contact Axios Technologies through our contact page for privacy questions, requests concerning your information, or help accessing account deletion. Submitting the contact form does not automatically delete your account; use the in-app deletion option for that action.
Disclosures required before approval
The following details must be verified and supplied before this draft can become an approved privacy policy:
- The specific account, device, capture metadata, and analytics fields collected.
- Backend and AI provider identities, recipients, processing locations, international transfers, and training practices.
- Retention periods for each data category and the treatment of backups, provider copies, and legal retention after deletion.
- Production security measures and the actual behavior of privacy controls.
- The legal operator's contact details, applicable lawful bases, privacy rights and request procedures, minimum age, and launch-market requirements.
These are missing disclosures, not assurances that the corresponding collection, sharing, or retention does not occur.