Engineering knowledge base

Personal data on a WordPress site

A calm map of forms, cookies, recipients, and uncovered decisions without an automated legal-compliance verdict.

Direct answer

What a scanner checks — and what it cannot decide.

The plugin and engineering review record observable signals. Processing grounds, documents, notification, and the final legal view remain with the controller and legal adviser.

Three layers

What is visible, reviewed, and decided by the controller.

01

Automatically observable

Forms, cookies, scripts, endpoints, policy links, selected settings, and network destinations.

02

Manual engineering review

CRM/mail, first-write location, backups, access, retention, deletion, and conditional flows.

03

Controller decision

Purposes, grounds, texts, notification, internal documents, and threat model.

Topics

Six questions without mixing contexts.

01

Website requirements

Forms, documents, processors, security, and roles.

02

Forms and consent

A separate action, minimization, and evidence.

03

Cookies and analytics

Inventory before choosing a banner.

04

Localization

First-recording routes and external systems.

05

Notification

Assessment and filing stay with the controller.

06

Safeguards

WordPress is one part of a wider information system.

Tell us what the site needs.

A goal, the current difficulty, and an optional website address are enough. Do not send passwords, keys, or private exports.