testfit-privacy

TestFit – Privacy Policy

Effective date: November 3, 2026 Applies to: the TestFit – Playwright Recorder for Your Framework extension for Google Chrome (“TestFit”, “the extension”)

TestFit helps you create automated Playwright tests: it records what you do in a browser tab, re-runs those steps to check they work, and can turn them into test code that fits your own test repository.

In short: TestFit has no account, no server of its own, and no analytics or tracking. What it records stays in your browser. The only time anything leaves your computer is when you ask it to generate code with an AI provider you choose, using your own API key.

1. What the extension handles, and where it stays

Everything below is stored only in your Chrome profile on your computer, in the extension’s own storage. The developer of TestFit never receives any of it.

Data	What it is	Where it’s kept
Recorded sessions	The steps you record (as Playwright code), the pages you visit while recording, test titles, tickets and tags you enter	IndexedDB in your browser
Run results and failure details	Each step’s pass or fail, error messages, a screenshot of the page when a step fails, and console errors or failed requests the page reported (addresses are kept without their query strings)	IndexedDB in your browser
Traces	Playwright traces of recordings and re-runs: screenshots and snapshots of the pages, which can include what was on the page and what you typed	IndexedDB in your browser (you can turn traces off in Settings › Privacy)
Settings and your AI key	Your choices, and the API key of the AI provider you set up	Chrome extension storage on your computer (never synced to your Google account)
Secrets you choose to remember	Passwords or codes the tests need, only if you choose “Remember for” when asked	For a set time (minutes, today, until Chrome quits): in Chrome’s memory only, never on disk. “Always”: encrypted (AES-GCM) in IndexedDB with a key that cannot be exported from the browser
Your test repository	The folder you connect: the extension reads its files to find page objects, fixtures and helpers, and writes only the files you accept	Your own disk. The extension keeps a local index of names and signatures, and the folder permission Chrome gives it
Interface preferences	Theme, last device and feature chosen, and similar	Your browser’s local storage

Secrets and personal data while recording

• Passwords, one-time codes, PINs and card details you type are masked in the recorded steps and replaced with environment variable names (such as process.env.TEST_PASSWORD). Their values are not saved with the session.
• Values you type for a re-run are kept only while the page is open, unless you choose to remember them as described above.

2. When data leaves your computer

AI code generation (optional, only when you use it)

If you set up an AI provider and click Convert (or let the extension fix generated code), TestFit sends a request directly from your browser to the provider you chose: Anthropic, OpenAI, Google Gemini, or a local or private server you entered (for example Ollama or LM Studio on your own computer).

The request contains what is needed to write the test:

• the recorded steps, test title, ticket and tags;
• context from your connected repository: project facts, your guidelines file, relevant page objects, fixtures, helpers, reference tests, and any files you chose;
• when fixing code: the generated code and the problems found in it.

Before sending:

• email addresses and phone numbers are replaced with placeholders, as are any patterns you add (Settings › Privacy), and they’re put back only in the code you receive;
• secrets are never included: they are environment variable names, not values;
• you can preview the exact request and confirm it before the first send of each session (on by default).

The request goes to the provider under your API key and your agreement with them. Their handling of it is governed by their privacy policy, not this one. TestFit asks Chrome for permission to reach only the provider you choose, at the moment it’s needed.

Opening a trace (optional, only when you click it)

Open in Trace Viewer opens Playwright’s Trace Viewer page (trace.playwright.dev, provided by the Playwright project) in a new tab and hands it the trace file inside your browser. That page reads the trace locally and states that it does not upload it. You can instead Download the trace and open it however you like.

Nothing else

• No analytics, telemetry, crash reporting, advertising or tracking of any kind.
• No data is sold, shared with, or transferred to anyone, and none is used for any purpose other than the extension’s single purpose described above.
• Desktop notifications about runs are shown by your computer and are not sent anywhere.

Google may collect information about installs and usage of extensions through the Chrome Web Store, under Google’s own privacy policy.

3. Browser permissions and why they’re needed

• Debugger: to record and re-run steps in a tab through Chrome’s DevTools Protocol. It attaches only to the tab you choose to record or re-run, and to popups that tab opens, never your other tabs. Chrome shows its “started debugging this browser” banner while it is attached.
• Side panel: the extension’s interface.
• Storage: your settings, and secrets you choose to remember for a while.
• Context menus: right-click options while recording, such as “Assert this element”.
• Alarms: starting the scheduled runs you set up.
• Notifications (optional, asked when you turn them on): telling you whether a run passed.
• Access to websites (optional, asked when needed): only the AI provider, or the one local or private model server, that you choose.

4. Your control over your data

• See it: everything is shown in the extension: sessions, steps, results, traces, and the names (never values) of remembered secrets.
• Delete parts of it: delete steps, sessions, features or projects; forget remembered secrets (project menu › Secrets); turn traces off.
• Delete everything: Settings › Your data › Clear all data removes your AI key, settings, sessions, traces, schedules, remembered secrets, the repository connection and its index, and interface preferences. Files in your repository are never touched.
• Uninstall: removing the extension makes Chrome delete all of its stored data.

Data is kept until you delete it or remove the extension.

5. Security

Data stays within your Chrome profile, protected by your operating system account. Secrets remembered “Always” are encrypted, but anyone who can use your Chrome profile can still run tests with them; the extension says so when you choose that option. Requests to AI providers use HTTPS (unless you enter a local server address yourself).

6. Children

TestFit is a developer tool and is not directed at children under 13.

7. Changes to this policy

If this policy changes, the new version will be published at this address with a new effective date. Significant changes that affect how data is handled will also be noted in the extension’s release notes.

8. Contact

Questions or requests about privacy: [bobadesagarwd@gmail.com] or [Sagar Bobade].

TestFit is not affiliated with or endorsed by Microsoft or the Playwright project.