Esta tradução foi gerada por máquina e está pendente de revisão.Mudar para inglês
Escuro
Solicitar uma demonstração guiada
Nesta página
Visão geral para desenvolvedores

Data subject scope, erasure requests and account deletion

When one of your visitors or users asks for their data to be deleted, a tenant administrator works through the tools on this page. Backoffice has separate routes for browser intelligence data, identity verification data, administrator accounts and your Noxtica account. This page names each route, who runs it and what it leaves untouched.

Backoffice does not decide whether a request is valid and does not give legal advice. You verify the requester and decide the response with your counsel.

What it is

Availability: depends on your plan, role and the modules enabled for your organisation.

RouteWhat it removesWho runs it
Data Operations → End-user dataSoft-deletes fingerprints, events and visits for devices or an external user ID.Tenant administrator, with step-up.
KYC Verifications → DeleteIdentity verifications you select, with their evidence files.Tenant administrator, with a reason, a typed confirmation phrase and step-up.
KYC Erasure RequestsIdentity verification data for a verification subject.A request is opened for the subject. A different tenant administrator approves it in Backoffice, with step-up.
Data Operations → Admin accountsSoft-deletes a Backoffice administrator account.Tenant administrator, with step-up.
Server API for behavioral baselinesErases a subject’s behavioral baseline, when the module is enabled for your organisation.Your server, with an API key that has the erase scope.
Delete your Noxtica account formStarts a reviewed account deletion request from the account email.The account owner.

Backoffice has no screen that assembles a per-person access report. To answer an access request, use the export tools described in Audit log and data export.

Data Subject Scope

Open Backoffice → Privacy & Legal → Data Subject Scope. The page is read-only. It explains a boundary: your organisation can record its own lawful basis as controller, but it can never supply a visitor’s consent. Consent belongs to the visitor.

Three cards explain what that means.

CardWhat it saysLink on the card
Session replayYour organisation can stop recording per domain at any time. It cannot declare that a visitor consented to being recorded.Turn recording off in Replay policy
Per-domain consent and DNT/GPCEach domain records whether consent is required and whether DNT and GPC signals are honored. Overriding a signal needs a recorded lawful basis and is never the visitor’s consent.Review per-domain decisions
Behavioural and biometric signalsCollection can be turned off in each signal’s own section, and a recorded assertion can be withdrawn in one click.Withdraw an assertion in the Legal basis register

Everything reachable from the page turns collection off or withdraws an assertion. Turning something on is not offered. Recording “consent is not required” for a domain is a controller statement that another lawful basis applies. It is never a record that consent was obtained.

End-user soft delete in Data Operations

Data Operations soft-deletes browser intelligence data. The records are hidden from views and exports. Permanent removal is a separate step that a Noxtica platform administrator performs, and this page gives no timeline for it. The operation reports fingerprints, events and visits. Every operation is audited and listed in the History tab.

Erasure can be paused platform-wide while Noxtica reviews its safeguards. While it is paused, the end-user delete is refused with HTTP 503, a one-hour Retry-After and the message “Customer data erasure is temporarily on hold while its safeguards are reviewed.” Backoffice does not show whether the pause is on. Ask your account team.

Identity verification data

Identity verification data is separate. Noxtica does not remove verification details or evidence by itself and sets no retention date for them. They stay until a tenant administrator deletes them. Backoffice has two routes that delete them: Delete verification and Delete selected in KYC Verifications, and KYC Erasure Requests.

Delete verification removes the verifications an administrator selects (up to 25 at a time) together with their evidence files. The administrator gives a reason of 3 to 500 characters, types a confirmation phrase such as delete 2 verifications permanently and completes step-up. Billing usage records, legal-basis receipts and the audit trail are kept, two audit entries record the delete, and a legal hold or an open erasure request blocks it. No server API key can delete a verification. Business (KYB) and merchant (KYM) items are erased from their own pages with a reason. The full steps are in Verification data.

A right-to-erasure request is opened for a verification subject, and Backoffice lists it with the name of the requester. A different administrator approves it. Approving your own request is refused. A request can be placed on legal hold, which stops it from proceeding to deletion until the hold is released. When a request completes, Noxtica sends the kyc.erasure.completed event to your webhooks. It is not sent for a partial result and carries no subject identifier, and deleting verifications directly does not send it. Execution depends on what is enabled for your organisation. How a request is opened, its reach and its limits are in Verification data.

Admin accounts and your Noxtica account

Removing an administrator in Data Operations soft-deletes the account. The user loses access at once and disappears from lists. You cannot remove your own account, and the last active administrator cannot be removed. Backoffice has no screen that deletes a workspace. To close a workspace, contact your account team. Your contract and the DPA govern what happens to customer data after termination.

The public form at Delete your Noxtica account starts a reviewed deletion request for a Noxtica account. You enter the account email, receive a one-time verification code, enter it and submit. The page lists what may be retained. Read it before you submit.

Prerequisites

  • The administrator role and a multi-factor method. Data Operations asks for a fresh check before it runs an operation.
  • For an end-user delete, a list of device IDs, up to 500 per operation, or an external user ID. A date range or a domain narrows the match.
  • For Delete verification, the administrator role, a fresh step-up check and the identity verification module enabled for your organisation.
  • For KYC Erasure Requests, the identity verification module enabled for your organisation and an administrator other than the requester to approve.
  • For the behavioral baseline API, a server API key with the erase scope and the module enabled. See API reference.
  • For the account deletion form, access to the email address of the account.

Steps

1. Review the data subject boundary

Open Privacy & Legal → Data Subject Scope. Read the three cards. Use the links to switch off collection that depends on a visitor’s decision.

2. Soft-delete end-user data

  1. Open Backoffice → Administration → Data Operations and select End-user data.
  2. Enter Device IDs (one per line) or an External user ID (optional). You can add a Domain (optional), From date and To date.
  3. Add a Reason (optional), up to 280 characters. It is stored in the audit log. Use a reference such as your request number.
  4. Select Preview impact. Read the estimated fingerprints, events and visits. The preview is a dry run.
  5. Select Proceed with soft delete.
  6. Type DELETE and select Confirm soft delete. Complete the step-up check.
  7. Read the banner “Soft-deleted: … fingerprints, … events, … visits”.

3. Delete identity verification data

To delete verifications you choose:

  1. Open Backoffice → Identity Verification → KYC Verifications.
  2. Open a case and select Delete verification, or tick the rows and select Delete selected (up to 25).
  3. Enter a reason of 3 to 500 characters, type the confirmation phrase the dialog shows, select Delete permanently and complete the step-up check.

To work an erasure request:

  1. Open Backoffice → Identity Verification → KYC Erasure.
  2. Find the request in the list. The Requested by column names who opened it. Requests appear after a subject or an operator submits one for your workspace.
  3. As an administrator other than the requester, select Approve and confirm. Complete the step-up check.
  4. If a legal hold applies, select Hold. Select Release hold when it ends.
  5. Watch the status column until the request completes. Select View items to see per-artifact progress.
  6. Subscribe a webhook to the KYC erasure completed event to receive the completion signal. See Identity verification events.

4. Remove an administrator account

  1. Open Data Operations and select Admin accounts.
  2. Select the user, add a reason and confirm with DELETE and the step-up check.

5. Request deletion of a Noxtica account

  1. Open Delete your Noxtica account.
  2. Enter the account email and select Send verification code.
  3. Enter the code from the email and select Submit deletion request.

Verify it works

  • The preview shows “Dry run · no data deleted yet” before you confirm anything.
  • After confirmation the History tab shows an “End-user delete” row with a status of Completed. A “PARTIAL run” banner means the row limit was reached and you must run it again with tighter filters.
  • The audit log records approvals and refusals of an erasure request. An end-user delete shows data_ops_end_user_delete with the reason. A verification delete shows kyc_verification_delete_requested and kyc_verification_deleted with the reason.
  • A deleted verification no longer appears in KYC Verifications.
  • A KYC erasure request moves from requested to authority verified after a different administrator approves it. It ends as completed or partial.
  • The account deletion page answers “Your account deletion request has been accepted for review.”

Troubleshooting

SymptomCauseFix
The end-user delete fails with HTTP 503 and “Customer data erasure is temporarily on hold while its safeguards are reviewed.”Erasure is paused platform-wide.Ask your account team. Retry after the pause is lifted.
The delete is refused because no subject identifier was given.A delete needs a device ID list or an external user ID. A date range or a domain alone is not enough, although the preview accepts them.Add device IDs or an external user ID.
“Too many device IDs” appears.The list exceeds 500 entries.Split the list into several operations.
The external user ID matches too many devices.The match exceeded the limit of 10,000 devices.Narrow the date range.
A PARTIAL run is reported.The operation hit the row limit for some tables.Re-run with tighter filters, as the banner says.
Approve is refused with “You cannot approve your own erasure request — a different admin must approve it.”Dual control requires an approver other than the requester.Ask another administrator to approve.
The KYC Erasure page says the KYC module is not enabled.The identity verification module is not enabled for your organisation.Ask your account team.
Delete verification is refused with “Blocked by a legal hold or an open erasure request.”A legal hold is in place in your tenant, or an erasure request for the same subject is still open.Release the hold or let the request finish, then delete again.
“Cannot remove the last active admin.”A workspace must keep one active administrator.Add another administrator, then remove the account.
The account deletion form says too many attempts.The form limits repeated attempts.Wait a while and try again.