Privacy and terms
What this is
This service connects your Pebble app to your account so you can post from your watch. Your account's access and refresh tokens are kept off your watch.
What it stores
- Your OAuth session: access token, refresh token, and the key that binds them.
- One token per paired device.
- While you sign in, a pending login and a sign-in code. Both expire in ten minutes.
- A count of wrong sign-in codes, to limit guessing. It is stored against a one-way hash of the address it came from, never the address itself, and expires in ten minutes.
Your session, device tokens and sign-in codes are encrypted before they are written, with a key held only by this server. The wrong-code count and expiry times are not encrypted, and contain nothing about your account.
What it does not store
You sign in at your own provider, so this broker never sees your password. The broker sends posts to your account's server and does not store them.
What it can do
Within the permissions you grant, this broker can create records in your repo whenever your device asks, without you being present. Naming collections when you sign in limits it to exactly those. You can review or revoke the grant at your account provider at any time.
Who else is involved
Cloudflare runs this and stores the encrypted rows. Your PDS and its authorization server receive the requests. A public identity service is used to turn a handle into a DID.
Removing yourself
Remove my account revokes this broker's access at your provider, unpairs every device and deletes the stored session.
Terms
Provided as-is, with no warranty and no promise that it keeps running. You are responsible for what you publish through it. The operator may remove any account.