Privacy policy

1. What we collect

My Chart Check collects only what's needed to compute your birth chart and deliver your reading: your birth date, birth time (if you provide it), and birthplace; the optional name, question, and context you provide; and the natal chart the system computes from these inputs. We do not require account creation, and there is no login or profile, and we don't ask for your email on the site (if you buy, Whop collects it as the payment processor and we don't keep it; see section 9). If you only look at your free chart, your birth data is used to compute it and is not saved. When you start a checkout, we keep your birth data under a random checkout reference for up to 7 days, so the reading can still be generated if your payment takes a while to confirm or you come back to your link later or on another device. If you buy a reading or horoscope, we keep your birth data with the order for 30 days, and a note of which checkout reference the payment belongs to, so the reading can be generated and replayed from your link, even from another browser (see section 6).

2. Cookies and local storage

We use a short-lived browser cookie (pendingChart, or pendingMatchfor the couple reading) to carry your birth data and any question from the preview page to the result page during checkout. It expires after 24 hours. We use localStorageto remember small preferences and prevent duplicate ratings. When you compute a free chart, we also keep a copy of its computed placements in your browser's localStorage(mc_last_chart: signs, degrees, houses and aspects, and whether a birth time was given; never your name, birth date, time, place or coordinates) so the site can offer "See your last chart" when you come back. It never leaves your device; the "Forget" button next to that link, or clearing this site's data, removes it. Right after you submit the birth-chart form, a one-time session flag (mc_reveal) plays the short "Big Three" animation once and is deleted. The share buttons are plain links to the networks' own share pages: they load no third-party scripts. What they share (the text, the image and a public page address such as /big-three/leo-pisces-virgo/) contains only your Sun, Moon and rising signs, never your name or birth details, and nothing about it is stored on our side. No third-party tracking cookies are set by our application. We count anonymous page and funnel events (for example, how many people opened the birth-chart form this week) in our own database; these counts carry no identifier and we never store IP addresses with them. Your browser also keeps a small note in its session storage (mc_land, gone when you close the tab) about how your visit began: the kind of page you arrived on and its language (for example "zodiac date page · es"), the website name of the page that linked to it (for example google.com), the link's utm_source label if it had one, and, if you came from one of our sister sites, a short tag naming where you clicked there (for examplesrc=tarot-footer). The note is sent along when you start a chart, when your chart is shown, when the reading offer comes into view and when you start a checkout. Our server keeps only kinds: the page section, the language, the kind of source (search engine, social network, AI assistant, one of our sister sites, direct or other), the device type (phone, tablet or computer) and the country code. It never keeps the website name, the label or the tag themselves. A link in one of our emails carries a tag such assrc=email-november; the server keeps only that the visit came from an email, never the campaign name. The note also records, in your browser, how fast the first page loaded (good, needs improvement or poor) and whether you interacted with the site (a tap, click or key press, or 10 seconds with a page on screen; never what you clicked or typed); it is also sent once when that first interaction happens. For a visit from an AI assistant, the server also keeps which one (ChatGPT, Perplexity, Claude, Gemini, Copilot or other). These kinds are only added to daily totals. When you start a checkout, those kinds are kept with the order reference for 7 days, or 30 days once you have paid, to learn which pages lead to readings. When a payment is counted, one line with the page section, language, kind of source, device type and the product is stored under the first 8 characters of the payment number for 400 days, so it can be matched with the payment record. That line holds no name, email address, birth data or IP address. 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. 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. Visiting a page with ?track=off sets an optional no_track preference cookie (1 year) that stops us counting your visits; ?track=on removes it.

Visit statistics without cookies. Each page you open sends us its address (without the query string), the address of the page that linked to it and, if the link had one, its utm_source label and a src tag from one of our sister sites (only tags of a fixed form are read; the server keeps just the fact that the visit came from a sister site). Our server reduces these to aggregate daily counts: pages are grouped by page type (for example "Spanish zodiac date page", not the date itself), the linking page is reduced to its website name (for examplegoogle.com) and a category (search engine, social network, AI assistant, direct, other), your browser's user-agent string is reduced to "mobile", "tablet" or "desktop", and the country comes from the country code Cloudflare attaches to the request. To count unique visitors and visits (a visit ends after 30 minutes without activity), the server combines your IP address and user-agent string with a random value that changes every day and turns them into a one-way hash; the random value is deleted after about 26 hours, so a hash can't be traced back to you or linked across days. The hash is kept for 30 minutes after your last page view to recognise the same visit, and the IP address and user-agent string themselves are never stored. Your IP address also feeds short-lived rate-limit counters against abuse, kept for at most an hour. We also count how long pages stay visible, summed per visit into ranges such as "1 to 3 minutes", and how many visitors interacted with a page (counted with the same daily one-way hash).

Page speed. To keep the site fast we measure how quickly pages load and respond in your browser (Google's open-source "Web Vitals": loading, interactivity and layout-shift timings) on every page view. These numbers are sent with the page type only and added to daily totals. When a tap or key press responds slowly, we also note which kind of control it was (for example "date field" or "buy button"), never what you typed or chose. The measuring script is served from our own domain; no third party receives the data.

None of this uses cookies, and none of these counts is linked to your birth data or to any identifier. The only link to an order is the one described above: the kinds of page, language, source, device and country kept with a checkout and with a counted payment. Opting out with ?track=off stops these counts too.

3. AI processing

Your chart data and question are sent to Anthropic's Claude API to generate a personalized interpretation. Anthropic processes this data per their privacy policy. We don't keep the prompt. The reading text we get back is stored with your order for 30 days so your link can replay it (section 6), then deleted automatically. The same goes for follow-up questions you ask about a reading and their answers: they are kept with that reading and deleted with it.

4. Payments

Payments are processed by Whop, which acts as merchant of record for card processing and settlement only; we are the seller of the readings. Whop collects payment details directly — we never see your card number. With each checkout we send Whop only the random checkout reference and the product name, never your birth data, so a paid order can be matched to its reading. Whop holds your email address and account details as the payment processor; we keep only the order details and a one-way buyer code (section 9). See Whop's privacy policy.

5. Geocoding

When you enter a birthplace, we use OpenStreetMap's Nominatim service to convert it into coordinates. The place string is sent to Nominatim. No personal information is associated with the lookup.

6. Paid readings and shared links

Paid readings. For each reading or horoscope you buy, we store the birth data you entered (and any name and question) and the generated text, including any follow-up questions you ask about the reading and their answers, under your order's payment reference, for 30 days, then delete them automatically. This lets the result page generate your reading even if you return from checkout in another browser, and replay it, with those answers, from your link. Anyone holding that link can see the reading, so treat it like a private link.

Couple reading. For a couple reading you enter another person's first name and birth details. Only do this with their knowledge. Their data is handled exactly like yours.

Shared links.If you choose to create a share link for a reading (a /r/{token} URL), we store the name you entered, the birth data used, and the reading text in our Redis store so the link resolves. These share records are kept for 30 days and then deleted automatically. Anyone with the link can view that reading, so only share it with people you trust.

7. Hosting and delivery

The site runs on servers rented from Hetzner Online GmbH in Germany, where the data described above is stored. Cloudflare delivers the site and protects it from abuse, and in doing so processes connection data such as your IP address. SeeHetzner's andCloudflare's privacy policies.

8. Your data rights (GDPR)

Data controller. My Chart Check is an independent project operating mychartcheck.com. It is the controller for the personal data described here.

What we process. The personal data we handle is your birth data (date, optional time, and birthplace) and any name, question, or context you choose to add. We use this solely to compute your chart and generate the reading you asked for.

Legal basis. We process this data on the basis of your consent and to perform the service you requested. You provide the data voluntarily; if you don't, we can't compute a chart.

Retention. There is no account system. The intake cookie expires after 24 hours. Birth data kept for an unfinished checkout is deleted after 7 days, so a payment that confirms late can still be delivered. Paid orders (birth data, name, question, reading text, follow-up questions and their answers, and the link between a payment and its checkout reference) and share links are deleted after 30 days. Birthplace look-ups are cached as place names only, with nothing linking them to you. Beyond that we keep only anonymous, aggregate counters (for example, how many readings ran in a week) that are not linked to you. Weekly totals, and the daily visit, page-speed, sales and AI-usage totals, are deleted automatically about 13 months (400 days) after the week or day they count, so we can compare a period with the same period a year earlier; daily error counts are deleted after 60 days.

Your rights. You have the right to access, correct, or erase your personal data, and to withdraw consent. Because we don't run accounts, the practical way to exercise these rights — for example, to delete a share link before its 30 days elapse — is to email us with the link or details, and we'll action it. Contact[email protected].

9. Buyer records, retention and your requests

If you buy something, Whop holds your email address and account details as the payment processor. We keep a one-way buyer code (below) and the order details (product, date, amount, and any refund or dispute) for 730 days, to count repeat purchases, handle refunds and disputes and answer support. We don't keep a customer record with your email address. 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.

• Order details and the buyer code: 730 days.
• Birth data, readings and follow-up answers 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] from the address you used at checkout, or send the payment ID or link from your order, so we can find your order. We answer within one month. Deleting removes the order content on our servers (birth details, the reading, its follow-up answers and its share links); 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.

10. Contact

Questions: [email protected]