Audit Logs

Forget API maintains an audit trail for every sub-request created for each integration when a deletion Request is submitted. Each log entry captures what happened, when it occurred, the outcome, and the exact HTTP request sent to the integration along with the exact HTTP response returned.

Viewing audit logs

Go to the Requests page.
Click a specific deletion Request.
Select any of the sub-requests (one per attached integration) to see the full audit trail for that integration.

This view shows every operation recorded for that sub-request, in chronological order.

What’s captured

Request creation and updates per sub-request
Integration calls, retries, status checks, and outcomes
Cancellations (where supported by the integration)
Data retention actions based on your organization settings
Raw HTTP request and response details for each integration call

Operations

REQUEST_USER_DELETION: Logged when a deletion is requested for a specific integration. If the Request is retried, this operation is logged again.
CHECK_USER_DELETION_STATUS: Logged when Forget API checks the status of a deletion on the destination. This can be triggered manually (UI or API) or automatically on a recurring schedule. Only some integrations support this.
CANCEL_USER_DELETION: Logged when a member cancels a deletion for a specific integration. Only some integrations support cancellation.
COMPLETE_USER_DELETION: Logged when an integration reports that the deletion has completed. The resulting status at completion time is recorded.
DELETE_DELETION_REQUEST: Logged when the deletion Request is removed from Forget API systems per your data retention settings.
HASH_DELETION_REQUEST: Logged when the identifier for a deletion Request is hashed in Forget API systems per your data retention settings.

HTTP request and response transparency

For each relevant audit entry, you can view the exact HTTP call made to the integration and the exact response received:

Request details: method, URL, and body
Response details: status code and body

This provides end-to-end visibility for debugging and verifying how each integration handled the deletion.

Notes

Some operations depend on integration capabilities (for example, status checks and cancellations).
Retries create additional entries so you have a full history of attempts.
Timestamps and outcomes are included to support audits and compliance.