Privacy Policy

Last updated: November 1, 2026

Introduction

My Day Check ("we," "us," or "our") operates the website mydaycheck.com. This Privacy Policy explains how we collect, use, and protect your information when you use our service.

We are committed to protecting your privacy. We do not create user accounts, do not use tracking cookies or advertising, and collect only the minimum information necessary to deliver our service.

Information We Collect

Payment Information

When you purchase a tarot reading, your payment is processed by Whop, which processes the card payment and settlement as merchant of record; we are the seller of the readings. Whop collects your email address and payment details to process the transaction, and passes us your Whop account id, email address and order details (see Buyer Records below). We do not directly collect, store, or have access to your full payment information. Please refer to Whop's Privacy Policy for details on how they handle your payment data.

Question Text

If you provide a question for your tarot reading, that text is sent to an AI service provider (USA) to generate your personalized interpretation. When you start a checkout, we keep your question (and any context you add), the cards and the spread on our server under a random checkout reference for up to 7 days, so the reading can still be written if your payment takes a while to confirm, or if you open your result link later or on another device. Once you have paid, we keep them with your order for 30 days, together with a note of which checkout reference the payment belongs to, and the generated interpretation for 30 days under your payment reference, so your result link still works if you reload or come back. All of it is then deleted automatically.

Card Selection Data

The cards you draw and the spread you choose are used to generate your reading. This data is temporarily stored in your browser (session storage and a short-lived cookie) while you check out, and on our server with your order as described above. While a checkout you started is open, your browser also keeps the drawn spread in session storage (for up to 12 hours, or until you close the tab), so reloading the page or coming back from the payment page shows the same cards.

Oracle Coin

The question you type into the Oracle Coin never leaves your browser. To recognise a repeat question, we keep only a short one-way hash of it (not the text) and the answer it got in your browser’s session storage. It is ignored after 10 minutes, cleared the next time the page loads, and deleted when you close the tab.

Cookies

We use one functional cookie (pendingReading, up to 30 minutes) to temporarily store your reading data (selected cards, spread type, and question) between the card drawing page and the results page. This cookie is:

  • Created when you complete your card selection
  • Used only to deliver your reading
  • Automatically cleared after your reading is generated
  • Not used for tracking, advertising, or analytics
  • If you visit a page with ?track=off, an optional no_track preference cookie (1 year) stops us counting your visits; ?track=on removes it

We do not use any tracking cookies, advertising cookies, or analytics cookies.

Third-Party Services

Whop (Payment Processing)

Whop processes the card payment and settles it with us, acting as merchant of record for card processing and settlement only; we are the seller of the readings. Your email and payment information are subject to their privacy policy. With each checkout we send Whop only the random checkout reference and the product name ("reading"), never your question or cards, so a paid order can be matched to the reading it paid for.

AI Interpretation Service

Your question text and card data are sent to an AI service provider (USA) to generate personalized tarot interpretations. The provider processes it under its own privacy policy.

Hetzner (Hosting)

The site runs on servers rented from Hetzner Online GmbH in Germany, where the limited data described in this policy is stored.

Cloudflare (CDN and Security)

Our website is served through Cloudflare, which provides content delivery and security services (CDN/WAF). Cloudflare may process standard connection data (such as IP addresses) as part of delivering and protecting our website, and gives us cookieless, aggregate visit statistics (Cloudflare Web Analytics). Please refer to Cloudflare's Privacy Policy for details.

Data Storage and Retention

We do not maintain user accounts. For a checkout that is started but not paid, the question, cards and spread are kept for up to 7 days under the random checkout reference, so a payment that confirms late can still be delivered. For each paid or free reading we keep the generated interpretation for 30 days under its payment reference, so the result page can replay it if you reload or return, the question, cards and spread (and, for a paid order, the link between the payment and its checkout reference) for the same 30 days, and a payment record (payment ID, amount, currency and time) for 730 days so we can help if a reading goes missing and handle refunds. All of it is deleted automatically. Whop, our payment processor, holds your email address, your Whop account details and your payment details; we do not store your email address.

User Accounts

My Day Check does not require or offer user accounts. You do not need to register, create a profile, or provide personal information beyond what is needed for payment processing; the buyer code and order details described under Buyer Records are not an account and you cannot log in to them.

Analytics and Tracking

We do not use Google Analytics, advertising pixels or tracking cookies. We count anonymous, aggregate events (for example, how many people opened the question page this week) in our own database; these counts carry no identifier and we never store IP addresses with them, and Cloudflare gives us cookieless visit statistics.

Our own visit statistics are cookieless and aggregate. When a page loads, our server counts per day: page views, unique visitors, visits (a visit ends after 30 minutes without activity), visits that viewed only one page, roughly how long a visit lasted (in ranges such as "30–60 seconds"), the type of source (for example a search engine, social network or direct visit) and the referring website's domain name (never the full address), the first page of the visit (without its query string), the device type (mobile, tablet or desktop), the page language and the country, which Cloudflare derives from the connection. To tell visitors apart within a single day without cookies, we compute an anonymous one-way hash of your IP address and browser user-agent combined with a random value that changes every day; the random value is discarded after about a day, so hashes from different days cannot be linked, and neither your IP address nor your user-agent is stored. The hash is kept only as a visit marker that expires 30 minutes after your last page view, and in a unique-visitor counter that cannot be read back as a list. We also count, per page type, browser loading-speed timings (Core Web Vitals: how quickly the page appears and responds, and how much it shifts while loading), measured on every page view by a small script served from our own site. For paid readings we add up the number of orders and the amount paid per day, and we record how much we use the AI service that writes readings (number of requests, their size in tokens and how long they take). These daily totals are kept for about 13 months and then deleted automatically. Visiting any page with ?track=off stops the visit and speed counting for your browser.

On the first page you open in a browser tab, we keep a small note in that tab's session storage (md_landing): the section and language of that page, the domain name of the site that sent you there, the campaign name in the address if there is one (utm_source), and a short tag when you came from one of our sister sites or from a link in one of our emails. Later in the visit it also notes how fast that first page loaded (fast, moderate or slow) and that you interacted, once you tap, click or type or the page has been open in front of you for 10 seconds; a separate note (md_eng) makes sure that is counted only once per tab. It goes away when you close the tab. It is sent with a few steps of the reading and numerology flows (cards drawn, offer seen, calculation shown) and with a checkout, and our server keeps only kinds from it: the page section, the language, the kind of source (for example a search engine, a social network, an AI assistant, one of our sister sites or one of our emails) and the device type, plus the country (from the code Cloudflare attaches to the connection; no IP address is stored), which AI assistant sent you when one did (for example ChatGPT or Perplexity), the loading-speed class and whether you interacted. The domain name, the campaign name and which email you came from are not stored. We also count per day how many visitors interacted, in a second counter of the same kind as the unique-visitor counter described above. When you start a checkout, those kinds are kept with the order, to learn which pages lead to readings. For each purchase we keep one row with those kinds and the product, filed under the first 8 characters of the payment number so it can be matched with the payment record; it is deleted with the daily totals after about 13 months. So that each payment is counted only once, we also keep a record for the payment itself (counted_payment: the full payment number, the day, the product, those kinds and the amount) for 40 days. The tab also keeps notes that are never sent to us: md_once:* (that a step was already counted in this tab, for example a question already drawn, kept as a short code: your question, name or date is not stored as text and never leaves your browser) and md_tool_tarot (whether the cards you drew have been counted as seen). They go away when you close the tab.

If a page fails in your browser, it sends us an anonymous error report (the error message, the page address without its query string and a coarse browser family such as "Chrome on mobile"), kept for at most 30 days. We do not build user profiles or share data with advertisers. Our web server also keeps a short technical request log (the page address without any query string, the response status and timing, and the browser's user-agent string) with no IP address, cookies or referrer, kept for at most 7 days to spot errors and slow pages.

Buyer Records, Retention and Your Requests

If you buy something, Whop, as our payment processor, holds your email address and your Whop account details; we do not keep your email address or a customer record. From Whop we use your Whop account id and the order details. We keep a one-way buyer code (below) plus the order details (product, date, amount, refunds and disputes) for 730 days, to count repeat purchases, answer support and deletion requests and handle refunds and disputes. Our legal basis is the contract (delivering your purchase) and our legitimate interest in support, preventing fraud and understanding repeat purchases. You can object to the legitimate-interest part at any time.

Buyer code. To count repeat purchases across the My Self Readings sites (My Chart Check, My Day Check and My Personality Check), we make a buyer code from your Whop account id: a one-way code that cannot be turned back into the id or your email address. It is kept for 730 days, like payment records.

AI usage records. We log each AI request by purpose (for example "reading" or "report") with its size in tokens, how long it took and its estimated cost, to watch our costs. The log holds none of your answers, question, scores, birth details or the text that was written. It is kept as daily totals for about 13 months, like our other visit statistics, which stay cookieless and aggregate as described above.

How long we keep it.

  • Payment records, order details (product, date, amount, refunds and disputes) and the buyer code: 730 days.
  • Your email address and Whop account details: held by Whop, not stored by us.
  • Question, cards, spread and reading of an order: 30 days (7 days for a checkout that is not paid).
  • Daily visit, sales and AI-usage totals: about 13 months.
  • Backups: anything deleted on request is gone from backups within 14 days.

Your requests. You can ask for access to your data, a copy, correction or deletion, and you can object to its use. Email [email protected] with the payment ID or the link from your order (or from the address you used at checkout, which we look up with Whop), so we can find your orders. We answer within one month. Deleting removes the order content and your buyer code on our servers; a minimal record of the payment (amount, date, refund status) may stay until its 730 days are over, because we may need it for claims and accounting. Whop is a separate controller for the data it holds: ask Whop for that. If you are not happy with our answer, you can complain to the Lithuanian data protection authority (VDAI, vdai.lrv.lt) or to your local one.

Children's Privacy

Our service is not intended for individuals under the age of 18. We do not knowingly collect personal information from children.

Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated "Last updated" date.

Contact Us

If you have questions about this Privacy Policy, please contact us at [email protected].