Privacy Policy

For the Regares app and the pages of this site about it.Last updated: 14 October 2026

This Privacy Policy explains how P and A LLC (“we”, “us”), a company registered in the Republic of Kazakhstan and trading as Panda LLC, handles your information when you use the Regares mobile application (the “App”) and the pages of pandallc.dev about it.

Contact for privacy matters: privacy@pandallc.dev

Regares 1.1 and the redesigned app

This section describes the redesigned client, including its test releases. The sections below it describe the earlier Regares app, which remains in use. Where their features differ, use the section for your version.

Accounts and saved data

You can explore an identified sample chart without signing in. To save a personal cloud profile, use Apple or Google on iOS, or Google on Android. The redesigned app has no email/password registration and does not create a personal anonymous cloud account merely for viewing the sample. We receive your provider identity and, where supplied, your email or Apple’s private relay address.

We store the birth details you enter, calculated charts, saved people, compatibility results and personal readings in your account. Enter another person’s details only with their permission. Previous Regares profiles, purchases and reports can be associated with your new account after verified sign-in; we do not give you access to another person’s records based on an unverified email address.

Notes and saved places are stored locally, separately for each account, and do not sync between devices. Today provides rotating reflection prompts from natal placements, not a live transit forecast. The new interface does not provide the earlier app’s assistant conversations, tarot, numerology, daily-horoscope notifications or data-export screen.

Supabase provides authentication, database and private file storage for the redesigned app. Render hosts its API and calculation workers. Google Firebase and Google Cloud remain involved in verified recovery of previous accounts, purchase ownership and reports, in legacy report services, and in deletion of linked previous-app data. RevenueCat, Apple and Google process purchase records and subscription access; we do not receive card details. RevenueCat receives account/purchase identifiers, not your birth details. The astrology computation service processes the birth data needed for requested calculations.

For a personal AI interpretation, the reading screen asks permission to send calculated planetary positions and their connections to OpenAI. For this new reading feature, we do not send your name, birth date, birth time or city. The generated reading is saved in your account. You can withdraw consent and delete the reading from that screen. Without permission, the app does not generate this personal AI reading; your calculated chart and reference material remain available.

OpenAI API data is not used for model training by default. We disable response storage for these requests; OpenAI may retain abuse-monitoring logs for up to 30 days, with legal exceptions. See OpenAI API data controls. These statements about the new reading payload do not describe the earlier app’s chat or report payloads, which are explained below.

Our current Supabase database and Render API are hosted in Frankfurt. Legacy Google storage and functions are hosted in the European Union. Authentication, payments, AI, support and other processors may process data outside the EEA under their applicable data-protection arrangements; this is not a promise that every processor or log remains in the EU. Basic request/security logs may include IP addresses and timestamps. We do not use this data for advertising or sell it.

Optional product analytics (new releases)

New releases offer optional PostHog product analytics. It is off by default and is enabled only when you choose “Allow optional analytics” in Profile → Privacy & analytics. Viewing the sample as a guest is not tracked. Turning analytics off stops future event collection; it does not remove events already collected. Deleting your account requests deletion of its analytics profile and associated events as part of account erasure.

We send only named feature-use events: opening the chart, world map, Today, People, Library, subscription, personal reading or compatibility screens, saving a birth profile (without its contents), and successfully verified subscription purchase or restoration. Events include their time, application source/environment and a random analytics code stored separately from your sign-in identifiers. This is pseudonymous usage data, not a claim of complete anonymity. We do not send your name, email, Apple/Google identity, birth date/time/place, other people’s details, notes, planetary positions, reading/report text or payment information to PostHog.

Events pass through our API, which does not forward your phone’s IP address or device advertising identifiers. We disable analytics geolocation, session recordings, automatic screen/click capture and automatic person-property collection. No PostHog mobile tracking SDK is embedded. We use a dedicated PostHog EU cloud project on its capped Free plan, which currently retains event data for up to one year unless deleted earlier. Collection remains unavailable until setup and deletion verification are complete. PostHog processes the pseudonymous event data to provide usage statistics and funnels, not to advertise to you. See PostHog privacy information.

PostHog deletes profiles and events asynchronously; event cleanup may run during off-peak periods, including weekends, rather than immediately. Our erasure processor waits for confirmed completion before marking your account deletion complete; failed or pending deletion is retried. Restricted security and purchase-ownership records described below may remain. Older installed versions without this optional setting do not begin collecting these new events merely because this policy was updated.

Deletion and retained records

Open Your account using the profile icon, then Delete account. Request account deletion opens a preliminary confirmation; Keep my account closes it without submitting a request. Submitting requires fresh identity confirmation. A recorded request is processed within seven days and is not described as already completed. Access is restricted during processing, with a safety interval before erasure so running tasks can finish safely.

Deletion covers saved birth details, charts, People, compatibility, readings and personal reports, including verified linked previous-app data. Notes and saved places on the requesting device are cleared when the request is recorded. We cannot remotely erase exported/shared PDFs, store purchase histories or offline copies on other devices. Remove those separately where desired.

Limited purchase records may be retained where legally required. We retain restricted security and purchase-ownership records necessary to prevent fraud, duplicate transfers or reassignment of a previous purchase to another account. These records do not preserve the deleted birth profile, chart or reading and are not used for marketing.

Deleting an account or uninstalling the app does not cancel an Apple or Google subscription. Cancel it separately in your store account if you do not want further charges.

You can initiate a deletion request without reinstalling at Delete your account, or by writing to privacy@pandallc.dev with “Regares account deletion” in the subject. Explain your sign-in method and the account address if known. If you used Apple relay or cannot access the address, tell us so we can arrange ownership verification. Do not send passwords, sign-in codes or payment card details. An email address alone is not sufficient authority to erase an account.

You may request access, correction or a copy of your personal data through privacy@pandallc.dev. The rights, children and contact provisions below apply to both versions; references to removed screens apply only to the earlier app.

Earlier Regares versions

The following feature descriptions apply to the earlier native client, not to the redesigned 1.1 interface.

The short version

  • You never have to give us a name, an email or a password. The App creates an anonymous account for you on first launch. You can later link it to Sign in with Apple or to a Google account so that it survives a lost phone — that is the only point at which we learn an email address, and it stays optional.
  • Your birth details are stored in that account on our servers, not only on your phone — that is what lets your charts and purchases survive a reinstall.
  • Chart bookmarks and their notes stay on this device, separately for each account. They are not uploaded to our servers or sent to AI and do not sync between devices. You can include them in an account-data export. Delete a bookmark to remove its note; deleting the account clears its bookmarks from this device. Removing the App may also remove these local notes.
  • We collect only what the App needs to work: the birth details you choose to enter, your settings and your purchases.
  • We show no ads and sell nothing. The App keeps crash reports and three anonymous usage events — the subscription screen was shown, a purchase was made, onboarding was finished — so that we can see what breaks and what works; nothing you enter trains a model.
  • The texts you read — horoscopes built from your chart, chart readings, numerology, tarot, compatibility, reports and the assistant’s answers — are written by GPT, a language model run for us by OpenAI. The App asks your permission before any of your data is sent to it; without it you read the astrology service’s original texts and the assistant stays off. Assistant conversations are kept for 30 days.
  • If you turn on daily-horoscope or sky-event notifications, we keep a push token for your device and the hour you chose; turning them off removes it.
  • Card details never reach us — purchases are processed by Apple and Google.

What we collect

An anonymous account id. The App creates one on first launch so that your data can belong to something. It is not tied to your name, email or phone number, and we cannot use it to identify you as a person.

An email address, only if you sign in. Linking your account to Sign in with Apple (iOS) or to a Google account keeps the same account id and everything already saved in it; what it adds is an email address, so that the account can be found again from another device. With Sign in with Apple you may hide your address, and we then receive only Apple’s private relay address — we never see the real one. We use the address to recognise the account and for nothing else: no newsletters, no marketing.

Birth details. To build natal charts and personal readings you can enter a name, a date of birth, a time of birth and a place of birth. Certain paid reports — a compatibility report, or a chart for another person — let you enter the same details about someone else. Please only do so with that person’s permission. The name is one you choose; we never ask anyone to prove who they are.

Your settings. App language, house system, zodiac.

Purchase information. Subscriptions and one-time purchases are processed by the Apple App Store or Google Play. We receive confirmation of the purchase — the product, the date, the status — and never your payment card details.

Technical data. Our infrastructure providers automatically record basic technical logs, such as IP address, device type and timestamps, needed to operate and secure the service.

Assistant conversations. If you subscribe and use the assistant, the questions you type and the answers you receive are stored in your account for 30 days so that the conversation can continue where it stopped. Each question is sent, together with the chart data already in your account and the screen you asked from, to the language model that writes the answer. The assistant is limited to astrology, declines medical, legal and financial topics, and its answers are for entertainment — not advice.

Your choice about the language model. Whether you allowed your data to be sent to the language model, when, and where in the App you decided — see «Texts written by AI» below.

Notification settings. If you turn on the daily horoscope or sky-event notifications, we store the push token of your device, the hour and time zone you chose, and your sun sign, because the notification is built from them. Turning the notifications off removes the token.

Diagnostics and usage events. The App reports crashes (Firebase Crashlytics) and three usage events — the subscription screen was shown, a purchase was made, onboarding was completed — through Google Analytics for Firebase. These carry a device-level app identifier but no name, email or account id, contain no advertising identifier, and are never used for advertising. We do not collect your contacts, your location or advertising identifiers.

Texts written by AI

Regares uses GPT, a language model made by OpenAI, to write the texts you read from the results of the astrology computation service. The App asks for your permission before any of your data is sent to OpenAI — during onboarding, or before the first reading that needs it — and you can change your choice at any time in Profile › Settings › Privacy.

What is sent, if you allow it:

  • your chart and the numbers derived from your birth details — planetary positions, houses, aspects, numerology numbers — and the readings the astrology service computed from them, for personal horoscopes (including the morning notification), chart readings, numerology, tarot, your relationship profile, compatibility reports and PDF reports;
  • the names you enter — yours and those of the people you add — where they appear in those texts;
  • your messages to the assistant, together with your chart data and the screen you asked from.

What is never sent: your email address, your account id, device identifiers or your purchases.

What it is used for: OpenAI processes the data to generate the requested text. API data is not used to train its models by default. We disable response storage for synchronous generation. Abuse-monitoring logs may retain content for up to 30 days, or longer where legally required. For scheduled generation of public sun-sign horoscopes, we upload batch files and request their deletion after processing; these files contain no personal data. Details: OpenAI API data controls.

During the transition, older versions may continue to use Claude by Anthropic under the earlier disclosure. The consent screen identifies the provider. Permission for Anthropic does not permit transfer to OpenAI, and permission for OpenAI does not permit transfer to Anthropic. We ask for a new decision when the provider changes. If the app version and the server provider do not match, personal AI processing stays disabled until you update and consent to the displayed provider.

If you do not allow it, nothing about you is sent to OpenAI: you read the astrology service’s original texts, and the assistant is unavailable. Horoscopes for sun signs are the same for everyone and contain nothing about you, so they are written with the model either way.

What we use it for

  • To provide the service — computing your chart, horoscopes and reports from the details you enter, and keeping them in your account.
  • To manage purchases — verifying subscriptions and one-time purchases and unlocking what you paid for.
  • To operate and secure the service — debugging, preventing abuse, keeping it available.
  • To answer you when you write to us.
  • To write your horoscopes, readings and reports in plain language, and to answer the questions you ask the assistant, with the language model described above — only if you allowed it.
  • To send the notifications you turned on, at the hour you chose.
  • To find and fix crashes and to see whether the main flows of the App — onboarding, the subscription screen, purchases — work.

Under the EU General Data Protection Regulation our legal bases are: performance of a contract (providing the App and the content you ask for), legitimate interests (security and operation of the service, and knowing whether the App works) and, for the notifications you turn on and for sending your data to the language model, your consent, which you can withdraw at any time in the settings.

We do not use your data for advertising, we do not sell it, and we do not use it to train machine-learning models.

Who processes your data

  • Google Firebase (Authentication, Firestore, Cloud Functions, Cloud Storage, Cloud Messaging, Crashlytics, Google Analytics for Firebase) — the anonymous account, your saved birth details, charts, readings and generated report files, the assistant conversation, the delivery of notifications, and the crash reports and usage events described above.

  • Astrology computation service (astrology-api.io) — the date, time and place of birth and the name you typed for that chart, which is what the calculation and the reading are built from. It receives nothing else about you: no account id, no email, no device data.

  • OpenAI — OpenAI processes the data to generate the requested text. API data is not used to train its models by default. We disable response storage for synchronous generation. Abuse-monitoring logs may retain content for up to 30 days, or longer where legally required. For scheduled generation of public sun-sign horoscopes, we upload batch files and request their deletion after processing; these files contain no personal data. Details: OpenAI API data controls.

  • RevenueCat — subscription and purchase management. Receives your anonymous account id and purchase receipts. Never birth details.

  • Apple and Google as sign-in providers — if you choose to sign in, they confirm to us that the account is yours and pass an email address (or Apple’s relay address). They learn that you use Regares; they learn nothing about your birth details or readings.

  • Apple App Store / Google Play — payment processing, entirely under their own privacy policies; we never see card data.

Where your data is stored. Our database, our server functions and the report files are held in the European Union (Google Cloud: Firestore in the eur3 multi-region, everything else in Belgium). Some of the processors above operate outside the European Economic Area — RevenueCat, the astrology computation service and OpenAI among them — and those transfers are protected by recognised safeguards, including the EU Standard Contractual Clauses.

How long we keep it

Account data and generated content are kept while your account exists. If you delete your account, your birth details, charts and readings are deleted from our systems. Purchase records may be kept longer where accounting and tax law requires it. Technical logs are short-lived and rotate automatically. Assistant conversations are deleted automatically 30 days after each message. Notification tokens are removed when you turn notifications off or delete your account. Crash reports are kept for 90 days and usage events for 2 months in Google’s tools, and neither is tied to your account.

Your rights

Depending on where you live — including under the GDPR and the law of Kazakhstan — you have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict certain processing, and to withdraw consent at any time.

You can edit your birth details, export a copy of your data and delete your account in the App’s Profile tab, and allow or stop sending your data to the language model in Profile › Settings › Privacy, or follow the instructions at pandallc.dev/delete-account. You can also write to privacy@pandallc.dev. If you are in the EU or EEA you may also complain to your local data protection authority.

If you have signed in, write from the address linked to the account and we can recognise it. If you have not, the App itself is the only place that can prove an account is yours: the anonymous id lives on your device, and we have nothing else to match you against. In that case write to us anyway — we will tell you what we need, and we will not delete data on the word of someone who cannot show it is theirs.

Children

Regares is not intended for children under 16 and we do not knowingly collect personal data from them. If you believe a child under 16 has given us personal data, write to us and we will delete it.

Changes

We may update this policy as the App changes. The date at the top always reflects the latest revision, and material changes are announced in the App.

PRO chart questions and weekly study

In redesigned Regares, chart questions require a separate opt-in consent before the first submission. If you choose this feature, we send your question text and reliable calculated planetary positions and connections to OpenAI. We do not add your name, birth date, birth time or birthplace. Anything you type in a question is included, so avoid personal or sensitive details. Each question is processed independently; your journal and other saved notes are not included. OpenAI processes these requests under its API data policies, and we request no provider-side response storage.

Question text and answers are saved in your account so you can revisit them. Unlike the earlier assistant's retention period, this new chart-question history remains until you withdraw question consent and delete history, or delete your account. You can withdraw consent in Ask your chart → Questions & privacy. This removes the saved question text and answers and prevents an in-flight answer from being saved. Request identifiers, timestamps and usage counts, without question or answer text, remain for limits and accounting until account deletion.

The weekly study is a curated reflection programme based on reliable placements in your natal chart, not a transit forecast. Its dated journal entries stay on this device, separately for each account. They are not sent to our API, OpenAI or PostHog and do not sync between devices. You can read and remove saved entries in Library → Study journal without an active PRO subscription. Removing the app may remove these entries; account deletion clears them on the requesting device. The journal currently supports up to 200 entries and does not automatically replace an earlier entry when a new one is saved.