Dolya
Privacy
Last updated 2 November 2026.
Dolya asks for a birth date, and if you buy the full version or make an account, for an email address. This page says what happens to both, on this site and in the Dolya app for Android. There are no analytics and no tracking on this site or in the app, and no cookies unless you sign in.
Who is responsible
Magnetis OÜ is the controller of the personal data described here.
- Registry code 17046992, Estonian Commercial Register
- VAT number EE102766734
- Rävala pst 2, 10145 Tallinn, Estonia
- readings@dolya.app
Email is the fastest way to reach us and the address to use for anything about your data. Post reaches us at the registered address above.
What is collected, and why
Your birth dateTyped on the first screen. It is what the chart is made from, so without it there is nothing to read. It is sent to Anthropic to write the reading, stored in our cache against the reading it produced, and, if you buy the full version, recorded against the purchase so that the link knows which reading it opens. The basis is performing our contract with you, or taking steps at your request before one - article 6(1)(b) GDPR.
Your email addressCollected by Stripe at the checkout, and passed back to us. We use it for one thing: sending you the link to the reading you bought. The basis is performing the contract - article 6(1)(b).
Your IP addressRead from the request while you are on the site, and used only to count how many readings and how many payment pages one address has opened in the current hour. It is not attached to your birth date, your email address or your purchase, and it goes nowhere else. The basis is our legitimate interest in keeping a free service, and the bill behind it, from being drained - article 6(1)(f).
The consent you gave at the checkoutThe sentence about the fourteen-day right, which version of it you were shown, and the moment you ticked it. Recorded against the payment at Stripe and in our own record of the purchase, because consumer law requires us to be able to show it. The basis is a legal obligation - article 6(1)(c) - and our legitimate interest in being able to answer a dispute about it - article 6(1)(f).
What was paidThe amount, the currency and Stripe's reference for the payment session; for a reading bought in the app, Google Play's order number and the time of the purchase instead. The basis is a legal obligation: accounting and VAT - article 6(1)(c).
If you make an accountYour email address, and the birth dates you choose to keep in it, each with the name you gave it. If you sign in with Google or Apple, they tell us your email address and may tell us your name, and Google also sends the picture on your Google account; we keep what they send with your account and use none of it but the address. We use your account for one thing: keeping your dates, and listing the readings you bought with the same address, so you can come back to them. Deleting your account removes the dates and their names too. The basis is performing our contract with you - article 6(1)(b).
Other people's birth datesIf you keep somebody else's birth date in your account, it is kept for you and shown to nobody else. It is not connected to any account of theirs, and nothing is done with it but drawing that chart when you ask. The basis is our legitimate interest in providing the account you asked for - article 6(1)(f).
We do not ask for your name. You never need an account: reading a chart and buying a reading work the same without one.
In the Dolya app
The app draws your chart on your phone, and most of what you give it never leaves the phone.
What stays on your phoneYour birth date, the people and the children you add with their names and birth dates, how each evening felt as you marked it, your settings, your sign-in if you sign in, the books you open, the readings you bought in the app and the texts already fetched. They are kept in the app's own storage on the phone. No birth date is sent to us whole; what the app does send is below. The reminders are set on the phone, and the widget is drawn there. Removing the app, or clearing its data, removes all of it.
Texts the app asks forThe app asks this site for each day's text with one key: a few numbers from your chart and the day's own number. Thousands of people share every key, so it says nothing about who you are, and your birth date is not in it. The reading for two asks with the three numbers of each of the two charts. A chart's first number is the day of birth when it is 22 or less, and its second is the month of birth, so for most people that request carries both people's day and month of birth - never the year, only a number made from it, and never a name. If you have said what the other person is to you, the request also carries that one word, partner, family, friend or colleague, and the reading is written for it. The reading is written once for those numbers and kept for anyone who opens the same two charts. These requests reach Vercel, which sees your IP address as it does on this site. The basis is performing our contract with you - article 6(1)(b) - and, for the other person's numbers, our legitimate interest in giving you the reading you asked for - article 6(1)(f).
If you sign in from the appSigning in works as it does here: the app sends your email address to Supabase, which sends you a code, and the account is the one described above. The dates you keep in the app are not added to it. Signed in, the app lists the readings bought with your address and opens them; to open one, it sends the birth date the account already holds for that reading and the token that opens it, and nothing else.
Updates to the appWhen the app opens, it asks Expo, the service that delivers updates to the app's own code, whether there is a new version. Expo receives your IP address, your phone's operating system, the app's version and a random identifier the app makes for itself, which lets Expo tell whether that install already has the update. If the app failed to start the time before, it also sends the text of that error and which updates failed, so that a broken update can be found and withdrawn. It carries no birth date, no email address and nothing you typed. The basis is our legitimate interest in keeping the app working and correct - article 6(1)(f).
If you buy the full reading in the appThe payment is taken by Google Play, on Google's own sheet: your card, your Google account and its address stay with Google, and we are never told them. Before paying you tick the same sentence about the fourteen-day right as on this site. The app then sends this site the purchase token Google Play gives it, which product it was, the birth date the reading is for and the moment you ticked the sentence. This site asks Google whether that purchase was paid, and records the purchase as a purchase on this site is recorded - the birth date, the consent, Google's order number and the time - against a new reading token. That token is kept on your phone, in its secure storage, so the reading opens there without an account. If you are signed in, the reading is also listed in your account, so another phone can open it. Every few hours this site asks Google which purchases were refunded, and a refunded reading stops opening. The basis is performing our contract with you - article 6(1)(b) - and, for the consent and the order number, a legal obligation - article 6(1)(c).
Google PlayThe app is installed through Google Play, which Google runs under its own privacy policy. Google Play also takes the payment for a reading bought in the app, as the controller of the payment data, under its own terms.
Your birth date goes to the United States
This is the part a reader may not expect, so it is here in plain words. The reading is written by Claude, a language model run by Anthropic, and to write it your birth date and the nine numbers it makes are sent to Anthropic's API in the United States. There is no European-only version of that API for us to use. Nothing else travels with it: not your email address, not your IP address, and there is no name to send.
Anthropic deletes inputs and outputs within 30 days of receiving or generating them, with exceptions for features that retain for longer, for arrangements agreed separately, and for enforcing its usage policy. Anthropic does not train its models on data from its commercial API.
Who else sees it
StripeTakes the payment, on its own page. No card number, expiry or security code ever reaches us. Stripe collects your email address and the country detail it needs to work out the VAT, and it receives the birth date the reading is for and the consent sentence you ticked, both stored against the payment. For much of what it does with payment data Stripe is its own controller, under its own privacy policy.
AnthropicWrites the reading, and receives the birth date and the chart, as above.
ResendSends two kinds of email. The first goes when you buy the full version, with the link to your reading. For that one it receives your email address, the birth date - which is in the subject line and in the message - the link to your reading, and the confirmation the message carries below it: what was bought, what it cost, and the consent you gave at the checkout with the moment you gave it. The second goes when you ask to sign in with your email address, and Supabase passes it to Resend to send. It carries your email address, a sign-in code, a link that signs you in, and a line saying to ignore it if you did not ask. It carries no birth date and nothing about a purchase.
VercelHosts the site and runs its code. Every request passes through Vercel, which sees your IP address and the ordinary details of a request, and our own server logs are held there.
SupabaseRuns the accounts and the database they are kept in, on AWS in the European Union, in Frankfurt. It holds your email address, how you signed in, the birth dates you kept with the name you gave each of them, and the list of readings bought with your address. Deleting your account removes those too.
Google, for a purchase in the appTo check a purchase made in the app, this site sends Google the purchase token and the product (the Google Play Developer API), and Google answers whether it was paid; later it lists the purchases that were refunded. Nothing else is sent: no birth date, no name, no email address.
Google and AppleOnly if you choose to sign in with one of them. You sign in on their page, and they tell us who you are. What they do there is covered by their own privacy policies.
Expo650 Industries, Inc., in the United States, which delivers the app's updates. It receives only what the app sends when it checks for one, as above, including the error report after a failed start.
UpstashUpstash Redis, connected through Vercel and run on AWS in us-east-1, N. Virginia, United States. It holds the record of your purchase, the hourly counters behind the rate limit, and the cached readings.
Nobody is sold this data and nobody is sent it for advertising.
Where it goes
Our functions run in the United States: a request made in Europe is received in Europe and answered from Washington DC. Anthropic's API, Resend and Upstash - the key-value store behind it, run on AWS in us-east-1, N. Virginia - are in the United States too. Those are transfers of personal data outside the EU, and they are how the product works rather than an incident.
The safeguard relied on in each case is the European Commission's standard contractual clauses, the 2021 set adopted in decision 2021/914. Anthropic incorporates them through the data processing addendum built into its commercial terms; Vercel, Resend, Upstash and Supabase through their own data processing addenda; Stripe through its data transfers addendum. Accounts are kept in the EU, but Supabase is an American company, so its addendum covers them too.
Expo, which the app asks for its updates, is in the United States as well. It is certified under the EU-U.S. Data Privacy Framework, which the European Commission found adequate in its decision of 10 July 2023, and that is the safeguard relied on for it.
How long it is kept
The record of a purchaseThe birth date, your email address, the payment reference, the amount and the consent; for a purchase in the app, the birth date, Google Play's order number, the time and the consent, and no email address. Two years from the purchase, after which it deletes itself. That is also how long your link keeps opening the reading.
The note that a reading was refundedTwo years. It holds the birth date and the payment reference, so that a link opened afterwards can say what happened rather than nothing.
Your accountUntil you delete it, which you can do yourself at any time, from the app or from the account page - see Deleting your account. Deleting it removes your email address, the birth dates you kept and the list of your readings, at once. It does not stop a reading you bought from opening: that link belongs to the record of the purchase above, and keeps opening for as long as that does.
The rate-limit countersOne hour - the length of the window they count. They expire on their own and nothing renews them.
Cached readingsOne year. A cached reading is stored under the birth date alone, with nothing attached to say who asked for it.
What the app keeps on your phoneUntil you delete it in the app, clear the app's data or remove the app. We never receive a copy.
Our server logsThey record birth dates and payment references, never email addresses and never IP addresses. We have not set a period of our own for them; they are held by Vercel under its own schedule.
Stripe, Resend, Anthropic and Expo each keep their own records under their own schedules. Anthropic's is the 30 days above. Stripe keeps the payment record for as long as its own legal obligations require, which is longer than any period above.
Deleting your account
You can delete your Dolya account yourself, at any time, in any of three ways.
In the appSigned in: You, then Your full reading, then Delete your account at the foot of the page. It opens the account page here.
On this siteOpen your account, sign in with the code sent to your email, and choose Delete my account at the foot of the page.
By emailWrite to readings@dolya.app from the address the account was made with, and we will delete it for you.
Deleting removes your email address, the birth dates you kept and the list of your readings, at once. The record of a purchase is not part of the account: it stays for its two years so that a reading you bought keeps opening from the link in your email, as set out under How long it is kept. What the app keeps on your phone was never in your account; remove the app, or clear its data, to delete it.
Your rights
If you are in the EU you can ask us for a copy of what we hold about you, to correct it, to delete it, to restrict what we do with it, to have it handed to you in a portable form, and to object to anything we do on the basis of our legitimate interests. You can withdraw any consent you have given, without that affecting what was done before.
Write to readings@dolya.app. What lets us find you is the email address you bought with, or the payment reference from Stripe's receipt. A birth date on its own will not find anything, because a cached reading is not attached to a person. If you have an account, you can delete it yourself from the account page.
No decision is made about you based solely on automated processing that has legal or similarly significant effects on you, in the sense of article 22 GDPR. The reading is written by a language model, but it decides nothing about you.
One thing is worth saying plainly. Our record of your purchase is what makes your link work, so deleting it stops the link opening the reading. We will say so before we do it.
Complaining
If you think we have handled your data badly, tell us first at readings@dolya.app and we will try to put it right.
You can also complain to a supervisory authority. Ours is the Estonian Data Protection Inspectorate, Andmekaitse Inspektsioon, at Tatari 39, 10134 Tallinn, Estonia, info@aki.ee, aki.ee. You may complain to the authority in the country you live in instead.
What this site does not do
Dolya's own pages set no cookies unless you sign in. Signing in sets the cookies that keep you signed in, on this site only, and signing out removes them. They carry nothing but your session, and they are never set for anybody who has not asked to sign in. There is no analytics, no advertising, no tracking pixel and no third-party script; the fonts are served from this site rather than fetched from anybody else. Neither kind of email we send carries an image or a tracking pixel. Stripe's payment page is Stripe's own, and what it does there is covered by Stripe's privacy policy. The app has no analytics, no advertising and no tracking either.