The High Priestess
Privacy Policy
This policy explains what information The High Priestess collects, why, who it is shared with, how long it is kept, and what you can do about it. It is written to match what the app and its server actually do.
Who we are
The High Priestess is operated by Nimble Tide LLC (“we”, “us”). Questions about this policy or your data: support@nimbletide.dev.
The short version
- The questions you ask in a Tarot reading, and the conversation that follows, are sent to a third-party AI provider to generate the reading, and are stored on our server.
- You can use the app without an account. We identify your device with a random ID the app creates; we do not use Apple’s advertising identifier.
- We do not sell your data, show ads, or use third-party analytics or tracking SDKs.
- Journal entries stay on your iPhone and are never sent to us.
- You can request permanent deletion of your account or guest data from Profile in the iOS app (see “Deleting your data” below).
What we collect and why
A random app ID
The first time you use the app it generates a random identifier and stores it in your iPhone’s Keychain. It is sent with every request so we can keep your readings and daily pages together. It is not derived from your device hardware or Apple’s advertising identifier. If you sign in, the app ID is linked to your account so your history follows you.
Account information (only if you sign in)
Signing in is optional. Sign-in is handled by Clerk, our authentication provider. Depending on the sign-in method you choose, Clerk receives and stores details such as your email address, name, phone number, or the identity from a third-party sign-in (for example, Sign in with Apple). Our own database stores only the account ID Clerk gives us, linked to your app ID. The app shows your first name on the Profile screen.
Tarot readings
When you ask a question we store, on our server:
- Your questions and follow-up messages, exactly as you typed them.
- The cards drawn and the AI-generated reading.
- A technical log of each request to the AI provider (the messages sent, the raw response, and token usage), used to debug and improve readings.
The Almanac (daily page)
- Your birthdate, if you choose to enter it. We use it to calculate a numerology “personal day” number.
- Each day’s page: your local date, the card drawn, moon details, your personal numbers, the generated reading, and its suggested question.
- The yes / partly / no mark you give a page in the evening.
Technical and usage information
- IP address, device/app version (user-agent), and language setting. These are stored with your app ID when you request a reading, to understand usage and investigate abuse.
- Server request logs. Every request to our server is written to our hosting provider’s log stream with its time, IP address, and the address requested (including query parameters such as the date). The content of your questions is not included.
- Error logs. When something fails, the error message is stored on our server.
- If you joined through an invite link, a record that you redeemed it.
We do not collect your precise or approximate location from your device, contacts, photos, health data, or advertising identifiers. We do not look up your location from your IP address.
Stored only on your iPhone
- Journal entries are saved in the app’s private storage on your device and are never uploaded to us.
- The server address shown in Profile is stored in the app’s settings on your device.
AI providers
The text you enter in a Tarot reading (your question, follow-up messages, and the earlier conversation in that reading), together with the cards drawn, is sent to a third-party AI service to generate the response. For the Almanac, the AI service receives the day’s card, moon details, your personal day number, and your recent yes/partly/no marks. It does not receive your birthdate. We do not send your name, email, account ID, app ID, or IP address to AI providers.
By default readings are generated by Anthropic (Claude). Depending on configuration, a reading may instead be generated by OpenAI, DeepSeek, or xAI. Each provider processes this content under its own API terms and privacy policy (linked below). DeepSeek is based in China, so if your reading is routed to DeepSeek your content may be processed there.
Who we share data with
We share data only with service providers needed to run the app. We do not sell personal data or share it for advertising.
| Provider | What it receives | Privacy policy |
|---|---|---|
| Anthropic | Reading and Almanac content, as described above | anthropic.com |
| OpenAI | Same, if configured for a reading | openai.com |
| DeepSeek | Same, if configured for a reading | deepseek.com |
| xAI | Same, if configured for a reading | x.ai |
| Clerk | Account and sign-in details, if you sign in | clerk.com |
| Render | Hosts our server, database, and logs, so it stores everything our server stores | render.com |
| Apple | App distribution, TestFlight, and any crash or usage data you choose to share with developers in iOS settings | apple.com |
We may also disclose information if required by law, or to protect the rights and safety of our users or others.
Subscriptions and payments
The app does not currently offer in-app purchases or subscriptions. If we add them, payments will be processed by Apple through the App Store, and we will never see or store your card details. We will update this policy, including naming any subscription-management provider, before purchases go live.
How long we keep data
- Readings, Almanac pages, marks, birthdate, account links, model preferences, and usage records are kept until a deletion request is processed. In-app requests have a 30-day grace period, followed by manual processing by an administrator; deletion is not automatic at the end of the grace period. A reading hidden from history is still kept until data deletion.
- Server request and error logs are not purged by account or data deletion. They are retained according to our hosting provider’s retention; error files remain on the hosted server until cleared or removed with that storage. These logs are not indexed by your app ID for individual deletion.
- AI providers keep the content they receive according to their own API data-retention policies. In-app deletion does not delete copies already held by those providers.
- Journal entries stay on your device until you delete them, the app confirms completion of your deletion request and finishes local cleanup on that device, or delete the app.
Deleting your data
In the iOS app, open Profile and choose Delete account if signed in, or Delete my data if using the app as a guest, then confirm your request. There is a 30-day grace period. If signed in, the app signs you out as soon as the request is saved. Your server data and local account journal are retained during the grace period. To request cancellation, contact support@nimbletide.dev with the request reference shown in Profile. Support can cancel before an administrator starts processing the deletion. After the grace period, an administrator manually runs the deletion; it does not happen automatically on the eligibility date.
When processed, deletion permanently removes your readings (including hidden readings, messages, raw AI exchanges, and saved system prompts), Almanac pages and marks, birthdate, model preferences, stored IP/device/language usage records, invite-redemption records, and all identity links for your resolved app ID from the configured server’s database. It also deletes Clerk accounts linked to that app ID, including accounts linked during the grace period.
We store your app ID, linked account identity, request and eligibility dates, and processing status in a deletion queue so an administrator can process or retry your request. After completion, we remove the app ID and account identity from that queue and retain a receipt containing the request ID, dates, status, and attempt count. Cancelling an unprocessed request removes its queue record.
The iOS app checks the receipt when you open Profile or choose Check deletion status. When it confirms completion, it removes that account’s journal on this iPhone, resets its device identifier, and clears the current reading and profile state if that account is active. Guest journal data and the guest identifier are also cleared when they belong to the current deletion session. Keep the app installed and open Profile to finish this device cleanup. If cleanup fails, choose Retry device cleanup.
Journals on other devices, other accounts’ data, and separate guest identities are not removed. Request and error logs are not purged and remain subject to hosting retention, as described above. Shared invite definitions and administrator-written notes are also retained. For other data requests, inaccessible accounts, cancellation help, or errors, email support@nimbletide.dev. We may need to verify that the data is yours.
Deleting the app does not delete data already on our server. Keychain identifiers can survive app removal; use the in-app deletion option and complete device cleanup to reset them.
Your rights
You can ask us to:
- Access a copy of the data we hold about you.
- Correct it. You can change your birthdate in the app at any time.
- Delete it, as described above.
Email support@nimbletide.dev to make any request. We may need to verify that the data is yours before acting on it. Depending on where you live (for example the EU, UK, or California), you may have additional rights under local law, including the right to complain to a data protection authority.
Children
The High Priestess is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child under 13 has used the app, contact us and we will delete their data.
Security
Traffic between the app and our server is encrypted with HTTPS. Your app ID is stored in the iOS Keychain, and journal entries use iOS file protection. No system is perfectly secure.
Changes to this policy
If we change this policy, we will update the effective date above.