AstralPause

Privacy notice

This notice explains how AstralPause handles your information when you use readings, email sign-in, optional notifications, and usage analytics.

Data controller: Ivan Mihajlovic, operating as AstralPause. Operator details.

Contact: office@astralpause.com.

Your readings

Questions matching our high-stakes topic rules receive fixed guidance without being sent to OpenAI. For other questions, your question and the dice result are sent to OpenAI to generate a reflection. The app does not store question text. The current free reading is stored temporarily to restore it on refresh and is cleared by cleanup after the weekly reset. We disable storage of the response object at OpenAI. OpenAI may still retain API content in abuse-monitoring logs, normally for up to 30 days, with exceptions for legal obligations or protecting its services and others from harm. See OpenAI’s API data controls. Avoid entering sensitive personal information.

Accounts and notifications

Sign-in uses a single-use email confirmation link valid for 15 minutes. Session cookies expire after 30 days. When you request a confirmation link, we temporarily store your email address, the purpose of the request, and a hashed confirmation token. The link expires after 15 minutes; expired token records are removed by a daily cleanup. Separately, we keep the requested email address, signup purpose, request count, and first/latest request times for 30 days after the latest accepted request to troubleshoot confirmation problems. Only the site owner can view this operational list. Confirmation removes the matching pending record; otherwise it is removed by daily cleanup after expiry. An unconfirmed request does not establish ownership of an address and is not consent to marketing. No reminder or marketing email is sent from this list. Contact us to request removal.

Confirming sign-in creates an account containing your email address. Accounts expire 365 days after the latest email sign-in and are removed by daily cleanup. Existing accounts without a recorded sign-in date receive a 365-day grace period from migration.

Under Account settings, you can permanently delete your account, sign out all its sessions, and remove its notification signup, pending requests, confirmation links, and linked usage records. This also removes the current account reading and this browser’s saved reading. Signing out or removing only a notification signup does not delete the account. Email us for help with deletion, including requests without an account. Unlinked activity from other browsers cannot automatically be identified. Short-lived pseudonymous suppression records prevent in-flight analytics from recreating deleted records for one day. Reading-limit markers and abuse counters remain until their scheduled cleanup; deletion does not provide another weekly reading. Provider-held copies follow provider retention periods separately. Resend delivers our confirmation links. Its retention is separate from the application’s retention periods below.

A confirmed waitlist entry is created only after you confirm your email and request one notification when extra readings become available. Before confirmation, the temporary email-link record described above still contains your address. Waitlist entries become eligible for deletion after 180 days and are removed by the next daily cleanup. You can sign in to remove yourself from the list, or contact us.

Aggregate page-request counts

Without using visitor identifiers for these counters, our server counts successful requests for the public homepage and guides. Each request increments a daily total for a fixed page category and, where specified in the URL, a supported language. These counters do not store IP addresses, browser or account identifiers, user-agent strings, referrers, full URLs, questions, or individual event records. To provide a separate filtered total, we transiently inspect the user-agent and prefetch headers and Cloudflare bot signals when available. Only daily counts of fixed categories (unflagged, bot, prefetch or unknown) and signal availability are retained; header values and bot scores are not stored. Filtering is approximate and does not block access. Older totals remain unclassified. We do not link requests across visits. An authorized owner report sets a fixed internal-testing cookie for 90 days to exclude that browser from our first-party page counters and optional events. It contains no unique identifier. Owner-linked browsers are excluded from visitor reports. Totals can still include bots, reloads and unmarked internal checks and are not unique-person counts. They are retained for about 90 days with daily cleanup. There is no historical backfill.

For the minimal request processing needed to produce these totals, we rely on our legitimate interest in understanding aggregate demand and maintaining the site, with immediate aggregation and no visitor identification. Cloudflare still processes network data to deliver the service. You can contact us to object to processing based on legitimate interests. Anonymous totals cannot be linked back to you or removed per visitor. Declining optional analytics stops detailed tracking, but does not stop these aggregate counters.

Optional usage analytics

We ask permission before recording detailed usage events. These include visits, practice rolls, starting/submitting a reading, reading outcomes, interest in more readings, and confirmed notification signups. We use a pseudonymous browser identifier and, where applicable, a separate pseudonymous account identifier. Analytics contains no question text, reading text, email address, or raw IP address. Identifiers are not anonymous data. With analytics consent, predefined campaign labels from tagged links are associated with these usage events to compare acquisition sources. We do not store full referral URLs or arbitrary URL parameters.

Event summaries are retained for approximately 90 days, with removal by daily cleanup. Unique-browser figures are estimates of consenting browsers, not a count of people. Changing devices or clearing cookies can affect them. Declining analytics does not affect access to readings. Use “Analytics choices” on the main page to withdraw consent; this removes analytics linked to the current browser identifier. Other browsers are not automatically identified for deletion.

Necessary storage and security

A signed browser cookie lasts up to one year to support the weekly allowance. A separate consent-choice cookie lasts six months. Daily network abuse limits use an IP-derived keyed hash, cleared by daily cleanup. Cloudflare processes network addresses when serving the site and checking Turnstile. Budget counters protect against excessive AI spending. These service/security functions are separate from optional analytics. We store your language preference in your browser; if storage is blocked, we use the choice available on the page or your browser language.

Why we process this information

We rely on performance of the requested service for readings and account sign-in, consent for optional detailed analytics and the launch notification, and legitimate interests in preventing abuse and controlling costs for proportionate security measures and diagnosing email-confirmation failures. You may object to processing based on legitimate interests and withdraw consent to optional processing without affecting its earlier lawfulness. Providing an email address is necessary for email sign-in or notification signup, but not for a browser-based free reading.

Providers and rights

Cloudflare hosts the service and provides security checks; OpenAI generates readings; Resend sends confirmation emails. These providers receive the information needed for their functions. The public site also uses Cloudflare Web Analytics for aggregate traffic and performance measurement. Cloudflare describes this service as not collecting or using visitors’ personal data. It is separate from our consent-based event analytics, and the Analytics choices control applies to our event analytics. See Cloudflare Web Analytics.

Our providers may process data outside Portugal and the European Economic Area. Their processing agreements provide safeguards for restricted international transfers, including European Commission Standard Contractual Clauses where applicable. Details are available in their processing agreements: Cloudflare, OpenAI, and Resend. Contact us to request further information or copies of applicable safeguards. Resend currently publishes a 30-day email and log retention period for its Free, Pro and Scale plans. This is separate from the application retention periods above. See Resend data protection information and Cloudflare processing terms.

You may contact us about access, correction, deletion, restrictions, objections, portability, or withdrawal of consent where applicable. You may also contact Portugal’s supervisory authority, CNPD. We normally respond to rights requests within one month. Where necessary, we may request proportionate evidence to verify the request. Astrology reflections are generated automatically for entertainment; we do not use them to make decisions with legal or similarly significant effects about you.

Updated 6 October 2026.

Paid readings and billing records

Paid reading text and dice are kept for up to 30 days and removed by daily cleanup; account deletion also removes this content once no reading is processing. Minimal request records remain to prevent duplicate credit use. Billing, tax and payment evidence is separate from optional analytics and is retained for the applicable legal period, generally 10 years for Portuguese fiscal records. Unexpired credit entitlements are retained as necessary to honour them. Contact office@astralpause.com to resolve remaining credits before account deletion and to request access or deletion of data not legally required. Stripe processes payments and Moloni processes invoices; their records and retention are separate.