LifeBeacon Privacy Policy

1. Scope and privacy summary

LifeBeacon is a voice-first productivity application provided by Lunamous Tech, LLC ("Lunamous," "we," "us," or "our"). This Privacy Policy explains how we access, collect, use, disclose, retain, and delete information when you use the LifeBeacon mobile application, website, support services, and related features (collectively, the "Service").

LifeBeacon is designed to organize information for you, not to monetize it. We do not sell personal information, share personal information for cross-context behavioral advertising, use imported contacts or calendar data for marketing, or create advertising profiles from your activity.

This policy is a notice of our practices. Where a permission or affirmative choice is required, LifeBeacon requests it separately in the app. Contacts, Calendar, Location, Microphone, notifications, and AI/voice processing are optional features unless a particular function requires them.

2. Information we access or collect

2.1 Account and subscription information

When you create or use an account, we process your email address, account/user identifier, authentication status, and subscription entitlement. Supabase handles authentication. Lunamous does not receive or store your plaintext password. Apple, Google, and RevenueCat process payment and subscription information; Lunamous does not receive your complete payment-card information.

2.2 Profile and user content

We process information you choose to enter or save, such as your preferred name, nickname, home city or address, saved places, preferences, settings, Actions, Goals, milestones, notes, decisions, research items, checklists, brain dumps, reminders, calendar links, and related organization data. Account content is stored so it can be displayed and synchronized across your devices.

Free-form fields can contain information about you or others. LifeBeacon does not request structured medical records, government identification numbers, Social Security numbers, bank account numbers, or biometric identifiers, but users control what they place in free-form content.

2.3 Selected contacts

If you grant Contacts permission, LifeBeacon reads your device address book only after you choose to allow access and only to present contacts for selection. Only contacts you affirmatively select are copied into LifeBeacon and uploaded to Supabase for account synchronization. Unselected address-book records are not uploaded.

For a selected contact, the cloud record may contain the displayed name, given name, family name, nickname, company, phone numbers and phone labels, and the Personal or Business classification you choose. LifeBeacon does not upload the native device contact ID, locally derived contact key, normalized phone values, local import timestamps, contact email address, contact postal address, or other undisclosed address-book fields.

If you classify a contact as Business, LifeBeacon does not automatically perform a Places search. If you choose to search Google Places and confirm a result, the contact may also store the provider, confirmation time, Google place ID, business name, address, business phone, website, business email when returned, Google Maps link, coordinates, business status, and retrieval time. These are confirmed business/place details, not fields copied from the device contact record. Saved details may be reused for later matching Actions so the app does not need to repeat the same Places lookup unnecessarily.

Selected contacts are used only to provide contact matching, call or text actions, classification, reminders, calendar and assistant features, account synchronization, and confirmed Places reuse requested by you. We do not use imported contacts for advertising, create a general contact database, or contact imported people on our own initiative.

Revoking Contacts permission stops future device-address-book access but does not delete copies already imported to your account. You may delete an individual imported contact or all imported contacts in LifeBeacon without changing the contacts stored on your phone.

2.4 Calendar information

If you grant Calendar permission, LifeBeacon may read and display device-calendar events and may create, update, or delete calendar entries when you direct it to do so. Calendar access is optional and can be revoked in device settings.

LifeBeacon does not upload your complete device-calendar database. Specific calendar details may be transmitted when you ask LifeBeacon to interpret them, save or synchronize an item, or perform another calendar action you request. Revoking Calendar permission does not remove events already written to your device calendar or delete calendar details already saved as LifeBeacon account content.

2.5 Location and Places searches

If you grant Location permission, LifeBeacon may use precise or approximate device location to provide nearby Places results, distance calculations, and navigation-related features. You may enter an address manually where supported. LifeBeacon does not continuously track your location in the background or create a location-history profile.

For a Places search, the search terms and location used for the query are sent to Google Places through the authenticated LifeBeacon service. Google may also receive routine network and request metadata. A location becomes stored account content only when you save it as a home address, saved place, confirmed business contact, Action, Goal, note, or other LifeBeacon content.

2.6 Voice, microphone, and AI interactions

LifeBeacon currently uses tap-to-talk. It does not continuously listen for an activation phrase or run an ambient Athena wake listener. Recording begins only after you explicitly tap the microphone, and the app displays a listening indicator while capture is active. You may tap again to stop. Saying 'Athena' at the start of a request is optional; after transcription, a leading Athena phrase is removed before command interpretation.

After you begin a voice request, the audio you provide is sent through the LifeBeacon backend to OpenAI for speech-to-text processing. Typed text, transcriptions, and only the relevant request context may also be sent to OpenAI to interpret a command or generate a response. Relevant context may include a selected contact, calendar item, saved place, confirmed business detail, or location when your request requires it.

Before the first AI or voice transmission, LifeBeacon presents a versioned disclosure with Not now and Continue choices. Acceptance is stored with the signed-in account. You may withdraw that acceptance in Settings, which blocks future AI and voice requests while leaving non-AI app functions available.

The temporary local recording file is stored in the application cache during processing and is deleted through the app's cleanup paths after processing, cancellation, interruption, a short or empty capture, or a handled error. Lunamous does not use recordings to identify you, create a voiceprint, build an advertising profile, or train a LifeBeacon voice model.

LifeBeacon configures OpenAI Responses requests with store set to false and does not intentionally save OpenAI response IDs or create server-side OpenAI conversation state. OpenAI states that API data is not used to train its models by default unless the customer opts in. OpenAI's actual processing, abuse-monitoring retention, and training/data-sharing treatment are governed by its API data controls and the applicable account settings, which can differ by endpoint and configuration. We therefore do not promise one fixed OpenAI retention period in this policy.

2.7 Device, diagnostics, security, and support information

The Service and its providers generate limited technical information needed to authenticate requests, prevent abuse, troubleshoot failures, provide subscriptions, deliver media, and respond to support requests. This may include app version, operating system, device type, account identifier, IP address, request timestamp, route, status/result code, duration, security event, subscription state, and support communication.

Protected LifeBeacon backend routes are designed not to intentionally place prompts, transcripts, goal titles, selected contacts, locations, audio filenames, or user IDs in application log messages. Provider infrastructure may still create routine network, security, billing, and platform logs under its own configuration. The current LifeBeacon mobile app does not intentionally include app-level advertising, cross-app tracking, analytics, or crash-reporting SDKs.

3. How we use information

• Provide, personalize, synchronize, and support LifeBeacon features.
• Authenticate accounts and maintain subscription entitlements.
• Import and synchronize only the contacts a user selects.
• Match contacts to requested call, text, Action, calendar, and assistant functions.
• Process voice, text, calendar, location, Places, and AI requests initiated by the user.
• Create, update, display, synchronize, or delete content as directed by the user.
• Maintain security, apply rate and size limits, prevent fraud and abuse, and troubleshoot failures.
• Respond to support and privacy requests, comply with law, and enforce our agreements.

4. When we disclose information

We disclose information only as needed to operate the Service, when you direct a feature to interact with a device or third-party service, to comply with law or protect rights and safety, or as part of a business transaction subject to applicable notice and safeguards.

We do not sell personal information, share it for cross-context behavioral advertising, or use imported contacts, calendar data, voice audio, Actions, Goals, notes, or Places searches for marketing. The LifeBeacon mobile app does not use advertising SDKs or the Apple advertising identifier for targeted advertising.

5. Service providers

LifeBeacon uses the following principal providers. The information sent depends on the feature you choose and the request you make. Providers process information under their own terms, privacy notices, contracts where applicable, and our technical configurations.

We may replace or add a provider as the Service evolves. We will update this policy when a change materially affects how personal information is processed.

6. Permissions and your choices

• Contacts: Decline access, choose contacts individually, revoke future access in device settings, and delete imported copies in LifeBeacon. Revocation alone does not delete previously imported copies.
• Calendar: Decline or revoke access in device settings. Revocation stops future access but does not remove calendar events already created or LifeBeacon content already saved.
• Location: Decline or revoke access and use manual address entry where available. LifeBeacon does not require background location.
• Microphone and voice: Decline microphone access or use typing. No recording starts until you tap the microphone.
• AI and voice processing: Select Not now before the first transmission or withdraw acceptance later in Settings. Non-AI functions remain available.
• Notifications: Disable notifications in device settings without deleting the underlying reminders or calendar items.
• Account content: Edit or delete imported contacts, Actions, Goals, notes, reminders, saved places, and other account content inside LifeBeacon.

7. Retention and deletion

We keep account information and synchronized user content while your account is active or until you delete the content or account, subject to technical, security, legal, accounting, fraud-prevention, dispute-resolution, and provider limitations described below.

Temporary local voice recordings are deleted through the app's recording-cleanup paths. Short-lived in-memory service caches expire under configured limits and disappear when the backend process restarts. OpenAI and other providers may retain limited request or abuse-monitoring data according to the endpoint, provider configuration, and applicable law.

When account deletion succeeds, LifeBeacon revokes active sessions, deletes the Supabase authentication user, and removes active user-scoped LifeBeacon database content through the account-deletion process and database relationships. The device completing the deletion clears LifeBeacon local application storage. The backend also attempts to delete the associated RevenueCat customer record. Apple and Google subscription and transaction records remain controlled by those platforms.

LifeBeacon maintains a limited non-content deletion receipt containing a keyed subject hash, status, processor result codes, and timestamps. It does not contain the user's Actions, Goals, contacts, prompts, transcripts, notes, or other user content. Completed receipts currently have a configurable default retention of 365 days.

Operational logs, platform security records, provider records, and backup or disaster-recovery copies may not be removable immediately and follow the applicable provider configuration and operational lifecycle. We do not state one universal fixed retention period because the period can differ by service and configuration. Residual copies are not restored to active product use except where needed for legitimate recovery, security, legal, or compliance purposes.

8. Account deletion and privacy requests

You may initiate account deletion from LifeBeacon Settings. LifeBeacon also provides a public account-deletion web flow that uses the same authenticated deletion backend. The deletion process requires identity verification, a recent sign-in, and exact confirmation before the account is permanently deleted.

Deleting a LifeBeacon account or uninstalling the app does not cancel an Apple App Store or Google Play subscription. Cancel the subscription separately through the applicable store. Account deletion also does not delete records controlled independently by Apple, Google, or another provider.

You may contact [email protected] for access, correction, export, or deletion assistance. Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of personal information, object to or restrict certain processing, or withdraw consent. We may verify your identity before completing a request.

9. Security

We use administrative, technical, and organizational safeguards designed to protect information, including encrypted network communications, authenticated requests, user-scoped database access controls, request limits, service-provider controls, and modern cloud infrastructure. No transmission or storage system can be guaranteed completely secure.

10. Children

LifeBeacon is not directed to children under 13, and we do not knowingly collect personal information directly from a child under 13. If you believe a child under 13 has provided personal information, contact us so we can investigate and delete it. Users who are at least 13 but below the age of legal majority must have permission from a parent or legal guardian as described in the Terms of Use.

A contact selected by an adult user may describe another person, including a minor. We process that contact only as account content directed by the user and do not use it to contact, profile, or advertise to that person.

11. International processing

Lunamous is based in the United States. Information may be processed in the United States and other countries where service providers operate. Those countries may have different privacy laws. Where required, we use appropriate contractual or other safeguards for international transfers.

12. Changes to this policy

We may update this policy as LifeBeacon changes. We will post the revised policy, update the Effective Date, and provide additional notice when required for a material change. If a change requires a new affirmative choice or consent, LifeBeacon will request it rather than treating continued use alone as consent.

13. Contact

Privacy inquiries and requests may be sent to:

Lunamous Tech, LLC

Email: [email protected]

Website: https://life-beacon.com