Summary
Short version: inspecting pages, finding locators, recording bugs and journeys, checking security and generating code all happen inside your browser. The only data that reaches our servers is what is needed to sign you in and to check whether your trial or lifetime access is active. Your API calls, Swagger specs, timings, recorded journeys, screenshots, bug reports and security findings are never sent anywhere by TestMaadu. A few things are kept on your device only: the last Swagger link and server, the shape of API answers (field names and types, never values) so Live Page APIs can spot changes, and the Log a Bug scenarios you choose to save. We do not sell your data and we do not run advertising.
This policy covers the TestMaadu Smart Inspector extension for Google Chrome and Microsoft Edge (“TestMaadu”, “the extension”) and this website. The same extension and the same practices apply in both browsers. They are operated by Kaushik VM, an individual trading as TestMaadu, based in Bengaluru, India, who is the data controller. Questions go to kaushik.v2802@gmail.com.
Data that stays on your device
Find Element
When you use Find Element, the extension reads the page you chose to inspect: element attributes, text and structure. That data is used to generate code inside your browser. It is not sent to TestMaadu or to any third party. Generated code is copied only when you click Copy.
Log a Bug
When you press Record in Log a Bug, the extension watches only the tab you recorded (and tabs it opens) until you press End Recording or discard the bug. It notes the steps you take (clicks, typed values, choices, uploads by file name only, alert popups), the console messages and the API calls the page makes, and the last element you used. Password fields are never read; they are stored as ••••. End Recording takes a screenshot of the visible part of the tab. If you tick Also record a video of this tab, the extension also records a video of that tab while you record (it pauses while you are on another tab), with your voice only if you also tick Record my voice with the video and allow the microphone. Password, OTP, card and other secret fields are blurred in the video. Tab sound is not recorded. The report also includes environment details such as browser, screen size, the start and captured URL, page title, time zone, language and app version.
All of this is kept only in temporary browser memory (chrome.storage.session) so that closing the side panel loses nothing. It is cleared when you discard the bug, start a new one, or close the browser. The video is kept in the browser’s own database (IndexedDB) on your device, in small pieces so a crash keeps it, and is deleted when you discard the bug, start a new one, or after 2 hours. None of it is sent to TestMaadu or to any third party. It leaves your browser only when you click Copy bug, Copy screenshot, Download video or Download zip, and then only to your clipboard or your downloads folder. Tokens, cookies, passwords and secret URL values are masked in what you export unless you choose to export real values.
The test script (for example repro.spec.ts, or a Page objects project) is written from the recorded steps inside your browser, in the same temporary memory. Masked values appear in it as empty testData entries, not as the real values. It leaves your browser only when you click Copy code, Download or Download zip.
Play it back runs the recorded steps again in a new tab of your browser, only while the side panel is open. It reads that tab the same way the recording did (its failed API calls and console errors) to tell you whether the bug still happens. Nothing is sent to TestMaadu.
Saved scenarios are kept only when you press Save scenario. A scenario holds its name, the steps with their locators and your step edits, the failed API calls and console errors used for the bug check (without request or response bodies), and its history (when it was created and edited, and the last 50 runs). It does not keep the screenshot or the video. Up to 20 scenarios are kept in the browser’s own database (IndexedDB) on your device and are never uploaded. Delete removes one; uninstalling the extension removes them all.
API Tests: Live Page APIs, and Performance Quick check
When you use Live Page APIs in the API Tests tab, the API test in DevTools, or the Performance Quick check, the extension reads the same page data, and also the network requests and responses captured from that page: URLs, headers, request and response bodies, the response timings the browser records, and, only when you turn on “replay captured authentication”, the cookies that matter for that request.
That data is used to generate code inside your browser. It is not sent to TestMaadu or to any third party. Generated code is copied only when you click Copy.
We do not send your API data anywhere. Your API requests, responses, headers, timings and generated code are not saved to a file or a database, and none of it is sent to any server. The calls Live Page APIs records, and the call you select, are held only in the side panel’s memory or in temporary browser memory (chrome.storage.session) while you work. A recording stays there so it survives closing the side panel, and is cleared when you press Clear or close the browser.
Recording only starts when you press Record, and only for the site you are on (its sub-domains included). Tabs of another site are never recorded unless you say yes when the panel asks. Recording ends when you press End Recording, after 15 minutes, or when your login on the site expires. Export writes a HAR file or a Postman collection to your computer only when you click it; tokens, cookies, emails and passwords are masked by default. The file is not sent anywhere.
One thing is kept on your device so Live Page APIs can warn you when an API’s answer changes: the shape of each API’s answer, meaning its field names and their types (for example “price: number”), never the values. It is saved in chrome.storage.local for up to 300 APIs, the oldest dropped first, and it is never sent anywhere. Uninstalling the extension removes it.
Secret values such as authorization headers and cookies are written into generated code as environment-variable references by default. You choose whether to include literal values.
API Tests: Swagger
When you use Swagger in the API Tests tab, the extension reads a Swagger or OpenAPI spec: it fetches the spec itself from the link you give, or reads it from the Swagger page you have open when you press Load all APIs from this page. The spec is fetched the way your browser opens that link, so a site you are signed in to can recognise you. If you add the optional sign-in header for the spec, it is used only to read the spec, sent only to the site you chose, and never saved.
The spec, the request values you type and the responses are kept only in the side panel’s memory and are gone when you close the panel. Only the last spec link and the server you picked are saved, in chrome.storage.local on your device. None of it is sent to TestMaadu or to any third party, and generated code is built inside your browser.
A request goes to your API only when you click Execute, straight from your browser to the server you picked, and POST, PUT, PATCH and DELETE ask you to confirm first. Your browser cookies for that site are sent with it only if you tick “Send my browser cookies for this site”. Tokens, API keys and passwords are written into generated code as environment-variable references, never as values.
Performance: JMeter load test
When you press Record journey in the Performance tab, the extension notes what happens on the tab you recorded until you press Stop: the pages you open, the form fields you fill in (except passwords, which are never recorded), the API calls the pages make, and the values found in their responses that later steps use, such as tokens and ids. From that it writes a load test plan for JMeter or k6 inside your browser.
The recorded journey is kept only in temporary browser memory (chrome.storage.session). It is cleared after 2 hours or when you close the browser. It is not sent to TestMaadu or to any third party, and nothing is sent to a server. The plan leaves your browser only when you click Download zip, and then only to your downloads folder. In users.csv the password is written as CHANGE_ME. TestMaadu does not run the load test; you run the plan yourself in JMeter or k6.
Security
When you press Check this page in the Security tab, the extension runs passive security checks. It reads the page you are on, its cookies and its response headers. The headers come from DevTools when it is open; otherwise the extension requests the same page once more from your browser, as you would by reloading it. That extra request is skipped for logout, delete, confirm, reset and OAuth sign-in links, and for URLs that carry tokens or one-time codes. Nothing is sent to attack the site.
The findings, the evidence and any generated tests are built inside your browser and are not sent to TestMaadu or to any third party. Secret values found on the page are masked in the evidence, the report and the tests. They leave your browser only when you click Copy, Download report, Copy bug or Download zip, and then only to your clipboard or your downloads folder. Findings you choose to ignore on a site, and the reason you give, are kept in the extension’s storage in your browser.
AI Chatbot
When you press Record in the AI Chatbot tab, the extension records the chat on the tab you choose: the questions you type or click, the bot’s answers as they appear on the page, the chat API calls the page makes and their replies, and timings. Passwords are never recorded. The chat is turned into checks and test code inside the extension. Nothing is sent to us or to any AI provider. The generated tests talk to your chatbot only when you run them yourself.
If you check a page in the Security tab after recording a chat on the same site, the AI features area reads that recording to report problems such as a system prompt sent from the browser.
Data sent to our servers
We use a secure cloud database provider for sign-in and for the database that records whether your access is active.
| Data | When | Why |
|---|---|---|
| Google account identifier, email address and display name | When you choose Continue with Google | Create your account and sign you in |
| Email address and a one-time 6-digit code | When you choose to sign in with another email | Email you the code, check it and sign you in. The code expires after 10 minutes. |
| Trial start and end times, lifetime-access flag, created and updated times | Stored in your profile | Decide whether generated code is unlocked |
| Authentication tokens | Kept in your browser and sent to our secure cloud database with each verification request | Keep you signed in and verify access |
| Product settings such as trial length and price | Fetched when the extension opens | Show the right trial and price information |
We do not send inspected page content, selected elements, generated code, API requests, responses or timings, Swagger or OpenAPI specs, recorded journeys, load test plans, bug recordings, screenshots, security findings, or captured credentials to our database provider.
Google runs the sign-in screen under its own privacy policy. If you sign in with an email, the 6-digit code is sent to that address through our email delivery provider (Brevo), which processes only the address and the message. Our database provider processes data under its own terms as our infrastructure provider.
Data stored in your browser
| Item | Storage | Why |
|---|---|---|
| When your anonymous trial started | chrome.storage.local | Apply the anonymous trial window |
| Sign-in session (access and refresh tokens) | chrome.storage.local | Keep you signed in |
| Cached product settings | chrome.storage.local | Show trial and price information when offline |
| Cached access result (user id, access level, time verified) | chrome.storage.local | Keep a verified trial or lifetime user unlocked for up to 7 days if our server is briefly unreachable |
| The element selected on the current tab | chrome.storage.session | Keep your selection while the extension restarts in the background |
| The bug you are logging: steps, screenshot, console messages, API calls, element snapshot and your edits | chrome.storage.session (temporary memory only) | Keep the bug while you record and review it, even if the side panel closes. Cleared when you discard it, start a new bug or close the browser. Never written to local storage. |
| The video of the bug you are logging (and your voice, if you turned it on) | IndexedDB on your device | Keep the video while you record and review the bug. Deleted when you discard it, start a new bug or after 2 hours. Never sent to a server. |
| Whether you last ticked the video and voice boxes in Log a Bug | chrome.storage.local | Show the boxes the way you left them |
| The API call you select on the current tab | chrome.storage.session (temporary memory only) | Used by the API tests and the Performance Quick check while you work. Cleared when you refresh the page, close the tab or close the browser. Never written to local storage. |
| Live Page APIs: the recording (the API calls listed by screen) until you press Clear | chrome.storage.session (temporary memory only) | Keep the list when you close and reopen the side panel. Cleared when you press Clear or close the browser. Never sent to a server. |
| Live Page APIs: the shape of each API’s answer (field names and types, never values), up to 300 APIs | chrome.storage.local | Warn you when an API’s answer changes shape. Uninstalling the extension removes it. |
| Log a Bug saved scenarios (only when you press Save scenario): name, steps with locators, your edits, failed calls and console errors without bodies, history; up to 20 | IndexedDB on your device | Play the steps again later. Never uploaded. Delete removes one. |
| Swagger: the last spec link and the server you picked, and whether you used Live Page APIs or Swagger last | chrome.storage.local | Open Swagger where you left off. The spec, the responses, request values and any sign-in header are never stored. |
| The journey you record for a load test: pages, form fields except passwords, API calls and values found in responses | chrome.storage.session (temporary memory only) | Build the JMeter or k6 plan while you review it. Cleared after 2 hours or when you close the browser. Never written to local storage and never sent to a server. |
| The chat you record in AI Chatbot: questions, answers, timings, chat API calls and your checks | chrome.storage.session (temporary memory only) | Review the chat and build the tests. Cleared after 2 hours without use, when you discard it or when you close the browser. Never sent to a server. |
| AI Chatbot saved questions (only when you press Save questions): questions and answers per site, up to 100, with personal data masked | chrome.storage.local | Show which answers changed the next time you record that site. Stays on this device. |
| Your last Find Element framework, language and Playwright version (for example Playwright, TypeScript and Any), when you are signed in | chrome.storage.sync | Open Find Element with the choice you used last. Only these names are stored, never page data. |
| Your last Log a Bug framework and structure (for example Selenium · Java and Page objects), when you are signed in | chrome.storage.sync | Open Step 4 (Generate test code) with the choice you used last. Only the names are stored, never bug data. |
| Whether you have opened Log a Bug before | chrome.storage.local | Remember that you have opened the Log a Bug tab |
Signing out removes your session and cached access result. Uninstalling the extension removes everything it stored.
Why the extension asks for each permission
| Permission | Why |
|---|---|
| Access to all websites | So you can inspect any site you test. The extension reads a page only to analyse it for you. |
activeTab, tabs, scripting | Attach the element picker to the page you are inspecting and notice when it navigates. For Log a Bug, follow the tab you are recording across page loads and take the screenshot of the visible tab when you press End Recording. |
sidePanel, contextMenus | Show the TestMaadu interface and the right-click Inspect and Log a bug entries. |
storage | The browser storage listed above. |
tabCapture, offscreen | Record the video of the tab you are testing in Log a Bug, only after you tick the video box and press Record. The recorder runs in a hidden extension page that is open only while a video records. The microphone is used only if you tick the voice box and allow it. |
cookies | For the optional “replay captured authentication” feature, which reads the cookies of the inspected site so you can generate an authenticated test, and for Security checks, which look at the cookies of the page you check and their settings (such as Secure, HttpOnly and SameSite). Cookie values never leave your device. |
identity | Google sign-in. |
clipboardWrite | The Copy buttons, including Copy bug and Copy screenshot. |
This website
This website is a set of static pages. It has no accounts, no forms and no comments. It does not use advertising trackers, analytics cookies or third-party scripts, and its fonts are served from the site itself.
Like any web host, our hosting provider may keep standard server logs (for example IP address, browser type and the pages requested) for security and reliability. If you email or call us, we use your details only to reply and to keep a record of the conversation.
If we add analytics or any other tracking to the website in future, we will describe it here first.
Why we process data, and where
We process your sign-in details and access status to provide the service you asked for (your account, your trial or lifetime access). We keep one hashed record after account deletion, described below, for our legitimate interest in preventing abuse of the free trial and in restoring a lifetime purchase you made.
Our service providers (our cloud database provider and Google) may process data in countries other than your own. Where the law requires safeguards for such transfers, we rely on the safeguards those providers offer.
Retention and deletion
- Profile data is kept while your account exists.
- Delete your data: email us from the address you signed in with and we will delete your profile and sign-in record, usually within 30 days. If you have bought lifetime access, tell us in the same message: deleting the account ends that access, unless you ask us to keep the purchase record so that it can be restored if you sign up again.
- Anti-abuse record: so that deleting and re-creating an account cannot be used to get a repeated free trial, and so that a purchased lifetime licence can be restored, we keep one irreversible hash of your email address (SHA-256 of the lower-cased address) with the trial end date and the lifetime flag. We do not keep the email address itself, and the hash cannot be turned back into it. To have this record removed too, contact kaushik.v2802@gmail.com.
- Data kept only in your browser is under your control: sign out, clear the extension’s data or uninstall it.
Sharing and payments
We do not sell your data and we do not share it with advertisers. It is processed by our cloud database provider (hosting and sign-in) and Google (sign-in) as described above.
Lifetime access is paid for through Razorpay (razorpay.com), the payment gateway that processes your payment under its own terms and privacy policy. You enter your card, UPI or bank details on Razorpay’s page, never in the extension and never on this website, so we never receive your full card, UPI or bank details. We receive only the confirmation we need to unlock your account: the payment ID, the amount, the currency and the email address used. We link that payment to your TestMaadu account using your account ID, which we send to Razorpay as a note on the payment link when you start checkout. Nothing about the pages you inspect or the API calls you capture is sent to Razorpay.
Security
Connections to our cloud database use HTTPS. Sign-in uses OAuth with PKCE. Database access is protected by row-level security, so a signed-in user can read only their own profile and cannot change their own access level. No service-role keys or payment secrets are included in the extension.
Your rights
Depending on where you live (for example under the GDPR, the UK GDPR, the CCPA or India’s Digital Personal Data Protection Act), you may have the right to access, correct, delete or export your data, to withdraw consent and to complain to a regulator. Contact kaushik.v2802@gmail.com and we will deal with your request. We aim to reply within 30 days.
Children
TestMaadu is a professional developer tool. It is not directed at children under 13, or under the minimum age in your country.
Changes to this policy
We will update this policy when how the extension or the website handles data changes, for example if we add or change a payment provider. We will change the “Last updated” date at the top of the page and, for material changes, tell you in the extension.
Chrome Web Store and Microsoft Edge Add-ons statement
TestMaadu’s use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Page and network data accessed by the extension is used only to provide the inspection, code-generation (including tests from Swagger or OpenAPI specs), bug-report, load-test and security-check features described above. The version published on Microsoft Edge Add-ons is the same extension and follows the same rules: we use this data only for those features, and we do not sell it, use it for advertising or transfer it to anyone else.
Contact and grievances
Kaushik VM, trading as TestMaadu
Email: kaushik.v2802@gmail.com
Phone: +91 73492 62012
LinkedIn: linkedin.com/in/kaushik-vm
Address: Door 595, 68th Cross, Kumaraswamy Layout, Bengaluru 560078, Karnataka, India
Privacy questions and complaints can also go to our grievance contact on the Contact page.