← Back to Ripple

Your information,
treated with care.

This notice covers Ripple’s early-access waitlist. Updated 17 November 2026.

What you share

We collect your name and email address, whether you’re joining as an individual or an organisation, and your answers to the sign-up questions. For individuals, that’s the causes you care about, any goal you share, the kinds of actions and time that suit you, your town or area and university if you give them, what has stopped you getting involved and what would keep you coming back. For organisations, it’s your organisation’s name, type, area, focus, what people could help with, what you’d like from Ripple, its approximate reach and your role. Most questions are optional. We record when you joined, your agreement to receive pilot and launch updates, whether you’re happy for us to contact you for feedback or a call, and whether you’ve confirmed your email address. We send one email asking you to confirm it.

Why we collect it

The Ripple team will use these details to contact you about the pilot and launch, to understand which causes and kinds of actions people and organisations are interested in, to plan the pilot and suggest relevant actions, and, if you agreed, to contact you for feedback or a call. Joining is optional. We won’t sell your details.

Where it goes

The waitlist is stored in the website’s database on Cloudflare infrastructure. Only the Ripple team can view, export and remove entries, through Cloudflare’s secured account dashboard. Hosting providers process the information to operate the website, and our email provider, Resend, processes your name and email address to send the confirmation email.

Changing your mind

You can ask to leave the waitlist, correct your details or request a copy by replying to any Ripple update you receive. The team can remove your record from the waitlist. Details will be kept while the waitlist is active, unless you ask for removal sooner.

Website operation

The waitlist does not require an account. To limit spam, submission attempts use an hourly hash of a network address; these temporary records expire after an hour and are cleared on subsequent successful submissions. Hosting providers may also maintain operational logs.

Back to the waitlist →