Skip to main content

End-user data erasure

Flex processes conversion data on your behalf. To request erasure of an end user's conversion identifiers, email privacy@tntgrowth.com with your client name and the user's email addresses and/or phone numbers. Raw identifiers or their SHA-256 hashes are accepted. Include all known aliases. Do not send API keys.

Our team verifies that the request comes from an authorized representative of the client before executing it. We confirm the result in writing after all supported stores have been processed and no ownership or active-worker conditions remain unresolved. A failed or pending request is not a confirmation of erasure.

You can also submit a request using a dedicated client-scoped API key whose route allowlist explicitly includes /api/privacy. Ask your account team to issue this key. Keep it on your server. Existing unrestricted keys and browser pixel keys do not grant erasure access automatically.

POST /api/privacy/erasure-requests
Content-Type: application/json
x-api-key: YOUR_CLIENT_API_KEY

{"email":["user@example.com"],"phone":["+14155552671"]}

The response is HTTP 202 and includes data.id. Use GET /api/privacy/erasure-requests/{id} with the same API key to check the status and per-store counts. Optional identifier arrays are externalId, clickId and tntId. A key with an explicit route allowlist needs access to these routes. Requests are restricted to the client that owns the API key.

This endpoint covers supported advertising conversion records, their delivery outbox and ledger, submissions, silent-loss diagnostics, linked web-attribution records, CRM attribution observations and raw events, CRM failure records, staged conversions, conversion webhook deliveries, call-tracking mappings and history, insurance-verification leads, iClosed webhook logs, Funnel and unified conversion reporting records, registered conversion queues, HubSpot event buffers, the Unvault conversion export, and the weekly Google Ads conversion export sheets.

Requests remain incomplete if matching legacy records have no verified client owner, a relevant worker is still active, or a store cannot be processed. Our team must resolve those conditions before confirming completion. Shared accounts and matching identifiers alone do not establish ownership. A completed endpoint request confirms processing of these supported stores; it does not assert that all systems holding personal data have been erased.

Reporting rows and conversion totals remain. Replayable identifying payloads are removed, while the audit retains hashed selectors, status, timestamps and counts. Restricted deduplication evidence prevents previously processed conversions from being sent again. Hashes remain personal data. Late retries of erased events are covered by their original event time; a later new conversion from the same person is treated separately.

Data already delivered to advertising platforms is outside this procedure. As the controller, you must use each platform's own deletion process. Database backups and historical logs follow their separate retention policies; restoration requires reapplying completed requests before serving restored data. This endpoint does not delete historical logs or backups.