UUtly Remote Download

Privacy

This page lists everything the Utly Remote service stores. If something isn’t listed here, we don’t collect it.

The service is run by Utly Development Studio. It’s made up of our server at broker.utly.dev, which helps computers connect and handles accounts, our relay at turn.utly.dev, and this website. All of it runs on one server we rent from Hetzner Online GmbH in Finland. We don’t use analytics, advertising or tracking of any kind, on the website or in the program.

Without an account

Your ID. When the program starts, it registers a public key with our server. The server gives it a nine-digit ID and keeps the two together for as long as the ID exists. It also stores when the ID first registered, which version of the program it runs and since when, and when it last connected. The matching private key never leaves your computer.

When you’re online and who you connect to. While the program is running, our server knows your ID is online and the internet address it’s connecting from, and it notes the date. When one ID asks to connect to another, the server passes on the request, the answer, and the technical details the two computers need to connect, which include both of their internet addresses. For every accepted session it keeps a record of both IDs, when the session started and ended, how long it lasted, whether it went through our relay, and how much data the shared computer sent. It doesn’t know, and can’t record, anything that happened during the session. Every five minutes it also counts how many IDs are online.

We keep session records, and the record of which days an ID was online, for ninety days. After that, only daily totals remain, and they don’t include any IDs: new installations, computers seen, the most online at once, sessions, how many went through the relay, total time and total data. We use these numbers to understand how the service is used and to plan the paid versions. Nobody outside Utly Development Studio sees them.

The server’s log records IDs going online and offline, with their internet address. It’s limited to a hundred megabytes, and the oldest entries are deleted as new ones are added.

The relay. When two computers can’t connect directly, our relay passes their data between them. It can see both internet addresses and how much data is sent, but it can’t read the data itself, because it’s encrypted between the two computers with keys the relay doesn’t have. The relay gives out a new login for each connection, and each one expires after ten minutes.

What happens during a session, meaning your screen, typing, clipboard, sound, files, chat and calls, only goes between the two computers. Our service never has it.

On your computer, the program keeps its identity key (protected by your Windows account), the public keys of computers you’ve connected to, your address book, your unattended access settings (the password itself can’t be recovered from them), your settings, and a session log. The installed version keeps these in %ProgramData%\Utly Remote, and the portable version keeps them in your local app data folder. None of this is sent anywhere, except as described on this page.

With an account

Accounts are optional. If you create one, our server stores:

  • your email address, which is used as your account name (we don’t check it or send you email);
  • a password record that the password can’t be recovered from;
  • the secret for the authenticator app you set up;
  • your eight recovery codes, stored in a form they can’t be read back from;
  • for each of your devices, including any browser you sign in with at utly.dev/account: the name the device gave itself (such as the computer and user name, or the browser and operating system), the internet address it last connected from, when it was added and last seen, and a scrambled copy of its sign-in token;
  • your address book in encrypted form. Each entry is stored separately under a label that means nothing to us, and is encrypted on your computer with a key made from your password. We can’t read an entry or tell which ID it’s for. We can see how many entries there are and when they change.

There’s no way to reset your password, because our server doesn’t store anything that could reset it.

Signing in at utly.dev/account sets two cookies, both only for that page: one that identifies your browser’s session with our server, and one that holds the device’s sign-in token. No other website can read them, and we don’t use tracking cookies.

Abuse reports

When you report an ID from the program, we store your ID, the ID you reported, what you wrote (up to 500 characters), your internet address and the time. A person reads every report, and we keep it until it’s been dealt with. If we block an ID, we store the reason and the date.

Crash reports

Crash reports are off unless you turn them on. When the program crashes, it saves a report on your computer only. Settings › About shows any reports waiting there, with a button to send them yourself and a switch to send them automatically. When a report reaches us, we store the time, your internet address, the program version, which part of the program crashed, your Windows edition and version, and the report itself. The report contains the error and the line of code where it happened, with your Windows user name removed. It doesn’t contain anything from your screen, clipboard or files. A person reads it, and we delete it once the problem is fixed.

Updates

The program checks this website for updates 30 seconds after it starts and then every six hours. The check doesn’t send your ID or your version. Like any web request, it includes your internet address, which our web server logs and deletes on a schedule (see below).

How long we keep things

Your ID’s record lasts as long as the ID does. If you delete the program’s data folder, the computer gets a new ID next time. Session records and the days an ID was online are kept for ninety days, and the daily totals made from them, which don’t include IDs, are kept. Account data is kept until the account is deleted, which for now means asking us. Abuse reports are kept until they’ve been dealt with, and crash reports until the crash is fixed. The server’s log is limited in size, as described above. The web server’s access log is replaced every day and kept for fourteen days. We back up the server’s database every night and keep the backups for thirty days.

Your rights

You can ask us what the service holds about an ID or an account, and ask us to correct or delete it. Write to mail@lohit.me.

Changes

We update this page whenever the service changes what it stores.