Privacy Policy

1. Introduction

Thoth: The Unknown ("we," "us," "our," or "Company") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application Thoth: The Unknown (the "App").

By downloading, installing, or using Thoth: The Unknown, you acknowledge that you have read, understood, and agree to be bound by all the terms of this Privacy Policy. If you do not agree with our policies and practices, please do not use our App.

2. Information We Collect

2.1 Account & Authentication

To use Thoth: The Unknown, you must create an account. We collect the following:

• Email address — used to send you a magic link for sign-in; stored in our backend.
• Apple ID credential — if you choose "Sign in with Apple," we receive your anonymised Apple user ID and, optionally, your name. Apple may provide a relay email address.

If you choose email/password sign-in, the password is submitted securely to Supabase Auth for authentication. The App does not store it as plain text or send it to an AI provider.

2.2 Profile Information

During account setup you may provide:

• Display name (optional) — a nickname shown only to you within the App.
• Date of birth (required) — used to personalise tarot interpretations and to verify you meet the minimum age requirement (18+). If you request an AI interpretation, the limited profile context described in Section 5.2 may be sent to the provider you authorize.
• Time of birth (optional) — used for natal chart context in interpretations.
• Place of birth (optional) — free-text field; used for natal chart context in interpretations.

2.3 Reading Data

We store the following reading-related data in our cloud backend to enable multi-device access and history:

• Cards drawn during readings
• Spreads used (the nine spreads currently shown in the catalogue, plus the Daily Card)
• Your intention or question text for a reading (optional)
• Dates and times of readings
• Personal reflections or notes added to readings (optional)
• Favourite status of readings

2.4 Physical Spread Photos (Optional)

If you choose the physical-spread scan, the App asks for camera access and asks you to confirm before the photo is sent for card recognition. The photo is sent through our Supabase backend to the AI provider used for recognition. We do not save the original photo in your reading history or database. To process retries reliably, a recognition result only—not the original photo—may be available for reuse in a service-only cache for up to 24 hours. The provider's handling is governed by its own terms and privacy policy; we do not make a separate retention guarantee for provider processing. You can use the digital card-selection flow without camera access or photo recognition.

2.5 Device Information (Automatic)

• Device model and type
• Operating system version
• App crash logs and performance data (only if enabled in your iOS Settings → Privacy → Analytics)
• AI-request operational data used for quota and cost management: request type, spread type, timestamp, model name, and prompt/completion token counts. This record does not contain the original photo or interpretation text.

2.6 Advertising Data (Rewarded Ads — Free Tier Only)

Free-tier users may optionally choose to watch a rewarded video ad to earn a free credit. Rewarded video is the only form of advertising in the App — there are no banner or interstitial ads. Google Mobile Ads and Google User Messaging Platform (UMP) may process operational, consent, diagnostic, and advertising data when consent information is refreshed or an ad service is used; a consent refresh can occur before you choose to watch an ad. This can include:

• Device identifiers (including the Identifier for Advertisers, IDFA, only if you grant permission via the iOS App Tracking Transparency prompt)
• IP address and IP-derived coarse region; the App does not request GPS location permission
• Advertising data and product interactions, such as ads seen, video views, and app-launch or consent interactions
• Performance, crash, and other diagnostic data related to the Google services

On a fresh install or after tracking is reset, the App requests Apple's App Tracking Transparency permission after the splash screen and before the sign-in and onboarding flow. Before an ad request, the App also obtains the consent information required by Google User Messaging Platform (UMP), including its form where required. If you decline, ads may be non-personalised or unavailable. You can revisit UMP choices from Settings → Privacy and Support → Advertising Privacy Choices where available.

3. How We Use Your Information

We use the information we collect to:

• Authenticate you and maintain your session securely across devices
• Provide and personalise the App — deliver readings, personalise interpretations, and maintain reading history
• Generate AI interpretations and recognize physical spreads — only after the applicable in-app consent, send the data described in Section 5.2 to the selected provider
• Process purchases — enable Pro subscriptions and credit packs and reconcile your entitlements (see Section 5.5)
• Serve optional rewarded ads — only if you choose to watch one to earn a credit (see Section 5.4)
• Improve the App — fix bugs, optimise performance, and develop new features
• Provide technical support — troubleshoot issues and respond to requests
• Comply with legal obligations — including age verification

We do not sell your personal data, serve banner or interstitial ads, or carry out behavioural tracking you have not consented to via the App Tracking Transparency prompt.

4. Data Storage & Security

4.1 Cloud Storage

Your account data, profile, and reading history are stored in our cloud backend operated by Supabase (see Section 5). Data is hosted in the eu-central-1 (Frankfurt, Germany) region. Reading data is also cached locally on your device for offline access.

4.2 Security Measures

• Authentication tokens are stored in the iOS Keychain with kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly — they do not sync to iCloud.
• Data sent between the App and our backend is protected in transit with TLS (HTTPS).
• Row-Level Security (RLS) policies ensure each user can access only their own data.
• Sign in with Apple nonces are generated using SecRandomCopyBytes and hashed with SHA-256.

4.3 Data Retention

• Active account: Your data is retained for as long as your account is active.
• Account deletion: All personal data is permanently deleted from our servers within 30 days of deletion. Authentication records are removed immediately.
• Device cache: Local cache is wiped immediately when you delete your account or sign out.
• Short-lived AI result cache: A physical-spread recognition result, not the original photo, may be available for reuse service-side for up to 24 hours. Expired entries are cleaned during subsequent request processing; we do not represent that physical deletion occurs at the 24-hour mark.
• AI usage ledger: User ID, request time, operation/spread type, model name, and token counts are retained for quota, billing, and abuse-prevention purposes. A separate fixed retention period for this operational record has not yet been set.

5. Third-Party Services

5.1 Analytics, Consent, and Diagnostics

We do not integrate a separate general-purpose analytics SDK such as Google Analytics, Firebase Analytics, or Crashlytics. Google Mobile Ads and UMP nevertheless process operational, consent, advertising, performance, crash, and diagnostic data as described in Section 2.5. Their collection may support app functionality, advertising, and analytics purposes under Google's documentation. The App does not request GPS location permission; Google may use an IP address to estimate a coarse region.

If you enable Crash Reporting in iOS settings (Settings → Privacy → Analytics), Apple may also collect crash logs. This control does not replace Google Mobile Ads or UMP's own diagnostic processing. See Google's iOS data-disclosure documentation and Google's privacy policy for further information.

5.2 AI Interpretation and Photo Recognition

The App uses AI to generate written interpretations and, if you choose it, to recognize cards in a physical-spread photo. Before sending data to an AI provider, the App shows a provider-specific consent prompt. Consent is stored for the signed-in account on that device and can be revoked in Settings → Privacy and Support → AI data sharing; revocation prevents later requests to that provider until you consent again.

For a written interpretation, the request can include the cards drawn, their positions, spread type, intention/question, and the birth-date, birth-time, birth-place, or gender context you supplied. It does not include your email address or authentication credentials. For photo recognition, the request includes the photo and the selected spread context. Requests are routed through our Supabase backend.

Google Gemini (Google LLC) is the sole AI provider for interpretations and photo recognition. Google processes submitted data under its terms and privacy policy. We do not represent a provider-specific retention period or make promises about provider model training beyond the provider's applicable terms.

Provider	Purpose	Privacy policy
Google LLC (Gemini API)	AI interpretation and photo-recognition provider	policies.google.com/privacy

5.3 Sub-Processor: Supabase

Attribute	Value
Provider	Supabase Inc.
Purpose	Authentication, database (profile + readings), account management, and AI request routing
Data hosted	eu-central-1 (Frankfurt, Germany)
Privacy policy	supabase.com/privacy

5.4 Advertising Provider: Google AdMob

We use Google AdMob (Google LLC) to serve optional rewarded video ads to free-tier users. AdMob is only invoked if you tap "Watch an ad for +1 credit"; it is never loaded otherwise. See Section 2.5 for the data involved and the consent prompts shown first.

Attribute	Value
Provider	Google LLC (AdMob)
Purpose	Serving optional rewarded video ads (free tier only)
Data collected	Device and advertising identifiers, IP address/coarse region, advertising data, product interactions, and performance, crash, and other diagnostic data (see Section 2.5)
Consent	UMP consent information is refreshed before consent-dependent ad requests and may refresh before a user watches an ad. ATT is requested on a fresh install or after tracking is reset, before sign-in and onboarding.
Privacy policy	policies.google.com/privacy

5.5 Purchases: RevenueCat & Apple

Pro subscriptions and credit packs are sold as Apple In-App Purchases and billed through your Apple ID; payment details are handled by Apple and are never seen by us. We use RevenueCat, Inc. to manage entitlements and validate purchases. RevenueCat receives your anonymised app user ID and purchase/transaction metadata (product purchased, purchase and expiry dates) — not your name, email, or payment card.

Attribute	Value
Provider	RevenueCat, Inc.
Purpose	Subscription & in-app purchase management and validation
Data collected	Anonymised app user ID, purchase/transaction metadata
Privacy policy	revenuecat.com/privacy

6. User Rights & Controls

6.1 Access Your Data

You can access all your reading data at any time through the App's Reading History feature.

6.2 Delete Your Account

You can permanently delete your account directly within the App:

This immediately revokes your session, permanently deletes your profile and all readings within 30 days, and wipes your local cache immediately. This action is irreversible. Alternatively, email admin@codewavemobile.com to request deletion.

6.3 Correct or Update Your Data

Update your display name, birth date, birth time, and birth place at any time via Settings → Profile.

6.4 Data Portability

Export functionality is not yet available in the App. To request a copy of your data in a portable format, contact us at admin@codewavemobile.com.

6.5 Opt-Out

• AI data sharing: Revoke a provider's consent in Settings → Privacy and Support → AI data sharing. The App will not send later interpretation or photo-recognition requests to that provider unless you consent again.
• Advertising & tracking: Change tracking permission in iOS Settings → Privacy & Security → Tracking. Rewarded ads are optional, but Google advertising and consent services may still process the Section 2.5 operational, consent, and diagnostic data when consent information is refreshed. Where available, revisit Google choices in Settings → Privacy and Support → Advertising Privacy Choices.
• Crash Reporting: Disable in Settings → Privacy → Analytics
• Location Services: Thoth: The Unknown does not request location access

7. Age Requirement

We do not knowingly collect personal information from users under 18. The App enforces an age gate during account setup — a valid date of birth confirming the user is 18 or older is required to create an account.

If we become aware that a user under 18 has created an account, we will delete that account and all associated data without notice. Parents or guardians who believe a minor has created an account should contact us immediately at admin@codewavemobile.com.

8. Your Privacy Rights by Region

To exercise any of these rights, contact us at admin@codewavemobile.com. We will respond within 30 days.

9. Changes to This Privacy Policy

We may update this Privacy Policy to reflect changes in our practices, technology, or legal requirements. We will notify you of material changes by updating the "Last Updated" date, posting the revised policy within the App, and requesting explicit consent if changes materially alter how we handle your data.

Your continued use of the App after changes become effective constitutes your acceptance of the updated Privacy Policy.

10. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy, please contact us:

• Email: admin@codewavemobile.com
• Mailing Address: Thoth: The Unknown Support, Istanbul, Turkey

We will respond to privacy requests within 30 days.