Skip to main content

Move to another device

Glitr does not have an account you export as a file from us. Your identity for messaging is:

  1. The git repository URL
  2. A token that can read and write it
  3. The encryption password

A new phone, laptop, or browser profile is a new local clone. Connect with those three facts and the conversation reappears as git fetch + decrypt.

On the new device​

  1. Open Glitr (or install the PWA there).
  2. Connect with the same URL and same encryption password.
  3. Use a token that still has write access. You can mint a new token; you cannot skip the password.

The first connect clones. Large history takes longer. Chats paint as documents decrypt.

Contacts on the new device​

Contacts live in your repository (encrypted). After connect and sync, they should return with the rest of the mailbox. You should not have to re-add everyone unless you never synced them, or you logged into a different repo by mistake.

Each device keeps its own local clones of peer repositories. The new device will fetch those peers again.

Two devices at once​

Both can be connected to the same mailbox. They are two checkouts of one repo.

  • Push/pull can race. Glitr treats document conflicts per record; you may be asked to resolve a clash if both sides edited the same row before syncing.
  • Live handshake is per running app. Two devices may not both stay Live with the same peer in a tidy way. Prefer one active sender if you are debugging ticks.

What does not travel​

  • Session storage and the on-device clone from the old browser. Logout or uninstall on the old device wipes local data only.
  • Tokens you did not save. If the old token was only in that browser, mint a new one on the host.
  • The encryption password, unless you stored it yourself.

Losing a device​

Revoke the token that device used. The repository on the host is still the mailbox — clone it elsewhere with a new token and the password. If the lost device might still be online, treat it like a lost laptop: rotate tokens, and assume anything that device could decrypt is in play until you stop trusting that password.