Skip to main content
Reflecto
How it works Privacy Agents Developers FAQ Blog
Get it on Google Play Add to Chrome
Get it on Google Play

Delete Your Data

Last updated: November 1, 2026

Reflecto is designed with privacy at its core. We use end-to-end encryption and do not maintain user accounts — your identity is tied solely to your device pairing, not to an email address or personal information.

Below you'll find how to delete your data and what gets removed.

Delete Data from the App (Recommended)

The fastest way to delete all your data is directly within the Reflecto app:

  1. Open the Reflecto app on your Android device
  2. Go to Settings
  3. Open the Danger zone section and tap Disconnect
  4. Confirm the disconnection

This immediately and permanently:

  • Revokes your device record on our server
  • Deletes your encryption keys from the device
  • Removes your FCM push token and any Web Push subscription
  • Clears all local preferences and app filter settings
  • Disconnects your paired devices (Chrome extension, web app, and any others). Each one deletes its copy of your text messages, if you used SMS mirroring, when it next connects
  • Deletes any items you shared to a connected AI assistant — the one kind of content our server can read, so the one that most needs removing rather than merely expiring
  • Revokes any AI-assistant connections and API tokens your phone created, so they stop working at once

After disconnecting, your device record is deleted and our server can no longer associate the rest of your data with your device. The one exception is a plan or perk tied to your phone: its record keeps the device continuity hash until the plan or perk ends.

If you pair again, your phone sends its device continuity hash again (see below). To keep it off your device record, uninstall the app after disconnecting.

Founding membership

If your phone holds a Founding membership, disconnecting does not end it, so that it comes back when you pair the same phone again. There is no option to end a Founding membership: it stays with that phone, and its plan and claim records keep the keyed hash, for as long as the Founding programme runs (see section 10.1 of our privacy policy).

Remove your text messages only (SMS mirroring)

If you turned on SMS mirroring, your computers keep a copy of your text messages so your history survives a restart. To remove those copies without disconnecting anything else:

  1. In the Reflecto app, go to Settings → SMS mirroring and turn off Mirror SMS messages

Mirroring stops immediately, and the phone tells each paired computer to delete its copy. A computer that stays offline the whole time can miss that notice and keep its copy; disconnecting that computer always deletes it. Deleting a text on your phone does not remove a copy a computer has already received. On Samsung phones, a text you delete stays in the phone's recycle bin for up to 30 days, where Reflecto can still see it, so it can also reach a computer you pair during that time.

What data does Reflecto store?

On our server (api.reflecto.dev)

  • A server-assigned device ID (random identifier, not tied to your name or email)
  • Your device's public encryption key (used to route encrypted messages)
  • On Android, a device continuity hash: a one-way, keyed hash of your phone's Android ID, used only to recognize the same phone after you reinstall Reflecto and to make sure one phone claims at most one Founding membership (see section 4.1 of our privacy policy). The Android ID itself never leaves your phone. Deleted with your device record when you disconnect; a plan or perk tied to your phone keeps its own copy until it ends
  • If your phone claimed a Founding membership, a Founding claim record: the keyed hash, a place number, the claim date and which kind of use qualified the phone. It is kept for as long as the Founding programme runs, so the same phone can't claim twice (see below)
  • Your FCM push token and/or Web Push subscription (used to deliver commands to your devices)
  • Encrypted notification, clipboard, and file-transfer data in a temporary queue (auto-deleted within 24 hours, or sooner once delivered and dismissed — large clipboard images and in-progress file transfers use their own short-lived, similarly temporary storage)
  • Encrypted text messages, if you turned on SMS mirroring: new ones wait in the same 24-hour queue, and batches of older messages are deleted once your computer confirms it received them, and after one hour at most
  • Items you explicitly shared to a connected AI assistant, if you use that feature (the 50 most recent, expiring about a day after you last shared anything, and removed when you disconnect your last assistant or fully disconnect your phone)

All notification, clipboard, file and text-message content is end-to-end encrypted. Our server cannot read it — it only stores opaque ciphertext until your other device picks it up.

The one exception is the last item above. Something you deliberately share to an AI assistant has to be readable by that assistant, which is not one of your key-holding devices — so our server holds the key for it. It is still stored encrypted, but we could read it, and we would rather say so than let the sentence above appear to cover it.

On your device

  • Your encryption key pair (stored in Android Keystore-backed encrypted storage)
  • Your paired devices' public keys
  • Your app filter settings (which apps to mirror)
  • Onboarding progress flags

On Firebase (Google)

  • Your FCM token (for push notification delivery)
  • Anonymized crash reports via Firebase Crashlytics (stack traces only, no notification content or personal data)

Lost or no longer have your device?

If you can't access the app, here's what happens automatically:

  • If the app was uninstalled or the device was factory reset: Your encryption keys are permanently destroyed on the device. Without those keys, the encrypted payloads on our server are cryptographically unrecoverable. They will also auto-delete within 24 hours.
  • All notification, clipboard, file and text-message content was already end-to-end encrypted before it ever reached our server. We cannot read it, and it becomes permanently inaccessible once your keys are gone.
  • Copies of your text messages on your own computers, if you used SMS mirroring, stay there until that computer is disconnected. Without your phone you can't disconnect it from the phone, so disconnect it from the computer's own Reflecto settings instead; either way it deletes its copy. They are never uploaded anywhere from there.
  • Items you shared to an AI assistant are the one exception to the reasoning above, and we would rather be explicit than let it look covered. That path is not end-to-end encrypted — the assistant that needs to read what you shared is not one of your key-holding devices, so our server holds the key. Destroying your device's keys therefore does not make those items unreadable the way it does for everything else. They are removed when you disconnect your last assistant or fully disconnect your phone, and otherwise expire on their own (the 50 most recent are kept, clearing about a day after you last shared anything).
  • Your device record (device ID, device name, push token, public key, and on Android the device continuity hash) will persist on our server in an orphaned state. Reflecto has no accounts and no email addresses. The device ID is random, and the continuity hash is one-way and keyed, so it cannot be turned back into your phone's Android ID, and we use it only to match a plan or perk to the same phone.
  • A Founding membership, if your phone held one, stays with that phone's keyed hash. It returns if you reinstall Reflecto on the same phone. Its plan and claim records are kept for as long as the programme runs.

In short: if you no longer have the device, your content is already unreadable or deleted. What remains is the orphaned device record described above.

After deletion

Once disconnected via the app:

Data Status
Device record Immediately revoked
Queued encrypted notifications, clips, and file transfers Deleted (or auto-expire within their retention window)
Items shared to an AI assistant Deleted
Text messages copied to your computers (SMS mirroring) Deleted by each computer when it next connects
Push token / subscription Deregistered from our server
Crashlytics data Retained by Firebase per Google's policy (anonymized, no personal data)
Local encryption keys Destroyed
Local preferences Cleared

You can re-pair at any time by setting up Reflecto again. A new device ID and new encryption keys will be generated — there is no continuity with the previous session.

Crash report data (Firebase Crashlytics)

Reflecto uses Firebase Crashlytics for crash reporting in release builds. This data is:

  • Fully anonymized (no notification content, no personal identifiers)
  • Limited to stack traces and non-sensitive log breadcrumbs
  • Managed by Google under their data retention policies

To opt out of Crashlytics data collection, disable "Usage & diagnostics" in your Android device settings (Settings > Google > Usage & diagnostics).

Questions?

Contact us at support@reflecto.dev

Reflecto
Google Play Web App Chrome Extension API Docs Agents Android on Mac Clipboard on Mac Phone Link for Mac File transfer Blog Community Contact Privacy Policy Terms Delete Your Data
© 2026 Reflecto. All rights reserved.