Privacy Policy

1. Overview

This Privacy Policy describes how CelestKin ("we", "our", "the App") collects, uses, stores, shares, and protects your personal information. We are committed to transparency and give you control over your data.

2. Data We Collect

We collect the following categories of information:

Account Data: Name, email address, and profile photo provided through your sign-in method (email, Google, or Sign in with Apple). If you use Sign in with Apple and choose to hide your email, we receive an anonymized Apple relay address instead of your real email, and Apple provides your name only on the first sign-in.

Birth Data: Name, date of birth, time of birth (optional), birth location, and gender (optional) that you enter for chart calculations and readings. Gender is used only where a tradition's own rules depend on it: the direction in which the Chinese Luck Pillars and the Purple Star (Zi Wei) ten-year periods run, your Feng Shui personal gua number, which person is read from which side in the four Vedic match factors that are read in one direction, and which palm a palm reading treats as your active one (on our website you can choose your writing hand instead; the app does not ask). It is also included in what we send to the model that writes palm, body and dream readings. It is not used to target content or advertising, and it can be left unset. In the app, this data is stored on your device in encrypted storage. If you are signed in, it is also saved to our cloud database, where your birth profiles are not encrypted with a per-account key; the database's access rules keep them to your account.

Reading Data: Generated readings, AI analyses, compatibility reports, and cosmic digests associated with your account.

Usage Data: Reading history, selected traditions, feature interactions, preferences, language settings, screen views, and question topics.

Purchase Data: Transaction records from Google Play or the Apple App Store (product ID, purchase token, order ID, the price paid and its currency, the country of your store account, the purchase time, and subscription status) and, for purchases on our website, from Stripe (the checkout reference, the product you bought, the price paid and its currency, and the Stripe customer ID linked to your account). We never receive or store your payment card details.

Device & Technical Data: Device type, operating system, app version, crash reports, and performance metrics.

Approximate Location: Our analytics and error-reporting providers derive an approximate city and region from the IP address your device connects with. The app never requests your device's location permission, so we do not collect precise location. The birth place you type is separate — it is a place you tell us about, not where you are.

Waitlist Data: Email address collected when you sign up for launch notifications. This is stored separately from account data and used solely to send the launch email.

Feedback & Reports: When you submit in-app feedback, a bug report, or a content report, we collect your message, the kind of submission (general feedback, bug report, report of a reading, report of a match), any optional context you provide about the content being reported, your support ID, app version, device OS, and locale. This is used for customer support, quality improvement, and content moderation. Feedback is stored in our Supabase backend and reviewed by our admin team; we do not share it with third parties.

3. How We Use Your Data

• Generate personalized astrology readings (birth data is sent to AWS Bedrock for AI processing)
• Compute charts across 9 astrological traditions
• Maintain your reading history and saved profiles
• Generate daily and weekly cosmic digests (if subscribed)
• Manage your credit balance and subscription status
• Enable compatibility matching between profiles
• Send notifications (cosmic briefings, streak reminders, transit alerts)
• Improve the App through usage analytics (described in section 15)
• Diagnose and fix crashes and performance issues
• Prevent fraud and enforce our Terms of Service

4. Data Sharing

We do NOT sell, rent, or trade your personal data. We share data only with the following service providers who process it on our behalf:

• Supabase — Authentication and database hosting. Row Level Security ensures no other user can access your data.
• Amazon Web Services (Bedrock) — AI reading generation. Birth data is sent for processing and is subject to AWS's privacy policy. The models that receive your data there are Anthropic's Claude, Meta's Llama and Amazon's Nova. An image model also runs there for us, drawing some Universe Feed pictures; it is sent no data about you. Our page How CelestKin Readings Are Made lists which does what. AWS does not use your data to train models, and Anthropic and Meta do not receive it.
• Railway — Hosts our API server, the service the app and this website send requests to. It processes what those requests carry: your birth details, the questions and chat messages you send, the photos you submit for a photo reading, the readings we return, and your IP address.
• Vercel — Hosts this website. Its servers receive your IP address and each request your browser makes to celestkin.app (including your sign-in cookie when you are signed in), and run the website's own server code, such as the waitlist form, which receives the email address you enter.
• Cloudflare — Sits in front of this website: every request to celestkin.app passes through Cloudflare's network on its way to Vercel, so Cloudflare receives your IP address and the request. Cloudflare also adds its own page-load measurement script, Cloudflare Web Analytics, to the pages it delivers. It sends Cloudflare the address of the page you are on, the page you came from, and how quickly the page loaded and responded. It sets no cookies and stores nothing in your browser, and our cookie banner does not control it.
• Sentry — Crash reporting and error monitoring. No birth data and no reading content are sent. Reports are not anonymous: they carry your account identifier so we can tell whether a crash hit one person or a thousand, and our server attaches the IP address of the failing request.
• Mixpanel — Usage analytics, keyed to your account ID so we can tell a returning reader from a new one. We send feature interactions, question topics, screen views, and language — never your name, email, birth data, readings, or chart results, and that includes anything calculated from them: your sign, your star, your numbers. Mixpanel additionally derives an approximate city and region from your IP address, and records when the app crashes.
• Google Maps Platform — Birth-place lookup in the mobile app. When you type a place name, the app asks Google directly for matching locations, so Google receives what you type and your IP address at that moment.
• OpenStreetMap Nominatim (OpenStreetMap Foundation) — Birth-place lookup. On our website, when you type a place name into a profile form, your browser asks Nominatim directly for matching locations, so the OpenStreetMap Foundation receives what you type, your IP address and the usual details a browser sends with a request. Our server also asks Nominatim for the coordinates of the birth place on a profile, or one you enter in a tool, when it needs them for a calculation; that lookup gives Nominatim the place name and nothing else about you. See the OpenStreetMap Foundation's privacy policy.
• Firebase Cloud Messaging (Google) — Push notification delivery. To send you notifications we store your device's push token with your account, and for each notification we give Firebase that token and the notification's text, which can include the first name on your profile. On an iPhone, Firebase hands the notification to Apple's push service to deliver. When your account is deleted, we delete your push tokens.
• MXroute — Email delivery. The emails we send you from [email protected] (for example deletion notices and replies to messages you send us) go out through MXroute's mail servers, which handle your email address and the content of each message.
• Resend — Star Book email delivery. When you buy a Star Book, we email it to the address on your account through Resend, which handles that address and the book itself, attached as a PDF. Resend may keep sent emails for a limited time under its own retention policy. We make the PDF when it is sent or when you download it, and we do not store it.
• Google Play / Apple App Store — Payment processing for credit purchases and subscriptions.
• Stripe — Payment processing for credit purchases on our website. You enter your card details on Stripe's checkout page, so they go to Stripe and never to us; we give Stripe your email address, your account ID and the product you chose.
• RevenueCat — In-app purchase receipt validation and subscription lifecycle management. We share an opaque user identifier (your account UUID), the purchase product ID, and the store transaction reference. RevenueCat does NOT receive your name, birth data, readings, or payment card details — it only sees the receipt token already issued by the store. See RevenueCat's privacy policy.

All service providers are bound by their own privacy policies, data processing agreements, and applicable data protection laws.

5. Data Storage and Security

On-Device Security:
• Birth profiles and sensitive data encrypted via Flutter Secure Storage (Android Keystore / iOS Keychain)
• Local reading cache encrypted at rest
• All local data cleared on sign-out

Cloud Security:
• Postgres Row Level Security — each user can only access their own data
• All API communication over HTTPS/TLS
• Server-side JWT verification for every authenticated request
• Database queries include explicit user_id filtering as defense-in-depth
• Service-role keys restricted to server-side operations only
• AES-256-GCM encryption, under a key derived for your account, for the text of readings the app saves and the text of chat messages (section 13 lists what is stored without it)

5a. Data Breach Notification

No system is perfectly secure. In the unlikely event of a data breach that affects your personal data, we will investigate promptly, take steps to contain and remediate the incident, and notify affected users and the relevant supervisory authorities without undue delay, consistent with applicable law (for example, within 72 hours of becoming aware where the GDPR applies). Notifications will describe the nature of the breach, the data involved, and the steps you can take to protect yourself.

6. Data Retention

Active Accounts: Your data is retained as long as your account is active and for a reasonable period afterward to fulfill legal obligations.

Sign-Out: All local data (profiles, readings, cached charts) is immediately cleared from your device.

Account Deletion: You may delete your account in the app (open settings from the gear icon, then Delete Account) or on the web at celestkin.app/delete. By default, deletion is scheduled with a 30-day grace period. During it your account is marked for deletion. To cancel within the grace period, sign in to the CelestKin app on your phone and tap "Cancel Deletion" on the screen that appears. This website has no cancel button, so if you use CelestKin only on the web, email [email protected] from your account's address and ask us to cancel it. A guest session in the app (one with no email address or sign-in provider) is signed out when its deletion is confirmed and has nothing to sign back in with, so a guest's deletion cannot be cancelled. In the app you can also choose immediate deletion, which skips the grace period. In both cases, all user-scoped data is purged from our active systems and fully removed from backups within 60 days of the hard-delete (30-day backup retention window). A deletion audit log is kept for compliance evidence. It records your user ID and email address, a reference ID, the IP address and browser or device the request came from, timestamps, and which tables were cleared — this is the evidence that a request was made and honoured, so it necessarily outlives the account. It holds none of your readings, charts or birth details.If your account had an email address, two email records also outlive it. The address stays on our do-not-email list, with your account ID, the reason and the date, so no marketing email is sent to it again. And our log of the emails we have sent keeps, for each one, the address it went to, what kind of email it was, whether it was delivered, and when; it keeps none of the text of the message. That log is our record of what we sent to an address and when. A few other records are kept against your email address or as our own records, and deleting the account does not remove them: messages we sent you from our support outbox, with their text; the history of changes to a tester record for your address; the log of actions our staff took on your account; in-app cards our staff addressed to your account; a partner program application, a partner referral code issued to your address and monthly partner earnings statements; and the record of the device on which your account first claimed a guest welcome grant. If you want any of them erased as well, email [email protected].Downstream, we delete the push notification tokens we store for your devices, which stops the push notifications we send to them; Firebase, which delivers them, is not sent a deletion request. Our usage analytics are not anonymous: they are keyed to your account ID. Deleting your account does not yet erase them at our analytics provider, Mixpanel, automatically; email [email protected] and we will ask Mixpanel to erase them. Our crash-reporting provider has no per-user deletion API, so we stop attributing anything further to you there and request removal directly when asked. In rare cases where your account is subject to legal process (subpoena, fraud investigation), deletion may be temporarily unavailable — if this applies, the app will show a neutral "contact support" message.

Crash Logs: Automatically deleted after 90 days.

7. Your Rights

Depending on your jurisdiction, you may have the following rights:

Access: View all your data within the App (profiles, readings, history).
Correction: Edit your profiles and birth data at any time.
Deletion: Delete individual profiles, readings, or your entire account.
Export: Share readings via the built-in share feature.
Portability: Request a copy of your data by contacting us.
Restriction: Turn on Ghost Mode in the app, or Incognito on this website, to keep new readings out of your reading history (sections 10 and 13 say what they do not cover), or email us.
Objection: In the app, Ghost Mode stops the analytics events the app itself sends (section 15 says what it does not stop); on this website, declining the cookie banner keeps our analytics (Mixpanel) from starting, though not Cloudflare's page-load measurement (section 4). To object to any other processing, email us.
Withdrawal of Consent: Delete your account to withdraw consent for data processing.

For EU/EEA residents (GDPR): You have additional rights including the right to lodge a complaint with your local data protection authority. Our legal basis for processing is consent (account creation) and legitimate interest (service improvement).

For California residents (CCPA/CPRA): You have the right to know what data we collect, request deletion, and opt out of sale (we do not sell data). We do not discriminate against users who exercise privacy rights.

To exercise any right: [email protected]. We will respond within 30 days.

Canadian Privacy Rights (PIPEDA)

CelestKin is a Canadian product and complies with the Personal Information Protection and Electronic Documents Act (PIPEDA) and applicable provincial privacy legislation, including Quebec's Law 25 for Quebec residents. You may request access to, correction of, or deletion of your personal information at any time. Our privacy contact is [email protected]; you also have the right to complain to the Office of the Privacy Commissioner of Canada.

8. International Data Transfers

Your data is processed in the United States: our database and authentication provider (Supabase) runs in a US region, and the models that write readings run on Amazon Web Services in US regions. If you use CelestKin from outside the United States, your information is transferred there. These transfers are protected by standard contractual clauses or equivalent safeguards as required by applicable law.

The other providers named in section 4 also handle some of your data on their own systems: Railway, Vercel, Cloudflare, Firebase Cloud Messaging and Google Maps Platform (both Google), OpenStreetMap Nominatim, MXroute, Resend, Stripe, Mixpanel, Sentry, RevenueCat, Google Play and the Apple App Store. Their systems may be in countries other than yours, so your information may also be transferred to those countries.

9. Children's Privacy

CelestKin is not directed at children under 13 (or under 16 in the EEA). We do not knowingly collect personal data from children. If we discover we have inadvertently collected data from a child, we will promptly delete it. Parents or guardians who believe their child has provided data should contact us immediately.

10. Incognito on This Website

On this website, the Incognito button in the menu bar (it reads Private while it is on) keeps the readings and tool results you get while it is on out of your reading history: the website does not save them to your account. It does not cover Ask the Stars conversations, which are stored in your account, or the tool results our server keeps (section 13 names those tools), and it does not change what the website sends to our analytics provider. In the app the same idea is Ghost Mode, described in sections 13 and 15. Neither affects data already stored.

11. Cookies and Tracking (Web)

The CelestKin web application uses essential cookies for authentication and session management. Analytics cookies (Mixpanel) collect the usage data described in section 15, keyed to your account ID once you sign in. No third-party advertising cookies are used. You may disable non-essential cookies through your browser settings. Cloudflare, the network in front of this website, also adds a page-load measurement script (Cloudflare Web Analytics, described in section 4); it sets no cookies, and the cookie banner does not control it.

12. Automated Decision-Making

CelestKin uses language models on AWS Bedrock (Anthropic's Claude, Meta's Llama and Amazon's Nova, as set out on our page How CelestKin Readings Are Made) to generate personalized readings based on your astrological chart data. These are automated outputs for entertainment purposes. No automated decisions with legal or significant effects are made about you. You may request human review of any reading by contacting us.

13. AI Processing of Birth Data

When you generate a reading, your birth data (date, time, and location) is transmitted to Amazon Web Services Bedrock, where it is processed by a language model (Anthropic's Claude, Meta's Llama or Amazon's Nova, depending on the task; our page How CelestKin Readings Are Made lists which does what) to produce your personalized reading. The following applies:

• What is sent: Birth date, birth time (if provided), birth location, your name, your age (worked out from your birth date), and any specific question you ask; for palm, body and dream readings, also the gender on the profile, if one is set. With many readings we also send what you told us during onboarding, if you answered: why you came, how you were feeling, and a preferred tradition.
• How it is processed: Data is sent over HTTPS to the AWS Bedrock API. Per Amazon's Bedrock documentation, AWS does not use your data to train AI models, does not share it with the companies that make the models, and by default does not store prompts or outputs; our page How CelestKin Readings Are Made lists the exceptions Amazon documents.
• Reading storage: The text of a reading the app saves to your account is encrypted by our server with AES-256-GCM, under a key derived for your account, before it is stored in Supabase (PostgreSQL), and so is the text of each chat message. Stored without that encryption: the question saved with a reading and the names, birth date and place saved beside it; readings and tool results saved from this website; your birth profiles; the results of the Aura, Feng Shui, Muhurat, Sade Sati, Upcoming Clashes and Vaastu tools that our server keeps so the same answer can be shown again; a chat thread's title, running summary and list of remembered facts; and the first 120 characters of each message you send in chat (and of a reply saved after you left before it finished). No other user can access your readings, through Row Level Security. To check answer quality, our team reads a small sample of questions and answers each day: an internal report sent to our own mailbox quotes a few of the day's questions with the start of each answer. Questions flagged as a crisis are never included.
• Analytics: Usage analytics are collected via Mixpanel, keyed to your account ID. We never send your name, email, birth data, chart results, or reading content to Mixpanel.
• Error tracking: Crash reports and errors are sent to Sentry. No birth data or reading content is included in error reports.

• Palm & body images (Palm Reading feature): When you use our Palm Reading or Body Reading features, photos of your palms, hands, forehead, or feet are captured on your device and sent over HTTPS to our API server (hosted by Railway), which checks in memory that each photo shows the right thing, and then to AWS Bedrock, where the reading is made. Before any photo leaves your device, we strip EXIF data, GPS coordinates, and other embedded metadata — only the visual content is sent. These images are NEVER stored in the cloud or written to our databases, and photo data is removed from our error reports. In the app, while a reading is open, its photos are held in encrypted device storage (Flutter Secure Storage / Android Keystore / iOS Keychain) so you can ask follow-up questions without taking them again, and a follow-up question may send them again; they are deleted from your device when you close the reading or sign out, or, if the app closed before the reading did, the next time you open the app. On this website your photos stay only in the page's memory and are dropped when the reading arrives; they are never stored in your browser. Only the text of the reading is saved: encrypted when the app saves it, as plain text when this website saves it. In Ghost mode the text is not saved to your account either. We do not have access to your photos after the reading is complete.

• Biometric Information Notice: Body reading photos may be considered biometric data under certain jurisdictions (e.g., Illinois BIPA). Photos are processed solely for generating your reading, are never stored permanently, are not used for identification purposes, and are discarded by our server and by AWS Bedrock once the reading is generated. Before any photo is taken or uploaded you consent to this: in the app by tapping “I agree, let's start” on the body reading's start page, on this website by ticking the consent box. We keep a record of that consent with your account: which body reading, which version of the consent text you were shown, its language, and when you agreed (by your device's clock and by ours). The record contains no photo and nothing taken from a photo; it is kept until your account is deleted and is erased with it. You may withdraw consent at any time by not using these features.

• Age Restriction for Body Readings: Body reading features are restricted to users aged 18 and older. Both the app and the server block users under 18 from capturing or submitting biometric photos. This protects children's privacy in line with COPPA (US), GDPR (EEA), and similar laws.

Data Retention by type:
• Birth profiles: retained until you delete the profile or your account.
• Readings: stored until you delete them or your account (see Reading storage above for which parts are encrypted); server-side purge within 30 days of account deletion.
• Waitlist emails: retained until the launch notification is sent or you unsubscribe, whichever comes first.
• Crash logs: automatically deleted after 90 days.

Ghost Mode: CelestKin offers a Ghost Mode in the app (the website has a similar Incognito button; see section 10). When it is on, a reading you ask for is not added to your reading history on our servers. From app version 4.37.2 the app also keeps it only in memory on your device for the current session; in earlier versions it could be written to the app's encrypted storage on your device the next time the app saved your history. Ghost Mode does not cover chat conversations, which are stored in your account, or the results of the Aura, Feng Shui, Muhurat, Sade Sati, Upcoming Clashes and Vaastu tools, which our server keeps under your account so the same result can be shown again. It does not affect data already stored before it was enabled.

Third-party processors and their roles:
• AWS Bedrock — AI reading generation (birth data sent for processing; models: Anthropic's Claude, Meta's Llama, Amazon's Nova; an image model there also draws some Universe Feed pictures and is sent no data about you)
• Supabase — Authentication and database, including reading storage
• Railway — Hosting for our API server (everything the app and this website send to it, and your IP address)
• Vercel — Hosting for this website (your IP address, each request to celestkin.app, and what you enter in the website's own forms)
• Cloudflare — Network in front of this website (your IP address and each request to celestkin.app), and its page-load measurement script, Cloudflare Web Analytics (the page address, the page you came from, and load timings; no cookies)
• Sentry — Error and crash tracking (keyed to your account ID; no birth data or reading content)
• Mixpanel — Usage analytics keyed to your account ID (no birth data, chart results or reading content)
• Firebase Cloud Messaging (Google) — Push notification delivery (your device's push token and each notification's text, which can include your first name)
• MXroute — Email delivery from [email protected] (your email address and the content of each message)
• Resend — Star Book email delivery from [email protected] (your email address and the book, attached as a PDF, which Resend may keep for a limited time under its own retention policy; we make the PDF when it is sent or downloaded and do not store it)
• Google Maps Platform — Birth-place lookup in the mobile app (what you type and your IP address)
• OpenStreetMap Nominatim (OpenStreetMap Foundation) — Birth-place lookup on our website (what you type and your IP address) and the coordinates of a birth place for our calculations (the place name only)
• Google Play / Apple App Store — Payment processing
• Stripe — Payment processing for purchases on our website (card details, email address, account ID, product)
• RevenueCat — In-app purchase receipt validation, subscription lifecycle, restore-purchases (opaque user UUID + product ID + transaction reference only)

Your GDPR rights (EU/EEA residents):
• Access: Request a copy of all personal data we hold about you.
• Rectification: Correct inaccurate birth data or profile information at any time within the app.
• Erasure: Delete individual profiles, readings, or your entire account. Server-side data purged within 30 days.
• Portability: Request a machine-readable export of your data by contacting us.
• Objection / restriction: Opt out of analytics or enable Ghost Mode to keep new readings out of your reading history (section 15 and the Ghost Mode paragraph above say what it does not cover).

To exercise any of these rights, contact us at: [email protected]. We will respond within 30 days.

14. Third-Party AI Processing (AWS Bedrock)

CelestKin uses Amazon Web Services (AWS) Bedrock to process your readings. When you request a reading, your birth data and chart calculations are sent to AWS Bedrock, where one of the models listed on our page How CelestKin Readings Are Made (Anthropic's Claude, Meta's Llama or Amazon's Nova) writes the reading.

For body readings (palm, thumb, nail, forehead, foot), your captured photos are sent to our API server, which checks them, and then to AWS Bedrock for AI analysis. On our server they exist only in memory during the request and are discarded when the reading is generated. The app keeps them encrypted on your device while the reading is open, as described above.

AWS Bedrock operates under Amazon's data processing agreement and does not use your data for model training. For more details, including the storage exceptions Amazon documents, see our page How CelestKin Readings Are Made and AWS Bedrock's privacy documentation.

15. Analytics and Tracking

CelestKin uses Mixpanel for analytics to improve the app experience. Mixpanel collects usage data including screens viewed, features used, and reading types generated. It is keyed to your account identifier, so it is linked to you rather than anonymous.

Mixpanel does not have access to your birth data, chart calculations, or reading content — and that promise covers anything derived from them. A sun sign, a lunar mansion, a life path number or a temperament type is a chart result, however simple the arithmetic that produced it, and none of them is sent.

Two things Mixpanel does receive that are worth naming plainly: it derives an approximate city and region from the IP address your device connects with, and it records when the app crashes. In the app, Ghost mode is the analytics opt-out: it stops the analytics events the app itself sends. It does not stop everything. From app version 4.37.2, opening the app in Ghost also stops the analytics library's automatic session events, but if you switch to Ghost while the app is open they continue until the app is closed and opened again; earlier versions send them in every session and also send your account's analytics profile details, such as your sign-in method, and do not tell our server about Ghost, so the server's own analytics events, such as a partial refund or a referral claim, still go out. A refund that Google Play issues is recorded under your account ID whatever mode you are in, because that notice comes from the store.

We also use Sentry for error tracking, which collects crash reports and performance data to help us fix bugs. Sentry receives no birth data and no reading content. Its reports are not anonymous: they carry your account identifier, and our server attaches the IP address of the failing request, so that we can tell whether a fault hit one person or everybody.

16. Partner Program & Invitations

If you arrive through a partner's invitation link, we store the invitation code in your browser for up to 90 days. If you create an account in that window, the account is associated with the inviting partner so we can credit them for the introduction. Partners see only aggregate numbers about the people they invited — counts of signups and purchases, and the amounts involved — never names, emails, birth details, readings, or any other personal information.

If you apply to become a partner, we collect the details you submit (name, email, links to your audience, signature on the Partner Agreement) to review the application and, if accepted, to run the partnership — including calculating and paying your revenue share. Application data is kept private and deleted on request.

17. Changes

We may update this Privacy Policy to reflect changes in our practices or applicable law. Material changes will be communicated via in-app notification. The "Effective Date" at the top will be updated accordingly.

18. Video Consultations

When you use a live video or audio consultation, we and our real-time provider (Agora) process your live audio - and, on a video call, your live video - to connect the call. We request microphone access when a call begins, and camera access too for a video call; on a video call you may keep your own camera off, and an audio call uses no camera. Consultations may be recorded for safety, quality, and to resolve disputes or refunds. Recordings and transcripts are kept only as long as needed - currently up to 10 days - and then deleted, unless a specific recording is under an active dispute, safety investigation, or legal hold. The astrologer never receives your name, email, phone number, account details, photo, or birth date, time or place. When you start a call you choose the profile the reading is for; our servers compute that profile's astrological charts from its birth details and share only those charts, and your question if you add one (with any contact details removed), with the astrologer. Because a chart is derived from birth details, someone with astrological expertise could estimate an approximate birth date from it. The astrologer can view the charts only while the call is ringing, during the up to 3 minutes they may take to review them after answering, and while the call is in progress. You are not charged for that review time and may cancel during it, and we delete the charts from the call when it ends. Astrologers must keep what they see confidential, must not try to identify you, and must not use it outside the session. We process session metadata (date, duration, amount) for billing, tax, and accounting, kept longer as the law requires. The astrologer reads these charts in the CelestKin app, which also offers AI-assisted insights and talking points to help them prepare their guidance; the guidance they give remains their own. Any text messages you send during the call are stored to run the chat and help resolve disputes, and are deleted with the call record or when you delete your account. Questions: [email protected]

19. Contact

Data protection inquiries: [email protected]