manifest / privacy / pixel-trackers-manager

Pixel Trackers Manager

Local-first WordPress privacy audit, documentation and consent assistant.

by Le Potager du Web · github.com/jasmin-abernathy/pixel-trackers-manager · website

★ 1stars

0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/jasmin-abernathy/pixel-trackers-manager/archive/refs/heads/master.zip

Readme github.com/jasmin-abernathy/pixel-trackers-manager ↗

Lire en français

Pixel Trackers Manager (PTM) is a local-first WordPress privacy audit, documentation and consent assistant developed by Le Potager du Web.

It helps administrators understand what their site actually does: identify trackers and third-party services, review legal pages, document relevant data practices and optionally manage visitor consent.

Current status: development build 0.0.2-test4. PTM is not a legal certification tool and does not replace advice adapted to the organisation's actual activities.

Core principles

Observe first, ask second. PTM reuses information already available in WordPress before asking the administrator to enter it again.
Local by default. Audit results, settings and questionnaire answers stay in WordPress unless the administrator explicitly starts a documented external lookup.
No silent legal publishing. PTM can prepare drafts and proposed updates, but important public changes require an explicit administrator action.
No dark patterns. If the native consent interface is enabled, Accept and Reject keep equal visual weight.
Builder-independent privacy engine. Consent works at WordPress level; Elementor, Divi and other builders are compatibility layers rather than dependencies.
Conservative writes. When PTM cannot safely understand a builder's internal structure, it falls back to a shortcode/manual workflow instead of rewriting unknown data.

Current coverage

Site analysis

progressive full-site scan;
tracker and third-party service detection;
distinction between active evidence, an available integration and something that still needs human verification;
failed URLs do not stop the remaining scan;
WordPress drafts/private/pending/scheduled pages can be distinguished from genuine public 404 errors.

Legal documentation

Legal Notice, Privacy Policy and Cookies / Consent reference pages;
guided GDPR assistant in a dedicated tab;
clickable documentation gaps that open the relevant assistant section;
separation between site publisher, data controller, public contact, privacy-rights contact and an actually designated DPO;
public legal shortcodes and draft creation;
explicit update workflow instead of silent publication.

Consent

optional native bar or centred panel;
interface mounted globally under <body>, independently from Divi/Elementor;
deny-by-default behaviour for recognised optional services once enabled;
equal visual treatment for Accept all and Reject all;
persistent Manage my choices control;
lightweight public API for theme/builder integrations;
administrator test mode and conservative compatibility work for dynamic builder modules.

WordPress ecosystem awareness

PTM can safely use or inspect information from WordPress/Gutenberg, Elementor, Divi, selected form plugins, backup plugins and known consent or analytics integrations.

The project also covers practices that happen outside WordPress when the website alone cannot reveal them, such as mass emails, messaging, external booking/forms, HelloAsso, payments, spreadsheets or cloud storage.

Automatic installable ZIP

The repository now builds a clean installable archive automatically on every push to master.

In GitHub:

open Actions;
open the latest PTM quality and distribution run;
download the pixel-trackers-manager-VERSION artifact.

The ZIP is built with the official WP-CLI wp dist-archive command and .distignore. Development-only material such as GitHub workflows, internal documentation, contribution files and temporary files is excluded.

The workflow also checks:

consistency between the plugin Version header, runtime constant and Stable tag;
PHP syntax on PHP 7.4, 8.3 and 8.4;
JavaScript syntax;
WordPress.org readme.txt metadata and size;
the five-tag WordPress.org limit;
the official WordPress Plugin Check action;
ZIP integrity and SHA-256 digest.

Test installation

Download the ZIP generated by GitHub Actions or place the repository in wp-content/plugins/pixel-trackers-manager/.
Activate Pixel Trackers Manager in WordPress.
Open PTM for the first time to launch the guided setup.

Current requirements:

WordPress 6.5+
PHP 7.4+

The metadata currently targets WordPress 7.1. Before a build is submitted to WordPress.org, the dedicated WordPress 7.1 test matrix must actually pass on that exact build.

Versioning and WordPress.org

0.0.2-test4 is a GitHub development version. A real WordPress.org release will use a numeric version such as 0.0.2 or 0.1.0, identical in the PHP header, runtime constant and Stable tag.

The WordPress.org SVN repository will be treated as a release repository rather than a mirror of every GitHub commit.

See docs/WORDPRESS-ORG-RELEASE.md for the complete procedure.

Documentation

README.fr.md — French project overview.
docs/WORDPRESS-ORG-RELEASE.md — WordPress.org preparation and release process.
docs/CONSENT-INTEGRATION.md — consent UI integration with page builders.
docs/STATUS-2026-08-30.md — latest consolidated product checkpoint.
docs/USER-GUIDE.md — English user guide.
docs/USER-GUIDE.fr.md — French user guide.
docs/TESTS-0.0.2-test4.md — current validation checklist.
docs/CAHIER-DES-CHARGES.md — internal product specification and roadmap (French).
changelog.txt — detailed development-build history.
CONTRIBUTING.md — contribution guide.
SECURITY.md — vulnerability reporting policy.

Development workflow

The repository is used for active pre-release development. The reference branch should remain installable; unfinished changes should use feature branches when practical.

Before selecting a release candidate, PTM should at minimum pass:

automated GitHub checks;
WordPress activation/deactivation tests;
the current manual validation checklist;
actual WordPress 7.1 validation;
Gutenberg, Elementor and Divi tests;
installation of the exact ZIP generated by GitHub Actions on a clean WordPress site.

Reporting issues

Use the GitHub issue templates for reproducible bugs and feature proposals. Never include passwords, API keys, personal data or client-site exports in public reports.

For a vulnerability that could expose data or compromise a site, follow SECURITY.md instead of publishing exploitation details in an issue.

License

See LICENSE. PTM is distributed under GPL v2 or later.