The extension, in plain words.

Who, and what this covers

The extension is made by Siliroid LLC d/b/a Liir, the company behind liir.net. This page covers the Liir extension for Chrome. Everything in our privacy policy applies to it too: your rights, how long things live, and what happens if something goes wrong. This page says what is particular to the extension.

What it sees, on the pages you visit

On secure (https) pages, the extension reads the page's form fields: their type, their name, their labels and placeholders, the heading above them, and whether they are empty. That is how it tells your email field from a friend's, and which fields your page can answer. It notes whether a field is empty, or a choice was changed, only so it leaves your own answers alone. It never fills password, payment card, one-time code or search fields.

All of this happens in your browser. None of it is sent anywhere or kept after you leave the page. The extension does not run on unencrypted (http) pages, or on liir.net, liir.tv and thiir.net.

What it sends, and when

Nothing leaves your browser until you press. The ring, and the card that slides down when a page asks for your email, are drawn from what this browser already keeps. Showing them sends nothing. Everything below goes to liir.net over HTTPS, and to no one else.

When you connect: the extension's page asks liir.net for a short code and sends a name for this browser, like “Chrome on Windows”. You type the code on liir.net, signed in, and touch your key. Liir checks that the code was typed from the same network that asked for it; that comparison happens in memory and is never written down.

When you press the ring, or Use Liir with your email on: the site's name (its domain, like example.com, and its host, like shop.example.com), so liir.net can find the address you already keep for that site, or make a new one. Nothing else about the page: not its address beyond the host, not the form, not what you typed.

When you press Use Liir with other details on: the kinds the card listed and you left on, like “name, phone, shipping address”. Not the site. liir.net answers with those details from your page, and only from rows you set to Public or Liir only: never a row on Ask, never a Vaulted one.

When you open the extension's page: a check that this browser is still connected, and which kinds your page keeps and on which dial (for example, “birthday: vaulted”), never a value, so the card can say “in your vault” before you press. At most once a day, opening it also asks which version of the extension is current, so it can tell you when a new one is out; that request carries nothing about you, not even the connection. When you disconnect: a request that liir.net forget this browser.

What it keeps in your browser

The connection: a random token, your Liir name, this browser's name, and when you connected, in the extension's own storage, which no web page can read.
Per site where you pressed: the address the last press filled there, so the card can show it next time without asking anyone.
Per site where you chose “Not on this site”: that choice, until you undo it on the extension's page.
Which kinds your page keeps, and on which dial. Never a value.

The details a press brings (your name, your address) pass straight into the form you pressed on. The extension does not keep them. Disconnecting clears the token, the remembered addresses and the list of kinds. Removing the extension clears everything it kept.

What liir.net keeps

The connected browser: its name, a hash of its token (never the token itself), which of your keys approved it, what it may do (make doorways, and fill forms if you ticked that box), when it was connected, last used, last filled a form and removed, and how many forms it has filled. You see it, and remove it, under Browsers on your account page. A browser unused for 90 days stops working, and connecting or removing one sends you a notice.

Each doorway it makes: the address, the site it belongs to, its label (the site's host), and the dates, exactly like a door you make yourself (“Doors” in the privacy policy). You can close it with one click.

Each fill: a line in the service log saying which of your browsers filled (by its id, never its token), how many kinds were asked for and how many were given. Never which site, and never the values.

Never kept: a list of the pages you visit (the only sites liir.net knows are the ones you pressed for a doorway), anything a page says, what you type, or your IP address.

What it never does

It never submits a form: the page's own button stays yours to press. It never fills a field you already typed in, or a field you cannot see. It cannot reach your mail, your Vault, your files or your account: a connected browser can make doorways and, if you allowed it, read the rows of your page set to Public or Liir only. Nothing else. It never sends your browsing history, and it loads no code from anywhere: everything it runs came in the package you installed. No analytics, no ads, no trackers, no other servers. Nothing it handles is sold, rented or shared.

Your controls

Before you press, turn off any kind on the card. “Not on this site” sends the card away from a site; the ring stays. Set a row on your page to Ask or Vaulted and no press ever fills it. “Disconnect this browser” on the extension's page, or remove it under Browsers on your account page, and it can do nothing more. Uninstall the extension, and what it kept here goes with it.

The Chrome Web Store's rules

Liir's use of what this extension handles follows the Chrome Web Store User Data Policy, including its Limited Use requirements: it is used only to fill your forms with your own Liir; it is never sold, never used for advertising, credit or lending; and no person reads it, except to keep the service secure or when the law requires it.

Questions

Write to hello@liir.net. A person reads it.