RKR Cookies: GDPR banner with Consent Mode v2, real blocking and consent logging for PrestaShop
- One year of technical support and lifetime updates; from the second year, support is extended for €36.28/year and includes taking on your general improvement ideas for the module.
- Renews automatically; cancel whenever you want, with no minimum term.
- One year of technical support and lifetime updates; after that, support ends (with the subscription it is extended for €36.28/year).
- A single payment, with no automatic charges.
Cookie banner with "Reject all" and "Accept all" options, Google Consent Mode v2, real blocking that doesn't affect your payment modules, logging of each consent with CSV export, automatic inventory with the Open Cookie Database, and a self-maintaining cookie policy. Imports settings from hicookielaw, Cookies Plus, and EU Cookie Law. Rekire module, tested in real stores.
Compatible with PrestaShop 1.7.6 to 9.x.
Cookies and consent
A banner that can't be declined is a penalty waiting to happen. One that blocks your payment gateway is a lost sale.
Many cookie modules either block too much and break the checkout, or they fake block and let cookies through before the visitor decides. RKR Cookies Withhold what you don't have consent for, leave your payment modules alone, and keep proof of every decision.
/ An honest banner that the visitor can change whenever they want
The banner can be a bar, a box, or a window, with options to "Reject all," "Accept all," and "Configure." In the settings, each category is disabled except for the essential ones, and next to each category, the providers your store actually uses are listed, along with their cookies, including name, provider, purpose, and duration.
The visitor changes their decision with a floating button, a link in the footer, or any link to #rkrcookies, For example, within your cookie policy page.
/ Google Consent Mode v2, in basic or advanced mode
The default value is the first thing in , Before GTM or gtag, it already carries the returning visitor's choice. Once they decide, the update is sent. Meta, TikTok, Microsoft UET, and Clarity are also notified if they are on the page.
/ Real lock, without removing modules
The HTML is rewritten before submission: scripts from unaccepted categories are rendered inactive, iframes (YouTube, Maps, etc.) are replaced with a "Load this content" message, and pixels and preloads are retained. In the browser, a guardian also blocks anything added via JavaScript (scripts, iframes, cookies, and localStorage keys).
The Payment modules are never blocked. This is how you stop, for example, the Amplitude AMP_* cookie that the Aplazame widget places, without ceasing to display Aplazame as a payment method. You don't have to disable or uninstall anything: your module hooks continue to function.
/ You have proof of each consent.
/ A self-populating cookie inventory
Each visit reports only the names of the cookies and localStorage keys it sees, never of their values. When three different visitors have viewed them on the same day, they are entered into the inventory and categorized using the technical cookies the module knows, your own rules, and the Open Cookie Database (Apache-2.0 license), included in the module.
Anything not recognized is marked as "Pending Review" and held for marketing purposes until you decide. The dashboard notifies you of each unnecessary cookie a visitor viewed before making a decision.
/ A cookie policy that stands on its own
Write the bookmark [rkrcookies_table] On any CMS page, it replaces the inventory table, including third-party sites without their own cookies, such as embedded YouTube. If you don't have a page, the panel creates one with basic text in six languages (Spanish, English, French, Portuguese, Italian, and German). This is a starting point: review it; it's not legal advice.
/ Switch from your current module in a little while
Import the settings from Cookie Compliance Pro (hicookielaw), Cookies Plus, and EU Cookie Law (lgcookieslaw): categories, cookies, blocked modules, scripts, policy page, text, and colors. Payment modules are excluded with a warning. The other module is deactivated, never uninstalled, because uninstalling it would delete its consent records. With Cookies Plus, you can respect the choice your visitors have already made; with the other two, you ask again.
/ Try it before anyone else sees it
/ What worries
The module is installed while disabled if another cookie module is already active, to avoid displaying two banners. When saving the colors, the contrast ratio is checked to ensure it reaches 4.5:1. If you uninstall, the consent log and its snapshots are retained as evidence. License AFL-3.0.
Remote scanner: available soon. A browser of Rekire It will visit your store without touching the banner, after you decline and after you accept, to find cookies from other domains and tell you who places each one. The module already includes this and it activates when the service is running. If you'd like us to set it up for you, Rekire It offers setup as an optional service (€149, excluding VAT): migration from your current module, review of pending items and verification of your payments.
/ Clear limits
RKR Cookies It is not a certified platform for the IAB TCF framework, These are only needed by stores that display third-party ads (AdSense). With Combined JavaScript (CCC), the files within a module cannot be blocked individually, but external scripts, inline snippets, iframes, and cookies can be blocked. Cookies placed by a third party on their own domain can only be prevented by not loading their script or iframe.
Compatible with PrestaShop 1.7.6 a 9.x
Developed and maintained by REQUIRE
- Referencerkrcookies
4 other products in the same category
También podría interesarte
Questions and answers
Nobody has asked anything about this product yet.
























