Privacy: browser extension

1. What this covers

This page covers the Chrome extension limena — session capture, and only that. Everything limena does with a session once it has one is in the main privacy policy, and the parts that matter most here are section 6, retention, and section 7, encryption. The two pages are meant to be read together.

The extension exists for one reason. Most of what is worth testing for accessibility sits behind a login, and some products, particularly anything signing in through Google or Microsoft, refuse a browser that limena drives. So you sign in yourself, in your own browser, and hand over the session that sign-in produced. Your password is not part of that exchange and never reaches us.

2. What it does, in order

1. In limena, you click Sign in from my browser. The console opens the product in a new tab.
2. The console posts a request into its own page: a one-time code, the address to sign in to, and which programme asked. The extension's content script, which runs on limena's console and nowhere else, passes that to the extension and the toolbar badge shows limena is waiting.
3. You sign in, exactly as you always do. The extension is not involved and cannot see it.
4. You click the extension, then Send session to limena. Only at that click does it read anything.
5. What it read goes back to the limena tab that asked for it, and that tab continues on its own.

Nothing in that sequence happens without your click. There is no step where the extension acts on its own schedule, because it has none.

3. What it reads, and when

At the moment you click Send session to limena, from the one tab you clicked it on:

• That site's cookies. Including the httpOnly session cookies that page JavaScript cannot read. That is the whole reason this has to be an extension: a bookmarklet or a script in the page physically cannot reach the cookie that carries your session.
• That tab's localStorage. Some products keep their session token there instead of in a cookie.

Both are read for the active tab's address only. The extension holds no host permissions at all, so between your clicks it has access to no site, including that one. If a page blocks the localStorage read, it is skipped and the cookies alone are used.

Be aware of what that sweep includes. It takes every cookie and every localStorage entry for that site, not only the ones carrying the session, because the extension cannot tell which is which and guessing would break the products where the answer is unusual. If that site keeps something else in localStorage, it is in the capture too. This is why we recommend a dedicated test account with representative permissions rather than a real user's account, and it is the same recommendation the main policy makes about evidence.

4. What it stores

One note, of what limena is currently waiting for: the one-time code, the address to sign in to, the programme, and which tab asked. It lives in the browser's session storage, which is cleared when your browser closes, and the extension discards entries older than ten minutes.

The session itself is never stored by the extension. It is read at your click, passed to the limena tab, and gone from the extension the moment that hand-off succeeds.

5. Where it goes

This is the part most extension policies are vague about, so: the extension does not talk to limena's servers. It has no network code. What it reads goes to the limena tab already open in your browser, through the extension's own messaging and the content script on console.limena.app, and the console then sends it to limena the same way it sends anything else you type into it.

From there the main policy applies. The session is encrypted with AES-256-GCM in our API before it reaches the database, so the database holds ciphertext only; it is decrypted on our servers when a scan runs and never returned to a browser; and it is deleted 30 days after it was last updated by a daily job, whether or not it has expired. You can clear it sooner in the console, and logging out of the product invalidates it wherever it is.

6. The clipboard route

The popup also offers Copy session to clipboard, for pasting into limena's Access tab by hand. It reads the same two things. The difference is that the result is then in your clipboard, where it stays until something else overwrites it, and any application that can read your clipboard can read it. That is your operating system's behaviour and not something the extension can undo, which is why Send session to limena is the route we point people at.

7. What it never does

• Your password. Never read, never stored, never sent. You type it into the product, not into us.
• Other tabs and other sites. No host permissions, so there is no standing access to anything.
• Reading limena's own pages. The content script on the console moves two messages and reads no page content.
• Analytics. No telemetry, no counting, no error reporting. The extension phones nobody.
• Remote code. Every line it runs is in the package you installed. No hosted scripts, noeval, nothing fetched at runtime.
• Selling or sharing. Nothing the extension reads is sold, transferred, or used for advertising.

8. Why each permission exists

• activeTab. Scopes everything above to one tab at the moment you click. It is what makes the absence of host permissions possible.
• cookies. Reading the session cookie, including the httpOnly one, for that tab's address.
• scripting. Running one short function in that tab to read its localStorage. That function is in the package.
• storage. The ten-minute note in section 4.
• The content script on console.limena.app. The relay between limena's console and the extension.

That is the complete list, and it is deliberately the shortest one that works. Requesting broad host permissions would have made the code simpler and is exactly the thing you should refuse to install.

9. Limits we would rather name

• The capture takes everything in that site's cookies and localStorage, not only the session, as section 3 describes.
• A copied session sits in your clipboard until something overwrites it. Prefer the send route.
• A session grants exactly the access the account you signed in with had. Capture with a test account, not a real user's.
• Google holds its own record of the installation, under its own policy, which we neither control nor receive.

10. Removing it

Uninstalling the extension takes everything it holds with it, which is at most that ten-minute note. To remove a session limena already has, clear it in the console under a programme's Access tab, or log out of the product, which invalidates it everywhere. Or write to us and we will do it.

11. Contact

Privacy questions: privacy@limena.app. Security questions, including the full data flow behind authenticated scanning: security@limena.app, or see the security page.

Who is responsible for your data

limena Technologies Inc. is incorporated federally in Canada under the Canada Business Corporations Act, corporation number 1812063-3, with its registered office at the address above. The record is public and can be looked up in the Corporations Canada register. It operates the limena platform and is the party you contract with, and the party responsible for personal information handled through the service.