Skip to content

EP GDPR

EP GDPR is a complete GDPR compliance toolkit for PageMotor. Cookie consent banner, data subject request handling (access, rectification, erasure, portability), consent logging across forms and subscriptions, and integration with every EP Suite plugin that touches personal data.

Published by ElmsPark Studio.

Three pillars of GDPR that the plugin handles:

A customisable banner that asks visitors to accept or reject cookies. Supports granular categories (necessary, analytics, marketing) so visitors can accept some and reject others. Remembers the choice across sessions. Provides a “Revisit consent” link visitors can click at any time to change their mind.

Adds an opt-in consent checkbox above the submit button on every EP Email contact form. The checkbox text and required-or-optional behaviour are configurable. Independent of the cookie banner: a site that has no third-party tracking and therefore needs no banner can still enable form consent for the personal data captured by enquiry forms.

Four rights, handled through a single admin dashboard:

  • Access — “What data do you hold about me?” Generates a JSON or HTML export.
  • Rectification — “This data is wrong, change it.”
  • Erasure — “Delete all my data.” Coordinates with every EP plugin that holds data.
  • Portability — “Give me my data in a machine-readable format.” JSON export.

Each request is logged with timestamps for the full lifecycle (received, confirmed by the requester, under review, completed) so you have an audit trail.

Every form submission, newsletter signup, and booking that happens while EP GDPR is installed logs the consent state at that moment. If a visitor later requests data, you can show them exactly what they consented to and when.

  • PageMotor 0.8.2b or later
  • EP Suite base class

Coordinates with (optional):

  • EP Email — logs consent on form submissions.
  • EP Newsletter — logs consent on subscriptions.
  • EP Booking — logs consent on booking submissions.
  • EP Ecommerce — logs consent on purchases.
  • EP Bunny Fonts — reports compliance on font delivery.
  1. Download ep-gdpr.zip from the EP Suite downloads page.
  2. Upload via Plugins → Manage Plugins. Activate.
  3. Open Plugin Settings → EP GDPR and work through the configuration.
  • Banner text. Shown when the visitor first arrives. The default placeholder (“This website uses cookies to ensure you get the best experience…”) is neutral English; replace with your own wording in any language or variant you prefer.
  • Categories. Necessary (always on, informational), Analytics (EP Analytics doesn’t set cookies, but listed for completeness), Marketing. Add custom categories if a plugin needs them.
  • Position. Bottom banner, top banner, or centre modal.
  • Colours. Match your site styling.
  • Google Consent Mode v2. Off (default), Basic or Advanced. Tells Google tags what each visitor chose: Analytics maps to analytics_storage, Marketing to ad_storage, ad_user_data and ad_personalization, and everything starts as denied. Basic keeps the Google Analytics tag waiting for consent. Advanced loads it at once and sends cookieless pings until the visitor accepts, so Google can model the visitors who decline. Advanced sends pings to Google before consent, so check that suits the rules where you operate; Basic is the cautious choice. The signals also reach a Google Tag Manager container pasted into your pages, ahead of it; set your GTM tags’ consent checks to match.
  • Google Tag Manager Container ID. Empty by default. Puts your GTM container in the head of every page, including pages added later, loaded in step with the banner: straight after the consent defaults when Consent Mode is on, after an Analytics or Marketing choice when it is off. Each choice also reaches the container as the event ep_gdpr_consent (with ep_gdpr_analytics and ep_gdpr_marketing), for tags that are not Google’s. Remove any GTM snippet you pasted into your pages or header first, or it loads twice. On a hosted site, some pages are standalone HTML documents with their own copy of the header: remove the snippet from each of those too.
  • Banner Text by Page Language. For a site in more than one language: one line per language, such as fr: Nous utilisons des cookies. | /fr/confidentialite/ (the part after | is that language’s privacy policy address, optional). A page under /fr/ uses the French line; otherwise the page’s own language decides. The buttons and labels switch too, with Danish, Dutch, English, French, German, Italian, Portuguese and Spanish built in. Pages with no line keep the main banner text.
  • Privacy policy link. Required — the banner must link to your privacy policy.
  • Change-your-choice link. Add [ep-cookie-settings], or any link to #cookie-settings, to your footer or privacy page. It reopens the banner with the visitor’s current choice ticked, so they can change or withdraw it.

Drop [ep-gdpr-request-form] on a dedicated page, typically /privacy-rights/ or similar, linked from your privacy policy.

The form collects:

  • Type of request (access, rectification, erasure, portability).
  • Name, email.
  • Description of the request.
  • Verification: the requester is emailed a link and must confirm the request is theirs. Until they do, the request cannot be exported or erased, and an unconfirmed request is deleted after 30 days.

Submissions land in the admin dashboard for processing.

From Plugin Settings → EP GDPR → Requests:

  1. Click the request to open it.
  2. Check it shows as confirmed (the requester opened the link in their email). A request that reached you another way, for example through EP Email Inbox’s privacy mailbox, needs Mark as confirmed once you have checked who sent it. For high-risk cases, ask for more.
  3. Click Gather data — the plugin queries every EP Suite plugin for records matching the email address, assembles them into a single export.
  4. Review the export for anything to redact.
  5. Send it to the requester (download and email, or use the plugin’s built-in send button).
  6. Mark the request completed.

For erasure:

  1. Click Gather data to see what will be deleted.
  2. Click Erase — every EP Suite plugin deletes or anonymises its records.
  3. The consent log entry for this email stays (audit requirement), but is flagged as “subject erased”.

Admin view shows:

  • Every consent event with timestamp, email, context (which form / plugin), and what they consented to.
  • Searchable by email.
  • Used as evidence when handling data subject requests.

When a plugin hooks into EP GDPR, it:

  • Logs consent on opt-in (form submit, subscription, booking).
  • Exposes data to the data subject request flow.
  • Responds to erasure by deleting or anonymising its records.

EP Email, EP Newsletter, EP Booking, EP Ecommerce, EP Comments, and EP Affiliate all integrate.

A single page shows your compliance status:

  • Cookie consent banner active.
  • Privacy policy linked.
  • Data subject request form configured.
  • Consent logging active on each integrated plugin.
  • Font delivery GDPR-compliant (via EP Bunny Fonts).

Red and green indicators. Green means that area is sorted.

Check Settings → EP GDPR → Cookie consent → Enabled. Also check the banner isn’t being hidden by an ad-blocker — some aggressive blockers hide consent dialogs.

“Erasure didn’t delete a record in plugin X”

Section titled ““Erasure didn’t delete a record in plugin X””

Not every plugin integrates with EP GDPR’s erasure flow. The dashboard shows which do. Manual deletion is required for non-integrated plugins. Log the gap in the review queue if you spot one.

“Data export contains fields that shouldn’t be there”

Section titled ““Data export contains fields that shouldn’t be there””

Plugins control what they expose. If a field shouldn’t be in the export, it’s either sensitive data that’s leaking (bug) or metadata the plugin considers user-facing (intentional). Log specifics in the review queue.

Retention is configurable. Default retains everything. Consider a 24-month retention for non-erasure consent events and indefinite for consents tied to existing active accounts.

“Visitors complain about the banner appearing on every page load”

Section titled ““Visitors complain about the banner appearing on every page load””

Check cookies are being set correctly. If the visitor’s browser blocks all cookies, the banner has no way to remember their choice and shows every time. Nothing to fix — their browser is actively preventing persistence.

For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.

For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.

  • Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.
  • Google Tag Manager, site-wide. A new Google Tag Manager Container ID setting under Cookie Consent Banner puts your GTM container in the head of every page, including pages added later. Remove any GTM snippet you pasted into your pages or header first, or it loads twice.
  • With the banner and Consent Mode on, the container loads straight away, after the consent defaults, so the Google tags inside it know what each visitor chose. With the banner on and Consent Mode off, it waits until the visitor accepts Analytics or Marketing. With the banner off, it loads as GTM’s own snippet would.
  • Each choice is also sent to the container as the event ep_gdpr_consent, with ep_gdpr_analytics and ep_gdpr_marketing set to true or false, so tags that are not Google’s (a Meta pixel, say) can wait for consent.
  • GTM’s noscript part, for visitors with JavaScript off, is not added.
  • The field is empty by default, so updating changes nothing on your site. Requires PageMotor 0.11.5.

A security update. Please install it.

  • The data request form does nothing when it is switched off in settings.
  • Consent to a request is recorded only once the person confirms their email.
  • Exports no longer include conversion tracking rows, and erasure clears the stored IP address and browser details.
  • A request’s confirmation page shows it as done only to the person holding its link.
  • Held scripts now run for returning visitors. A script you hold back with <script type="text/plain" data-consent-category="marketing"> (or "analytics") now runs on every page for a visitor who has already accepted that category, wherever it sits on the page. Before, it only ran on the page where they clicked Accept, so a tracking pixel placed in the page body never fired on their later visits.
  • Global Privacy Control is honoured. Some browsers send a signal asking sites not to share or sell the visitor’s data. When a visitor with that signal has not chosen yet, the banner still appears and adds a short line saying marketing cookies stay off unless they choose to allow them. Marketing stays refused until they act.
  • If that visitor then clicks Accept All, or ticks Marketing and clicks Accept Selected, their own choice wins and marketing is allowed. The saved choice notes that the signal was on, and so does the line in your consent log (gpc=yes).
  • A visitor who chose before is not asked again. The line is translated into all eight built-in languages.
  • Ask whether a visitor has consented. Other plugins and your own code can now ask instead of reading the consent cookie:
    • In the browser: window.epGdprHasConsent('marketing') gives true or false. It also takes 'analytics', and 'necessary', which is always true. It exists only when the banner is switched on, so check it first: if (window.epGdprHasConsent && window.epGdprHasConsent('marketing')) { ... }
    • In PHP: EP_GDPR::has_consent('marketing'), with the same categories and answers: if (class_exists('EP_GDPR') && EP_GDPR::has_consent('marketing')) { ... }. It reads the visitor’s saved choice from the request, so for a page that is saved once and served as it is, ask in the browser instead.
    • Before a visitor chooses, both answer false for analytics and marketing.
  • Pages that are already built pick up the banner by themselves. A page PageMotor hosts as a full HTML document keeps the head it was saved with. Where a host switches the banner on, or changes its text, those pages did not change until someone saved a setting by hand.
  • EP GDPR now notices on the next visit and updates every such page once. Switching the banner off takes it out the same way, and this update reaches your existing pages the same way, with no re-saving.
  • Choices are recorded from the first visitor. On a site where nobody had opened the admin since EP GDPR was switched on, the banner showed but a visitor’s choice was not written to the consent log. It is now.
  • Nothing changes for visitors without the privacy signal, and no settings need changing.
  • Requires PageMotor 0.11.5.
  • The cookie banner can follow the page’s language. For a site in more than one language, a new setting under Cookie Consent Banner, Banner Text by Page Language, takes one line per language: fr: Nous utilisons des cookies.
  • A page under /fr/ uses the French line. Otherwise the page’s own language decides, so a page marked French shows the French banner.
  • The buttons and labels switch with it. Danish, Dutch, English, French, German, Italian, Portuguese and Spanish are built in.
  • Each line can carry its own privacy policy address: fr: Nous utilisons des cookies. | /fr/confidentialite/
  • Pages in a language with no line keep the site-wide banner. One choice covers every language, so a visitor who accepts on a French page is not asked again on an English one.
  • Leave the setting empty and nothing changes.
  • Requires PageMotor 0.11.5.
  • Google Consent Mode v2. A new setting under Cookie Consent Banner tells Google tags what each visitor chose. Analytics maps to analytics_storage; Marketing maps to ad_storage, ad_user_data and ad_personalization. Everything starts as denied.
  • Basic sends the signals and keeps Google tags waiting for consent, as before.
  • Advanced loads Google Analytics straight away. Until the visitor accepts, Google gets cookieless pings only, which it uses to model the visitors who decline.
  • The signals reach Google Tag Manager containers pasted into your pages as well, ahead of the container.
  • Advanced sends pings to Google before consent. Check that suits the rules where you operate; Basic is the cautious choice.
  • Off by default, so updating changes nothing until you choose a mode.
  • Requires PageMotor 0.11.5.
  • Handle data requests from Claude or any AI assistant connected to your site. It can list your open requests with their legal 30-day due date, how many days are left and which are overdue.
  • It can show what your site holds on an email address, counted per plugin. That covers EP Events, EP Holiday Bookings, EP Booking, EP Newsletter and every other plugin that answers data requests. The records themselves stay out of the conversation unless you ask to see them.
  • It can move a request along, mark a requester’s identity as checked, and erase a person’s data. Each step that emails the requester, vouches for them or deletes anything first says what it will do and waits for your yes.
  • Erasure is still refused for a request whose email address has not been confirmed.
  • Requester IP addresses and confirmation tokens never appear in these answers.
  • Requires PageMotor 0.11.5.
  • Affiliate sales and bookings made by the person. When someone buys or books through an affiliate’s link, EP Affiliate keeps their email on the affiliate’s commission record. Look-ups and exports now include those records, and erasing the person removes their email from them. The commission record itself stays, because it is part of the affiliate’s earnings. Before, EP GDPR only found these records for the affiliate.
  • With EP Booking Zoom 1.0.23, a person’s Zoom meetings are now found, exported and deleted too.
  • The cookie banner now appears on sites built from standalone HTML pages. On a site whose pages are standalone HTML documents rather than built through a theme, the banner never showed, even with it switched on. It now shows on every page.
  • Google Analytics now waits for consent. With the banner switched on, the Measurement ID you enter in PageMotor’s own Google Analytics settings is no longer loaded straight away. It loads only after a visitor accepts analytics cookies, and not at all if they reject them. Nothing to change on your side: your ID stays where it is.
  • When Google Analytics is set up, the banner always offers the Analytics choice, so visitors can consent to it.
  • Data requests from affiliates work again. On a site running EP Affiliate, an access or export request for someone who is an affiliate stopped with a database error, because EP GDPR asked for affiliate details under names EP Affiliate does not use. The export now includes their affiliate account (with their earnings and balances), referrals, commissions and payouts.
  • Erasure requests from affiliates work again. Erasing an affiliate failed for the same reason, part-way through. The affiliate account is now anonymised and suspended (kept for your financial records, as before), and its custom link, notes and portal access are cleared too.
  • Requests must now be confirmed by the owner of the email address. The address gets a confirmation email, the request shows as “Awaiting email confirmation” until it is confirmed, and Erase Data and Export Data are not offered before then. If you have checked someone’s identity another way, use “Mark as confirmed”. Requests already on your list count as confirmed.
  • Tightens security on the data request form.
  • Erasure and export now match the exact email address only.
  • The newsletter send log is now included in exports and erasures (every newsletter or transactional email sent to the person).
  • Visitors can now change or withdraw their cookie choice. Once a choice was made the banner never came back. Add [ep-cookie-settings] (or any link to #cookie-settings) to your footer or privacy page and it reopens the banner with the current choice ticked. Withdrawing consent reloads the page, so blocked scripts stop running.
  • Cookie choices are now recorded. Each choice is saved in the consent log (no email address, just a random ID kept in the visitor’s cookie, what they chose and the banner wording shown), so you can show what was agreed and when.
  • The contact-form consent box now counts. When marked required, a message without it ticked is refused on the server too, not just in the browser. A ticked box is now saved in the consent log with the wording shown and the sender’s email address.
  • Tightens security on the emails sent about data requests.
  • Malformed form submissions now get a normal error message.
  • Request emails use your email provider. When EP Email sends through Mailgun, Brevo or SendGrid, the notice you receive about a new data protection request, and the acknowledgement the visitor receives, now go out through that provider. Before, they were handed to the server’s own mail function, which many hosts silently discard, so requests could arrive in your dashboard without anyone being told.
  • Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
  • Danish. Adds a Danish translation.
  • Section status. Each settings section shows whether that feature is switched on. On a site that also runs an older EP plugin, the section shows its plain title instead.
  • Fixes EP GDPR switching itself off for one admin page a day. Once a day, the first admin page to load ran the data-request deadline check, and on PageMotor 0.11 that check failed on its own saved list of reminders already sent. The failure stopped EP GDPR loading for that one page view, so its consent and privacy features were missing on that page, and the day’s reminder check never finished.
  • It only happened once at least one data request had been open long enough to earn a reminder. The check now reads that list correctly on every PageMotor version.
  • The daily housekeeping (old-data purge and deadline reminders) can no longer stop the plugin loading. If it ever fails again, it logs one line and the rest of EP GDPR carries on.
  • No reminders are sent twice: requests already reminded stay remembered.
  • Also brings the shared ElmsPark admin layout up to date: the brand-colour control has moved out of the page header into a Branding section in Settings. Nothing else about your settings changes.
  • Plainer punctuation in the words your visitors see. The consent categories, the data request form’s five rights, the retention and reminder choices in Settings, and every line of the generated privacy policy used a long dash to join a label to its explanation (“Right of access — obtain a copy…”). Those now read with a colon or brackets instead (“Right of access: obtain a copy…”, “Never (keep indefinitely)”). Nothing about what the form or the policy does has changed, and any wording you have overridden through the language file is left exactly as you set it.
  • Fixes a crash on the data request form when an older EP plugin is installed on the same site. Submitting the form returned an internal error and nothing was saved or sent. EP plugins share one common code library, and whichever copy loads first is the one every EP plugin on that site uses, so a single out-of-date plugin could leave this one calling a spam check its copy did not have. The check now carries its own fallback and no longer depends on another plugin being up to date.
  • No change on a site where this never happened: the same spam check runs, and nothing else changed.
  • Blocks a spam bot that was getting past the form honeypot. The scraper changed its network address on every single request, so blocking by address never caught it, but it always sent a malformed browser identifier that no real browser sends. Forms now reject anything carrying that signature, with the same silent response a caught bot already got.
  • It was not theoretical. One client site had taken 57 fake signups before this went in, and the same bot had hit 17 sites.