Privacy policy

1. Operator and contact

Little Sign is operated by Ming Zhu, an individual developer, who is responsible for the processing described in this policy.

For privacy questions, data requests, or concerns about children’s information, contact: ming.life@foxmail.com.

2. Information on your device

Daily cards, saved Explore readings, notes, intentions, the card meanings you write for your own deck, the action you marked for a reading, favorite cards, Decision Wheel options, themes, and language preferences are stored on your device. A local installation identifier helps keep draws consistent; it is not an advertising ID. Core guest features do not require an account.

These local records do not automatically sync to our servers. The current release has no cloud journal backup. We do not use advertising or analytics SDKs to upload these records. Signing out does not erase device data.

3. Email accounts, sparks, and service records

When you register or sign in, Supabase and the verification-email delivery service process your email address, your password (stored by Supabase only in hashed form), confirmation and password-reset codes, account identifier, and sign-in sessions to verify identity and provide account features. Sign-in sessions are stored on your device; passwords and codes are not saved in your journal or on your device.

We keep an account-linked AI request date and count on the server to enforce usage limits and control abuse. Those counters do not contain your question, answer, or notes. If you report a generated reading from inside the app, that report is stored on our service linked to your account, as described in section 4.

Readings written by Little Sign use sparks, a reading credit tied to your account. Our service keeps your spark balance and a ledger of every change: the welcome grant, the daily spark for a completed Today draw, the sparks reserved and charged for each reading, purchased packs, and refunds, each with an amount and a time. To claim the daily spark, the app sends your account identifier and the local date of the draw; the card you drew is not sent. A reading request records the account identifier, the amount, and a reservation identifier. The wallet never receives your question, cards, or notes.

If a spark pack is on sale and you buy one, Google Play handles the payment under Google’s own terms and privacy policy; we never receive your payment card details. The app then sends the Google Play purchase token and product identifier to our service, which confirms the purchase with Google and checks that it carries a one-way hash of your account identifier set by the app when the purchase started. We store the purchase token, Google order identifier, product, spark amount, and purchase time against your account so that each purchase is credited once and can be reversed if Google refunds or voids it. A daily check reads Google’s list of voided purchases for this app. No question, card, note, or email address is involved in any of this.

4. Optional AI questions

When you explicitly submit an AI reading request, your question, optional context, the reading format you chose, the app’s display language (the reading is written in it), and the drawn cards (position, artwork and orientation), together with any meaning you wrote yourself for one of those cards in the Deck, pass through our Supabase service to DeepSeek to generate a reading. If you leave the question blank, the reading’s own printed question is sent in its place. Your text may include personal information you choose to enter. Avoid sensitive information you do not want processed and other people’s private information.

We do not include your email, account ID, private notes, intentions, reading history, shuffle records, or the installation identifier in the AI prompt. Your account still authenticates the request to our service. The answer returns to the app and is written to local history only when you choose to save it. The app backend does not store questions and answers in a journal database or deliberately log question bodies. Provider operational logging, retention, and processing can be separate from this flow.

We do not use your local journal to train AI. This policy does not promise zero retention or no training by the AI provider for submitted text; those conditions depend on the applicable API agreement and configured settings. You can avoid AI processing and still use every card and reading in the app, which are written into it and work offline.

Every generated reading, including one saved in Collection, carries a Report link. When you choose a reason and send a report, the app sends the generated text exactly as displayed, the reading format, the name of the model that wrote it, and your chosen reason to our Supabase service, where it is stored in a private review queue linked to your account. Your question, context, notes, history, email address, and installation identifier are not attached, although the generated text may repeat words from your question. Reports are not sent to DeepSeek. The operator reads open reports to remove or adjust harmful generation paths and improve moderation, and records the action taken. The app shows a receipt only after the server has stored the report; a report that fails to send can be retried. Each account can send a limited number of reports per day. Reports are deleted together with your account.

5. Sharing, photos, and device permissions

When you choose to export or share a card, the app creates an image and passes it to the system sharing app you select, or saves it to your photo library. Current card sharing excludes private notes, intentions, and custom questions. Recipients and the apps you choose handle the shared image under their own rules.

Saving an image may require storage permission on older Android versions or permission to add photos on iOS. The app does not need to read your entire photo library, and its core features do not collect contacts, precise location, camera, or microphone content. Manage permissions in your device settings.

6. Providers, website, and network information

Supabase provides authentication, the database, and the app backend. Our Supabase project runs in the United States. Supabase keeps no automatic database backups of this project, and its server logs are retained for one day (authentication audit logs for one hour), so records deleted from our service are gone from Supabase within a day. Email delivery services send account confirmation and password-reset codes. DeepSeek processes submitted AI questions. Google Play processes spark-pack payments and confirms purchases to our service. GitHub Pages hosts this website. Network providers receive information such as your IP address needed to handle connections, and may process request times, browser or device information, and security logs to run, secure, and diagnose services.

The website sets no cookies of its own and stores nothing in your browser; the deletion request page only opens your email app with a prefilled message and sends nothing itself. The website adds no advertising or marketing tracking. The hosting platform may use its own security or access-control cookies. If you email us, email services process your address and the content you provide.

We do not sell personal information. We do not deliberately disclose your records except to providers delivering the service, recipients you choose when sharing, or where necessary for legal requirements or service security. Processing may occur outside your country. Provider information: Supabase · DeepSeek · Google · GitHub.

A provider’s policy for its own users may not cover data submitted through an API; this Little Sign policy and the applicable service agreements govern the corresponding processing.

7. Retention and deletion

• Local records remain until you delete them or use Settings → Clear my data on this device. Uninstalling, losing, or resetting a device can also cause data loss; exported images and other copies must be deleted separately.
• Account records remain until you delete the account. Use Settings → Delete my account in the app, or email a request as described on the account deletion page. In-app deletion runs immediately after verification and confirmation; an email request is verified by the sending address and completed within 5 days of a verifiable request, with a confirmation reply. Both remove the account, linked sign-in records, per-account usage counts, and other linked records covered by the deployed data relationships. Signing out or clearing this device does not delete the account.
• Deleting an account from the app removes identifiable AI history belonging to that account on that device. Guest records, older unowned records, and other accounts’ records remain. An email deletion request does not erase device data, and in-app deletion does not clear other devices. Clear any remaining local data on each device separately.
• Usage counts reset on a request on a new day; successful request processing removes counts older than two calendar days. Cleanup is request-triggered, not a timed guarantee. Account deletion removes its count; the global count without account identifiers remains.
• Spark balances, ledger entries, and purchase records remain until you delete the account and are removed with it. Google keeps its own order records under its policies; a refund that arrives after deletion changes nothing on our side.
• Reports of generated readings stay in the review queue until they are reviewed, and afterwards for as long as needed to keep a record of the action taken and to improve moderation. They are deleted with the account, whether deletion runs from the app or by email request.
• Supabase server logs expire within a day and the project has no automatic backups (section 6). The AI provider’s logs and submitted AI text may remain under applicable agreements for security, abuse prevention, service operation, or legal obligations; immediate account deletion does not guarantee erasure of those copies. Contact us below for the retention periods applicable to your request or deletion assistance. We create no new server account record to track deletion.

8. Security, choices, and rights

Account and AI requests use HTTPS. The backend verifies account authorization, and administrative keys are not included in the app or website. Local storage relies on device and app-sandbox protection; it is not a separately encrypted journal vault. Protect your device and email account; no system guarantees absolute security.

You can use guest mode, avoid submitting AI questions, sign out, manage permissions, delete local records, or request account deletion. Depending on your location, you may also have rights to access, correct, receive a copy of, delete, restrict or object to processing of your data, withdraw consent, and complain to a regulator. We may need to verify identity; we will not ask you to send a verification code or password.

For a rights request or assistance: ming.life@foxmail.com. Support.

9. Children and policy updates

Little Sign offers everyday reflection and is not directed at children. If you believe a child has supplied personal information, contact the operator so we can investigate and handle it under applicable law.

This page shows its update date. Material changes to data handling will be communicated through the app or another appropriate channel; consent will be requested separately where required.