Livia Privacy Policy
Last updated: October 14, 2026
Luxiphos develops Livia. This policy explains information used by our iOS and Android apps, the purposes of processing, and your controls. Features and permissions vary by platform and device. Contact admin@luxiphos.com with privacy questions or requests.
1. Account information and content you provide
We process your account identifier, sign-in information provided through your authentication method, and profile details you enter. These can include your name, email, birthday or age, gender, country, preferences, relationships, and information about yourself. We use them to operate your account and personalize Livia.
Conversations, journals, diary entries, moods, check-ins, routines, notes, and other content you save are processed by our service to provide those features, maintain your history, and generate relevant responses. Content you send to an AI feature is processed by our backend and the AI or voice providers supporting that feature.
2. Audio, photos, calls, and screen sharing
- Voice notes use the microphone when you choose to record. The recording is uploaded for transcription. The app removes its temporary voice-note file after the transcription attempt or when you cancel; the returned transcript can become conversation text.
- Photos you choose to save to Livia or send in a conversation are uploaded for the album, conversation, or AI image feature. A photo can contain people, surroundings, and other information visible in its pixels.
- Calls send microphone audio through our call infrastructure. Enabling call vision can send camera frames to the service for AI responses. If you enable screen sharing, the shared screen content is transmitted for that session after the system consent prompt. You can stop these features through their controls.
Temporary-file removal on your phone does not establish a single retention policy for server transcripts, conversation history, or provider records. See the retention and deletion sections below.
3. Optional location and maps
Location sharing is optional and off by default. When enabled, it can provide context for replies and arrival notifications. The app can resolve coordinates into place names, retain local visit history, and send arrival place/type information to our service. Coordinates can also accompany photos you choose to share with location and routes recorded during an outdoor walk. Walk and camera features may request their own relevant permissions.
Maps can request tiles directly from CARTO. The tile coordinates describe the area being viewed, and the provider receives network metadata such as your IP address. Android map requests also include the app package and signing-certificate identifiers for API access restrictions. These identify the app, rather than your account.
4. Activity, sleep, and health permissions
With your authorization, supported iOS features use Apple Health and Android features use Health Connect to read activity or sleep information and save supported session records. Android requests access to steps, distance, and sleep, and permission to write sleep sessions. You can manage this access in Apple Health, Health Connect, and your device settings.
An outdoor-walk session can upload its step total, route, duration, moods, and notes to your account. Health Connect sleep-history reads used by the Android history screen are processed on your device for the chart. Dream Guardian separately sends its own session times, duration, movement count, phone-unlock count, and notes to our service. These session features are distinct from uploading your entire health history.
5. On-device camera effects and device authentication
Supported iOS AR Selfie effects use Apple ARKit face tracking to position Livia and react to expressions. Supported Android camera effects use local processing, including MediaPipe hand tracking, to position the character. Tracking geometry for these effects is processed on the device; it is separate from an ordinary photo or camera frame you choose to upload or use in call vision.
A composed photo can show your face or hand even though it does not contain the tracking model. System biometric app-lock features use your device authentication system; they do not give Livia your fingerprint or Face ID template.
6. Service providers, analytics, and attribution
Providers process information needed for their part of the service. Our integrations include Supabase for authentication and storage, LiveKit for call infrastructure, Google Firebase Cloud Messaging for Android push notifications, and RevenueCat and the mobile stores for purchase and entitlement handling. Push processing uses a device registration token and notification payloads. Purchases involve product, transaction, and subscription-status information; the mobile store handles its checkout.
We use Mixpanel for product-usage analytics and AppsFlyer for installation and paid-ad attribution. Analytics and attribution can process interaction events, app/device identifiers, and account identifiers. Attribution can also receive registration and purchase events, such as product, revenue, and currency. Advertising identifiers depend on your platform, device settings, and available SDK configuration. Review your device advertising/privacy controls and contact us with questions about these uses.
Hosting, AI, transcription, and voice providers also process the content and operational information required by the features you use, under the terms and settings applicable to each service. Contact us with questions about provider processing or retention. Security and operational records can include error information, timestamps, and account references.
7. Security and your controls
We use authenticated service access and encrypted transport such as HTTPS/TLS. Livia does not offer end-to-end encryption that hides conversation content from our service and its AI processing providers: those services process the content to provide responses.
You can revoke microphone, camera, location, notification, and health permissions in the relevant app or device settings. Some optional features will then be unavailable. Permission changes control future device access; use a deletion request to address content already stored with your account. Copies you exported to your photo library, device backups, or other apps are controlled through those systems.
8. Retention, account deletion, and requests
We keep account content to provide your account and saved features. Account deletion removes your active profile and associated conversations, diaries, journals, moods, check-ins, routines, and related account content through our deletion process, including cleanup of associated uploaded chat photos and relationship avatars.
Some records are retained separately, including store transaction identifiers used for refunds and preventing duplicate purchase credits, and deletion-request and necessary security records. These can still include an account reference. Store/provider records and any applicable backup or legal obligations have their own requirements. Retention differs by record type and purpose. Contact us for the scope and status of your request.
See Delete your Livia account for the in-app steps and a public email request option, including when you cannot use the app. You can also contact admin@luxiphos.com to request access, correction, or deletion of your account data. We verify account ownership before acting on a request.
We may update this policy as the service changes. The date above identifies this version.