Delete your data

Use Factory reset Agentknock to remove the app’s local data and delete its live device registration on the relay. This is a self-service operation; no support request is needed.

Each installation has its own identity and relay records. If you use several phones, repeat the reset on each one. A reset does not stop automatic renewal; manage any recurring subscription separately through Plan and billing.

Delete data from a device

Factory reset erases the device identity and encryption keys, secret values, paired clients, requests, audit log, and settings. Save anything you intend to keep before continuing: Android backup cannot recover the installation’s secret values.

1. Open Settings and select Factory reset Agentknock.
2. Review the list of data to be erased.
3. Enter RESET AGENTKNOCK in Confirmation phrase, with the capitalization and spaces shown.
4. Tap Erase and reset Agentknock.

The app pauses request processing and asks the relay to delete the device registration. Once the relay confirms, the app asks Android to clear its data. The next launch starts setup with a new identity and pairing address. Every client must pair again.

Relay deletion disables device access, closes connections and stops sending push notifications. It requests deletion of the Firebase installation before removing the live mailbox, including client registrations, exchanges, push registration and the device’s subscription association. Separate subscription records are described below.

If Firebase cleanup fails, the disabled mailbox and its records remain while the relay automatically retries deletion. They are no longer available for normal use.

If relay deletion fails

If the app cannot confirm relay deletion, it shows Relay deletion not confirmed and leaves local data intact until you choose:

• Cancel to keep local data. The app can resume normal operation only if the relay registration is still active. Otherwise, retry the reset to complete deletion.
• Clear app data to erase local data anyway. The old relay registration may remain.

If Android refuses the local clear, the app tells you to clear Agentknock’s storage in Android settings.

Uninstalling the app, clearing its storage through Android settings, or resetting the whole phone does not perform Agentknock’s relay-deletion request. If you can still open the app, use its reset first.

When the relay registration has not been deleted explicitly, the relay automatically begins deletion after 180 days without authenticated activity from the device. This also covers a phone that is lost or no longer usable.

Phone backups

Android backup and device transfer can copy metadata, history, settings, and encrypted records. The installation’s encryption keys are excluded, so restoring those records does not recover the secret values or working client pairings.

Factory reset does not delete existing backup copies. Remove those separately through your phone’s backup settings or the backup provider’s account controls. Retention of those copies is controlled by that provider.

Other retained records

Record	What happens after reset
Pairing address	The current or pending address is reserved for 90 days to prevent immediate reassignment, without a link to the deleted Device ID. Previously retired addresses keep their existing expiry.
Relay recovery history	Cloudflare’s point-in-time recovery may retain historical database state for up to 30 additional days after deletion. This history is not accessible through the normal Agentknock protocol.
Firebase installation data	We request deletion when the device registration is deleted, and when its notification identifier is replaced or removed. Google states that associated data is removed from Firebase’s live and backup systems within 180 days of the deletion request.
Subscription records	Subscription records no longer linked to a device are normally deleted shortly afterwards. Expired Google Play records and limited records of replaced purchases follow the 60-day retention rules.
Purchase records	Purchase history and subscription records remain with the service used for the purchase. Manage any recurring subscription through that service; resetting Agentknock does not stop automatic renewal.

CLI pairing records

The CLI keeps its pairing credentials in pairing.json inside the Agentknock directory, which defaults to ~/.agentknock. Resetting the phone does not delete that file from your computers. After the reset, run this for each directory paired with that phone, using the same --agentknock-home or AGENTKNOCK_HOME setting as before:

agentknock pairing remove --force

--force removes only the local pairing file, without contacting the phone. To remove a working pairing from both ends while keeping the phone’s other data, use agentknock pairing remove without --force.

The CLI does not store delivered secret values in its pairing file. Files you uploaded, copies saved by commands, shell logs, and computer backups are separate and need their own cleanup. Deleting Agentknock data also does not revoke credentials at the services that accept them.