Requests are processed in a fixed order, and the order explains the timing.
- Submission - the request is recorded with its type, jurisdiction and who submitted it.
- Verification - a confirmation email goes to the address named in the request. Nothing is applied before this is clicked, because an unverified request is just somebody typing an address into a form.
- Application - once verified, suppression is applied automatically rather than sitting in a queue.
- Confirmation - the page confirms what was applied.
What suppression changes
- The contact stops appearing in search results.
- The contact is excluded from every export by default.
- The address is added to the suppression list, so campaigns run through the platform do not contact it.
- Any matching product account is marked opted out of marketing email.
What it does not change
Copies already downloaded by a customer before the request are in that customer's possession, not in our systems. We cannot reach into a third party's CRM. If somebody keeps contacting you from an old file, the productive route is to reply to that sender asking them to remove you, and their own obligations apply.
Timing
The verification email is immediate. Suppression is applied as soon as you verify. Correction requests involve a human review of the record and therefore take longer than suppression.
Acting for somebody else
Say so in the submitter field. Requests on behalf of another person still verify against that person's mailbox, which is the only way to confirm the request is genuine.
Questions about a specific request: privacy@argorant.com, quoting the address it concerns.