Privacy, in plain language.

This notice covers the Raahi website and launch waitlist—not a future astrology app.

What the website collects

The illustrative preview does not ask for birth details, record your voice or provide personalised readings. Optional sample audio uses your browser’s speech feature. Your browser or operating-system provider may process text to generate that audio.

Our hosting infrastructure processes technical request information, such as network addresses and browser information, to deliver and secure the website. This website does not promise complete anonymity.

If you join the waitlist

We store your email address, signup time, your agreement to a launch notification and a hashed removal token in the website’s Cloudflare-hosted database. Only authorised project administrators can access signup records. There is no public signup directory.

Your email is for letting you know when Raahi launches. Joining does not subscribe you to a newsletter. This form does not send an immediate confirmation email or connect your email to an AI model.

Spam protection

We use a hidden form field and a short-lived hashed identifier derived from a network address and hourly time window to limit repeated requests. This identifier is not used to build an advertising profile. Expired rate-limit records are cleared on subsequent requests.

Leaving the list

After a new signup, we show a personal removal link. Save it; anyone with that link can remove that signup. Opening the link does not remove you until you confirm. Duplicate signups do not generate a new link.

Without the link, email founder@meetraahi.com from the address you registered to request removal or ask about your information.

Signup records more than a year old are removed on subsequent waitlist requests. We do not use aged records for launch notifications. Removal deletes the live record; hosting backups and technical logs may have separate retention.

Before the app launches

Birth-chart information, voice conversations, accounts and memory will need their own disclosures and controls. We will explain those practices before asking you to use those features.