Privacy

Short version: we take one photo, use it to write one reading, then delete the photo. There is no account, and no analytics unless you accept them.

What we do with your photo

The photo you capture or upload is sent to our server, and from there to Anthropic's Claude API, which is the model that actually looks at your hand. Anthropic is the only third party your photo ever reaches, and it is involved because it is the reader. Your reading also reaches Resend, but only if you ask us to email it to you (see below).

Other third parties are involved in the pages themselves, and none of them is sent your photo. Every page on this site loads its typefaces from Google Fonts, which happens as the page loads and therefore before you answer the consent banner. Google receives the request for the font files, which means your IP address and your browser's user agent. It receives nothing else. No photo, no reading, no identifier.

Here is exactly what happens to the photo. Your browser sends it to our server at full resolution, together with a small, low resolution thumbnail it makes from it on your device. Our server sends the full photo to Anthropic twice: once to check that it shows a palm, and once to read it. As soon as your reading is written, the full photo is deleted from our server. A photo that turns out not to show a palm is deleted at once, thumbnail and all. A photo whose reading is never finished is deleted about a day after it was sent. What Anthropic does with what it receives is covered by its own terms for its API.

The thumbnail is kept with your reading so you can see which hand the reading came from, but it is deliberately too small for details like fingerprints to be legible. This holds for every mode: one hand, two hands, or a Saath.

Analytics, only if you accept

The banner at the bottom of your first page asks once. If you tap Accept, we use Google Analytics and Microsoft Clarity to see which pages help and where people get stuck. Google Analytics counts visits to pages and sets its own cookies to tell one visit from the next. Clarity records how a page is used, such as scrolling and taps, and sets its own cookies too. The text of readings is hidden from Clarity on every page that shows one. We never turn on Google's advertising features.

If you tap Only what's needed, or until you choose, Clarity is not loaded at all. Neither Google Analytics nor Clarity is loaded, and no request goes to Google or Microsoft for them. This page loads neither.

Separately, we use Cloudflare Web Analytics, which counts page views without cookies and without following you across sites, so it does not wait for a choice. You can change your choice any time with the switch just below.

Analytics on this browser: not chosen yet. Turn on

What we keep

• The written reading and the notes it was composed from.
• Which hand you told us it was.
• Your answers to the one or two co-sign questions, if you answered them.
• A short technical log of the run, for fixing things when they break.
• Your conversation with Hasta about the reading, if you use the chat, kept with the reading so it is still there when you come back.
• Any translation of the reading you ask for, kept so it does not have to be paid for in time twice.
• Whether the reading has been completed, and the email address you typed if you asked for the completed report by email. See the note below.
• If you downloaded your reading as a PDF: the address you typed for it, whether you ticked the box for updates, and when. See the note below.
• Where you arrived from, as your browser noted it on your first visit and on your latest one: the campaign tags on the link you followed (such as utm_source), which ad network's click marker was on it (the network's name, not the marker itself), the website that sent you, and the app whose built-in browser you are using, such as Instagram. It is sent with your photo and kept with the reading, so we can tell which places bring readers. It holds nothing about who you are.
• If you asked for a reminder to read your other hand: the address you typed, only until that one reminder is sent or you cancel it. Then it is deleted.
• If you sent a Saath invitation: the link's token, which of your hands it was for, and the Saath it made. Neither of you is shown the other's own reading.
• Which lines of the reading you marked as landing or not landing, if you tapped those.
• If you made a share link: the link's own token, a count of opens, and a random identifier per visitor so the same person opening twice is not counted twice. For a reading made by somebody who arrived through the link, we keep which reading it was and that browser's random identifier, so one browser counts once towards the referral unlock. That identifier is not a name.
• The purchase session that holds any completions on this browser, under a random session identifier this browser generates.

Each reading lives under a random identifier and nothing in it carries your name or your phone number, because we never ask for either.

About email. We do not ask for an email address to make a reading or to share it, and you never need one for either. An address is only ever asked for in four places, each for one stated purpose, and only if you type one:

• Email me my reading, under any finished reading. We send the free part of your reading and a link to it, once. The address is used for that one send and is not kept: we keep only that a send happened and whether it worked. There is one exception, and it is yours to choose: if you tick the unticked-by-default box offering follow-up mail, we also keep the address, the fact that you agreed and the time, with that reading on our server, and may write to you about Hasta. Ask us to delete it and we will.
• Remind me to read my other hand, under any finished reading. We send one email, once, three days later, as the page says when you ask. The address is kept with that one reminder until it is sent, then deleted. Cancelling before then deletes it at once.
• Download PDF, on a reading that has not been completed. We ask for an address before the download, save your PDF on your device and email you a copy. That address is kept, with that reading on our server, together with where you arrived from. Below it is a separate box, unticked unless you tick it: Send me occasional updates from Hasta. Only if you tick it may we write to you about Hasta later: a few short notes about your reading over the next two weeks, then only now and then. Every one of them has a link at the foot that stops them with one click, and stopping them also switches the box off on our side. Without the tick, the address is used for that copy only.
• Email the report, after a reading is completed. We send the report as a PDF. That address is stored with the reading, in entitlement.json, so we can tell you whether the send worked.

In each case the address is passed to Resend, the service that actually delivers the mail; they need it to deliver the message. Nothing else is ever sent to an address you type unless you ticked a box offering it: no newsletter, no marketing, no second message you did not ask for. To have a kept address deleted, use the delete link under that reading's email box, or write to us. If you would rather we did not hold it, do not type it, and the reading works exactly the same.

What stays on your device

Your list of readings is kept in this browser's local storage, under the key hasta2.readings. It holds only the reading identifier, the date and which hand it was. It never reaches our server. Next to it, under hasta2.src, is where you arrived from (see above); that one is sent with your photo when you make a reading. Your answer to the banner is kept under hasta2.analytics and hasta2.consent. Clear your browser data and the list is gone, though the readings themselves remain reachable by their own links.

What we do not do

• No accounts and no passwords. No email address is needed to make, read or share a reading. Downloading the PDF of a reading that has not been completed asks for one, as above.
• No advertising pixels, and no analytics unless you tap Accept. Then it is Google Analytics and Microsoft Clarity, as described above, and nothing else.
• One cookie, and only if you arrive on somebody's share link: h2ref, which holds that link's token for 30 days so the person who sent it can be told their link led to a reading. When two friends' own readings have been made through one person's link, that person's reading is completed free, once. It carries no name and nothing about you. That is our only cookie. If you accepted analytics, Google Analytics and Microsoft Clarity set their own cookies as well, such as _ga, _clck and _clsk. Without that, nothing else on this site sets a cookie.
• No selling or sharing of readings with anyone.

What Hasta is today

Hasta is early, and a reading stored here may be cleared at any time while the product is still being built. If a reading matters to you, complete it and download its PDF.

Removing a reading

Use "Forget" on the My readings page to drop a reading from this device. To have the stored reading itself deleted from the server, send us its reading number.