Crossed
Download Crossed on Android

A direct exit, without partner approval

Delete your Crossed account

Account deletion starts a durably retried cleanup. The cleanup closes the connection for both and removes your copy; it does not silently rewrite the other person’s already revealed memories.

Current product draft · 16 July 2026

This page accurately describes the private-beta build, but it is not ready for public publication until the controller identity, contacts, production configuration, and legal review are complete.
On this page

Delete in the Android app

  1. Open Crossed.
  2. Open Safety.
  3. Open Account controls.
  4. Choose Delete account and data.
  5. Read the confirmation and confirm only if you want the deletion to proceed.
You do not need the other person’s approval. The deletion cleanup closes the live connection for both.

The deletion request requires recent passkey or recovery-code verification before cleanup begins.

What is deleted from your side

Crossed starts a durable cleanup of your:

  • pseudonymous account and server-side authentication credentials;
  • active connection membership and waiting tap state;
  • invitations and invitation receipts tied to your account;
  • notification devices and Live Crossings choices;
  • caller-only daily counters and other active connection state;
  • block records involving your account;
  • your retained released-Crossing calendar copies and cumulative total;
  • recovery metadata and deletion-related local state once cleanup completes.

The backend retries cleanup until the data sweep and Firebase Authentication deletion succeed. Provider backup copies are not guaranteed to disappear at the same instant as the visible action.

A passkey copy may remain visible in your credential provider after Crossed deletes its server credential. That copy can no longer authenticate to the deleted account.

What happens to the other person

The cleanup disconnects the other person and removes their active membership, devices for that connection, counters, and Live choices. If a transient failure interrupts cleanup, the backend retries it.

They keep only their own copies of mutual Crossings that were already released, until each entry reaches its original 30-day expiry. They see no matched pair and may send a new invitation to someone else.

Crossed does not send a dedicated notification saying that you deleted your account.

Timing, retries, and confirmation

Deletion is designed as a retried job rather than a single fragile request. A short completion tombstone remains for 24 hours after success so the service can avoid recreating ambiguous state.

Physical database time-to-live deletion is asynchronous.

The provider backup-deletion schedule is being verified for the public privacy notice.

If the app closes during deletion, private phone state is cleared and account recreation is blocked. An opaque deletion receipt/status mechanism remains required so someone can confirm an ambiguous request after local authentication is gone.

If you cannot access the app

Request account deletion by email. You do not need to reinstall Crossed to start the request.

Crossed accounts do not contain an email address or display name, so support may need to confirm which pseudonymous account the request concerns before deleting it. Never email or paste an invitation fragment, passkey output, recovery code, device PIN, or the other person’s private details.

Before deleting

  • If you want a copy first, use Safety → Account controls → Export my data.
  • If you only want to stop the current connection, choose End connection instead.
  • If you need to prevent these accounts from reconnecting, choose End and block.
  • Deletion is intended to be irreversible after cleanup succeeds.