Title: Record of Consent Extension for Complianz Author: davidevalerio Published: 25.12.2025 Last modified: 09.10.2026 --- Поиск плагинов ![](https://ps.w.org/record-of-consent-extension-for-complianz/assets/banner-772x250. png?rev=3715773) ![](https://ps.w.org/record-of-consent-extension-for-complianz/assets/icon.svg?rev =3715768) # Record of Consent Extension for Complianz Автор: [davidevalerio](https://profiles.wordpress.org/davidevalerio/) [Скачать](https://downloads.wordpress.org/plugin/record-of-consent-extension-for-complianz.2.6.zip) [Предпросмотр в реальном времени](https://ru.wordpress.org/plugins/record-of-consent-extension-for-complianz/?preview=1) * [Детали](https://ru.wordpress.org/plugins/record-of-consent-extension-for-complianz/#description) * [Отзывы](https://ru.wordpress.org/plugins/record-of-consent-extension-for-complianz/#reviews) * [Установка](https://ru.wordpress.org/plugins/record-of-consent-extension-for-complianz/#installation) * [Разработка](https://ru.wordpress.org/plugins/record-of-consent-extension-for-complianz/#developers) [Поддержка](https://wordpress.org/support/plugin/record-of-consent-extension-for-complianz/) ## Описание This plugin works alongside the free Complianz plugin to helps you keep a clear, reliable record of your visitors’ consents so you can stay on top of privacy rules and audits. It is designed specifically to save and manage consent records, making it ideal if you don’t need all the bells and whistles of Complianz Pro. I built this plugin with care to give you a solid, easy-to-use tool that should meet GDPR requirements. However, it doesn’t guarantee full legal compliance, and none of its settings or descriptions should be considered legal advice. Please note that this plugin has been tested only with Complianz’s category-based consent configuration. Complianz also supports more granular consent per service from version 6.1 onward; service-level consent choices have not been tested and are not currently guaranteed to be recorded correctly. That said, here’s why you’ll like this plugin: * Keeps user IDs anonymous so your visitors’ privacy is respected while staying compliant with data laws. * 5-step wizard to get you started quickly. * Uses SHA-256 hashing to help ensure consent records cannot be changed or tampered with without being detected. * Lets you customize how you view consent records. You can show or hide details, pick custom dates, and see the full history of consents if you want. * Gives you advanced filters to find exactly the records you need. * Allows you to export all consent data, so you can keep a backup or review it offline. * Manages data with options to automatically clean up old records. * Thorough uninstall deletes all plugin data. ### Legal Notice & Disclaimer This plugin is provided «as is,» and the author makes no warranties, express or implied, regarding its accuracy, reliability, or legal compliance. By using this plugin, you acknowledge and agree that: * You are solely responsible for your compliance with GDPR, CCPA, and other applicable data protection laws. * You must update your website’s Privacy Policy to disclose the collection and processing of consent data. * You should regularly back up your data and keep your site well-maintained. * None of the settings or descriptions in this plugin should be taken as legal advice. * The author expressly disclaims any liability for damages, data loss, or other issues arising from the use, misuse, or reliance on this plugin. * You use this plugin at your own risk, and the author assumes no liability for any resulting consequences. * [Donations](https://www.paypal.com/donate/?hosted_button_id=7BQAL64REFATS) are welcome to support ongoing development but do not imply any warranty or official support. ## Скриншоты [⌊Record of Consent⌉⌊Record of Consent⌉[ Record of Consent [⌊Custom Label⌉⌊Custom Label⌉[ Custom Label [⌊IP Source Tooltip⌉⌊IP Source Tooltip⌉[ IP Source Tooltip [⌊Filtering Options⌉⌊Filtering Options⌉[ Filtering Options [⌊Settings⌉⌊Settings⌉[ Settings [⌊Data Integrity Tool⌉⌊Data Integrity Tool⌉[ Data Integrity Tool ## Установка 1. Install and activate the free Complianz plugin. 2. Upload and activate this plugin. 3. Go to Settings > Record of Consent and run the 5-step wizard. 4. Configure filters, labels, and retention options as needed. 5. Consent records will be stored automatically when Complianz triggers consent events. ## Часто задаваемые вопросы ### Does this plugin replace Complianz Pro? No. This plugin is made to work alongside the free Complianz plugin by adding just the consent recording part. If you want all the extra features, you would use Complianz Pro instead. ### Do I need Complianz installed for this plugin to work? Yes. This plugin relies on the free Complianz plugin to be active. Think of it as an add-on that extends Complianz’s consent features. ### Can I use this plugin with other consent plugins? No. This plugin is specifically designed to work with Complianz. ### Is this plugin compatible with W3 Total Cache? Yes. ### Is this plugin compatible with Autoptimize? Yes. ### How do I verify consent records integrity? Each consent record is protected with a SHA-256 hash that uses a secret salt. If someone changes a record directly in the database, the integrity check will detect the mismatch. ### Can I also add the country or city of origin of a visitor in each record? A GDPR consent record requires only strictly necessary information to demonstrate compliance. Detailed geographic data, like country or city of origin, generally exceeds data minimization principles. ### I don’t have any marketing cookies on my website, but I still see records showing “marketing allowed.” Why is that? If your website doesn’t use marketing cookies, Complianz hides that category in the banner but still keeps it in the background data. That’s why you might see “ marketing allowed” in your Record of Consent — it’s just a placeholder in the system. No marketing cookies are actually loaded or tracked, and you can safely ignore it. ### Why does the plugin store anonymized IP addresses? The plugin records an anonymized/truncated IP address as supporting evidence next to the User ID, timestamp, consent choices, and policy version. Storing anonymized/ truncated IPs are not mandated by GDPR, but are recommended practice, because they offer a perfect compromise between compliance and operational utility. ### Why are IP addresses not matching external analytics tools? This usually happens because some hosting providers use reverse proxies or load balancers that don’t forward the original visitor IP to PHP. In those cases, server- side tools (like this plugin) may record the proxy’s IP, while browser-based analytics tools (which are usually client-side JS) capture the correct visitor IP. This is a hosting infrastructure issue, not a plugin limitation. The plugin correctly stores consent records, but unreliable IP forwarding can make it harder to match records to specific users, which may affect compliance with data subject access or deletion requests. The plugin includes a PHP multi-header fallback system to detect the real visitor IP when possible, by checking headers such as `X-Forwarded-For` or `HTTP_CF_CONNECTING_IP`. However, this cannot guarantee accuracy in all environments. To improve detection: * Ask your hosting provider to enable `X-Forwarded-For` or `X-Real-IP` * Use a hosting service that fully supports IP forwarding * Use multiple identifiers (IP + User Agent + timestamp + UID) * Document this limitation in your privacy policy ### From a GDPR standpoint, why should I use the Trusted Proxy IPs setting? The Trusted Proxy IPs feature might matter if your site runs behind a proxy or CDN, meaning a service that sits between visitors and your server. In that case the plugin may record that service’s address instead of the visitor’s, so the truncated IP context is lost. ## Отзывы ![](https://secure.gravatar.com/avatar/6561fd74104513c1657f853a049a947a4a9f466eb77560b395bfa1a082c7f2c8? s=60&d=retro&r=g) ### 󠀁[I recommend it!](https://wordpress.org/support/topic/i-recommend-it-44/)󠁿 [Marcin](https://profiles.wordpress.org/jmszwp/) 27.05.2026 Easy setup, clear consent records, all the necessary features, and fast and friendly support. If you don't need all the features of the paid version of Complianz, it's a must-have add-on. ![](https://secure.gravatar.com/avatar/dcb9f340fc929b6531b2068c0921e806176c257dea2b8d47dbf44baeb2d9cb73? s=60&d=retro&r=g) ### 󠀁[This is why we love WordPress / Open-Source](https://wordpress.org/support/topic/this-is-why-we-love-wordpress-open-source/)󠁿 [Aert](https://profiles.wordpress.org/aahulsebos/) 06.03.2026 I encourage everyone to create, build and improve where possible; this is a great example.The extension delivers what it promises; and feedback was well received. The plugin itself lives between the 'Proof of Consent' feature in Complianz Free— which respects a GDPR principle called data minimization by not collecting any personal data whatsoever and the premium feature in Complianz that does; but connects more information to the specific user and timestamped consent actions.A great addition to the repository. ![](https://secure.gravatar.com/avatar/bb5e1623179495225409c4fca95ee23947f9938c8f35fa693c44614a049a1aaa? s=60&d=retro&r=g) ### 󠀁[Lightweight option to demonstrate consent per Art. 7 GDPR](https://wordpress.org/support/topic/lightweight-option-to-demonstrate-consent-per-art-7-gdpr/)󠁿 [bheching](https://profiles.wordpress.org/bheching/) 06.03.2026 Works very well after the latest updates! Recommended to everyone who's otherwise happy with Complianz (Free) and wants to be on the safe side when it comes to demonstrating consent. Oh, and excellent support too! (coffee incoming) [ Посмотреть все 3 отзыва ](https://wordpress.org/support/plugin/record-of-consent-extension-for-complianz/reviews/) ## Участники и разработчики «Record of Consent Extension for Complianz» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники: Участники * [ davidevalerio ](https://profiles.wordpress.org/davidevalerio/) [Перевести «Record of Consent Extension for Complianz» на ваш язык.](https://translate.wordpress.org/projects/wp-plugins/record-of-consent-extension-for-complianz) ### Заинтересованы в разработке? [Посмотрите код](https://plugins.trac.wordpress.org/browser/record-of-consent-extension-for-complianz/), проверьте [SVN репозиторий](https://plugins.svn.wordpress.org/record-of-consent-extension-for-complianz/), или подпишитесь на [журнал разработки](https://plugins.trac.wordpress.org/log/record-of-consent-extension-for-complianz/) по [RSS](https://plugins.trac.wordpress.org/log/record-of-consent-extension-for-complianz/?limit=100&mode=stop_on_copy&format=rss). ## Журнал изменений #### 2.6 * Fixed security issue. User IDs are now validated and safely escaped in the inline label editor. * Stronger export hygiene. Raw JSON exports now include only the fields relevant to an audit, without internal helper fields. * Improved export clarity. JSON exports now explain that anonymized IP addresses contain zeroed IPv4 octets or IPv6 segments, preventing them from being mistaken for visitors’ original IP addresses. * Fixed translation issue. The Integrity Salt controls now use translated labels and messages, and the regeneration confirmation is no longer skipped on translated admin screens. * Improved mobile layout. The Identifier column in User ID Labels now uses more available width, making identifiers easier to view and edit on smaller screens. #### 2.5 This release introduces a redesigned User ID Labels settings interface. Saved labels can now be reordered by drag and drop. Additional release improvements: * Fixed display issue. Consent badges in the Records table are now vertically centered consistently with other column values. * Verified compatibility with WordPress 7.1.2, with no known functional issues. * Updated screenshots. Repository screenshots now reflect the current plugin interface and features. #### 2.4 This release introduces the new Trusted Proxy IPs option in Core Configuration. When configured correctly, this gives the plugin more precise visitor IP detection. That can make it easier to find a specific visitor’s consent records later, for example when handling a deletion request. How it works: Normally, the plugin identifies a visitor by the address their connection arrives from. When a proxy or CDN sits in front of your site, that address belongs to the intermediary, while the visitor’s real address is passed along separately inside the request. Because that forwarded address could be spoofed, the plugin only accepts it from services you have explicitly marked as trusted. Trusted Proxy IPs is that list. If the field is empty, the plugin ignores forwarded addresses and falls back to the intermediary’s own address instead. Most sites do not need to change this setting. It only matters if your site runs behind a separate service that sits between visitors and your server. If you are unsure, leaving the field empty is the safe choice. It will not cause errors or prevent consent recording. The main drawback only affects sites that really are behind a proxy or CDN. In that case, leaving the field empty can cause multiple visitors’ consent records to store the same proxy address instead of their individual addresses. What to do: * Not sure what a proxy or CDN is, or do not recognize these terms? Leave the field empty. There is nothing else to configure; * Know your site uses one of these services and know its address? Add it here after confirming that it is correct. The Trusted Proxy IPs tooltip will show a possible proxy address when signs of one are detected, so you can review and add it manually if appropriate; * Using Cloudflare? Add Cloudflare’s published IP ranges rather than a single address, because Cloudflare operates through a large network of servers; * Using more than one such service? Add each trusted address or range that applies. Additional release improvements: * Improved reliability. Proxy trust checks now use consistent matching rules across consent recording and IP detection notices, preventing conflicting proxy detection results. * Improved compatibility. Verified compatibility with WordPress 7.1.1, with no known functional issues. * Improved IP Source guidance. Records table values now explain how each IP source is detected and how reliable it may be, using interactive labels and tooltips. * Improved bot filtering. Chrome Lighthouse is now detected by Aggressive bot filtering. * Improved Italian translation. Updated and refined the Italian localization for clearer and more consistent wording across the plugin interface. * Fixed translation issue. The Clear integrity salt confirmation dialog now correctly uses the available translation instead of falling back to English. * Fixed display issue. Core Configuration fields, buttons, and dropdowns no longer resize irregularly on screens between 783px and 799px wide. * Improved responsive consistency. Settings now switch to the stacked layout at the same breakpoint as the rest of the admin interface, eliminating an abrupt layout change around 800px. * Fixed mobile display issue. IP Source tooltips no longer extend beyond the viewport on narrow screens. * Fixed Safari display issue. Numeric identifiers in the plugin admin interface are no longer automatically formatted as phone numbers on iOS. * Fixed display issue. The Filters tile now keeps its open or closed state when sorting the Records table or moving between pages. #### 2.3 * Fixed critical bug. Records tab pagination and sorting now work correctly after AJAX refreshes, preventing links from returning a blank page after saving Settings or switching tabs. * Improved performance. Large CSV and JSON exports no longer trigger site-wide object cache flushes, preventing unnecessary cache cold starts on sites using Redis or Memcached. * Improved bot filtering. Hide Bot Records now offers Safe, Balanced, and Aggressive levels, allowing stricter or broader filtering depending on whether legitimate monitoring and testing traffic should remain visible. * Expanded bot detection. Added detection for additional crawlers and scraping tools, while refining Yandex detection to avoid incorrectly filtering its consumer browser. * Improved extensibility. Bot-detection lists can now be extended through filter hooks without modifying the plugin. * Simplified exports. Removed the Region, Integrity Hash, and internal database ID columns because they are not meaningful compliance data. * Improved reliability. Consent record storage failures are now logged in debug mode to aid troubleshooting. * Improved compatibility. Verified compatibility with WordPress 7.1, with no known functional issues. * Improved mobile table layout. Fixed Records table header and row alignment and improved responsive behavior in the WordPress admin. * Fixed display issues. Settings tooltips now reposition near interface edges instead of overflowing the visible layout. * Improved maintainability. Split shared variables, WordPress overrides, tooltip styles, and general admin styles into dedicated stylesheets, making the admin CSS easier to organize and maintain. #### 2.2.1 * Fixed critical compatibility issue. Upgrading from an earlier version could trigger a fatal error that blocked access to the WordPress admin area, while leaving the frontend and consent recording unaffected. #### 2.2 Version 2.2 brings a broad range of under-the-hood improvements to security, reliability, data integrity, and performance, along with several refinements to the admin interface. It also improves exports, bot detection, validation, and handling of larger databases. * Stronger data integrity. Consent record integrity hashes now use HMAC-SHA256 for keyed hashing, improving cryptographic security while preserving verification of existing records. * Improved data integrity. Consent records now store which integrity hash formula was used to create them, ensuring existing records remain verifiable if the formula changes in future versions. * Stronger security. IP forwarding headers are now trusted only from explicitly configured proxy servers, preventing IP spoofing that could bypass rate limiting and duplicate-consent protection. * Stronger security. The filterable region column name is now safely escaped before use in database queries, preventing potential SQL injection through custom hooks. * Stronger duplicate protection. Duplicate consent submissions are now also detected server-side, preventing repeated submissions if browser storage is cleared or manipulated. * Stronger rate limiting. Consent submission limits now rely solely on anonymized IP addresses, preventing simple browser header changes from bypassing the protection. * Stronger export security. CSV and JSON exports now protect additional fields against formula injection, preventing potentially unsafe values from being interpreted by spreadsheet applications. * Improved export privacy. Full-database exports now use POST requests instead of GET, preventing export actions and security tokens from appearing in browser history, logs, or referrer data. * Fixed critical compatibility issue. Latest-status filtering in the Records tab and CSV/JSON exports now works correctly on MySQL servers using ONLY_FULL_GROUP_BY mode. * Improved reliability. Table migrations now capture consent records created during migration, preventing rare data loss during table suffix changes. * Improved reliability. Changing the custom table suffix now uses the same verified migration process as initial setup and updates the active database connection immediately, reducing the risk of incomplete migrations or queries targeting the old table. * Improved reliability. Data integrity checks now detect records with missing or corrupted fields and report them as invalid instead of generating PHP warnings. * Improved reliability. Integrity verification now limits the number of invalid records retained during each check, preventing excessive memory usage on large databases. * Improved data integrity. The Policy Version setting now validates the expected version format before saving, helping prevent invalid configuration values without altering existing consent records. * More reliable rate limiting. Visitors are no longer rate-limited when no consent record is stored, preventing unnecessary submission limits after denying all cookies or reloading the page. * Improved performance. Large CSV and JSON exports no longer flush the entire site object cache during processing, preventing unnecessary cache cold starts on sites using Redis or Memcached. * Improved performance. Latest-status filtering now caches its results, reducing database load and speeding up the Records tab and exports on larger sites. * Improved performance. A new database index speeds up loading and exporting records when displaying only the latest consent status for each user, especially on large databases. * Improved performance. Admin tabs are now loaded on demand instead of all at once, reducing unnecessary database queries and speeding up page loads. * Improved performance. Daily maintenance checks now run only in the WordPress admin area, avoiding unnecessary database operations on public pages. * Improved performance. Filter dropdown caches are now refreshed only when new values are added, reducing unnecessary work during consent submissions. * Improved bot detection. Expanded the Hide Bot Records filter with 16 additional crawlers, including AI bots, link-preview bots, SEO tools, and regional search engines, for more accurate consent records. * Stronger input validation. User agent submissions now have a maximum length, preventing unbounded attacker-controlled data from being stored in consent records. * Fixed data display. User IDs and labels containing special characters now display and export correctly instead of appearing as garbled HTML entities. * Fixed data display. The Records tab Filters tile now stays expanded after applying filters. * Fixed display issues. Settings and Records tab dropdowns now initialize correctly when tabs are loaded on demand, eliminating the need to reload the page. * Improved input validation. The Database Table Suffix field now blocks invalid characters as you type and shows a validation message, helping prevent avoidable save errors. #### 2.1 * Improved privacy. Rate limiting now uses the anonymized IP address instead of the original client IP, ensuring that no trace of the non-anonymized IP is ever stored. * Safer CSV and JSON exports. Exported user_agent values are now protected against CSV/Formula Injection, preventing spreadsheet apps from executing malicious formulas. * Improved performance. Integrity verification now checks records in batches of 1,000 instead of loading the entire database table at once, preventing memory and timeout issues on large sites. * Improved Records tab performance. Region, policy version, consent method, and action type filters are now cached, avoiding unnecessary database queries every time the tab is opened. * More robust bulk actions. Bulk delete, CSV and JSON export now handle malformed requests gracefully instead of causing fatal errors. * Stronger input validation. Consent categories submitted through AJAX are now validated against an approved list and have a maximum size limit, preventing unexpected or oversized data from being stored. * Stronger input validation. The «Delete Old Records» setting now rejects invalid values before deletion and provides clear error messages, while also fixing an input display issue in Safari. * Clearer documentation. Tooltips now clarify that enabling Hide Bot Records doesn’t affect exports. CSV and JSON exports always include all records to preserve GDPR compliance. * Better settings validation. Invalid or empty custom table suffixes are now detected before saving, with a clear error message instead of silently ignoring the value. * More efficient upgrades. The legacy retention-period migration now runs only once during plugin upgrades instead of executing every time the Settings page is opened. * More consistent error handling. AJAX requests now use a standardized error format, preventing confusing “undefined” error messages in the admin interface. * Clearer messaging. Removed the admin notice suggesting an integrity salt is required for GDPR compliance; setting a salt remains a recommended but optional hardening measure. * Fixed display issue. Labels added from the Records tab now appear immediately in the Settings tab’s User ID Labels list without requiring a page reload. * Fixed display issues. The toggle switch markup in Display Settings has been corrected to prevent broken rendering. * Improved reliability. Removed an unused duplicate settings-save handler from the Bot Filter module to prevent conflicts with the central Settings save process. * Stronger security. Fixed an issue that could cause consent record operations to fail under certain conditions and closed an edge case where a compressed IPv6 address could bypass IP anonymization checks. #### 2.0 This release introduces a redesigned Settings page. The interface has been rebuilt from scratch for a cleaner, more intuitive experience. Additional release improvements: * Improved usability. Refined the Settings page layout and interactions for a smoother configuration workflow. * Better responsive design. Improved the layout of the Settings and Records pages on smaller screens. * Improved mobile readability. Optimized the Records table for easier viewing on mobile devices. #### 1.5.2 * WordPress 7.0 compatibility. Verified compatibility with WordPress 7.0. * Code cleanup. Consolidated the plugin’s color palette by removing redundant color variables. #### 1.5.1 * Safer database upgrades. Record migrations now match columns explicitly instead of relying on column order, preventing data loss if database schemas differ. * Improved upgrade reliability. Database migrations and the setup wizard now create the complete table structure, ensuring all required columns are available. * More robust IP handling. Fixed an edge case where certain malformed IPv6 addresses could cause the plugin to crash. * More reliable AJAX responses. Consent revocation requests now return consistent JSON responses, even when security tokens have expired. * Code cleanup. Removed unnecessary SQL escaping that could interfere with export queries. * Fixed invalid record exports. Exporting invalid records no longer attempts to access a database column that doesn’t exist. * Reduced code duplication. Consolidated duplicate export query logic into a single shared implementation. * More reliable consent tracking. Consent action types are now updated only after a successful server response, preventing incorrect values during rapid consecutive consent changes. * Stronger security. Salt generation in the Settings page now uses a cryptographically secure server-side source instead of client-side random values. * Improved extensibility. Consent records now adapt automatically when additional fields are added, preventing data from being silently omitted. #### 1.5.0.1 * Bug fix for searching functionality #### 1.5 * New look for the Filters section, with cleaner layout and responsive fields. * Improved searching functionality: Searching by IP address now works with any format or partial input. #### 1.4.5 * New feature. Added an optional Bot Filter module that hides well-known crawlers and vendor-specific bots from the Records view, making consent data easier to review. * Improved data quality. Bot filtering keeps the Records view focused on real user consents while preserving all records for auditing and exports. * Better extensibility. Added a new integration hook that allows modules to extend the Display Settings page. * Improved cleanup. The Bot Filter module now removes its settings automatically when the plugin is uninstalled. #### 1.4.4 * Stronger DoS protection. Reduced the rate limit to 10 requests per hour for each IP address and browser combination, making abusive traffic significantly harder. * Cleaner browser console. Removed development logging from JavaScript files to reduce unnecessary console output in production. * Improved module compatibility. Module detection now supports both folder-based and standalone module structures. * Better error diagnostics. Important error and warning messages are still logged to the browser console to simplify troubleshooting. * Improved performance. Eliminated unnecessary logging overhead in the production environment. #### 1.4.3 * More accurate consent tracking. Consent methods are now detected using reliable inference instead of unavailable Complianz events, correctly distinguishing content blocker consent from banner consent. #### 1.4.2 * Critical bug fix. Prevents duplicate consent records from being created on every page load, avoiding unnecessary database growth. This update is recommended for all users. #### 1.4.1 * Improved extensibility. Added new hooks and enhanced dynamic column support, making it easier for modules to extend the plugin. * More reliable pagination. Fixed an issue where page numbers with multiple digits were not handled correctly. #### 1.4 * Improved code quality. Refactored the codebase for better compliance with WordPress Coding Standards and more complete developer documentation. #### 1.3 * New feature. Introduced a modular architecture that allows optional functionality to be added through drop-in modules. * More reliable IP detection. Added support for Cloudflare, Nginx, X-Forwarded- For, Client-IP, and other common proxy headers. * Improved GDPR auditing. Consent records now store which HTTP header supplied the detected IP address. * Better security. X-Forwarded-For headers now use only the first IP address to prevent spoofing. * Improved usability. Settings sections can now be collapsed, with their state remembered between visits. * Automatic upgrades. Existing installations are updated automatically to support the new IP source tracking. #### 1.2.2 * Improved compatibility. Enhanced IP detection across Cloudflare, reverse proxies, VPS environments, and shared hosting. * Improved GDPR auditing. Consent records now include the source of the detected IP address. * Better security. X-Forwarded-For headers now use only the first IP address to prevent spoofing. * Automatic upgrades. Existing installations are updated automatically to support IP source tracking. * Improved debugging. Added optional diagnostic logging for IP detection when debug mode is enabled. * Improved usability. Updated timestamp format options and recommended ISO 8601 as the default format. #### 1.2.1 * Improved GDPR compliance. Consent refusals are no longer stored, as proof of refusal is generally not required. #### 1.2 * New feature. Added automatic database migration when changing the custom table suffix, including verification and automatic rollback on failure. * Safer database changes. Table migrations now require confirmation before proceeding to help prevent accidental data loss. * Improved compatibility. Consent records are now stored even when geographic region information is unavailable, improving support for Complianz Free. * Stronger security. Hardened input validation, output escaping, and database queries in line with WordPress security best practices. * Improved code quality. Enhanced WordPress Coding Standards compliance and internal documentation. #### 1.1.9 * Improved compatibility. Fixed consent storage when geographic region information is unavailable. * Stronger security. Hardened input validation, output escaping, and database queries in line with WordPress security best practices. * Improved code quality. Enhanced WordPress Coding Standards compliance and reduced unnecessary logging. #### 1.1.8 * Improved compatibility. Fixed consent storage when geographic region information is unavailable. * Improved error handling. Reduced unnecessary logging during cancelled consent requests. #### 1.1.7 * Improved WordPress compatibility. Resolved Plugin Check issues for WordPress. org compliance. * Better localization. Improved translation support and updated language files. * More reliable consent tracking. Fixed a JavaScript issue that could occur when all consent categories were rejected. * Improved code quality. Refactored internal code to improve maintainability and translation support. #### 1.1.6 * Improved code quality. Simplified CSS selectors for better maintainability. * Fixed responsive layout. Corrected an issue where table headers were hidden but their corresponding data remained visible. #### 1.1.5 * Fixed bulk actions. Bulk delete and export now work correctly from both bulk action menus. * More reliable consent tracking. Fixed consent storage issues and simplified category handling. * Better security. Improved nonce handling for bulk actions to avoid failures caused by expired security tokens. * Improved code quality. Removed unused consent processing logic. #### 1.1.4 * Stronger security. Added additional validation and permission checks to bulk exports and database operations. * Fixed setup issues. Resolved a problem that could prevent the consent database table from being created during installation. * Fixed navigation. Pagination and sorting now remain on the correct admin tab. * Improved error handling. Added clearer messages when required database tables are missing. #### 1.1.3 * Security update. Strengthened protection against SQL injection, XSS, CSRF, malformed input, information disclosure, and oversized requests. * Improved rate limiting. Requests are now identified using both IP address and browser information for more effective abuse protection. * Improved code quality. Simplified internal logging and maintenance. #### 1.1.2 * New feature. Added full localization support, including Italian translations. * Improved user interface. Refined layouts, alignment, and styling throughout the plugin. * Improved maintainability. Consolidated styles and introduced CSS variables for easier customization. * Simplified interface. Removed an unused consent category from the Settings and Records pages. #### 1.0 * Initial release. Introduced secure consent recording with tamper detection, privacy- preserving user labels, advanced filtering, data export, and automatic record retention. ## Мета * Версия **2.6** * Обновление: **5 дней назад** * Активных установок: **700+** * Версия WordPress ** 5.0 или выше ** * Совместим вплоть до: **7.1.3** * Версия PHP ** 7.4 или выше ** * Язык * [English (US)](https://wordpress.org/plugins/record-of-consent-extension-for-complianz/) * Метки: * [compliance](https://ru.wordpress.org/plugins/tags/compliance/)[consent](https://ru.wordpress.org/plugins/tags/consent/) [database](https://ru.wordpress.org/plugins/tags/database/)[privacy](https://ru.wordpress.org/plugins/tags/privacy/) * [Дополнительно](https://ru.wordpress.org/plugins/record-of-consent-extension-for-complianz/advanced/) ## Оценки 5 из 5 звёзд. * [ 3 5-звездный отзыв ](https://wordpress.org/support/plugin/record-of-consent-extension-for-complianz/reviews/?filter=5) * [ 0 4-звездный отзыв ](https://wordpress.org/support/plugin/record-of-consent-extension-for-complianz/reviews/?filter=4) * [ 0 3-звездный отзыв ](https://wordpress.org/support/plugin/record-of-consent-extension-for-complianz/reviews/?filter=3) * [ 0 2-звездный отзыв ](https://wordpress.org/support/plugin/record-of-consent-extension-for-complianz/reviews/?filter=2) * [ 0 1-звездный отзыв ](https://wordpress.org/support/plugin/record-of-consent-extension-for-complianz/reviews/?filter=1) [Ваш отзыв](https://wordpress.org/support/plugin/record-of-consent-extension-for-complianz/reviews/#new-post) [Посмотреть всеотзывы](https://wordpress.org/support/plugin/record-of-consent-extension-for-complianz/reviews/) ## Участники * [ davidevalerio ](https://profiles.wordpress.org/davidevalerio/) ## Поддержка Решено проблем за последние 2 месяца: 1 из 1 [Перейти в форум поддержки](https://wordpress.org/support/plugin/record-of-consent-extension-for-complianz/) ## Пожертвование Хотите поддержать улучшение этого плагина? [ Пожертвовать на развитие плагина ](https://www.paypal.com/donate/?hosted_button_id=7BQAL64REFATS)