Privacy

What we keep

A listing keeps the maker's email, the URL, and what they typed — for as long as the listing stays up.

An ask keeps the ask itself, and the email of anyone waiting on it — until it's answered, or they stop waiting.

The newsletter keeps the email and the time it was confirmed — until they unsubscribe.

A sponsor request keeps the email and the package — until it's settled.

Where a form or a click is counted we keep a hash of the network address, salted by the day, for the hourly limits and the counts; it is never the address itself.

What we do not do

No accounts · no cookies · no analytics scripts · no tracking pixels in email · no selling or sharing of a list · no names published from the Demand Board.

Who handles it for us

Supabase holds the database, in US East. Resend sends the email, from the US.

Google, for the two web fonts every page loads and for the small logo images of listings that have no logo of their own (their favicon service). Both see the request's network address; neither gets a cookie from us.

While a page is open it holds a connection to Supabase so the count on Home can include it; the connection carries no identifier and nothing is stored.

Resend's own security page says the transfer runs under the EU-U.S. Data Privacy Framework, alongside standard contractual clauses. Supabase isn't on that framework — it covers the transfer with standard contractual clauses and a UK addendum instead.

Your rights

See, change, or delete anything above — email support@replause.com and it's done inside 7 days.

The edit link in a maker's email changes a listing directly. Every newsletter email and every ask email carries its own one-tap stop.

Who we are

Replause. Contact support@replause.com.

Last updated 9 Sep '26.