Add LTC
One install. Then it comes to you.
LTC works the moment it is installed. There is no account to create and nothing to configure.
LTC is in Early Access and the browser stores review every extension before it is listed. Rather than show five identical buttons, here is where each one actually is today. While the listings are in review, check an agreement in the browser you already have.
Chrome
Also Edge, Brave, Arc and other Chromium browsers.
Developer install
The packaged extension is built, tested and downloadable now. Chrome only installs extensions from its own store, so until the listing is published this is a developer install: Developer mode, Load unpacked. It works today.
Firefox
Desktop.
Being prepared
The Firefox package is built. Firefox will only install an add-on that Mozilla has signed, and signing needs an AMO account we have not connected yet.
Edge
Chromium Edge, via the same package as Chrome.
Developer install
Edge takes the same package and loads it unpacked today. The Partner Center listing is prepared and not yet submitted.
Safari
macOS and iOS, via the LTC app.
Being prepared
Safari requires the extension to ship inside a signed, notarised macOS app. That needs an Apple Developer account, and there is not one connected to this build.
Android
Internal testing only.
Being prepared
Android is secondary to the browser. There is no Play Console account connected to this build, so nothing has been published to any track.
What LTC asks for, and why
LTC asks to run on all websites. That is a broad permission and it deserves an explanation rather than a shrug: a consent request can appear on any site, so LTC has to be able to see one wherever it happens.
What it does with that access is narrow. It reads a page only to classify a consent moment. Remote analysis is off by default, and when you turn it on, what leaves your device is the site’s domain, what kind of consent is being requested, and the shapes of the buttons. Not the page. Not the address. Not anything you type.
The full list of what is sent is on the privacy page, and it is the actual request schema rather than a summary of it.