Privacy Policy

Last updated: October 21, 2026

This policy explains how Pixmeknot Limited handles information when you use Little Lift on iOS, Android, and the web. You can explore default topics without an account. Signing in and AI personalization are optional.

Information we handle

• Account details: your email address, Firebase user ID, sign-in credentials handled by Firebase Authentication, and authentication/session information. If you choose Google or Apple sign-in, Firebase also receives the profile information you authorize, such as your name and email (including an Apple private relay address). Passwords are not part of your Little Lift library or sent to the AI provider.
• Your content: saved affirmations, personal deck names, the context you submit, generated statements, visualization and action cues, edits, card positions, and related timestamps.
• Preferences and credits: your sound selection, credit balance, and generation records such as completion/refund status and timestamps.
• Technical information: our hosting and service providers may process IP addresses, request details, device/browser information, and security logs.

What you write may reveal sensitive information about health, relationships, beliefs, or other personal matters. Include only what you want processed. Please do not submit passwords, payment details, identity documents, or someone else’s private information.

Notifications

If you enable notifications in the native app, Firebase Cloud Messaging and Apple Push Notification service process device registration identifiers to deliver messages. We store your device token, platform, registration ID, and update time with your account. Backend push messages are general. For optional 30-reminder plans, we store your goals, 30 generated messages, selected weekdays, a delivery window, cadence, scheduling progress, time zone, and lock-screen privacy choice in your account and cache them on your device. iOS or Android schedules these reminders locally, so they can arrive offline. Personal text appears in notifications only if you enable message previews. Otherwise the reminder is generic. Changing or deleting a plan on another device updates this device’s pending reminders when it next opens and syncs. Signing out or deleting your account on this device cancels its scheduled reminders. You can turn notifications off in Settings; signing out removes that device registration, and account deletion removes all registrations. Native push uses hosted Firebase even when account development uses emulators.

What stays on your device

Bookmarks are stored using IndexedDB. Personal decks, their context, card position, and preferences use localStorage. Default topics and bundled music do not need an AI request. These storage mechanisms support the service. Optional website advertising cookies and native ad measurement are described below.

Optional website ad measurement

If you allow it, our website uses Meta Pixel on public discovery pages to measure page visits and app-store link clicks. Meta receives the page URL, browser and network information, and cookie identifiers such as _fbp and _fbc to measure and improve advertising. We disable automatic event detection and do not send form contents, affirmations, selected topics, situations, goals, recordings, account details, or purchases through this website integration. The Pixel does not run inside our iOS or Android apps or on account, library and practice routes.

Website ad measurement stays off until you choose Allow. Your choice is stored in this browser. Global Privacy Control or a browser Do Not Track setting keeps measurement off. You can change your choice using Cookie preferences here or in Settings. Declining or withdrawing consent stops future website events and removes the Meta cookies we set on this domain; it does not erase events already received by Meta. Read Meta’s Privacy Policy for its processing and retention practices.

Signing in uploads your local text library to your account and enables background sync. “Sync now” requests an upload immediately. Voice audio is not part of that sync. Signing out clears the Little Lift text library, reminder plan cache, and scheduled local reminders on that device. Voice recordings remain on this device because they are not attached to an account. Other people who can access your device or browser storage may be able to read local content.

Optional ad measurement on iOS and Android

With your permission, the native app uses Meta’s SDK to share app activation events and device identifiers with Meta to measure and improve our Facebook and Instagram advertising. RevenueCat can send credit-pack purchase events, including the amount and currency, to Meta using permitted device identifiers and Meta’s anonymous app identifier. We do not send your affirmations, selected topics, personal situations, goals, recordings, account email, or passwords to Meta. Automatic screen, content and purchase logging is disabled.

Ad measurement stays off unless you allow it. On iOS, we also require permission through Apple’s App Tracking Transparency prompt. Change your choice in Little Lift Settings → Ad measurement; iOS tracking permission can also be changed in device Settings. Turning it off stops future app events and clears the attribution identifiers we set in RevenueCat when its SDK is configured. It does not erase information already delivered to Meta. Read Meta’s Privacy Policy and RevenueCat’s Privacy Policy for their processing and retention practices.

Welcome credits and abuse prevention

Eligible new accounts in the iOS and Android app may receive three free AI creations once per account and verified device. Web sign-ups do not receive this offer. We use Apple DeviceCheck on iOS or Google Play Integrity with device recall on Android to check whether a device has already redeemed the offer. These services process device verification tokens and a minimal offer-claimed flag. We do not use an advertising identifier or share these checks with Meta. We keep a server claim record containing a one-way hash of your account ID, verification status and timestamps to prevent repeat claims, including after account deletion. Claim records are scheduled for deletion after 180 days, subject to database expiry processing; Apple and Google retain their device flags under their own service policies.

Your unfinished personal-situation draft is kept on this device so you can continue after signing in or reopening the app. Its saved words and personal deck use the library’s normal storage and sync behavior. Voice recordings remain on this device.

How we use information

We use account information to authenticate you, recover access, and connect your library across devices. We use your content to display and save your affirmations and, when requested, generate personalized cards. We use credit records and technical information to operate the service, prevent abuse, troubleshoot failures, and respond to support requests. We do not sell personal information or use your content for targeted advertising.

AI personalization and service providers

When you submit a request to generate affirmations, your entered context and relevant topic/card text go to our backend and its AI service. The integration uses OpenRouter and OpenAI. Requests are restricted to OpenAI endpoints with training/data-collection routing disabled; generation fails if an allowed endpoint is unavailable. This is not a zero-retention service: providers may retain data under their security, abuse-prevention, and service policies. Do not assume an AI request remains solely on your device. Your account email and password are not included in the generation prompt. Creating a 30-reminder reminder plan sends the two or three goals you explicitly submit to the same AI providers after your consent.

Google Firebase provides account authentication and cloud storage in hosted deployments. OpenRouter and OpenAI process AI requests. Hosting providers process network requests. Local development uses Firebase emulators instead of the hosted Firebase service. We do not log AI prompts or responses in our application server. Training restrictions do not erase past requests or prevent all retention; OpenRouter account logging settings and providers’ technical/security metadata are separate. We do not promise that all technical metadata is immediately erased.

Read OpenAI’s Privacy Policy, Firebase’s privacy information and OpenRouter’s Privacy Policy. The provider list and processing arrangements must be reviewed and updated if the deployed service changes.

Purchases

Apple or Google processes native payments. RevenueCat validates store purchases using your Firebase account identifier, product and transaction information, purchase/refund status, country, currency, and technical app information. We do not receive your card number. Your Firebase profile holds your shared credit balance. We do not send your affirmation text or personal context to RevenueCat. Read RevenueCat’s Privacy Policy.

Audio, permissions, and exports

The speaker uses your device/browser speech service. Some voices may process text online under that service’s policy. Background music is bundled with the app. The optional Own voice feature requests microphone access only when you choose to record. Recorded audio and its card/cue snapshot stay in app-private files on iOS and Android, or IndexedDB on the web. Little Lift does not upload this audio or use it for AI generation. Local free recordings do not contact our server. If you use paid recording credits, we send an operation identifier, duration, completion status, and timestamps to maintain that paid balance. Little Lift does not request camera, contacts, or precise location access.

Voice recordings do not sync between devices. Device storage limits, browser eviction, clearing app/browser data, or uninstalling the app may remove them. Your operating system’s backup settings can also affect local files; Little Lift does not provide a separate audio-backup service. Listening to stored audio does not use credits.

Export includes deck titles and saved affirmation text, not your original context or account metadata. On native apps, you choose where to send the file using the system share sheet; its temporary app-cache file is removed after sharing finishes. Exported copies and copies sent to another app remain under your control.

Content reports

“Report this card” sends the card text, selected reason, and any details you add to our review queue. Your original deck context is not automatically included. Signed-in reports are stored in a central review queue with your account identifier and are removed when you delete your account. Reporting also adds those words to your private hidden-card list, so matching cards are excluded from your practice, saved list, and local reminders. That list stays with your account even after the report is resolved or expires; it is removed on account deletion. Guest hiding stays on the reporting device until its local data is cleared. Guest reports are not linked to a Little Lift account. Reports expire after 90 days plus the database’s expiry-processing delay. Contact us to request earlier removal.

Retention and deletion

Local content remains until you delete it, reset the relevant deck, clear app/browser data, or uninstall the app, subject to your operating system’s backup behavior. Cloud libraries and account/credit records remain while the account exists; this version has no automatic account-expiry schedule. Uninstalling the app or clearing browser data does not delete cloud data.

You can remove individual bookmarks, clear saved words, delete a personal deck, or reset a personalized topic. While signed in, those changes sync to your account when connected. A reset does not remove separately bookmarked cards. Unsynced devices, guest copies, backups, and files you exported can retain separate copies.

Open Settings → Delete account and confirm your sign-in to permanently remove your Firebase sign-in, cloud library, reminder plans and goals, context, reports, preferences, generation and voice-credit records, and unused credits. This also clears Little Lift’s local and guest text library on the device used to complete deletion. Voice recordings are device-owned and remain on that device after account deletion. To remove audio, delete the recordings in the app or clear app/browser data. Account deletion does not erase local audio on other devices. Deletion finishes when confirmation appears; if it fails, retry. You can also visit our account-deletion page or contact us for help or a request to remove specific data. We verify ownership for support requests and respond within 30 days.

Account deletion also requests deletion of your RevenueCat customer record, which RevenueCat processes asynchronously. Store payment records remain under Apple’s or Google’s policies. To prevent purchase replay and handle refunds, we retain a minimal receipt ledger containing hashed transaction/account identifiers, product, store, environment, credit adjustments, and timestamps after account deletion. It contains no email, affirmation text, or context.

A security marker containing one-way hashes of the former account ID and deletion-authorizing token, deletion state, and expiry date blocks delayed saves from recreating deleted accounts. Completed markers expire after 30 days plus database expiry-processing time; incomplete deletion markers remain until completion. They contain no email, words, or context. We do not intentionally retain deleted cloud libraries in application backups. External provider security logs and infrastructure backups have their own retention schedules, which must be verified for the hosted service before release.

Delete your account or request data deletion

Your choices and rights

You can use default topics without signing in, choose what context to submit, edit or remove saved words, export your saved affirmations, and decline AI processing before each request. Declining does not affect default topics. Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing of your information, obtain a portable copy, withdraw consent, or complain to a privacy regulator. Contact us to make a request. Withdrawal does not undo processing already performed.

Security and international processing

Hosted account access uses authentication and server-side access checks. Release builds require an HTTPS backend; emulator builds can use local HTTP connections for testing. These measures do not make any system completely secure. Service providers may process information outside your country, with applicable contractual and legal protections to be confirmed for the production deployment.

Age and wellbeing

Little Lift is intended for adults aged 18 and over. We do not knowingly seek information from children. Contact us if you believe a child has provided information. The app is for reflection and general wellbeing, not diagnosis, therapy, emergency monitoring, or a guarantee that an imagined outcome will occur.

Changes and contact

We may update this policy as the service changes. We will revise the date above and provide additional notice or request consent where required for material changes.

For support, privacy questions, or requests concerning your information, contact Pixmeknot Limited at vinay@littlelift.app. Please identify Little Lift and your account email, but never send your password.