For founders and agencies collecting launch emails from EU, EEA or UK visitors on a WordPress coming-soon or maintenance page.

Try it freeFull version · $60 →
What you get: Collect launch signups on your coming-soon or maintenance page with consent off by default, and keep the exact wording each person chose.
Updated 2026-10-11 · ReadyStack
For founders and agencies collecting launch emails from EU, EEA or UK visitors on a WordPress coming-soon or maintenance page. Under GDPR Art. 7(1) you must be able to show what each person agreed to. Type your details and one test signup below to see the exact row the plugin stores.
| created_at | |
| country | |
| consent | |
| Purposes covered | |
| Launch email (planned) |
This is one row of the plugin's signup table. The free plugin shows the consent wording in your WordPress admin, 50 signups per page. The full version exports every row with its date and time as a CSV.
Full version — $60 once · get the plugin with the CSV export
The full version adds a launch-day CSV export with the date and time of every signup, a receipt email to the subscriber, a new-signup alert to you, search by email and one waitlist per product (shortcode name attribute). One payment, not a subscription.
Many subscribe boxes keep the address only. If a data-protection authority asks you to demonstrate consent (Art. 7(1) GDPR), an address alone does not show when the person agreed or to what. Breaching the conditions for consent sits in the higher fine tier of Art. 83(5)(a): up to 20,000,000 EUR or 4% of total worldwide annual turnover, whichever is higher.
coming-soon-waitlist-consent-log.zip.[coming-soon-waitlist-consent-log] on your coming-soon or maintenance page.Requires WordPress 6.0 or later and PHP 7.4 or later; WordPress refuses the upload on an older PHP. Menu names vary a little by WordPress version and admin language. The form works on any page that renders shortcodes, including a page your coming-soon plugin shows. It does not switch your site into maintenance mode itself.
Collect launch signups on your coming-soon or maintenance page with consent off by default, and keep the exact wording each person chose. GDPR Art. 7(1): you must be able to show it; consent
One payment, one licence key for this tool. The key is shown right after payment.
GDPR Art. 83(5)(a): infringing the conditions for consent (Arts. 5, 6, 7, 9) carries fines up to 20,000,000 EUR or 4% of total worldwide annual turnover, whichever is higher. Art. 7(1): the controller shall be able to demonstrate
Buy the full version — $60I have a keyThis tool is 1 of 333 paid tools in English. All 333 with one key: Freelancer & Small Business Pass — $9.99/month · $79/year · Deadline reminders by email (free)
Need more than this one? ReadyStack Pass opens all 679 files and 561 full versions — $29/month or $199/year. See the Pass →
Paste this code into your page. It runs in your visitor’s browser and stays up to date. Nothing your visitors type is stored.
For businesses: your name and logo instead of ours, and each visitor’s result + e-mail in your inbox (only when they tick consent) — Pro from $19/month. See Pro →
· ReadyStack
Real numbers from this tool, line by line.

6 signups, 2 without consent: that is what a test coming-soon page waitlist showed. Those two are what a founder or agency in the EU or UK would be left holding if they emailed the whole list on launch day. We ran 6 signups through the free plugin. Four visitors picked a consent sentence; two left the answer at its default, "Not chosen: do not email me". Every row kept its created_at timestamp and the wording chosen:
| # | consent answer | |
|---|---|---|
| 1 | lena@example.eu | I agree: email me once when you launch. |
| 2 | tom@example.co.uk | Not chosen: do not email me |
| 3 | ana@example.es | I agree: email me at launch and about early-access offers. |
| 4 | marc@example.fr | I agree: email me once when you launch. |
| 5 | jo@example.de | Not chosen: do not email me |
| 6 | sam@example.com | I agree: email me once when you launch. |
The two "Not chosen" rows are the people you must leave out of the launch email.
Many coming-soon subscribe boxes either store the address alone or put a pre-ticked box next to it. The Court of Justice of the EU held in Planet49 (C-673/17) that a pre-ticked box is not valid consent. So this form makes the visitor choose. The consent question has 3 answers and starts at "Not chosen". Only a visitor who actively picks one of the two "I agree" sentences counts as consenting, and the plugin stores that exact sentence in the row.
Art. 7(1) GDPR: where processing is based on consent, the controller shall be able to demonstrate that the data subject has consented. An address alone shows neither when someone agreed nor to what. Each row of this plugin has the date and time, the country the visitor chose, and the consent sentence itself. The two "I agree" sentences separate a single launch announcement from launch plus early-access offers, so the purpose is in the record too.
Breaching the conditions for consent sits in the higher fine tier of Art. 83(5)(a): up to 20,000,000 EUR or 4% of total worldwide annual turnover, whichever is higher.
The form has 7 inputs: email, first name, company, country, what the product should do for the visitor, how they heard about you, and the consent answer. Email, country and consent are required. The 4 settings are who collects the emails, the privacy notice link, the planned launch date, and the address for alerts. The first three are printed above the form. Setup is 3 steps: upload the zip, activate it, and paste the shortcode on your coming-soon or maintenance page. A nonce check and a honeypot sit on every submission.
The free plugin is complete for collecting and keeping the record: the admin list shows every signup with its consent wording, 50 per page. The full version is for taking the list out of WordPress on launch day. It adds a CSV with id, created_at, all 7 inputs and the waitlist name, a receipt email to the subscriber, a new-signup alert, search by email, and one waitlist per product.
The free web page takes your company name, privacy link, launch date and one test signup. It shows the exact row the plugin would store and whether you may email that person at launch.
It adds a waitlist form to your coming-soon or maintenance page with one shortcode. The consent question starts at 'Not chosen: do not email me', so consent only counts when the visitor picks one of two wordings. Each signup is saved with its date and time and the wording chosen, the record GDPR Art. 7(1) expects you to be able to show.
Founders, agencies and freelancers who put a WordPress site into coming-soon or maintenance mode before a launch, collect emails from EU, EEA or UK visitors, and need to show each person's consent later. That could be for a client, an auditor or a data-protection authority asking for proof.
Many built-in subscribe boxes store only the address, and a pre-ticked box is not valid consent (CJEU Planet49, C-673/17). Art. 7(1) GDPR says you must be able to demonstrate consent. This form starts at 'do not email me' and stores the sentence each person actively chose.
The free plugin is complete for collecting: a form with 7 inputs and consent off by default, 4 settings (who collects, privacy link, launch date, alert address), honeypot and nonce checks, and the admin list of every signup with its consent wording, 50 per page. Setup takes 3 steps. Nothing is time-limited and no entries are hidden.
The paid version adds a launch-day CSV with the date and time of every signup, a receipt email to the subscriber, a new-signup alert, search by email and one waitlist per product. Under Art. 83(5)(a) GDPR, breaching the conditions for consent can be fined up to 20,000,000 EUR or 4% of worldwide turnover.
One question, answered by the person who built it. Your email only if you want the answer sent.
For a team or company: for an invoice with your company details, a quote or several licences, write to support@getreadystack.com.
ReadyStack is a small team. We build each tool for one job people keep asking about, from the rules and sources named on the page, and we run it on the worked example you see here before it goes live.
How this page was checked: Updated 2026-10-11
Something looks wrong, or you are stuck? Write to support@getreadystack.com or use the contact form. It goes to our own inbox, not to a bot.
ReadyStack
Calculators, templates and deadlines for the rules that change every year — free in your browser.