Privacy

Waitlist

When you join the Jeval Cloud waitlist, the server stores:

• your email address, lower-cased and trimmed, used as a unique key so repeat signups do not create duplicates;
• the optional answer to “What would you use Jeval to evaluate?” (up to 280 characters), kept from your first signup only;
• the page the form was on (site, docs, demo or cloud page) and an optional short campaign tag from an allowlist;
• the version of the notice shown to you and the time of signup.

The waitlist does not store IP addresses, user-agent strings, page URLs, query strings or browser fingerprints. Rate limiting uses a keyed hash of the request’s network address and email that is discarded after a day and cannot be reversed without the server secret.

Data lives in a Supabase Postgres database. Anonymous database access is denied by row-level security and revoked grants; only the server endpoint that handles the form can write, using a server-only credential. There is no public list, no email automation and no analytics on this site.

We use the email only to contact you about Jeval Cloud early access. Entries are kept until you ask for deletion or the waitlist closes. To be removed, email vrash@signalovernoise.xyz from the address you signed up with; an operator deletes the row with a script and confirms.

Demo

The default demo runs simulated fixtures in your browser and sends nothing. If a deployment enables live mode, the server sends only the bundled preset cases to TypeSafe, never anything you type. The site does not accept free-form prompts.

Open-source framework

The SDK and CLI do not send telemetry. A live run sends the selected fields of each case to TypeSafe using your own API key, under TypeSafe’s terms. Reports are written to your disk and nowhere else.