For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Login
HomeDocsAPI ReferenceMCP ServerChat SDKsRelease Notes
HomeDocsAPI ReferenceMCP ServerChat SDKsRelease Notes
  • Introduction
    • Overview
    • Authentication
    • Versioning
    • Limits
    • Pagination
    • Errors
    • Migrate to V2
    • Changelog
  • Knowledge
    • Overview
    • Sources
    • Articles
    • Tags
  • End Users
    • Overview
    • Getting started
    • Developer guide
  • Integrations
    • Overview
    • Getting started
  • Conversations
    • Overview
    • Getting started
  • Webhooks
    • Overview
  • Data Compliance
    • Overview
  • Data Export
    • Overview
    • Getting started
    • Conversations
    • Messages
Login
LogoLogo
On this page
  • How does the API find and delete user data?
  • How does the API match a user by email?
  • What is the recommended way to store an email for deletion?
  • Can I pass the user’s email using metafields?
  • Can I skip email matching entirely?
  • What data is deleted, and when?
  • What should I check before making a deletion request?
  • Rate limit
Data Compliance

Data Compliance API

Overview
Previous

Delete all data associated with a chatter's email address

Next
Built with

The Data Compliance API enables the deletion of personal data associated with an individual’s email address from Ada’s databases. This includes identifying the chatter ID linked to the provided email address and removing all records associated with that chatter ID.

Data deletion requests may take up to 30 days to fully process and be removed from Ada’s databases.

This API supports compliance with data deletion requirements under applicable laws, such as GDPR. However, it may not fully satisfy all data deletion requests, especially if the provided email address is not linked to a chatter ID.

How does the API find and delete user data?

Review these important guidelines to ensure the Data Compliance API correctly finds and deletes user data.

How does the API match a user by email?

To successfully remove a user’s data using the Data Compliance API, the system must first locate the user by matching their email address. This process only works when the email is saved in a variable named exactly email, and that variable is either a global variable or a metavariable. Custom names like account_email or user_email will not be recognized by the API.

Autocapture variables are not supported. While it’s possible to pass email values into a conversation using metafields, these only work if they result in a global or metavariable explicitly named email.

What is the recommended way to store an email for deletion?

The most reliable way to meet this requirement is by using a Capture Block with @ Email validation. This ensures the email address is stored in the correct place and formatted properly, making it eligible for detection during the deletion process.

Can I pass the user’s email using metafields?

Yes — if the email is passed using metafields or other backend methods, it must be saved into a variable named exactly email, and stored as a global variable or metavariable. The Data Compliance API does not search raw metadata — it only looks for specific variable names in supported storage locations.

Can I skip email matching entirely?

Yes! As an alternative, developers can skip the email matching requirement altogether by using the chatter ID in their deletion request. This directly identifies the user without relying on any email field.

What data is deleted, and when?

Once a deletion request is successfully processed, the system removes all associated user data. This includes the full conversation history, chatter profile data, and any linked variables. Deleted conversations will disappear from the Conversations View, and any filtering or reporting based on deleted variables will no longer function.

While some deletions may happen quickly, it can take up to 30 days for all associated data to be fully removed. This delay is expected behavior and ensures comprehensive compliance across the platform.

What should I check before making a deletion request?

Before you delete a user’s data, here’s a quick checklist to make sure everything’s set up correctly so your request works as expected:

RequirementTypeNotes
A variable named exactly emailRequiredMust be global or metavariable
Email captured with @ Email blockRequiredEnsures proper formatting and storage
No autocapture variables usedRequiredThese are not supported by the API
Deletion may take up to 30 daysRequiredUnderstand the processing timeline
Metafields populate email variableOptionalOnly works if stored in a supported variable
Use of chatter_id instead of emailOptionalCan skip email matching entirely

Rate limit

The Data compliance API is subject to the global rate limits.