Effective date: October 3, 2026
This policy describes personal data handled by Meow Tarot on the web, iOS, and Android. The platforms share an account and credit system, but use different payment routes.
Privacy requests: itrounder.korea@gmail.com
Questions and chat may contain sensitive personal details. Avoid entering information about other people or anything you do not want stored. Remove identifying details before sharing a result publicly.
For web purchases, our server sends Dodo Payments your account email (and name if available), internal user identifier, selected product, price and currency, and order identifiers to create checkout. We verify payment, cancellation, failure, and refund notifications to update credits. Dodo Payments’ public Privacy Policy and DPA describe Dodo, in its Merchant of Record (MoR) role, as an independent controller for buyer data it collects directly. Dodo may process buyer data for transaction/payment processing, fraud and risk checks, sanctions compliance, tax calculation/remittance, chargebacks and disputes. This describes Dodo’s published role; the seller shown on a specific receipt and the applicable agreement govern the transaction.
Our Supabase payment_attempts ledger stores the user ID, request key, product, credit amount, amount in USD cents, currency, Dodo checkout/payment identifiers, status, and processing timestamps. Refund records may include refund and payment identifiers, amount, currency, and outcome. A checkout URL may be retained to resume checkout. Meow Tarot does not store full card numbers or security codes in Supabase. Dodo and related payment networks may process checkout contact/billing details, payment method and transaction data. If a saved-payment-method feature is used, the payment provider may retain tokenized data or card details in its secure vault. Dodo's published Privacy Policy says it retains identifiable data for the minimum period needed for its lawful purposes, including an ongoing relationship or legal retention need, the applicable claim limitation period plus two months, and longer if a relevant claim is ongoing; it then deletes or anonymizes the data. It does not give one fixed number of years for every buyer record. Dodo-held data is outside our database expiry job. See Dodo Payments’ Privacy Policy and DPA.
In-app purchases use Apple App Store or Google Play billing with RevenueCat for purchase verification and status synchronization. The app links the signed-in Supabase user ID, or a RevenueCat anonymous app user ID before sign-in, to the purchase SDK. RevenueCat SDK/services may process the app user ID (including its anonymous app ID before sign-in), store, product, receipt/transaction identifiers, purchase status, IP address and technical details such as device type and operating system. RevenueCat says it may infer a country from the last-seen IP when transaction country is unavailable, then drop rather than persist the IP. The app code does not separately set email/phone attributes or call an advertising-identifier collection helper. Apple or Google process payment credentials and maintain their own store purchase records; RevenueCat processes purchase data for verification and status synchronization. RevenueCat’s public materials do not state one fixed numeric retention period for end-user data it processes for us. See RevenueCat’s privacy policy and customer deletion documentation.
RevenueCat webhooks provide our server with user, event, transaction and original transaction identifiers, app/store/environment, product/package, credit quantity, purchase time, price/currency, aliases, and refund event data. The raw webhook event may be stored in Supabase revenuecat_purchases, which is restricted to server access. Refund events update the purchase status and related credit and transaction records.
Supabase stores account credit balances and may record transaction type, quantity, description, provider, transaction identifier, amount, and currency in coin_transactions. This supports fulfillment, refunds, fraud prevention, and accurate balances.
We do not sell personal information. Service providers may process data to provide:
| Provider/category | Purpose | Data that may be processed |
|---|---|---|
| Supabase | Authentication, database, storage | Account identifiers, email, readings, credits, transactions, community data |
| Dodo Payments | Web MoR/seller, payment, tax, fraud prevention, refunds and disputes | Checkout email/name, billing/payment information, user/order/transaction identifiers, product, price, currency, payment status and technical data needed for payment |
| Apple App Store / Google Play | App billing | Store account and transaction data handled by the store |
| RevenueCat SDK/services | In-app purchase verification and management | App user ID (including its anonymous app ID before sign-in), purchase/receipt identifiers, IP address, device type and operating system technical information |
| Google Gemini API | Generate requested readings, chat, and talisman content | Prompt/question and conversation context needed for the requested feature, cards, and locale |
| Expo Updates | Check and deliver app updates on launch | Runtime/platform metadata needed for update requests |
| Hosting and email providers | Operate the service and send authentication email | Request/log information, email address, and messages |
The website loads Google AdSense, Adcash and Google Tag Manager scripts. These scripts and tags configured in Google Tag Manager may process IP address (which may be used to infer approximate location), browser/device information, cookies or similar identifiers, and page/click activity. These advertising scripts are not included in the native app code. The website source alone does not reveal every tag configured in the Tag Manager container; see the providers’ notices and your browser cookie settings.
The primary database runs in Supabase’s Sydney, Australia (ap-southeast-2) region, and the current project is on the Free plan. Its API/database log viewing window is the most recent 1 day; automated daily database backups are not included. If the operator creates a separate export, it is managed under a separate retention/deletion schedule.
Expo Updates receives update-check requests when the app launches. The native app code does not initiate push-token registration.
Providers may process data outside your country, including outside Korea, under their contracts and settings. Their legal entity, processing locations, retention periods, and subprocessors can change; consult their current privacy notices. We may disclose information when required by law or when you choose a public sharing feature.
| Data | Retention period | Deletion/retention method |
|---|---|---|
| Account, readings/chats, talismans, community content and remaining credits | While the account is active; deletion is initiated in the primary database when an account deletion request is completed | The account-deletion API removes saved content and balances and deletes the authentication account. Statutory transaction evidence is retained separately for the period below. |
| Guest session and guest readings/chats/talismans/credits | 12 months after the last verified guest-session activity | Expired records are automatically deleted daily. Returning to the app or website refreshes the activity time. |
| Completed, refunded or reconciliation-review purchase evidence and credit ledger held in our database | Up to five years from transaction processing | Minimum transaction identifiers, product, amount/currency, status/time and refund data in payment_attempts, refund records, revenuecat_purchases and coin_transactions are kept for fulfillment, balance reconciliation, refunds, fraud prevention and dispute handling, then automatically deleted daily after expiry. On account deletion we remove the account link and raw RevenueCat webhook payload first. Identifiers may remain linkable when combined with a provider’s records. |
| Failed, cancelled or other incomplete checkout attempts | 90 days from creation | Stale incomplete checkout attempts are automatically deleted daily after expiry. |
| Web buyer/payment/tax/dispute data held by Dodo Payments | Under Dodo’s published criteria: the minimum period needed for lawful purposes, including an ongoing relationship or legal retention need, the applicable claim limitation period plus two months, and any additional period needed for an active claim; no single fixed number of years is published | Dodo controls this data independently as MoR under its public DPA. Dodo says it deletes or anonymizes data after applicable periods, subject to legal-retention, dispute and fraud-prevention grounds. Meow Tarot account deletion and database cleanup do not delete Dodo-held records. |
| App-purchase customer profile and store-purchase data held by RevenueCat | Under RevenueCat’s customer-processing agreement and settings; its public materials do not specify one fixed numeric period for our end-user data | On account deletion we submit a customer-deletion request. RevenueCat queues deletion asynchronously and says deleting a customer clears its data/purchase history. Apple/Google source receipts and store records remain subject to each store’s policy and are not deleted by Meow Tarot account deletion. |
| Store account, receipts and purchase records held by Apple App Store or Google Play | Under each store’s policies and applicable law; not set or deleted by Meow Tarot | Deleting a Meow Tarot account does not delete a store account or original store records. |
| Supabase API/database/authentication logs | Under the current Free plan, the dashboard log window is the most recent 1 day | These operational logs are separate from application database records; the accessible window may change if the plan changes. |
| Supabase database backups | Automated daily database backups are not included in the current Free plan | If the operator creates separate exports, their retention and deletion depend on the destination storage settings. |
| Gemini processing records and hosting/email/payment-provider logs | Under each provider's settings, contract and policy | Our database expiry job does not delete logs held in external provider systems. See the Gemini retention note below. |
| Support emails | As needed to resolve the request and meet legal or dispute-handling duties | Subject to the email provider's retention and backup policy. |
When deleting an account, we request deletion from RevenueCat for the Supabase user ID used for in-app purchases. RevenueCat queues deletion asynchronously and says the customer profile and purchase history are deleted. If the app connects to RevenueCat again, a new anonymous customer may be created. This request does not cancel or delete the Apple App Store or Google Play account, original receipts, or store transaction records. In our own ledger, we remove the account link and clear the raw RevenueCat webhook payload, while keeping the minimum transaction date, store/provider, order/transaction identifiers, product, credits, amount, currency, status and refund information for up to five years from the transaction for refunds, balance reconciliation and disputes; expired records are automatically deleted daily. This five-year maximum applies only to our own service database, not to data held by Dodo, RevenueCat, Apple or Google. Dodo’s public Privacy Policy uses purpose-based retention, applicable legal retention and claim limitation periods plus two months, and does not publish a fixed number of years for all buyer data. Where Korean e-commerce statutory duties apply to the legally responsible seller, the Enforcement Decree provides five years for contract/withdrawal and payment/supply records and three years for consumer complaints/disputes. The responsible party may differ between Dodo web sales and Apple/Google store transactions. For rights requests concerning web buyer/payment data controlled by Dodo, contact Dodo using its Privacy Policy.
Failed, cancelled and other incomplete checkout attempts are kept for 90 days from creation and then automatically deleted.
Google may process and retain prompts, conversation context and responses sent to the Gemini API for up to 55 days for service safety and abuse monitoring. Google states that prompts and responses in its Paid Services are not used to improve products or train models; applicability depends on the API project's billing status and logging settings. Supabase’s log viewing window is separate, and the database expiry job does not delete those logs. The current Free plan does not include automated daily database backups.
Email itrounder.korea@gmail.com or use the account-deletion page to request access, correction, deletion, or restriction of data held by Meow Tarot. In the app, open My → Account settings → Delete account. Requests for web payment/billing data controlled by Dodo, or store account/receipt data controlled by Apple or Google, must be submitted to the relevant provider. Refunds may also need to be requested through the purchase provider.
In the mobile app, open My → Account settings → Delete account to request permanent deletion directly. This removes personal readings, chats, talismans, community content and remaining credits. You can also request deletion without accessing the app at the account-deletion page. Our own database keeps minimum transaction evidence separately for up to five years after removing the account link and raw RevenueCat webhook payload, then automatically deletes it. We submit a customer deletion request to RevenueCat, which queues it for asynchronous processing. Some identifiers may remain linkable to an individual when combined with provider records. Dodo-held web payment data and Apple/Google store records require separate requests to those providers.
Depending on applicable law, you may request access, correction, deletion, restriction, or withdraw consent. You may request removal of a community post through available controls or support. We may need to verify your identity. Refusing essential processing may prevent sign-in, saved history, purchases, or refunds from working.
The website may use cookies or similar technology for login sessions, Google AdSense/Adcash advertising and Google Tag Manager tags. The app stores account/guest identifiers and settings on the device. Restricting cookies may affect login, some features or ad-personalization settings. Actual tag behavior depends on provider and Tag Manager configuration.
The service is not designed for children whose data requires guardian consent under applicable law, and we do not knowingly collect their personal data. We use reasonable measures such as access controls, authentication and permission checks, secret-key protection, webhook verification, duplicate-purchase prevention, and server-only access to purchase ledgers. No internet transmission or storage can be guaranteed completely secure.
We may update this policy when the service or law changes. Material changes will be announced through the service or website, and the effective date will be updated.