Plain-language policy
Names, birth dates, and personal tarot questions are not stored by default. If a saved reading option is added later, it must ask for clear consent before anything becomes shareable.
Return to toolslegal
Tarot Tools Privacy Policy
How Tarot Tools handles names, birth dates, questions, analytics, and private result inputs.
Continue from here
What is processed by default
Tarot Tools calculates names, birth dates, topics, and questions only for the current reading experience and does not persist them by default. This matters because tarot tools invite sensitive reflection even when they are entertainment-only. You can try a result without accidentally publishing personal context onto a shared web page.
- Birth dates are used to calculate a card and are not echoed into public URLs.
- Names in compatibility tools are used for the current calculation only.
- Questions are treated as private input and not saved by default.
How result pages are handled
Personal result pages are designed as private surfaces. That means the site can support useful private experiences without trying to turn every input into a shared web page. New readers should land on tools, guides, and card meanings; private reflections should stay private unless the reader clearly chooses to save or share them.
- Private by default is the rule for personalized results.
- Public navigation includes informational and tool pages only.
- Saved readings use tarot-tools:saved-results in this browser only and can be cleared from the private result page.
User control and correction
Privacy questions, licensing concerns, and content corrections deserve a monitored response path. The standard is simple: if a reader asks what was stored, Tarot Tools should be able to answer clearly. If the answer is not clear, the safer choice is to store less until the data policy is stronger.
- Keep data collection minimal.
- Local analytics counters use tarot-tools:event-counts and track only public tool, card, result-type, and link labels.
- Treat tarot questions as sensitive by default.
Practical privacy examples
A love compatibility calculation may feel personal because it uses names or birth dates, but the result should still behave like a temporary reflection unless the reader chooses a sharing action. A yes/no question may mention work, money, health, or a relationship; the safer privacy rule is to keep that question in the browser flow and route public learning to guides, card pages, and tools that do not reveal the original input. Current local analytics events are limited to public tool, card, result-type, and link labels; they must not store names, birth dates, personal questions, journal notes, or result text. Readers should be able to understand the difference between a private tool state, a save action, a share action, and a public article before entering sensitive details.
- Do not place personal questions in public navigation or sitemap entries.
- Give readers a clear choice before saving, sharing, or downloading a result.
- Use public articles for learning and private tool states for personal reflection.