Legal foundation
Privacy Policy
Development privacy draft — requires GDPR/legal review and final processor inventory before production.
Privacy by architecture
EP Diagnostics is designed to minimize collection.
Site-side evidence
EP Site Check is intended to keep results local by default. Evidence should leave the website only after explicit administrator authorization.
Site-control verification
Authorized site-side diagnostics may require technical site-control verification. WordPress verification uses a short-lived challenge through the administrator-installed EP Site Check plugin. The planned non-WordPress route requires an authenticated EP account plus a short-lived server verification token. Verification establishes technical control of the target site for diagnostic authorization; it does not establish legal ownership.
Verification tokens are temporary and are not reused as permanent connector credentials. Diagnostic evidence transfer remains a separate authorized step.
Problem descriptions
The optional problem description is processed only to guide the current public diagnostic request. The public diagnostic application does not persist that text in its diagnostic storage. Do not enter passwords, API keys, personal data or confidential information.
Diagnostic usage control
Development status: the diagnostic usage limit is currently disabled for QA testing. When the production usage-control mechanism is enabled, EP Diagnostics uses an essential opaque browser identifier and a minimal server-side timestamp record for the same website. The usage-control record is separate from diagnostic evidence and is not used for advertising or profiling.
Optional knowledge enrichment
Any knowledge-enrichment participation must be optional and explicit, with a genuine No choice that does not change diagnostic access or results. Only deliberately de-identified, non-customer-specific technical patterns may be used for that purpose. Raw customer/site data, domains or URLs, content, credentials, raw logs, account identifiers and similar customer-specific data must not enter the enrichment dataset.
Controlled advertising privacy model
Controlled advertising uses the same manually approved advertisement for every visitor during the campaign period, without behavioral profiling or user-specific ad selection.
Advertiser creative does not use advertiser tracking pixels, third-party ad scripts or cross-site behavioral identifiers in the initial model.
Google Analytics
With the visitor's consent, EP Diagnostics may load Google Analytics to measure website traffic and record aggregate events such as clicks on controlled advertisements. Google Analytics is not required for the website or diagnostic functions to operate.
If analytics consent is not given, EP Diagnostics does not load Google Analytics. Ordinary server request logs remain a separate privacy and retention matter and must be documented in the final production policy.
Production completion
The production policy must identify the controller, contact details, lawful bases, processors, hosting, retention, deletion and transfer details.
