Privacy
Privacy Policy
What TweakLine keeps, what it sends, and how to remove it. Last updated 15 November 2026.
In brief
TweakLine works inside your own browser. Your edits stay on your computer unless you sign in, connect an agent, or copy them somewhere yourself.
Usage analytics are off by default. If you switch them on, TweakLine sends feature-usage events to PostHog. Those events never contain what is on the page: no addresses, selectors, edits, notes, text, tokens or screenshots.
Once you hand changes to a coding agent, the company behind that agent handles them under your account with them and their own privacy terms.
What TweakLine keeps in your browser
To do its job TweakLine looks at the page as rendered: its elements, their computed styles and their size and position. Chrome does not let it run on its own internal pages or on extension stores. Please do not point TweakLine at passwords, private form contents or anything you are not allowed to share.
- Extension storage: your settings, shortcuts, notes, MCP connection settings and related values. They stay until you delete them or remove TweakLine.
- Browser sync storage: presets, but only the ones you choose to save. Chrome syncs them with your browser profile.
- Session storage: the style, text and structure changes for each page during the current browser session. Where session storage is not available, extension storage is used instead.
When TweakLine talks to the network
- Fresh install: no connection is open. Copy as Prompt needs none.
- Local MCP, the default: TweakLine talks to a companion program on your own computer through an authenticated localhost connection. It does not use any server of ours.
- Cloud and Self-hosted MCP: not available in this release. This policy will be updated before either one launches.
- Sign-in and analytics: only when you choose them, as described below.
Screenshots and hand-off
Your browser takes the screenshots and they stay on your computer. The exception is an agent action you start that asks for one, which returns it to that agent.
Copy as Prompt puts a Markdown summary of your changes on your clipboard. Send to your AI agent makes your recorded changes readable by the agent you connected. Neither one gives TweakLine access to your code.
Your account and synced projects
An account is optional. If you create one, Supabase Auth stores your email address, display name, profile picture link and the identity you signed in with. Google is involved only if you pick Sign in with Google. TweakLine never handles a password.
While you are signed in, TweakLine copies your projects into your account: project names, each recorded change (selector, label, property, before and after values, notes and annotations) and the screenshots attached to them. Nothing is uploaded while you are signed out, and signing out stops further uploads.
Each stored row is locked to your own account with row-level security. Sharing with other people is not part of this release.
Cookies: a Supabase session cookie and the sidebar state. Your theme is kept in local storage. The dashboard sets no advertising or analytics cookies.
Usage analytics
Analytics stay off, and no analytics ID exists, until you turn them on in Settings. You can turn them off again at any time. When they are on, TweakLine creates a random ID in extension storage and sends events to PostHog (US region) along with your browser, TweakLine version, language, timezone and user agent. We use this to count active installs and see which features get used. Page content is never included. Builds without analytics configured send nothing.
Why TweakLine asks for each permission
- scripting: to load the editor into the page once you open TweakLine.
- storage: to keep the data listed above.
- sidePanel: to show TweakLine in Chrome's side panel.
- Access to all sites: so TweakLine works on whatever page you open it on, and can reconnect after a reload. It does nothing on a tab until you open it there.
- identity (optional): asked for only when you press Sign in, to show Google's sign-in window.
Removing your data
- Delete a page's change history from Review.
- Delete saved presets and notes inside TweakLine.
- Remove the extension to wipe everything it stored in your browser.
- Email us (see below) to delete your account along with the projects and screenshots stored for it. We aim to finish within 30 days.
Contact
Questions about privacy or your data: support@dive.samsad.dev, or the support page at /support.
Reporting a security issue
Please tell us about vulnerabilities privately instead of posting them publicly, and leave real credentials out of your report. Include what you found, the TweakLine version and how to reproduce it.