Qiksy Legato — Privacy Policy

Last updated: 6 August 2026

Who we are

Qiksy Legato is a desktop web browser that repairs accessibility problems on a page before your screen reader reaches it. It is operated by Dmytro Liesniak, sole proprietor (ФОП), Ukraine. Contact: hello@qiksy.app — write in any language the browser speaks, and somebody may write on your behalf.

This policy is about Legato only. The Qiksy Bridge extension has its own Privacy Policy, and so does MultiLogin Tabs.

What never leaves your computer

• The repairs themselves. Turning fake headings into real ones, fixing focus order, freeing you from dialogs that trap you, and naming a button whenever the rules or the judge on your machine can work out what it is — all of it is decided and applied here, and works with no internet at all.One exception, and it is opt-in: when nothing on this machine can name a control, and you have agreed to it once, its markup — plus a small picture of it cut from the page, when the markup alone does not say enough — is sent with the site's name so a model can name it. That request is described in full below.
• The built-in judge. When the rules alone cannot name something, Legato can ask a small language model that runs on your computer. It does not connect anywhere, and its answers do not come back to us.
• Your history, bookmarks and open tabs, including everything brought across from Chrome on the first run. They stay in files on your machine.
• What you do in the browser. There is no telemetry, no usage counter, no analytics and no crash reporting. We cannot tell whether you opened Legato today, and we have deliberately built nothing that could tell us.
• Your settings, sounds, callsign and saved repairs — local files in the browser’s own folder.

The AI features, and where their data actually goes

Three things in Legato create text that a page simply does not have: describing an image out loud, retelling a page in plain words, and summarising a form before you start filling it. These cannot be done on the page alone. When you ask for one of them, the browser sends that one request to our server, and our server asks an AI provider — Google (Gemini) — using an account of ours, not one of yours. The answer comes back and is read out to you.

This changed on 3 August 2026. Until then these features ran through Claude Code installed on your own computer, and nothing passed through us. It is now the other way round, and we would rather say so plainly than leave a comfortable sentence standing: you no longer need any AI tool of your own, and the cost is that the content of that one request reaches us.

What travels with a request, and nothing else does:

• The thing you asked about — that one image, or the text of that one page, or the fields of that one form (their labels and types, never what you have typed into them).
• Which feature it is, and the language you want the answer in.
• For naming unnamed controls only: the site's name — example.com, never the rest of the address. A model that does not know what site it is looking at names these controls wrongly far more often, which is why this one piece travels.
• A one-way code for this computer, and your licence key if you have one — that is how the monthly allowance is counted, and how a free month cannot be restarted by reinstalling.

The address of the page is never sent — for naming unnamed controls the site's name travels and nothing after it, so your searches, your filters and your order numbers stay here. Neither your history, your bookmarks, your passwords, anything you typed into a field, nor any page you did not ask about is ever sent. Describing a picture, briefing a form and saying a page in plain words happen only when you press the key or choose the menu item, one page or one image at a time. Naming unnamed controls is the one that runs by itself — during the automatic pass after a page loads, several controls in one request — and it does that only after you have agreed to it once, only on pages you are not signed into, and never on a page where the rules and the local judge already did the job.

What we keep, and what we cannot keep

We keep the answer, and we keep it under a fingerprint of the thing it describes. Before asking the provider, our server takes a one-way hash of the image (or of the page text) and looks it up. If somebody has asked about that same image before, you get the stored answer straight away — it costs you nothing from your monthly allowance and costs us no request at all. That is why the same picture is described once, for everybody, and why this gets cheaper for everyone as more people use it.

That store holds four things: the hash, the answer, when it was first stored, and how many times it has been reused since. It holds nothing about who asked — no licence key, no code for your machine, no address of a page, no record that it was you. We cannot look up what you personally asked about, because the link between a person and a request is not written down anywhere. Separately, and tied to your licence key, we count how many requests of each kind you have made this month and what they cost us — numbers only, never content.

Two honest consequences. A page you asked to have retold is stored as its retelling, so do not use “explain in plain words” on a page you would not want written down — a bank statement, a medical letter — and use the free repairs and your screen reader there instead. And the request itself is handled by Google under the terms of its paid API, which does not use it to train models. If you want a stored answer removed, write to hello@qiksy.app and tell us what the page or the image was — we will find it by its hash and delete it.

The other thing sent to us: turning a licence key on

The browser is free, and everything it does without AI stays free — no account, no key. If you buy Care and enter its key, the browser has to ask our licence server to bind that key to this computer.

We also hold what any shop holds about a sale: the email address you typed at checkout, the amount and the date. The browser does not send that — we already have it from the purchase, and it is where your key and your renewal reminder are sent.

Like any request over the internet, this one carries your IP address. It is used only to rate-limit abuse of the licence endpoints, it lives at most an hour in a counter that holds no key and no device, and it is never stored next to your licence.

How often. When you enter the key, and after that only when the term is close to its end, so a renewal is picked up without you retyping anything — in practice about twice a year. Between those moments Legato verifies your licence offline, from a signature it already holds. An outage on our side can never lock you out of your own browser.

What is never sent with it: no address, no page, no history, no search, no screenshot, no document, no list of what you repaired and no “last seen online”. The request contains the three items in the table and nothing more.

How long we keep it, and how you delete it

The device entry — the code, the name, the day it was first activated and the day it was last used — is kept for as long as the licence exists, because that is what a device limit is: a memory of which places are taken.

You can delete an entry yourself, at any time, without writing to anybody. In Legato, open Settings → License, find the device under Where this key works and choose Free this place. The entry is deleted from our server immediately and the place becomes available for another computer. Freeing the place for the computer you are sitting at also removes the licence from that computer. If you would rather we did it, write to hello@qiksy.app from the address you bought with — we will delete one device, all of them, or the whole licence record, whichever you ask for.

Stored AI answers have no expiry date today, and we would rather write that than round it up: a description that is kept is a description nobody has to pay for twice, and the store holds no link to the person who first asked for it. The monthly counters are kept per month and per licence key, so deleting your licence record deletes them with it. If you want a particular answer gone, tell us which page or image it was and we will delete it by its hash.

Other places the browser connects to — because it is a browser

Legato is a real web browser, so most of its traffic is you visiting websites. Those connections go to the sites you chose, not to us, and we see none of them. Three are worth naming because the browser starts them:

• Search suggestions. While they are on, what you type in the address bar goes to your chosen search engine before you press Enter — the same as in Chrome or Safari. Turn them off in Settings and only your own history suggests; that works with no network at all.
• Search results. The results page fetches results from the search provider you configured. Your query goes to that provider under their policy, and never to us.
• Installing an extension downloads it from the Chrome Web Store, and signing in to a Google account talks to Google — both exactly as they would in Chrome, and both only when you ask.

What we never do

• We never sell, rent or share anything about you. There is nothing to sell — see the table above.
• No advertising, no profiling, no tracking of any kind, in this or any Qiksy product.
• We do not use anything from your browser to train a model. The judge that runs on your machine is finished before you install it and does not learn from your pages.
• We never disable a browser remotely. There is no kill switch, and the licence check cannot lock the free part of the browser even if our server disappears. For some people this browser is the only door to the internet, and that has to hold regardless of what happens to us.

Your rights

You can ask what we hold about you, ask for a copy, ask for a correction, or ask us to delete all of it — write to hello@qiksy.app. In practice what we hold is your purchase (email, amount, date) and your device entries, and the device entries you can delete yourself in seconds. Legato is not intended for children and we do not knowingly collect anything about them.

Changes

If this policy changes materially, the date at the top changes with it and the text says what changed. Continued use after an update constitutes acceptance.