Privacy Policy

Last updated 13 October 2026

This describes what actually happens to what you give us, written from the code rather than from a template. Where something is kept, it says where and for how long.

Who is responsible for it

Mantas Karalius, trading as ReadPalm — a sole trader established in Lithuania under individual-activity certificate No. 1546358, Tiekėjų g. 4, Kretinga, Lithuania — is the controller: the one who decides what happens to your data and answers for it. Write to support@readpalm.net.

The short version

Your photograph is read once and never reaches your account. If you give your email and leave before buying, we keep it for up to seven days so that a reminder can bring you back to where you were; it is deleted when you buy, when you unsubscribe, or after seven days.
Until you type your email, everything stays in your browser. Your answers are kept on your own device for seven days so you can pick up where you left off; your photograph only until the tab closes. Nothing reaches us.
Buying makes an account, because a reading you paid for should not vanish with a tab. Your reading and your birth details are then kept against that account so you can open them on another device.
One cookie, and it does one thing: it keeps you signed in.
We count how far people get through the questions, so we can see where the site is confusing. It is counting, not watching: no advertising script on the page, nothing that follows you to other sites, and nothing that survives you closing the tab.
If you came here from a Facebook or Instagram advert and go on to buy, we tell Meta that the advert worked — from our server, with nothing of theirs on the page. If you did not, Meta hears nothing.

What stays in your browser

Your photograph, the computed chart and the finished reading are held in your browser’s session storage, which belongs to one tab and is erased when that tab closes. Your answers and your birth details are also kept in your browser’s local storage for seven days, so that if you leave in the middle of the questions — to look up an email address, say — you come back to the question you were on rather than the first one. Start again in Settings clears them at once. We cannot read any of it.

Until you type your email address, that is the whole of it — nothing about you is kept on our side at all. What is kept from that moment, and what changes when you buy, is described below.

One thing outlives the tab: the email address you type is also kept in local storage on your own device, so that a receipt and your way back to the reading can find it. You can clear it with Start again in Settings.

What reaches our server, and what it does with it

Your photograph

When a reading is made, the photograph is sent to our server and passed straight to Anthropic’s model, which reads it and returns text. It is never written to disk here. Anthropic processes it for the duration of the request and does not use it to train models. The photograph takes this detour through our server only so that the key that authorises the call never has to be put in your browser.

The one exception, since 13 October 2026. When you type your email address, the funnel sends your photograph, the lines traced on it, your answers and the identifier of the reading being written to our server, where they are kept together under a random identifier for up to seven days. They exist for one purpose: if you have not bought, we send up to three reminder emails — about two hours later, then on the second and the fourth day — whose link puts you back on the price screen with your own hand on it. That kept copy is deleted the moment you buy, the moment you press unsubscribe in any of those emails, or after seven days, whichever comes first. It is never copied to your account, and it is not kept at all if your browser sends “Do Not Track” or Global Privacy Control. Our basis is our legitimate interest in letting you finish a purchase you started; the unsubscribe link is how you object, and it works at once.

Your birth details

The date, time and place you were born are used in your browser to compute the chart. A summary of that chart — signs, houses and the decisions your answers earned — is sent with the reading request so the text can be written about it.

If you have bought a reading, the birth details are also kept with it against your account. This is not incidental: the pages that draw your reading are drawn from the birth moment, so a reading opened on a second device without them is a reading that cannot be shown. They are kept for as long as the account has the reading, and they go when it does.

A reading made before you buy it

The reading takes about two minutes to write. If it was started while you were still in the questions, the finished text is held on our server until you collect it, and no longer than seven days. It is kept under a random identifier only your browser holds, it is deleted the moment it is collected, and it contains no name, address or photograph.

Your account and your reading

Paying makes an account, identified by the email address you gave at checkout. We keep that address, the dates the account was made and last used, and the readings bought with it — the text of each reading and the birth details it was written from. That is what lets you sign in on a different device and find the reading you paid for.

Your photograph is not among it. It is never uploaded to your account, on any device. A reading opened somewhere other than the phone that took the picture is the whole reading, drawn without the hand behind it.

Signing in sends a six-digit code to your address. The code is never stored — only a one-way fingerprint of it, which dies ten minutes later or the moment the code is used. The email sent after you pay carries a sign-in link as well; the link’s token is held the same way, as a one-way fingerprint, for fourteen days or five uses, whichever comes first. The session that follows is a cookie holding a random value; the server keeps only a one-way fingerprint of that too, so a copy of our storage would not let anyone sign in as you. The cookie lasts thirty days, is marked HttpOnly so no script can read it, and is used for nothing but knowing you are you. Logging out deletes the session on our side, not just in your browser.

At most ten readings are kept per account; older ones are deleted to make room.

Writing to us

If you use the contact form, what you write and the address you give are sent to our support mailbox as an email. Nothing from that form is kept in a database here; it lives in the mailbox, like any other message, for as long as we keep correspondence.

Rate limiting

To stop the service being run up as a bill by somebody else, we count requests per visitor. Your IP address is not stored: it is turned into a one-way keyed hash that cannot be reversed back into an address, and only that hash and a count are kept. Those counters are deleted after two days.

Timing

We record how long each reading took to write and how much text it came to, so we can tell whether the wait is getting worse. These lines contain no personal data.

The record of your own account

Separately from the counting described below, and for a different reason, your account keeps a short record of what it did: when it was paid for, when a reading was delivered to it, when you signed in and when you opened your reading. Each line has the time, the IP address it came from and which browser was used.

Why we keep it. Two reasons and no others. It is how we can tell you what you bought and when, if you ask. And it is how we answer a bank: when someone tells their card issuer that a payment was never authorised or nothing was ever supplied, the issuer takes the money back unless the seller can show otherwise, on a deadline of a few days. That record is the showing. In the language of the law, we keep it to perform our contract with you and to establish and defend legal claims.

It holds no reading, no birth details and no photograph — only that something happened, when, and from where. It is kept for two years after the account was last used, which is longer than any card scheme allows a dispute to be raised, and then deleted. Asking us to delete your account deletes it at once.

Counting how the site is used

We need to know where people stop. Twenty questions stand between the first screen and a reading, and without counting we would be guessing which of them is the one that loses you — so each screen sends a line saying which screen it was, and a handful of moments send one too: a photograph arriving, a payment starting, a reading finishing or failing.

What those lines contain. The name of the screen, its number, the size of your browser window, whether the page was opened inside the Facebook or Instagram app, and — if you arrived from an advert — which advert. Nothing else is allowed into them, and that is enforced in the code rather than promised in this paragraph: the list of things that may be sent is written out in one place, and anything not on it is discarded before the message is built. Your photograph, your birth date, time and place, your name, your address, your reading and every answer you gave are all absent from it.

Before you have an account, no cookie and no memory of you. The counting uses a random number that lives in the tab you are reading this in and dies when you close it. Come back tomorrow and you are somebody new. There is no cookie for this, nothing stored on your device that outlives the tab, and nothing that could recognise you on another site — which is why this site has no cookie banner: there is nothing to ask you about.

Once you give us your email address, these lines carry it. That happens on the screen after your photograph, where you type it in, and again if you sign in later. From that moment the counting is no longer anonymous for you: the screens you walked through beforehand are joined to your address, and so is everything after it, on every device you use.

We do this for two reasons. So that we can see where people stop when they have gone as far as giving us an address — which is the part of this site worth improving most. And so that we can say what a named customer bought and used, on the day a bank asks. Those are our legitimate interests in running and defending the service, and once you buy, performing our contract with you.

What does not join it: your birth details, your photograph, your reading and your answers. Those have never been part of these lines and are not now.

Your address stops at our server. The lines go to PostHog, and they pass through this site rather than being sent from your browser to them. That lets us cut the last part off your IP address first — enough is left to say which country a visit came from, and not enough to say which connection.

PostHog stores them in the United States. They are certified under the EU–US Data Privacy Framework and its UK and Swiss extensions, which is the basis on which that transfer is made.

If your browser sends “Do Not Track” or Global Privacy Control, none of this happens at all.

Adverts, and telling Meta which one worked

An advert on Facebook or Instagram puts a click id on its link. If you arrive with one, it is kept in the tab you are reading this in, and if that visit goes on to open the payment screen or to pay, our server tells Meta so: the click id, a one-way hash of your email address, your IP address and which browser, and for a payment the amount. That is what lets Meta say which advert brought a customer, and it is all it is used for. The click id, IP and browser ride on the subscription record at Stripe until the payment is confirmed, which is how the confirmation can carry them back.

Nothing from Meta runs in your browser — no pixel, no script, no cookie. The message goes from our server to theirs. If you did not arrive from an advert, nothing is sent at all; if your browser sends “Do Not Track” or Global Privacy Control, the click id is never kept in the first place. Meta matches the hash to an account it already holds rather than being given the address, and stores what it receives in the United States under the EU–US Data Privacy Framework. Our basis is our legitimate interest in measuring advertising we pay for; you can object, below, and it stops.

Who else sees anything

Hostinger, which provides the server this site runs on, in its data centre in Lithuania. Everything kept on our side — accounts, readings and the record described above — is on that server’s disk, inside the European Union.
Anthropic, in the United States, for the length of the request that writes your reading — the photograph and the chart summary, and nothing else. They process it for that request and do not use it to train models, under data-processing terms that include the European Commission’s standard contractual clauses.
Stripe, when you pay. Your card details are entered into Stripe’s own fields and never reach this site; we see only that a payment succeeded, and Stripe holds your address to send the receipt and to run the subscription.
Resend, in the United States, which delivers our email — the sign-in codes, the welcome email after you pay with its sign-in link, the reminder the day before each renewal, the reminders if you left before buying, and what you write in the contact form, on its way to our mailbox. They handle the address and the message for as long as delivery takes, under the same kind of terms.
PostHog, in the United States, which counts the screens as described above — and, from the moment you type it in, your email address, so that the counting can be attached to you. They receive no name, no birth details, no photograph and no reading, and a shortened IP address rather than yours.
Meta, in the United States, only when you came from one of their adverts and went on to checkout or pay — the click id, a hash of your email, your IP address, your browser and the amount, as described above. Nothing else, and nothing at all for anybody who did not arrive from an advert.

No advertising script runs on this site and there is no social plug-in; what Meta is told, and only when, is described above. The only cookie this site sets is the sign-in session described above; nobody sets one through it.

What you can do

Forget the photograph and Forget the reading, separately, in Settings.
Start again, which clears everything this browser holds, including the saved email address.
Close the tab, which does most of the same thing without being asked.

Logging out, in Settings or in the menu, ends the session on our side as well as in your browser.

If you have an account and want it and everything in it deleted, write to us through the contact form and say so. We delete the account, the readings kept against it and the birth details with them. There is nothing else of yours to delete: the photograph was never stored, and the counters described above cannot be traced back to you.

On what basis

The law asks a company to say which of its allowed reasons applies to each thing it does. Here they are, matched to the sections above.

Performing our contract with you: writing the reading, taking the payment, keeping the account and the readings bought with it, and the record of what the account did.
Our legitimate interests in running and defending the service: counting where people stop, rate limiting, measuring the adverts we pay for, and the same record of the account when a bank asks. You can object to the counting and the measuring — see below — and they stop.
A legal obligation: keeping the record of each payment for as long as tax and accounting law requires. Stripe holds it, and so do our books.

Your rights

You can ask us what we hold about you and get a copy of it; ask for it to be corrected; ask for it to be deleted; ask us to stop using it while a question is settled; object to the counting and the advert measuring described above; and ask for the readings and details kept against your account in a form you can take elsewhere. Write to support@readpalm.net or use the contact form. We answer within a month, and we do not charge for it.

If you think we have handled your data wrongly, you can complain to the State Data Protection Inspectorate of Lithuania (Valstybinė duomenų apsaugos inspekcija, L. Sapiegos g. 17, 10312 Vilnius, vdai.lrv.lt), or to the data-protection authority of the country you live in.

Children

This is not for people under 16, and it is not intended to be used by them.

Changes

If what happens to your data changes, this page changes with it and the date at the top moves.