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.

Diagnostic usage control

To apply the user-requested diagnostic usage rule, 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.

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.