PRIVACY POLICY
Privacy
This page covers Tallylamp Link, the browser extension, and this website. The short version: the extension talks only to the Tallylamp server you connect it to, which is software you run yourself. It sends nothing to us.
What we receive from the extension
Nothing. Tallylamp Link has no analytics or crash reporting, and it shows no ads. We run no server that it contacts, and it loads no code from the internet. Everything in it ships in the extension package, and the source is public on GitHub.
The one exception is a link. When another extension blocks sharing, the panel offers "Why, and other fixes", which opens a guide on tallylamp.dev in a new tab. That visit is an ordinary page view on this website, covered further down.
"We" on this page means Rafael Aslanian, who makes Tallylamp.
What the extension keeps in your browser
It keeps the address of your Tallylamp server and the link token that server issued when you approved this browser. Both stay in the extension's local storage until you press Disconnect or remove the extension.
While you are connecting, it keeps the pairing code for up to 10 minutes.
It keeps a list of the tabs you have shared, with their site limits, so sharing survives Chrome restarting the extension's background worker. That list is in session storage, which Chrome clears when the browser closes.
What it sends to your server
When you connect, it sends a name for this browser made from the browser's brand and your operating system, such as "Chrome on macOS". Each time it reconnects it also sends the link token, the browser's version number and its user-agent string.
For a tab you share, and only while it is shared, it sends:
- the tab's address and title
- what the agent reads or does in that tab through Chrome's DevTools Protocol. That can include the page's content, screenshots, network requests and responses, console messages, and the cookies and storage that belong to the page's own site
- the position and size of the window that holds the tab
It sends nothing from tabs you have not shared. The side panel does read the address, title and icon of the tab in front of you, so it can show you what you are about to share. That stays in your browser.
What it refuses to send
Some DevTools Protocol commands reach past a single tab. The extension refuses those before Chrome runs them, so the agent can't read every cookie in the browser, list or open your other tabs, upload files from your computer or read another site's storage. It also refuses to share or open your Tallylamp dashboard. The full list is in the linked browsers documentation.
Your server, and the agents you approve
Your Tallylamp server receives what the extension sends and passes it to the agents you approved in its dashboard. You run that server, or whoever gave you its address does. They decide what it records and for how long. If you use someone else's server, ask them.
The agents you approve receive what they read in a shared tab. If an agent runs on an AI service, that service's own privacy policy covers what it does with the data.
How the data is used
The extension uses this data for one thing: letting the agents you approve use the tabs you share. We don't sell it, and it isn't used for advertising or to judge anyone's creditworthiness. The extension's handling of data follows the Chrome Web Store User Data Policy, including its Limited Use requirements.
How to stop it
- Press Stop sharing in the side panel, or Cancel on Chrome's debugging bar. The tab is handed back at once.
- Close the tab.
- Press Disconnect in the side panel. The extension deletes its token and stops talking to your server.
- In your dashboard, press Revoke link. The token stops working everywhere.
- Remove the extension. Chrome deletes everything it stored.
If your server is unreachable for a minute, the extension hands back every shared tab on its own.
This website
tallylamp.dev counts visits with Umami, which we host ourselves. It sets no cookies and does not follow you to other sites. For each visit it records the page, the site that sent you, your browser, operating system, device type, screen size, language and approximate location. Umami works out the location (country, region and city) from your IP address, then discards the address. It also records a few events, such as which links were clicked, how far a guide was read and how fast the page loaded. If your browser sends Do Not Track, nothing is recorded.
The guide about Dray shows a video hosted on YouTube. It uses YouTube's privacy-enhanced mode, and nothing loads from YouTube until you press play. Once you do, YouTube receives your IP address and the usual details of the request, and Google's privacy policy applies.
Changes and questions
If this policy changes, this page will show the new date at the top. Ask questions or report a problem on GitHub.