Privacy guide
Use AI tarot without oversharing
Tarot questions often involve relationships, work, fear, or uncertainty, so even a short prompt can reveal sensitive context. Privacy begins before submission: understand what the product needs, remove identifying detail, and distinguish the reading itself from the aggregate events used to measure whether the experience works.
Share the decision, not the identity
A useful question usually needs the situation, the decision, and one relevant constraint. It rarely needs a legal name, workplace, address, account identifier, exact message history, or information that identifies another person. Replace names with roles and keep only details that change the meaning of the choice.
Birth date and profile information should be treated as optional product context, not proof of identity or a requirement for symbolic accuracy. Before entering any personal detail, check whether the selected reading actually uses it and whether the same question can be asked more safely without it.
- Lower-risk: “What boundary should I clarify before our next conversation?”
- Unnecessary detail: Names, contact information, employer, private message excerpts, and account numbers.
- Never submit: Passwords, payment credentials, medical records, legal documents, or emergency information.
Separate product operation from analytics
Neural Tarots uses a bounded event taxonomy for public experience measurement. Events describe fixed actions such as a reading start, completion, error category, or pricing view. They must not include the question, reading text, email, device identifier, full URL, or free-form error message.
Aggregate measurement can show that a flow was used without recreating the private story behind it. This limitation is intentional. If a future dashboard requires raw prompts or user-level profiling, that is a new privacy decision and must not be introduced as a routine analytics field.
Understand anonymous and account boundaries
An anonymous session and a signed-in account serve different purposes. Public or anonymous use should collect the minimum needed for the current request. Saved history, subscription access, restoration, and account linking require verified ownership and an explicit user action.
A browser-provided identifier is not proof that a person owns an account or its history. Requests for private records must be authorized on the server. If you sign in or save a reading, review the product's current retention and deletion controls rather than assuming anonymous and account-linked data behave the same way.
Choose another channel for high-risk information
Do not use a tarot prompt as a place to store medical details, evidence of abuse, legal correspondence, financial credentials, or crisis information. Use qualified and appropriately protected services. Removing names does not make a detailed private record harmless if the remaining context still identifies someone.
Privacy also includes the device around you. Consider screen visibility, shared browser access, notification previews, downloads, and saved history. If another person controls or monitors the device, opening or saving a reading may create risk even when the service itself minimizes data.
Continue exploring
Related guides to spread selection, card meaning, and safe reflection.