Your data. Your next move.

1. In Xem, open Settings → IMAP and find the connected Google mailbox. A workspace administrator can select Disconnect.
2. Xem disables the linked inbox and sender and clears the saved authorization secret from its active database. Requests already in flight may finish; disconnecting cannot recall delivered mail.
3. To revoke Google’s grant as well, open Google Account connections, select Xem or the consent-app name shown during connection, and remove access.

Revocation can affect other Xem connections or Google sign-in that use the same Google app. Have another way to sign in before revoking it. Reconnecting later requires a new authorization.

Disconnecting or revoking does not erase existing Gmail messages, Xem’s saved outgoing messages and attachments, the connection’s address, or backup copies.

Send your request to team@xem.email. Include your account email, workspace name and whether you want a specific connected mailbox’s saved data, your account, assistant history, or the whole workspace removed. You do not need to send message contents.

We will check identity and authority through the account or another proportionate method, confirm the affected data, and explain any impact on other members. An individual member cannot authorize deletion of an organization’s entire workspace. Export anything you need before confirming permanent deletion.

If you received a campaign sent by another organization, use that sender’s unsubscribe option for future campaigns and contact the organization about your contact record. You may also contact us for help routing a request.

Our proposed hosted-service commitment is to complete a verified deletion request within 30 calendar days. Residual copies in backups would expire within 90 calendar days after active-system deletion. The backup period is additional; it does not start when you first email us.

Backups are for recovery, not normal product access. Deleted data must be removed again before a restored backup returns to service. Any legally required or security-related exception must be limited to the relevant records, documented and explained when permitted.

These timelines are not yet in effect. We are validating deletion coverage and backup expiry before making the commitment active. A request can still be sent to our privacy contact now.

Deleting a saved assistant conversation removes the application’s active conversation and its pending proposals. Conversations otherwise expire seven days after their last save. Deleting history does not undo actions already approved and performed, recall sent messages, or delete other workspace resources.

AI-provider logs and recovery backups are separate from application history. Their retention and deletion terms must be confirmed before the proposed hosted policy takes effect. Ask for provider-side deletion to be included in your request where applicable.

A Xem deletion request does not delete your Google Account or independently erase mail held by Google, a recipient, or an integration you connected. Those providers have their own controls and obligations. Deleting an account also does not automatically delete content an organization is entitled or required to retain.

For a self-hosted installation, contact its operator. They control its database, credentials, backups and configured service providers. The hosted-service deadlines above do not automatically apply to independently operated installations.

Write to team@xem.email. You can request access, export or correction instead of deletion. Read the full draft privacy policy for the proposed commitments and how connected email is handled.