Your testing data.
Clearly explained.

01. Identity and scope

This policy describes how QualityStudio — QA Companion, a Google Chrome extension developed by Rishabh Asthana, accesses and handles data. It covers the current version, 1.1.2, built on Manifest V3 and preparing for Chrome Web Store submission.

Its purpose is to help QA testers and developers inspect and document website behavior, record testing flows, collect evidence and prepare automation drafts.

This policy covers the extension. It does not describe iamrishabh.com’s own analytics, cookies, hosting logs or contact forms. The website’s operation is separate from the extension’s local data handling.

02. Data accessed and recorded

To provide its testing features, the extension accesses website content, element attributes, page URLs and diagnostic information.

• While flow recording is active: browser interactions, non-password field values, page URLs, timestamps and relevant control metadata. Ordinary fields can contain names, usernames, email addresses and other personal or sensitive information. File uploads capture filenames rather than usable local filesystem paths.
• Console observation: messages provided by the page, which can include sensitive information.
• Network observation: fetch/XHR metadata such as URLs, methods, status codes and durations. It does not capture full request or response bodies.
• Screenshots and checks: visible-tab or selected-element content, discovered resource URLs and information needed for resource and layout checks.

Page diagnostic observation can begin when extension content scripts attach, independently of starting flow recording. Clicking Record is not the start of all extension processing.

03. Local processing and developer collection

The extension processes testing data in your browser. Recorded flows, recording state, replay start URL, configuration and interface preferences are stored locally using chrome.storage.local. Diagnostic buffers and current results are held in browser memory. The recorder retains up to 500 events.

Local handling of website information is different from collection by the developer: the current extension has no developer-operated backend, telemetry, analytics SDK, advertising system or external AI upload. It does not automatically send recorded flows, screenshots or reports to Rishabh Asthana. It uses no AI model or external AI service.

When you request an export or download, screenshots, reports and test drafts are saved to your computer. Sharing those files is under your control.

04. Resource checks and network requests

Resource checks make requests to discovered resource URLs, including resources on different domains. Destination servers receive normal network-request information, such as the requester’s IP address. Those requests are part of the resource-check feature; the extension does communicate over the internet for this purpose.

Destination services handle requests under their own practices. This policy does not promise that third-party resource servers avoid logging requests.

05. Sensitive content and redaction limits

Password input values are redacted in the recorder. This does not guarantee that secrets are removed from URLs, console messages, page content, screenshots or other fields. An ordinary text field may contain a token, credential or other sensitive value.

Use test data where appropriate, test only with proper authorisation, and review recordings and exports before sharing. Avoid entering sensitive production information into testing flows unnecessarily.

06. Retention, clearing and downloads

• You can clear recorded flows in the extension.
• Information saved in chrome.storage.local remains local until cleared through the applicable controls or removed with the extension. Clearing a recorded flow is not a promise that every preference or stored setting is reset.
• Diagnostic buffers and current results are held in memory rather than a developer database; their lifetime follows the relevant browser or extension context.
• Removing the extension clears its extension-local storage.
• Previously downloaded screenshots, reports and test drafts remain on your computer until you delete them. Clearing flows or uninstalling does not remove these downloaded files or copies you have shared.

07. Permissions and user controls

You choose when to start or stop recording, which screenshots to capture and which exports to download. You can clear flows and manage extension site access, disable the extension or remove it through Chrome’s extension settings. Restricting access or permissions may limit the associated features.

All executable extension scripts are bundled locally. No remotely hosted executable code is used.

08. Purpose limits and Limited Use

QualityStudio’s use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Data access and use are limited to the testing features described in this policy.

The current implementation does not sell user data, use it for unrelated advertising or other purposes unrelated to the stated testing purpose, or use or transfer it to determine creditworthiness or for lending. It has no advertising system.

The extension does not automatically transfer recorded flows, screenshots or reports to the developer for human review. Review and sharing of exports are controlled by you. These statements describe the extension’s practices; they do not imply Chrome Web Store approval or a security certification.

09. Policy updates

This policy may be updated to reflect changes to QualityStudio or its data practices. Revisions will be posted on this page with an updated effective date. Review the policy when updating the extension.

10. Contact

For support or questions about this policy, contact developer Rishabh Asthana at hello@iamrishabh.com. Review any information or attachments before choosing to include them in a support email.

← Back to QualityStudio