What we collect, and what we do with it.

What the beta form stores

When you request beta access, we store the fields you submitted:

• Your email address — required, because it is how we reply.
• Your company, expected volume, service interests and note — optional or chosen from a list, and used to decide who to invite and in what order.
• The time you submitted the form.

What we do not store

We do not store your IP address. To stop one machine from flooding the form, we store a one-way HMAC of it against a counter — the address itself is never written down, and the hash cannot be turned back into it.

PixelDepot sets no cookies of its own, and the site carries no advertising or third-party tracking scripts.

What we use it for

To contact you about beta access to the services you selected, and to plan capacity for them. That is the entire purpose.

We do not sell it, rent it, or share it with anyone for their own marketing. We do not add you to a newsletter. If we ever want to email you about something other than the beta, we will ask first.

Where it is held

In a Supabase Postgres database in AWS us-east-1, and on Vercel, which serves this site. Both process data on our instructions as our providers.

The table is not readable by the browser: the key that ships to your browser has no access to it at all, and only PixelDepot staff can read the list.

How long we keep it

Until you ask us to remove it, or until the beta programme ends and the list has served its purpose — whichever comes first.

Removing your details

Email privacy@pixeldepot.ai and we will delete your row and confirm that we have. You do not need to give a reason. You can also ask what we hold about you and we will send it back.

If you are in the UK or the EU, this is your right of erasure and right of access. We answer both the same way regardless of where you are.

The API, when it exists

No PixelDepot API is serving traffic today, so no customer images are being processed or stored. The homepage describes how images will be handled — deleted within 24 hours by default, never used for training without a separate agreement — and that becomes a commitment when the service launches, documented here against what the code does rather than what the marketing says.

Changes

This notice is versioned in the same repository as the site, so every change to it is a dated, reviewable commit. If a change affects what we do with information you have already given us, we will email the address you gave us before it takes effect.