Privacy Policy
This policy explains what Orrery does with personal data. It describes the service as it actually works — what is stored, what is sent elsewhere, and what never leaves the server.
The short version
- You can draw a natal chart without an account. It is calculated and discarded — nothing is written to our database. The chart itself waits in your own browser for a week, so that signing in can add it to your account; if you never sign in, it expires there.
- With an account, we store the charts you save, including the birth details they are built from.
- Place search runs against our own copy of the gazetteer, so the places you type never leave our server.
- AI readings are the exception: to write one, your chart details and anything you typed in the note field are sent to an AI provider, and the finished reading is stored in your account. Read that section before using the feature.
- There is no advertising, no tracking pixels, no third-party analytics, and nothing is sold or shared for marketing. We do count how the site is used — on our own server, with no cookie and no one else involved. The section below says exactly how.
Who is responsible
Oleksandr Nazaruk, an individual entrepreneur ("ФОП") registered in Ukraine, tax number 3746203132, of 307 Akademika Pavlova Street, Kharkiv, Ukraine, operates orrery.info and is the controller of the personal data described here. For anything in this policy — including a request to see or delete your data — write to [email protected].
What we collect
Account data, when you register:
- Your email address, and your name if you give one.
- Your password, stored only as a cryptographic hash — we cannot read it.
- If you sign in with Google: the basic profile Google returns (email, name, picture) and the tokens needed to keep you signed in. We ask Google for nothing else.
- A profile picture, if you upload one — and, if you signed in with Google, a copy of the picture Google returned. Both are stored in our own object storage rather than linked from anywhere else, so that displaying your picture tells no one but us that you are here. It is shown to you; it appears nowhere public. Removing it deletes the file.
- Whether your address has been confirmed.
- Which version of the Terms was in force when you created the account, and — for each subscription or upgrade you buy — the version in force at that moment. Kept so that what you agreed to can be established later rather than assumed.
- Your default chart configuration, if you change it: house systems, orb settings, which stars are drawn, and the other calculation options. Nothing is stored until you change something, and it is used only to set up charts you create afterwards.
Charts you save:
- The name you gave the chart, its type, and the birth date, birth time, place name and coordinates it is calculated from — plus the country we work out from that place, so that you can search your own charts by it.
- If you filled them in: the person's own name, their gender, and a time zone you chose by hand instead of the one we derive from the coordinates. All three are optional and the chart is calculated without them.
- The same details for any partner, relocation or forecast moment you add to a chart.
- Your workspace preferences for that chart — which panel was open, which settings were applied.
Technical data, for security and abuse prevention:
- The IP address and browser user-agent attached to each sign-in session.
- Ordinary server logs of requests.
AI usage records, so quotas can be counted:
- Which service you ran, when it started and finished, whether it succeeded, which model answered, and how many tokens it used.
- The finished reading itself — its text, and the note and accent you gave it — linked to the chart it was written for. It is stored so that a reading you paid for survives a dropped connection, and so that opening the chart in another of your browsers can show it. It is deleted with that chart, or with your account.
Payment data: your plan, its status and renewal date, the payment provider's reference for each transaction, and — so renewals can be charged without asking you again — a token standing for your card, together with its masked number, its brand, and whether you paid by card, Apple Pay, Google Pay or monobank. The token is issued by the payment provider and can only be redeemed by them, against this account. The card number, its security code, the cardholder name and the expiry date are entered on the provider's page and never reach our servers.
What we deliberately do not do
- No advertising or ad networks, no tracking pixels, no third-party analytics service, no profiling for marketing.
- No analytics cookie, no device fingerprint, and no identifier that follows you from one day to the next or from one site to another.
- No selling, renting or sharing of personal data.
- No storing of birth details entered by visitors without an account: until you sign in, the chart stays on your own device.
- No sending of place searches to an external geocoder — the gazetteer is a local copy.
Counting how the site is used
We keep a record of how the service is used, so that we can tell whether it is working: how many people arrive, how many draw a chart, how many go on to open an account or subscribe. It runs entirely on our own server. No third-party analytics service is involved, no data about you is sent anywhere for this, and nothing about it is used for advertising.
It does not set a cookie, and it cannot follow you. To count a person twice in one day without knowing who they are, the server derives a short key from your IP address and browser user-agent using a secret that is regenerated every day and never written down. The key it produces cannot be turned back into your address. When the secret changes, the same visitor produces a completely different key, and yesterday's key cannot be reproduced — so the record can tell that someone came back this afternoon, and can never tell that they came back this month.
Each recorded event holds:
- What happened — a page was viewed, a chart was calculated, an account was created, a panel your plan does not include was opened, a subscription was bought or cancelled.
- The day's key described above, and — if you were signed in at the time — your account, so that questions like “do people who sign up go on to use it” can be answered.
- The page path, without its query string; the language; the country your address resolves to; and whether you were on a phone, tablet or desktop.
- Where you arrived from, if you followed a tagged link or came from another site: the campaign name in the link and the referring site's domain. The address of the referring page is discarded, so a search you typed elsewhere is never recorded.
Requests from bots and crawlers are discarded rather than counted. Raw records are deleted automatically after 90 days; only the operator can read any of this, and it is never shown to anyone else or shared.
If you hold an account, these records are attached to it, which means they are also covered by your rights below: asking for a copy gets them too, and deleting your account detaches them, leaving counts that are no longer connected to any person.
We rely on our legitimate interest in understanding whether the service works. If you would rather not be counted, write to [email protected] and we will exclude you.
AI readings: what is sent, and to whom
When — and only when — you ask for an AI reading or year forecast, the following is sent to an AI provider so a model can write it: the chart's birth date, time and place, the calculated positions, the accent you selected, the display name you entered, the gender recorded on the chart if you gave one, and the free-text note where you describe your question or your wishes for the year. Whatever you write in that note is sent verbatim. Please do not put anything there you would not want processed by a third party.
The finished text is stored in your account, together with your note, attached to the chart it was written for. That is what makes a reading durable: if the connection drops while it is being written, or you come back hours later, or open the chart on another of your devices, the reading is served from our database rather than lost — and redelivering it never spends a second run from your allowance. Delete the chart, or the account, and the stored readings go with them.
The provider is Google (Gemini, via Google AI Studio), with OpenRouter as a second rail: it takes over when Google is unavailable, and it carries every reading requested from the EEA, the United Kingdom or Switzerland. OpenRouter routes the same request to the same model family, on paid terms. Both process the request in order to return the text, and neither is given your email address or account identity.
Important, and stated plainly: outside the regions above, readings run on Google's free tier, and Google's terms for free-of-charge use permit them to use submitted content to improve their products, including human review. Treat anything you send to an AI reading through that tier as potentially seen by the provider. Readings requested from the EEA, the UK or Switzerland never touch the free tier — Google requires paid service for those regions, so those requests go straight through OpenRouter, whose paid terms do not carry that content-use permission. Charts you merely calculate and view in the app are not affected either way; this applies only to the AI features. If this arrangement changes, this section changes with it.
Who else processes data for us
| Processor | What it receives | Why | Where |
|---|---|---|---|
| Contabo | Everything stored by the service | Server hosting and the database | Germany (EU) |
| Cloudflare | Your IP address and request metadata; a bot-check token on sign-up | Network protection, DNS, blocking automated abuse | Global network |
| Cloudflare R2 | Your profile picture, if you have one | Storing it and serving it back to you | EU region |
| Resend | Your email address and the message text | Sending confirmation and password-reset emails | EU region |
| Google (Gemini) | Chart details and your note, when you request an AI reading | Generating the reading | United States |
| OpenRouter | The same, for readings requested from the EEA, UK or Switzerland — and elsewhere when Google is unavailable | Writing the reading over a paid rail | United States |
| monobank (Universal Bank) | The amount, the order reference, the plan name and an account identifier; your card details, which you enter on their page | Taking payment, renewing a subscription and preventing card fraud | Ukraine |
Transfers to providers outside the EU rely on the European Commission's standard contractual clauses in those providers' terms. We add no other recipients without updating this page.
Cookies and local storage
- A session cookie, set when you sign in. Strictly necessary — without it you cannot stay signed in.
- A cookie remembering your chosen language.
- A cookie set by Cloudflare's bot check on the sign-up form.
- Cookies remembering how you have arranged the workbench: whether the sidebar is collapsed, and whether today's sky is drawn as a band or as a dial.
- Your theme choice, kept in your browser's local storage and never sent to us.
- The city you picked for today's sky, if you changed it from the one guessed from your country. It is kept in your browser's local storage and sent back with the request that computes the sky, because that is the only way the times shown can be the ones you asked for. It is a city, not your location, and nothing is stored at our end.
- The last AI reading for each chart, kept in local storage so the chart can show it instantly: its text, and the note you wrote when you asked for it. This is a working copy — the reading itself is stored in your account, as the AI readings section describes.
- A chart drawn without an account, kept in your browser's local storage for a week so that signing in can add it to your account. It reaches us only at that point, and is removed from the browser once it has been saved.
There are no advertising or analytics cookies, which is why the site does not confront you with a consent banner: everything above is either strictly necessary or a preference you set yourself. The usage counting described in the next section sets nothing at all.
Why we are allowed to process it
- To perform our contract with you: running your account, saving your charts, delivering the features your plan includes.
- Our legitimate interest in a service that works: keeping it secure, preventing automated abuse, counting usage against quotas.
- Legal obligation: retaining transaction records required by Ukrainian tax law.
- Your consent, where a feature is optional — asking for an AI reading is a deliberate act you initiate each time.
How long it is kept
- Charts: until you delete them, or until you delete your account.
- Account and authentication data: until you delete your account, after which it is removed along with everything linked to it.
- Your profile picture: until you replace it, remove it, or delete your account. Replacing one deletes the file it replaced.
- Sessions: until they expire or you sign out.
- AI usage records: kept while your account exists, because lifetime and monthly quotas are counted from them.
- AI readings: until you delete the chart they were written for, or your account. A reading written for a chart you never saved is attached only to the account, and goes when it does.
- Database backups: taken nightly and kept for 30 days, then overwritten. Deleted data can persist in backups until that window passes.
- Usage records: 90 days, after which they are deleted automatically. The totals worked out from them — how many people visited in a month, how many became subscribers — are kept, because they are numbers about the business rather than about anybody.
- Payment records: as long as Ukrainian tax law requires.
- The card token: while it can still be charged. Once your subscription ends it is used for nothing — resubscribing asks for a card on the provider’s page and issues a new one — and deleting your account removes it.
Your rights
You can ask for a copy of your data, correct it, delete it, take it elsewhere in a portable form, or object to a particular use. Deleting your account removes your charts and everything attached to them. Write to [email protected] and you will get an answer within 30 days.
If you are in the EU or the UK and think we have handled your data badly, you may complain to your national data protection authority. In Ukraine, that is the Verkhovna Rada Commissioner for Human Rights.
Security
- All traffic is encrypted in transit.
- Passwords are stored only as hashes.
- The database accepts connections from the application server alone; it is not reachable from the internet.
- The origin server accepts traffic only through Cloudflare.
- Access to the server is limited to the operator.
No system is perfectly secure. If we ever discover a breach affecting your data, we will tell you and the relevant authority as the law requires.
Other people's birth data
The service lets you build charts for other people — a partner, a client, a family member. When you do that, you are the one deciding to process their data, and you must have a proper basis for it: their agreement, or another lawful reason. Do not enter details about someone who would object. If a person asks us directly to remove data you entered about them, we will contact you about it.
Children
Holding an account requires being at least 18, as the Terms state. The service is not directed at children, and we do not knowingly collect their data. If we learn that an account belongs to someone under 18, we will delete it.
Changes to this policy
When the service changes, this page changes with it, and the date at the top moves. If a change materially affects what happens to your data, account holders will be told by email before it takes effect.