Revue

Privacy

This page says what this Revue server keeps, why and for how long. Revue itself is a desktop app: it talks straight to GitHub, Bitbucket, Forgejo, Jira and Slack from your computer, and none of that passes through here.

Who is responsible

This server is run by [email protected], who decides what happens to the data below (the controller, in GDPR terms). Write to them about anything on this page.

Images and links

Revue accounts

A Revue account keeps your sign-ins, settings and favourites so every computer you use has them. They are end-to-end encrypted: your computers encrypt them before sending, with keys made from your password that never leave them. This server stores ciphertext it can't read, and never sees your password, your tokens, or which services you use (but see signing in to a service from the web, below).

The account's web page (/account) can list, add and remove your sign-ins too. Your browser opens them there the same way, with your password: this server still sees only ciphertext. A token you paste there is checked with its service and encrypted by your browser before it's sent. What keeps them safe in the browser is the page's strict policy: it runs only this server's own scripts, never inline ones, and decrypts in a background worker, out of the page's reach.

This server also offers Sign in with GitHub, Jira, Slack… on that page. Such a sign-in goes through this server: it swaps the service's code for the token and hands the token to your browser, which encrypts it. For that moment, this server sees the token. It keeps it in memory only until your browser takes it (10 minutes at most), and never stores or logs it, or the code. Pasting a token instead keeps it end-to-end.

What it does keep, and why:

DataWhyKept
Your email address and the language of your mailsTo sign you in and send codes and security noticesUntil you delete the account; 7 days for one never confirmed
The encrypted vault, its wrapped keys and saltsThe service itselfUntil you delete the account
Your computers' names, systems, app versions, and when they were last seenSo you can see and remove themUntil signed out, then 30 days
Your passkeys: their public keys, names, a use counter, when added and last usedTo sign you in with a passkeyUntil you remove the passkey or delete the account
Activity: sign-ins and security changes, with IP address and browser or appSecurity: so you can spot what wasn't you90 days; IP addresses cut to their network (/24 or /48) after 7
A browser signed in to the account pages (/account): one cookie holding its sessionTo keep you signed in there; it's needed for that and nothing else (no tracking)Until you sign out, after 15 minutes unused, or 8 hours at most; with "Keep me signed in on this browser" ticked, 30 days
A browser that starts "Sign in with …" there: a second cookie, a random valueSo only the browser that started a sign-in can finish it10 minutes
Mails waiting to be sentDeliveryThe text is deleted once sent; the record after 30 days
IP addresses and emails in rate limitsTo stop abuse (mass sign-ups, password guessing)In memory only, at most a day

The legal basis is providing the service you asked for (GDPR Art. 6(1)(b)), and, for the activity log and rate limits, the legitimate interest of keeping accounts safe (Art. 6(1)(f)).

Mails are only codes and security notices: no newsletters, no tracking pixels, no tracked links, no cookies. They are delivered by the mail service at smtp.seznam.cz, which sees the address and the mail's text (codes and notices, never vault data).

Your rights

You may also complain to your data protection authority (in Czechia, the ÚOOÚ).