Lamp · Native · Android

Privacy policy

Native operates Lamp for Android. Firebase handles sign-in and provider profile data. Google Play processes payments. Minimal product analytics and crash reports start enabled; crash reports can be turned off in Settings. Android backups do not include on-device records. Optional faith preferences and reports you submit are stored for personalization or review. Firebase receives the name and email supplied by your sign-in provider. Analytics uses installation and account IDs. Google receives app, device and licensing data for security.

Your profile, journal and questions are stored on our server with server-managed encryption (not end-to-end). OpenAI receives your questions, reflection answers, optional faith details, prayer list details and Scripture passages to write answers and prayers. When speech is generated, the text to be read aloud is also sent. RevenueCat receives your account identifier and purchase information to connect your subscription.

Crash reports include device model, OS version and technical details of the crash — never your journal, questions or reading. Usage data is which steps you take, such as finishing a reflection, reading a chapter or opening the subscription page, sent to Amplitude to improve Lamp — never the text of your journal, questions, answers or reading. On-device data is your journal, reading progress and completion days kept without an account.

Analytics also include an installation identifier, your account identifier after sign-in, device details, language and locale, and time zone.

Analytics include approximate country information when available.

Cloud content is kept until deletion. Limited security, legal and purchase records, and provider backups, may remain longer. Processing may occur in the US or other countries. Contact Native for access, correction, objection or deletion. Lamp is not intended for children under 13.

Product analytics remain after account deletion to measure app use and account closures. Contact Native with questions or requests about these records.

This deletes live app data first, then your Firebase login. If login deletion fails, you can retry. If you connected subscription services, we queue a request to remove RevenueCat records; this can take time. Backups and limited deletion records are handled separately.

Firebase · Amplitude · RevenueCat · OpenAI · Render · Neon · Cloudflare · Google Play