Dendrila Privacy

Description

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.

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.

External services

Public organisation lookups (optional)

Dendrila Privacy can optionally query a public register to prefill organisation information. Nothing is sent automatically: an administrator chooses a country, enters the required identifier or search term, and clicks Search.

These lookups never include site-audit results, assistant answers, visitor consent choices, page contents, or unrelated WordPress settings.

France — Recherche d’entreprises API

For France, Dendrila Privacy sends only the administrator’s search term (company name, SIREN, or SIRET) to the public Recherche d’entreprises API operated by the French Interministerial Digital Directorate (DINUM).

Service page: https://www.data.gouv.fr/dataservices/api-recherche-dentreprises
API documentation: https://recherche-entreprises.api.gouv.fr/docs/
Terms of use: https://www.data.gouv.fr/pages/legal/cgu
Privacy information: https://www.data.gouv.fr/en/suivi/

Norway — Brønnøysund Register Centre

For Norway, only the organisation name or number entered by the administrator is sent to the official open Enhetsregisteret API. Returned public identity, address, legal form and activity data may be used for optional prefill.

API: https://data.brreg.no/enhetsregisteret/api/dokumentasjon/en/index.html
Privacy: https://www.brreg.no/en/about-us/privacy-policy/

EU / Northern Ireland — VIES VAT validation

For supported EU countries and Northern Ireland (XI), Dendrila Privacy sends only the selected country code and VAT number to the European Commission VIES service. VIES validates VAT registration for intra-EU trade. Depending on the national database, the response may not contain the organisation name or address.

VIES service: https://ec.europa.eu/taxation_customs/vies/
Information about VIES: https://europa.eu/youreurope/business/finance-and-tax/vat/check-vat-number-vies/
European Commission privacy information: https://taxation-customs.ec.europa.eu/privacy-statement_en

Detection signatures are not external connections

Dendrila Privacy contains literal domain and path signatures for services such as Google Analytics, Google Tag Manager, Meta/Facebook Pixel, YouTube, Vimeo, and Google Maps. Those strings are used locally to recognise third-party services in the site’s own markup and to classify or block them when the optional Dendrila Privacy consent feature is enabled.

Their presence in Dendrila Privacy’s source code does not mean that Dendrila Privacy loads those services or sends data to them. Dendrila Privacy itself does not add analytics or advertising trackers. A request to one of those providers can only originate from the site, theme, or plugin integration that Dendrila Privacy is inspecting, subject to that integration and the site’s consent configuration.