Apelles Request beta access

Legal

Privacy Policy

Last updated October 29, 2026. Short version: the only thing you give us is an email address, only if you ask for beta access, and we do not store your IP address — plus cookieless, anonymous visit stats every page load sends automatically.

What this site collects

If you use the "Request beta access" form (on the home page, or the one in the hero), we store a row about you in our own database. Exactly these fields: the email address you typed (lowercased); what you make, only if you chose to answer, from a fixed list; which of the two forms you used; whether you have confirmed your address, unsubscribed, or not yet done either; two random single-use link codes (one for confirming, one for unsubscribing); and the times you signed up, were last sent the confirmation email, confirmed and unsubscribed; and a flag that says whether the confirmation email is waiting to be sent (we cap how many we send per day). We also keep a bare count of when confirmation emails were sent, with no address attached. We do not store your IP address, browser, device or any other detail of the request, and the signup does not set a cookie. Nothing else on this site asks you for anything.

What we do with it

We email you once to confirm the address (so nobody can sign up someone else), and after you confirm, we use it to tell you about new builds and news of Apelles. Every such email carries an unsubscribe link, and mail programs that support it show their own unsubscribe button. We do not sell it, rent it, or share it with anyone for their marketing.

Who actually receives it

Two service providers handle your address on our behalf, and nobody else does. A third, Cloudflare Turnstile, checks that you are a person and never sees your address (below). Cloudflare, which hosts this site, runs the database that holds the row described above. Resend sends our email: your address goes to it for the confirmation message, and once you confirm, it also keeps a copy of your address in a contact list we use to send announcements (with your unsubscribe status). Resend's open and click tracking is switched off for our messages. Confirmation emails come from mail.apelles.studio and replies reach hello@apelles.studio. Read Cloudflare's and Resend's privacy policies for how they handle data on their side. We use no CRM and no analytics tool to process your address further.

The bot check

To stop scripts from mass-subscribing other people's addresses, the signup forms use Cloudflare Turnstile. When you load the page, Cloudflare's script runs a short check in your browser (usually invisible) and returns a one-use token. We send that token to Cloudflare to confirm it is genuine, and we store nothing from it. Cloudflare processes the signals from your browser to make that decision, under its own privacy policy; we do not receive them, and the check does not set a cookie of ours.

Cookies and tracking

This site sets no cookies of its own, and runs one analytics script: Cloudflare Web Analytics, which the site's own infrastructure host enables automatically for any site it hosts. It is built specifically to avoid the things a cookie banner exists to gate: no cookies, no browser storage, and — per Cloudflare's own design for this product — no fingerprinting or persistent identifier used to recognise you across visits or other sites. What it does send, on every page load, is aggregate, anonymous traffic data (which pages get visited, roughly how fast they load, in what country and browser) that cannot be tied back to you individually. Read Cloudflare's own privacy policy for exactly what it collects and how. Because none of this identifies you or persists across visits, it doesn't trigger a cookie-consent requirement, so this page still has no cookie banner — a banner gating consent for tracking that isn't the identifying kind would be exactly the kind of decoration this site tries not to ship. This is the one thing that changed since this page was first written (found live, via a Lighthouse trace, not assumed); if the site's own behaviour changes again, this page changes with it, in the same commit.

The home page embeds two videos with YouTube's own player, using its privacy-enhanced mode (youtube-nocookie.com). The players load as you scroll to them, and from then on YouTube receives what any embedded player sends it, under Google's privacy policy; in privacy-enhanced mode YouTube says it does not use your viewing of the embed to personalise what you see elsewhere. No other page loads anything from YouTube.

One narrow exception, for transparency: a development-only tool used while building this site (a position-tuning panel for the home page's hero image) writes a few numeric values to your browser's own localStorage if you happen to load the site while it is running in development mode. That tool is compiled out of the production build entirely — it does not exist in the site you are reading this on.

How long we keep it

Until you ask us to delete it. If you unsubscribe, we keep the row, marked as unsubscribed, so that we do not email you again; ask us and we will delete it entirely, from our database and from Resend. An address that never confirms is never mailed again unless its owner signs up again. There is no automated deletion schedule.

Your choices

  • Don't want to be contacted? Don't use the form, or ignore the confirmation email and nothing further happens.
  • Want to stop? Every email has an unsubscribe link.
  • Want your address deleted? Email us and we will remove it.
  • Want to know exactly what we hold? Ask. It is the fields listed above, for your address only.

Contact

For anything on this page — a deletion request, a question about what we hold — email ashish.1999vns@gmail.com, the owner's own inbox.

Changes to this page

If what this site actually collects or does with it changes, this page changes in the same commit — that is a standing rule for this whole codebase (see this repo's own CLAUDE.md), not a promise made separately from the code.

This page is a good-faith, factually accurate description of what this site's own code does, written and checked against that code rather than assumed — it is not a substitute for legal advice, and has not been reviewed by a lawyer. Before relying on it for a real public launch, especially for visitors in the EU (GDPR) or California (CCPA), have it reviewed by one.