A rights channel should be secure before it is public.
This site does not ask visitors to upload identity documents or sensitive information through an unsecured public form.
Before submitting a request
Do not send identity documents, special-category data, client-confidential material, or passwords through the public contact prototypes.
Request scope
A verified process should support access, correction, deletion or destruction where applicable, objection, portability where applicable, and information about processing.
Identity verification
Verification should be proportionate to the request and the risk. The final operating procedure must define secure intake, authentication, logging, escalation, and response.
Timing
Applicable response deadlines depend on the governing regime. The final channel will state the relevant process and escalation route without combining it with marketing consent.
Version 1.0 · Reviewed 23 July 2026