Privacy Policy
Last updated: 2026-11-16
What we collect
On the landing page, before you buy anything, we ask for your email in the hero, pricing, and footer sections. If you never complete a purchase, we keep that email to follow up about the Profile, and to reach you at hey@cyclecompass.app if you ask us to delete it.
When you buy a Profile, we collect your full name and the birth data the chart is calculated from: birth date, birth time, birth city, and the latitude/longitude we resolve from that city (via its GeoNames id). Your full name also feeds the numerology calculations (life path, expression, soul urge). Purchasing does not require creating an account — we identify your purchase by the email you pay with.
How we use your email, and why
We use the email you give us for these purposes:
- To deliver your Profile once you buy it — necessary to perform that purchase.
- When you submit your email on the home page, we send up to two reminders about an unfinished purchase, with an unsubscribe link in each email.
- To send occasional communication about Cycle Compass itself — the same legitimate-interest basis, with the same opt-out at hey@cyclecompass.app. A separate, opt-in newsletter is planned; subscribing to it will be a deliberate choice, unchecked by default.
- If you get the free monthly reading and do not subscribe, from the 25th to the end of that month we send you one email offering the next reading, with a link to stop emails. It is not sent if you have paused emails or unsubscribed.
Third parties that process your data
We work with the following processors:
- Stripe — payment processing. We never see or store your card number.
- Resend — delivery of your Profile and purchase reminders by email.
- Cloudflare — Turnstile anti-bot check on the email and purchase forms. It sets no cookie; it reads browser signals and your IP address to tell people from bots.
- Vercel — our hosting provider also counts visits (Web Analytics) and measures page speed (Speed Insights), as aggregate statistics. This runs for everyone, without asking, based on our legitimate interest (LGPD art. 7, IX) in measuring audience and performance; it sets no cookie. To object, write to hey@cyclecompass.app. Per Vercel, a visitor is a code calculated from the request (which includes the IP address) and discarded after 24 hours. Vercel records your approximate location (city in Web Analytics, country only in Speed Insights), browser, operating system and device type. Details in the privacy pages of Vercel (Web Analytics) and Vercel (Speed Insights). We strip the query string and access tokens from page addresses before they are sent.
- PostHog — usage analytics, session recording and technical error reports, on its United States region. If you accept the "Analytics" cookies, it receives: the pages you open (clean address, with no parameters or access codes, and the page you came from); the ad campaign you came from (utm_ tags); the steps of the purchase and its value; the errors the forms report (which field failed, never what you typed) and, if a page fails to open in your browser, a technical report of that error, with emails and access codes masked and the message shortened; how long you wait for your Profile after paying and whether you contacted support; and a recording of the home and buy pages, with every typed field masked and the city suggestions and the payment area blocked, and of your customer area, with all the text on the screen hidden (only the layout, scrolling and clicks are recorded, never your name, birth details or the text of your Profile). If you decline, it only counts the visit, with no cookie or browser storage (see "Cookies and consent"). Technical errors on our servers are always sent, with emails and access codes masked and the message shortened; when the error belongs to a Profile, with its internal identifier. We also always send technical metrics of the Integrated Reading generation (time and tokens, without the text), with a pseudonymous code of the Profile, with no name, email or birth details, and technical reports of content your browser blocked for security, with clean addresses (no parameters or access codes). We never send PostHog your name, email, birth data or account id. PostHog records your location only down to the country, and your IP address is not stored.
- Anthropic — writing of the monthly reading and, optionally, of the Integrated Reading (first choice), with pseudonymized chart and number data (see "Optional AI processing").
- DeepSeek — writing of the monthly reading and, optionally, of the Integrated Reading (backup when Anthropic fails), with pseudonymized chart and number data (see "Optional AI processing").
- Our hosting provider and database, which store your account and Profile data.
Advertising measurement (Meta)
If you accept the "Advertising" cookies, we load the Meta Pixel, from Meta Platforms, Inc. (Facebook and Instagram). Its purpose is to measure which ads lead to a purchase or to a monthly reading request. Only on the home pages, the buy page, the monthly reading page and the payment-confirmation page. Meta receives the address of the page, the cookies _fbp and _fbc, your browser and IP address, on a purchase its value and currency, and on a monthly reading request only that it happened. The Pixel does not send your name, email or birth data. Meta may link these events to your Facebook or Instagram account, if you have one, and use them for advertising, under Meta's privacy policy. The data goes to Meta servers, including in the United States, an international transfer under LGPD art. 33. If you decline, or later withdraw, none of this happens: the Pixel stops sending events and the _fbp and _fbc cookies are deleted. The Pixel only loads once we have set it up with Meta.
If you accept "Advertising" and buy, we also send Meta the purchase from our servers, once the payment is confirmed (with Pix, that can be hours later, even if you have closed the page). Meta receives your email and a code that identifies you in our system, both only as a SHA-256 hash (a scrambled code that cannot be read back, but that Meta can match against its own users), your IP address and your browser (user agent) as they were when you started the payment, the _fbp cookie and the identifier of your click on the ad (_fbc), and the value and currency. We never send your name or birth data. This is decided when you start the payment: if you withdraw "Advertising" afterwards, that purchase is still sent. Purchases made in test mode are not sent. Meta may link it to your account and use it for advertising, as described above, and the same international transfer (LGPD art. 33) applies. If you decline, none of this is sent.
Cookies and consent
The only cookie we set without asking is the one that keeps you logged in — see "What we collect" above. The Analytics category is off until you turn it on, and so is advertising. The advertising category sets the Meta cookies _fbp and _fbc (up to 90 days) — see "Advertising measurement (Meta)".
We manage that choice with vanilla-cookieconsent, an open-source library that runs entirely in your browser: no visit or choice you make in the cookie banner is sent to us or to anyone else. Your decision is stored on your own device, and nothing outside the essential cookie above loads until you accept that category, except the cookie-free visit count from Vercel, which always runs, and PostHog's cookie-free count, which runs only after you decline, both described in "Third parties that process your data".
The "Analytics" category is for PostHog. If you accept it, PostHog receives what is listed in "Third parties that process your data", and stores cookies and browser storage whose names start with "ph_", deleted if you withdraw. If you decline, PostHog only counts the visit, with no cookie or browser storage: on its servers, it calculates a code from your IP address and your browser, with a key that changes every day and is then deleted, so the same visitor cannot be followed from one day to the next. The IP is used only for that calculation and is not stored. No recording and no visitor profile. Either way, PostHog receives the technical errors on our servers, with emails and access codes masked and the message shortened (and the internal identifier of the Profile, when the error belongs to one); the technical metrics of the Integrated Reading generation (time and tokens, without the text), with a pseudonymous code of the Profile; and the technical reports of content your browser blocked for security, with clean addresses. If you accept, it also receives a report of an error that stops a page from opening in your browser.
If you accept "Analytics" and continue to payment, we also save a random identifier made by PostHog (ph_id) in the Stripe payment session, next to your email, to link the purchase to the visit. Because it sits next to your email, it is pseudonymized data, not anonymous, and Stripe receives it. Without that acceptance, no such identifier exists.
If you accept "Advertising" and continue to payment, the Stripe payment session also stores, next to your email, your IP address, your browser (user agent), the Meta cookies _fbp and _fbc and the identifier of your click on the ad, so the sale can be tied to that ad. Stripe receives them. Without that acceptance, none of them is stored. The campaign marks of the link (utm_source, utm_medium, utm_campaign, utm_content and utm_term) are always stored, with or without acceptance, because they describe the campaign, not your browser.
You can change your mind at any time — the "Cookies" link in the footer reopens the same panel you saw on your first visit, with no fewer steps than accepting.
Optional AI processing
By default, the text of your Profile comes from a pre-written knowledge base, and no data goes to an AI provider. An optional layer, controlled by a switch on our side, asks Anthropic (Claude) to write the Integrated Reading, the closing part of your Profile, and falls back to DeepSeek if Anthropic fails. When the switch is off, nothing is sent to either.
What Anthropic or DeepSeek receives: the positions in your birth chart (planets by sign and house, rising sign, midheaven, house cusps), the aspects between planets, and your numerology numbers. It does not receive your name, email, birth date, birth time, birth place, coordinates or exact degrees. Where the text needs your name, the AI writes a marker and we put your first name in on our side.
This data is pseudonymized, not anonymous: it is derived from your birth data, so it is still personal data under the LGPD. DeepSeek processes it outside Brazil, an international transfer under LGPD art. 33; we treat Anthropic the same way.
We keep each attempt made to DeepSeek or Anthropic (the answer it returned and the checks that approved or rejected it) for 90 days, to study the quality of the text; a daily job deletes older ones. The text that goes into your Profile stays with your Profile.
The monthly reading of the newsletter is also written by Anthropic (Claude), with DeepSeek as a backup, and it does not depend on that switch. For it they receive the same chart and number data, the text of your Profile with your name removed, the cycles and transits calculated for you for the month, and a short summary of the themes of your previous readings. We remove your name from the Profile text before sending, and we do not send your email. This data is pseudonymized, not anonymous, and is processed outside Brazil (LGPD art. 33).
International data transfer
The following processors handle data outside Brazil: Vercel (hosting the site and app), Stripe (payment processing), Resend (email delivery), and Cloudflare (anti-bot check). Each of them makes standard contractual clauses or an equivalent transfer mechanism available for international transfers, and we are in the process of formalizing that coverage. Anthropic and DeepSeek (optional AI processing) also process data outside Brazil; see 'Optional AI processing' above. PostHog (usage analytics, session recording and error reports) runs on its United States region; sending data there is an international transfer under LGPD art. 33.
Our database runs on Supabase, hosted on AWS in the Canada (Montréal) region — so this data also leaves Brazil, under the same kind of safeguard we described for the processors above (standard contractual clauses or an equivalent mechanism).
Your rights over your data
Under LGPD art. 18, you have the right to: confirmation that we process your data; access to it; correction of incomplete, inaccurate, or outdated data; anonymization, blocking, or deletion of unnecessary or excessive data; portability to another provider; deletion of data processed under your consent; information about who we share your data with; information about your right to refuse consent and what that means; and revocation of your consent.
Write to hey@cyclecompass.app to exercise any of these. If you're logged in with a magic link, /perfil also lets you export or delete your data directly — see 'Export and deletion' below.
Data protection officer
Under LGPD art. 41 and ANPD Resolution CD/ANPD 2/2022, which relaxes the formal appointment requirement for small-sized processing agents, our data protection contact channel is hey@cyclecompass.app.
Revoking consent
Revoking consent is as easy as giving it (LGPD art. 8 §5). For anything you have opted into, write to hey@cyclecompass.app to revoke it — your message is the record, and we stop that processing from then on.
Automated decision-making and profiling
Your Profile is an automated definition of a personality profile, built from your birth date, time, and location, plus your full name (LGPD art. 20). The astrology reading comes from a pre-written knowledge base matched to positions calculated with the Swiss Ephemeris, and the numerology reading is calculated from your name. The Integrated Reading that closes your Profile can be written by Anthropic or DeepSeek, and so is the monthly reading of the newsletter; see 'Optional AI processing'. Write to hey@cyclecompass.app if you want a human to review how your Profile was generated.
Export and deletion
Log in with a magic link and use your private account area to export or permanently delete your data yourself — this covers your full name, birth details, and the generated text and PDF of every Profile you've received, not just your account info. The export also includes your monthly reading data, granted editions, renewal and delivery status. It does not include the reusable editorial text of the internal Profile; a purchased Profile remains available through its existing access. You can also write to hey@cyclecompass.app to request help.
Retention
We keep the generated PDF of your Profile stored in our database so we can resend it to you if you lose it, until you ask us to delete it as described above.If you claim a free monthly reading, deleting your account removes the reading and birth details, but retains a keyed fingerprint of birth date, time and city to prevent a second free claim. It contains no name or email. This fingerprint is pseudonymous personal data, not anonymous data; contact hey@cyclecompass.app to request review.If you request the monthly reading and do not confirm your email, we send a single reminder and delete the request, with its birth details, 7 days after the last email. The email you typed is kept for occasional communication about Cycle Compass, with the same opt-out at hey@cyclecompass.app.For billing reconciliation, we retain a minimal technical record with the deleted account and checkout IDs, provider customer, renewal and invoice IDs when available, edition, amounts, currency, consent confirmation, status and dates. It remains after cancellation confirmation and has no automatic purge. A message already sent before deletion cannot be recalled.Separately, for a paid monthly edition, we retain the provider invoice ID, amount, currency and dates as a transaction record without an account link in that record or automatic purge.
Contact
Questions about this policy or your data: hey@cyclecompass.app.