Privacy

Use synthetic data, not visitor data.

What SubmitCanary stores during the public beta, why, who processes it, and how you stay in control. Last updated 4 November 2026.

Who is responsible

SubmitCanary is operated by John Gilbert Soliveres, an independent freelancer (Partita IVA, Italy), who is the data controller. Privacy contact: jg.soliveres93@icloud.com.

When you create a beta monitor

We store the alert email address you give us, the form name, the website address and exact form page, the language you signed up in, and the source, campaign and first page that brought you to the site. We then store each check: when it ran, the result of each stage (page, form, submission, email), short error descriptions, and the alert emails we sent you. We use this to run the service: performing the checks, emailing you about failures and recoveries, and showing your status page.

Synthetic tests, not visitor data

Each test uses clearly labelled fictional details (a "Synthetic Monitor" name, a .test email address and a unique run ID). The companion plugin reroutes only that signed test message to our test inbox, where we record its sender, recipient, subject and arrival time to confirm delivery. Genuine enquiries from your visitors stay on your normal mail path and are never sent to us or stored by us.

Free page check

The free check receives the public address you enter and reads that page once to report technical form signals. It never submits the form. To learn whether the check is useful, we count completed checks, whether a form was found, and the source, campaign and landing page that brought you here. We do not store the checked address, your IP address or any visitor identifier in these records.

Where visitors come from

To learn which channels bring people to the beta, your browser keeps one small note for up to 30 days: the source you arrived from (for example a LinkedIn post, a Google search or a direct visit), the campaign name in the link, and the first page you opened. It is stored in your own browser's local storage, contains no identifier and nothing personal, and is never shared with other sites. When you create a beta monitor, that source, campaign and page are saved with your monitor. You can clear the note at any time by clearing this site's data in your browser. We also use Vercel Web Analytics, which counts page views without cookies.

Launch list

If you joined the earlier launch list, we store your email address, selected plan, signup page, consent time and status, plus the campaign source and landing page when present in the link you followed.

Service providers

Vercel hosts the website. Supabase stores the data in the European Union (Paris region). Resend sends our emails and receives the test messages, in its EU region. GitHub Actions runs the scheduled checks and only processes the page address and the synthetic test. If paid plans are enabled, Stripe handles payments directly; we never store card numbers. Some providers are US companies and may process data outside the EU under their standard contractual safeguards.

How long we keep it

Monitor details and check history are kept while your monitor exists. Launch-list records are kept until launch, withdrawal or a legal retention need. Ask us at any time and we delete your monitor and its history.

Your choices and rights

Every alert email links to your private status page, where you can pause or resume monitoring at any time. You can ask to access, correct, export or delete your data, or object to how we use it, by emailing jg.soliveres93@icloud.com. You also have the right to complain to the Italian data protection authority (Garante per la protezione dei dati personali) or the authority where you live.

This is a plain-language policy for the public beta, not legal advice.

Check your form before a customer does.

Free during the public beta for one simple WordPress contact form.

Set up free monitoring