Request paths
Authenticated users should use the available account or workspace controls in Echo. Behind those controls, the supported technical request is POST /tenants/me/deletion-request. This endpoint is documented for integrators and support teams; ordinary users are not expected to call it manually.
Meta may submit its signed data-deletion callback to POST /data-deletion/meta/callback with a signed_request. Echo validates the request before starting deactivation.
What is deactivated
If the requester is the last active member of a workspace, Echo deactivates the full workspace. If other active members remain, Echo deactivates only the requester's membership.
Deactivated business and user records are hidden from normal product access. Deactivated data cannot produce messages, AI context, signed file links, jobs, usage, or billing activity. Private files are quarantined, and disposable caches and temporary credentials may be physically removed.
Credentials and external integrations
Active sessions and stored provider credentials are revoked during deactivation, preventing new access through connected services such as Google Calendar, Microsoft Calendar, or Meta channels. Restored workspaces must deliberately reconnect revoked integrations and billing.
Deactivation does not delete records held independently by a connected provider. In particular, calendar events that Echo already created in a provider calendar remain there unless an authorized user removes them through that provider.
Retained records and recovery
This process is recoverable soft deactivation, not irreversible erasure. Persistent records may remain stored for security, legal obligations, dispute resolution, service integrity, or reliable recovery, but are marked as deleted and excluded from normal product access.
Restoration is not automatic or guaranteed. A platform administrator must assess whether restoration is appropriate and safe. Revoked integrations and billing are not silently re-enabled as part of a restoration.
Status checking
Meta callback requests return a confirmation code. Meta, support teams, or technical integrators can check progress through GET /data-deletion/meta/status/:confirmationCode. Users who request deactivation through Echo can rely on the product or support channel rather than calling the status endpoint themselves.
Support
For help with a request, contact your workspace administrator or the support channel provided with your Echo account. Privacy-related contact details are listed in our Privacy Policy. You can also review the Terms of Service.