Security

Your pushes are end-to-end encrypted. A link, its title, and a file’s name and contents are encrypted on your device before they leave it, and are opened only on the devices you sign in to. Our servers, Google’s (which run them), and anyone with access to either hold only what they cannot read.

YOUR PASSWORD IS THE KEY

When you sign in, the app turns your password into two keys on the device: one signs you in, and the other unlocks the key your pushes are encrypted with. That second key never leaves the device, so we cannot read your pushes. It also means we cannot reset your password for you and keep your pushes: only the recovery key, below, can do that. Your password reaches Google’s sign-in service in these cases: when you reset it, since the reset is made on Google’s own page, and when a sign-in with the first key is refused (a mistyped password, say), since the app then tries the password itself in case the account was made before encryption. A version of the app from before encryption also sends the password itself whenever it signs in. After a reset, the password Google holds is replaced with the first key once you have entered your recovery key or chosen to start over.

A key is only as strong as the password it comes from. Making it is deliberately slow, about a second on a phone, and every guess at your password costs an attacker the same; a short or common password is still guessed in the end. That is why PushThat asks for at least 10 characters.

WHAT IS ENCRYPTED
  • The link you push, and the title and icon of its page.
  • A file’s name, its type and its contents. Files are stored under a random name.
  • The words search looks for. Search uses scrambled tokens made with your key, so the server can match a search without reading the words.

Notifications carry none of it. A device that receives one fetches the push and decrypts it itself before showing anything.

WHAT IS NOT
  • When and how much. Which account pushed, when, whether it was a link or a file, roughly how large a file is, which of your devices sent it and how many pushes you make. The monthly limits, file expiry and notifications need these.
  • Search patterns. The server can tell that two of your pushes share a word, or the start of one, without knowing what the word is.
  • The apps. We make the apps, and a changed app could send your key anywhere. This is true of every end-to-end encrypted app that updates itself: the servers cannot read your pushes, and the apps you install from us are what you trust.
  • Pushes made before encryption. A link pushed before your apps updated, and its title, stay as they were sent until an updated app signs in to your account and encrypts them in place, which it does on its own. A file pushed before then was stored as it was sent, under its own name, and stays that way until it expires, within 30 days.
  • An unlocked device. The key is kept in the device’s secure storage, where the app can use it, so a device that is unlocked and in someone else’s hands shows them what it shows you.
THE RECOVERY KEY

When your account’s encryption is set up (when you create your account, or the first time an updated app signs in to an account made before encryption), PushThat shows a recovery key once: 32 letters and numbers in groups of four. It is a second way to unlock your pushes, and the only one besides your password. Keep it somewhere safe and apart from your devices, such as a password manager or on paper.

If you lose it while you are still signed in, the Android, iPhone and Mac apps can show you a new one from their menu. The new one replaces the old, which stops working.

IF YOU FORGET YOUR PASSWORD

Reset it from the sign-in page, with the link we email you. After you choose a new password, you are asked for your recovery key. With it, nothing is lost.

Without it, the pushes you made before the reset cannot be read again, by you or by us: they were encrypted with a key that only your old password or the recovery key could unlock. Your account gets new keys, and the old pushes stay in your list as locked rows that you can delete. Files are deleted within 30 days either way.

OLD VERSIONS OF THE APPS

A version of the app from before encryption cannot read an encrypted push, and its pushes are refused. It was not written to know why, so it may say the push could not be saved, or that you have used this month’s pushes when you have not. Update it and the push goes through.

YOUR DEVICE ID

Each install of PushThat makes a random device ID, which the web app shows on the Account page. It goes with every push so that the device that sent one does not notify itself, and it says nothing about the device: it replaced the device’s name (the one you gave it, its model name, or the browser’s user agent), which pushes used to carry.

QUESTIONS

Write to hello@pushthat.link. If you think you have found a security problem, say so in the subject.