LoicBot: privacy policy
Chrome extension published by 5000.dev. Last updated: November 10, 2026.
What LoicBot is for
LoicBot is for clients of the 5000.dev agency. When 5000.dev needs an access key for your application (for example a Google sign-in or an API key), it sends you a request. With your approval, the LoicBot assistant does the steps for you in your browser, in plain view, and stores the key it obtains in your project's vault. That is all it does.
What the extension reads
- Only the work tab it opens itself for a request, placed in a tab group named "LoicBot". During a session, the assistant reads that page (its structure, its text and, when needed, a screenshot), clicks and types text.
- When the requested key is shown by the provider, the extension reads its exact value in that page to store it.
- Control of the tab lasts only for the session; Chrome shows its usual banner meanwhile. It ends when you stop the assistant, when it pauses, when the request is done or when you close the LoicBot panel.
- The assistant only opens the sites planned for the request, common sign-in pages (Google, Microsoft, Apple, GitHub) and a search engine (DuckDuckGo) to find the right console. For any other site it asks your permission in the panel.
What it sends, and to whom
The extension only talks to the 5000.dev space on Nexrai, https://5000dev.nexrai.ai. It sends:
- your LoicBot token, obtained by signing in on your usual client space page (the extension never sees your password);
- what you do in the panel: accept or decline a request, "Done", allow a site or not, your messages;
- what the assistant reads in the work tab (structure, text, page address and title, requested screenshots) and the result of each action;
- the value of the key obtained, which is stored in your project's encrypted "Access and keys" vault.
To decide each action, the 5000.dev server sends the work page content to the Claude AI model (Anthropic) through the OpenRouter service. If a key is shown in clear on the page, it can be part of that content. The exact reading of the key goes straight to the vault and is not sent back to the assistant.
What it does not do
- It refuses to type a password, a verification code (2FA) or a payment card: those steps stay yours, the assistant pauses and asks you.
- It does not read your other tabs, your history, your cookies or your bookmarks.
- It does nothing on a request you have not approved.
- No usage analytics, no ads, no tracking. No data is sold.
- No remote code: all its code is in the package published on the Chrome Web Store.
What is kept, and for how long
- In your browser: the LoicBot token and the space address (
chrome.storage.local), and the work tab number for the browser session. The token expires after 30 days; "Sign out" in the panel cancels it at once. - At 5000.dev: the request, its thread (messages and steps) and, for each access, the address and title of the last page visited, to be able to resume. They stay in your project while 5000.dev works for you. Page content and screenshots are not stored in your project: they pass through the server encrypted and are deleted within 5 minutes.
- The keys obtained stay in your project's encrypted vault until they are deleted.
- Processing by the AI model follows the terms of Anthropic and OpenRouter.
Permissions requested
debugger: drive the work tab (read the page, click, type), only during a session.identity: sign you in with your client space account.sidePanel: show LoicBot on the side of the browser.storage: keep the token and the work tab.tabGroups: put the work tab in the "LoicBot" group, so you always know which tab the assistant drives.https://*.nexrai.ai/*: talk to the 5000.dev space on Nexrai.
Contact
Any question about LoicBot or your data: loic@5000.dev.