Skip to Content

Deletion and recovery

Suspension, deletion, Undo, backup restore and provider cancellation are different operations. Read the confirmation and preview for the object you are changing.

Suspend a customer

Suspension refuses customer access without serving as a refund or cancellation. Modem can refuse suspension or deletion while a purchase is unfinished. Let that purchase settle or expire, then inspect the customer again.

Unsuspending cannot revive an identity revoked by its authentication provider. Repair the identity-provider connection or sign-in lifecycle first. See Authentication lifecycle.

Delete a customer

The deletion preview distinguishes a native Modem customer from one linked to an authentication provider. For a provider-linked customer, the configured deprovisioning policy determines what happens:

PolicyResult
Retain product grantsDeletes the local identity/customer while retaining grants
Complete product grantsSuspends access, cancels known Stripe subscriptions, rechecks subscription state, then completes product access and deletes the local identity

This deletes Modem identity/access. It does not itself delete the user from Clerk, Firebase or another upstream authentication service.

Completing grants can stop after suspension if Stripe credentials are missing or cancellation fails. A subscription discovered during deletion can require another attempt. Fix the reported cause, inspect subscriptions and customer access, then retry; do not assume already accepted cancellations rolled back.

Native customer deletion removes the customer, grants, allowance and transaction-period data from ordinary views, including associated request history and stars. Soft-deleted rows retained by the server are not a guarantee that the app still exposes their history.

Delete a project

Project deletion can be refused until:

  • Pending identity-provider lifecycle work completes.
  • Recurring subscriptions reach a known terminal state.
  • Unfinished purchases settle or expire.

Inspect and resolve the reported lifecycle state instead of repeatedly deleting. Where an operation offers preserving request history, that choice concerns request history; it does not preserve a working project or its customer access.

Undo versus restore

The shared deletion UI provides an eight-second Undo window before server commit, and can offer Redo. It is held in the current app’s memory. Closing or reloading the app is not a way to preserve an Undo history.

Server restoration is separate. It restores only records deleted by the same deletion operation; independently deleted records stay deleted. Project restoration does not restore authentication identities/providers or billing-provider configuration, and does not re-add removed stars. Reconnect and verify those systems before resuming service.

A backup restore has its own scope, protected-state rules and credential opt-in. It is not equivalent to Undo.

Delete the owner account

Deleting your Modem account schedules server-side cleanup and signs you out. It also revokes admin API keys. Deleting the owner is subject to project lifecycle guards; it is not a shortcut around active subscriptions or unfinished purchases.

The current source configures a 30-day permanent-deletion delay outside local/test and two minutes in local/test. These are deployment defaults, not a verified promise for every hosted environment. Account restoration is an operator action, not a documented self-service restore button. Restoration cancels the scheduled cleanup and restores data from that account-deletion operation; revoked API keys stay revoked.

Before deleting an account, keep any required export and finish provider or billing actions. To clear only a browser replica, use Reset local data instead.

Last updated on