

ConsentOwl is a lightweight, cache-friendly cookie consent manager for WordPress. It shows a consent banner, groups cookies into categories, and only loads analytics and marketing scripts after the visitor agrees.
Built with privacy laws in mind — GDPR, ePrivacy, Russian Federal Law No. 152-FZ “On Personal Data” and Belarus Law No. 99-Z — ConsentOwl helps you meet these requirements out of the box.
For sites operating in Russia, Federal Law No. 152-FZ treats cookies that can identify a user (for example via IP address or browsing history) as personal data. Their processing requires the visitor’s informed, active consent (Art. 6). ConsentOwl shows a consent banner before non-essential cookies load, lets visitors accept, reject or choose categories, keeps an audit log of every decision, and can generate a draft cookie policy page — the building blocks for 152-FZ compliance. Note that full compliance also requires actions outside any plugin (such as filing a notification with Roskomnadzor and publishing a personal-data policy); ConsentOwl is a tool, not legal advice.
Languages: ConsentOwl ships with English, Russian and Spanish (Spain and Mexico) translations. On a fresh install the banner texts appear in your site’s language automatically; after changing the site language you can refresh them with one click in ConsentOwl Texts.
Core features (free forever):
[consentowl_settings_link] shortcode for a footer “Cookie settings” linkThe core features are free forever.
ConsentOwl stores every consent record in your own WordPress database — nothing is ever sent to an external cloud, third-party server, or the plugin author. There is no external account, no data transfer abroad, and no dependency on a SaaS service.
This local-only storage matters for compliance:
ConsentOwl is a tool that helps you meet these requirements; it is not legal advice, and full compliance also depends on your hosting location and other measures.
The free version is fully functional, but it asks you to do one thing by hand: find every tracker on your site (in your theme, widgets or Google Tag Manager) and wrap it so it only loads after consent. Miss one, and you may be loading cookies without permission — the exact thing privacy law penalises.
ConsentOwl Pro removes the manual work:
In short: Free keeps you compliant if you’re willing to configure trackers by hand. Pro does it for you automatically — saving time and reducing the risk of missing something.
What’s in Free (free forever):
What Pro adds:
ConsentOwl Pro is available at https://itorbita.by/product/consentowl-pro
This plugin can load the following third-party services only after the visitor gives consent for the corresponding category. None of them are contacted before consent.
Google Analytics / Google Tag Manager (gtag.js)
When you enable the built-in “Google Analytics” service and a visitor consents to the Analytics category, the plugin loads the gtag.js script from https://www.googletagmanager.com/gtag/js. This sends the visitor’s analytics events to Google so you can measure site traffic. It is only used if you enter your Measurement ID and the visitor consents.
Terms: https://policies.google.com/terms — Privacy: https://policies.google.com/privacy
Meta Pixel (Facebook)
When you enable the built-in “Meta Pixel” service and a visitor consents to the Marketing category, the plugin loads the Facebook events script from https://connect.facebook.net/en_US/fbevents.js. This sends marketing/conversion events to Meta. It is only used if you enter your Pixel ID and the visitor consents.
Terms: https://www.facebook.com/legal/terms — Privacy: https://www.facebook.com/privacy/policy/
Yandex Metrica
When you enable the built-in “Yandex Metrica” service and a visitor consents to the Analytics category, the plugin loads the Metrica script from https://mc.yandex.ru/metrika/tag.js. This sends analytics events to Yandex. It is only used if you enter your counter ID and the visitor consents.
Terms: https://yandex.com/legal/metrica_termsofuse/ — Privacy: https://yandex.com/legal/confidential/
Google Maps and YouTube are handled as click-to-load placeholders and are only requested from Google when the visitor explicitly loads them.