Dendrila Privacy

Dendrila Privacy helps WordPress administrators understand what their site actually does with trackers and third-party services, keep privacy-related documentation up to date, and optionally manage visitor consent. Dendrila Privacy is designed local-first: audit results, settings, and assistant answers stay in WordPress by default. The plugin does not certify GDPR compliance and does not replace legal advice adapted to an organisation's actual activities. Main features:

• standard or full analysis of public site content;
• detection of known trackers, third-party services, external content, and consent tools;
• distinction between observed technical evidence, an available integration, and something that still needs human verification;
• progressive scans where one failing page does not stop the remaining analysis;
• a guided privacy assistant that reuses information WordPress can already provide before asking questions;
• documentation coverage based only on requirements that actually apply;
• management of Legal Notice, Privacy Policy, and Cookies / Consent reference pages;
• explicit draft creation and updates, without silently publishing legal content;
• conservative compatibility with Gutenberg, Elementor, Divi, and several other page builders;
• an optional native consent interface that is disabled after installation;
• protective blocking of recognised optional services before the visitor's choice when Dendrila Privacy consent is enabled;
• Accept all and Reject all actions with equal visual weight;
• a persistent Manage my choices control, Elementor widget, and universal shortcode;
• initial checks for practices outside WordPress, including email, messaging, booking tools, external forms, payments, and files/lists;
• local age-gating plugin detection, with a manual review when a different age-assurance tool is installed.

Consent The Dendrila Privacy consent interface is independent from the page builder. It is mounted globally on the page to avoid positioning and stacking conflicts caused by themes, Divi, or Elementor. When Dendrila Privacy manages consent:

• no optional category is preselected;
• closing the interface is not treated as consent;
• visitors can change their choice through Manage my choices;
• recognised optional services stay blocked before a choice;
• the real blocking engine is disabled inside visual page-builder editors.

Public shortcodes: [dendrila_privacy_legal_notice], [dendrila_privacy_privacy_policy], [dendrila_privacy_cookies], [dendrila_privacy_services], [dendrila_privacy_rights], [dendrila_privacy_documents], and [dendrila_privacy_consent_settings]. Page builders WordPress / Gutenberg: Dendrila Privacy uses WordPress APIs and public shortcodes for supported content. Elementor: Dendrila Privacy can inspect known local widget content, explicitly create supported legal pages, and provides a Manage my choices widget. Divi: Dendrila Privacy reads recognised content conservatively. It prefers a native structure only when that structure is clearly understood and falls back to a shortcode when a safe rewrite cannot be guaranteed. Other builders: Dendrila Privacy recognises several common page-level signatures conservatively and prefers a manual fallback over modifying unknown builder storage. Data and privacy Dendrila Privacy does not send site-audit results to the plugin author and does not include advertising telemetry. Visitor consent preferences are stored locally in the visitor's browser. Administration and audit data stay in the site's WordPress database unless an administrator explicitly starts the documented external lookup below.

0.0.6

• Fixed admin styles and scan JavaScript not loading after the public plugin rename.
• Restored first-open setup routing and the default overview tab.
• Constrained logo dimensions even when styles fail to load.
• Added regression coverage for all admin menu pages and scan configuration.
• Included local age-assurance companion detection already described above. Detailed release history is kept in changelog.txt.