1. Who controls your information

Liforiah is operated by the person identified above ("we," "our," or "us"). We are responsible for the personal information we control when providing the service. Other providers, including Google and Supabase, are separately responsible for their own services under applicable contracts and policies.

Contact us at the privacy address above if you have a privacy question, a data request, or a concern about a child using Liforiah.

2. Information that may be processed

The information involved depends on the features and choices you use:

  • Account and profile: Email address, account identifier, sign-in status and an optional display name that you choose. If you sign in with Google or Apple, that provider supplies the limited identity data you authorize, such as your name and email address. Liforiah does not store a profile picture.
  • Content you save: Photos, screenshots, documents, receipt information, notes, extracted text from documents, titles, places, links, purchase details, warranties, subscription information, reminders and relationships between saved records.
  • LifeTogether: Space or album names, invitations (including the invited email address), member identities and roles, contribution and activity metadata, and content that a member deliberately shares with authorized participants.
  • Drive backup and recovery: The Google account selected for Drive, files created or expressly authorized for Liforiah, file identifiers and backup manifests, upload and integrity status, and information required to reconnect, restore or delete backups.
  • Liora and voice: Typed commands, voice transcripts, conversation history, action confirmations and supporting context required to fulfill an instruction. The microphone, speech recognition, background wake phrase and notifications require device permissions or settings. Audio may be processed by local components or the phone's speech recognition provider according to the chosen mode and device configuration.
  • Technical and security information: Session and security events, synchronization errors, integrity/attestation outcomes, update compatibility and limited operational diagnostics. Some data may be processed by the hosting or authentication provider to keep the service working and secure.
  • Support inquiries: Messages and information voluntarily sent when requesting help.
  • Age and guardian information: If an age-appropriate account or parental-consent flow is enabled, the minimum information needed to determine appropriate access, contact or verify a parent/guardian, record consent, and manage requests. We should not collect more than needed for these purposes.

Liforiah is not designed to collect advertising profiles or sell personal memories. The app and the public website do not use advertising or behavioral-analytics trackers, and the website loads no third-party scripts or fonts. If this changes, this policy and any necessary consents must be updated before the change.

3. Where information is stored

  • On your device: Personal memories and selected media remain in local application storage for offline access. This data may be lost if you uninstall the app, clear its data, lose the phone or experience device failure. Your sign-in session is kept on the device in encrypted form. Reminders are delivered by your phone's notification system and are not sent through a server.
  • Supabase or a trusted backend: When account or LifeTogether features are enabled, authentication and selected structured information, such as user profiles, public encryption keys, wrapped key bundles, memberships, invitations and encrypted shared descriptions, may be held by these services. This is distinct from storing the full media library.
  • Your Google Drive: When you separately connect Drive and approve backup or sharing, selected encrypted backup and media files may be uploaded to the Google account you chose. Liforiah does not store users' photos in Supabase Storage. Files use that Google account's storage allowance and can be affected by its quota, deletion, suspension or access restrictions.
  • Other members' devices: People you choose to share with may retain downloaded, cached or exported copies of permitted shared content. Removal from a shared space cannot recall copies already kept by someone else.

4. Why we process information

We use information as necessary to provide requested features, including creating and securing accounts; locally organizing and finding information; searching or retrieving saved content; displaying reminders; processing optional backup/restore operations; managing membership and shared files; responding to requests; preventing unauthorized access; resolving technical errors; and complying with legal obligations.

Where processing requires consent, we ask before enabling optional cloud AI, Google Drive access, microphone use, notifications or sharing. Other processing may be necessary to provide the service requested or be otherwise authorized by applicable privacy law. We do not treat consent as the only possible legal basis in every jurisdiction. Consent can be withdrawn through the relevant settings or by contacting us, but this may affect functionality and does not make previously lawful processing retroactively unlawful.

We do not use Google API user data for targeted advertising, sale to data brokers, credit eligibility decisions, or training generalized AI models.

5. Google Sign-In is separate from Google Drive

Google Sign-In: If offered and selected, Google helps authenticate your account and supplies the limited profile data authorized in that sign-in process.

Connect Google Drive: This is a separate, optional step. You can use a different Google account for Drive than for your Liforiah login. Liforiah requests the limited https://www.googleapis.com/auth/drive.file scope to access files Liforiah creates or that you explicitly authorize. It does not request permission to browse your entire Google Drive merely to make a backup.

With that authorization, Liforiah may create or update its backup files (in a folder named "Liforiah Backup"), read relevant app-authorized content and metadata, download backups you choose to restore, and remove app-created backup files when you expressly request deletion. Where enabled, content you contribute to LifeTogether is stored as encrypted files in a folder named "Liforiah Shared" in your Drive and made available to authorized members using approved sharing and encryption controls. Liforiah does not keep a Google refresh token on its servers or on your phone.

Liforiah will request Google permissions in context and use them only for the disclosed user-facing purposes. Use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including applicable Limited Use requirements. Transfers are limited to uses needed to provide requested features with appropriate authorization, security purposes, compliance with law, or other transfers that policy permits. Human review of Google API user data is not allowed except in policy-permitted circumstances, such as with specific user permission, security investigation, or legal requirement.

You can disconnect Google Drive in Liforiah or revoke authorization in your Google Account. Disconnecting or revoking access stops future authorized Drive operations; it does not necessarily delete files already in your Drive, copies you shared, or separate Liforiah account records. Manage each copy separately using available deletion tools, including the "Delete my backups" action in Backup & Sync.

6. Encryption, backup and restoration

Liforiah's backup design encrypts selected data on your phone before uploading it to Google Drive and uses integrity checks to detect corruption. Encryption, key handling and a complete device-loss restore have been tested only with test accounts and simulated storage, not yet with live production services; do not rely on a feature as a successful backup unless the app reports that upload and verification completed.

When you set up backup, Liforiah shows you a recovery key once. Recovering an encrypted backup may require access to the original Google Drive, available backup files and that recovery key. A copy of your encryption keys, wrapped by the recovery key, is stored with your backups and in your account; it cannot be opened without the recovery key. If all copies of the key are lost, the data may be unrecoverable, including by the operator. Backups can fail because of network disruption, storage limits, permissions, lost accounts, removed files or software defects. The app reports its actual backup state rather than implying files are safe before verification.

7. LifeTogether: shared spaces and photos

If LifeTogether is enabled, members you authorize may see the information you share with a private space, including associated album names, content, contribution timestamps and relevant member identities. Titles, notes, places, links and captions are encrypted on your phone with a key shared among the space's members. Shared photo and document contributions are held in the contributing member's connected Drive, subject to that member's storage and access controls.

Sharing makes content available to the people you invite, not to the public by default. Those people may be able to retain copies. Changes to membership or encryption keys may limit subsequent access but cannot force deletion of already downloaded copies. A shared file can become unavailable if the contributor removes the only accessible copy or loses Drive access. Do not upload images or documents of other people unless you have a lawful basis and appropriate permission, especially where children are involved.

8. Liora AI, model downloads and voice features

Liora uses deterministic local capabilities and, where compatible and enabled, on-device AI such as Google's Gemini Nano, Apple's on-device model, or a small open model that you choose to download (from Hugging Face). Local processing is intended to reduce how often information leaves your device. Some speech-to-text services provided by the phone may process speech online depending on device configuration; check the relevant platform controls.

Optional cloud AI is off until you turn it on after reading a disclosure. When it is on and a request needs more reasoning, Liforiah sends your question and a few short excerpts from the memories it found for that question (titles, notes, amounts, dates and text read from files) to Liforiah's server, which asks Google's Gemini model and returns the answer. Liforiah never sends your photos, screenshots or documents themselves, and never your whole library. Liforiah's server does not keep your questions. To protect the service from abuse, the app proves to the server that it is a genuine installation of Liforiah (Google Play Integrity). Do not assume every request stays on-device if cloud processing or online speech recognition is selected. We do not use Google Drive information to train generalized AI models.

Background wake-word listening and microphone access depend on your affirmative settings and the phone's system permissions. When the wake phrase is turned on, an on-device model listens for it; audio is not saved or sent unless you then give Liora a request. Liforiah is not intended to record or share background conversations for advertising.

9. Children, teenagers and families: all ages

Liforiah is intended to be useful for families and people of all ages. This does not mean every age group can independently create an online account or use every sharing feature without safeguards.

Parents and guardians may use Liforiah to organize lawful family information and preserve family photographs. Minors should receive an age-appropriate experience. Where a child cannot legally consent to online processing, an authorized parent or guardian must provide the legally required permission and supervision before the child receives an online account or accesses cloud sharing. Requirements depend on location and age.

For children under 13 in the United States, covered online collection of personal information generally requires parental notice and verifiable parental consent under COPPA unless a recognized exception applies. Other countries may impose different ages and protections. A checkbox or statement that someone is a parent is not necessarily enough to verify consent. Parents should be able to understand the collection, review or request deletion of their child's information, and withdraw permission when required by law.

Current implementation status: Liforiah's age screen, verification of parental consent, parent-managed child accounts and guardian controls are not yet implemented. Liforiah is a personal project in development and testing and is not offered to the public. Public child accounts are not currently offered, and online accounts, Google Drive backup and LifeTogether sharing are not yet released. Before any of these is offered to the public, Liforiah will add the age and parental-consent safeguards that the law requires, and until they are in place it will not offer independent online accounts, Google Drive authorization or LifeTogether sharing to children who require parental consent. Optional cloud AI is off by default and should be enabled only by an adult or with a parent's permission. A parent may use their own account to manage family memories in accordance with law and service settings. Do not ask a child to falsely state their age or use an adult account without the adult's supervision.

We do not knowingly sell children's information or use it for behavioral advertising. Where parental permission is required, we will provide the necessary direct notices and controls before enabling the relevant online features. If you believe a child provided information without necessary permission, contact the privacy address listed above so we can investigate and take appropriate action.

10. Service providers and cross-border processing

Depending on which features are enabled, providers include Supabase (authentication and structured data), Google (Sign-In, Drive, Gemini and Play Integrity), Apple (Sign in with Apple on iPhone), Hugging Face (an optional on-device model download), Expo and GitHub (delivery of app updates, with no personal data from your memories), and the hosting infrastructure for Liforiah's AI server. The final provider list, exact retention settings and cross-border arrangements will be checked against the live services before any public launch. Providers may process data in jurisdictions different from yours. Where required, we take appropriate contractual, organizational and security measures for these transfers.

Liforiah is designed so that server operators do not hold decryption keys for private media and backups. This must be verified against the deployed system before it is relied on, and it is not a promise that encrypted contents are inaccessible in every circumstance.

11. Retention, deletion and recovery copies

Locally saved content is retained on the device until it is removed through the app or deleted by the operating system. Signing out does not erase it. Cloud account records and sharing metadata are retained while necessary to provide the applicable account or space, and then deleted or de-identified when appropriate, subject to lawful retention and operational constraints.

Server logs. Liforiah's AI server records, for each request, the time, route, status, duration, a request identifier and a short non-reversible tag derived from the installation; it does not record the contents of questions, answers or tokens. A specific retention period for these logs has not been verified and is not represented here as a fixed number of days.

The backup system keeps a limited number of versioned restore points (the latest three); older backups are replaced or deleted. Users' own Google Drive files and previously downloaded member copies may survive account closure until separately removed. Data removal from operational systems, backups and third parties may occur at different times depending on technical constraints and legal requirements; we will explain any material delay where required.

Account deletion. In the app you can delete your account (Account, then Delete account). This removes your account and the records tied to it from the databases we operate. Spaces you own that other members remain in pass to a longstanding member; spaces with no other member are deleted. It does not remove files in your own Google Drive, data on your phone, or copies that other members already saved. You can also export your data from Profile and delete your backups before you delete your account.

To request access, correction, export or deletion, use available account tools or contact the privacy address above. We may need to verify account ownership or parental authority before completing a request. We do not require sensitive identification documents unless reasonably needed for verification.

12. Your rights and choices

Subject to applicable law, you may have rights to be informed, access or correct personal data, withdraw consent, object to certain processing, request deletion or restriction, and receive a copy in an available format. Where Philippine law applies, these may include rights under the Data Privacy Act of 2012; you may also contact the National Privacy Commission if appropriate.

You may decline optional Drive access, choose not to share content, change microphone and notification permissions, and leave or manage shared spaces subject to your rights and their access rules. Parent/guardian rights for child data are described in Section 9.

13. Security and limitations

We use or plan security measures such as account authentication, least-privilege access, membership checks enforced by database access rules, on-device encryption, encrypted backups and integrity checks. Security measures are tested as features become available. No internet service, device or backup method guarantees complete security or permanent data availability. Keep account credentials and recovery keys secure, and promptly report suspected unauthorized access.

14. Changes to this policy

We may update this document as functionality and legal requirements change. Material changes to the use of personal information will be disclosed appropriately, and new permission or consent will be requested when required before processing information for a materially new purpose. The effective date will be updated on publication.

15. Contact and guardian requests

Service: Liforiah
Operator: Marc Dhave Maure
Privacy/support and parent/guardian requests: hello@marcmaure.com
Website: https://liforiah.marcmaure.com/

Parents and guardians may contact us to ask about child accounts, request access to or deletion of information within our control, or withdraw parental consent where applicable.