Privacy policy.

Effective Date: August 21, 2025
Contact: privacy@revopsctrl.com

This Privacy Policy explains how the Complainer Chrome extension and related services (“Service”) collect, use, and share information. It is written to comply with the Chrome Web Store Program Policies, including Limited Use, Privacy, Use of Permissions, and Handling Requirements, and will be posted both in our Chrome Web Store listing and on our website.

1) What Complainer does (summary)

Complainer injects a feedback button into approved workplace web tools (e.g., CRMs, BI dashboards, internal portals). When a user submits feedback, the internal team that owns the tool receives the message such as a screenshot, page details, and recent navigation events to help reproduce and resolve issues quickly.

We only collect and use data as needed to provide or improve this user-facing feature and as disclosed here. We do not sell data, use it for unrelated purposes, or use/transfer it for creditworthiness or lending. These commitments reflect Chrome Web Store Limited Use rules.

2) Data we collect

A. Account & Authentication

  • Authentication information for our Service (e.g., account email/ID and service password and/or access tokens you supply to log in to our backend). Tokens are stored in Chrome local storage on your device; we also use IndexedDB to maintain pre-submission navigation context. Authentication information is sensitive and handled per secure-handling guidance. Chrome for Developers

B. Browsing & Page Context (only to support the feature)

  • Navigation events surrounding a feedback submission (e.g., URLs, titles, timestamps, clickstream, active tab changes, tab open/close, and page state signals) captured on domains where Complainer is permitted to run, to provide context to the internal team.

  • Website content necessary for context, such as selected text or DOM snippets relevant to the issue, and a screenshot at the time of submission (when you trigger feedback).

  • Active tab info and tab lifecycle via the tabs permission to assemble user-journey context and to communicate authentication state to content scripts.

  • Host-permission page access (limited to domains you or your admin allow) to inject the feedback button and enable screenshot capture on submission.

Collecting website content, screenshots, and web browsing activity is “personal or sensitive user data” and is permitted only insofar as required by the user-facing feature described above. Chrome for Developers

C. Diagnostics & Device

  • Extension version, Chrome version, basic device info, error logs, and performance metrics, solely to maintain and improve the Service.

D. What we do not collect

  • We do not collect credit, bank, or government ID numbers.

  • We do not collect your passwords to third-party websites you visit in the browser (outside of credentials you voluntarily provide for our Service).

3) How we use data

We use data strictly to provide and improve Complainer’s single purpose:

  • Deliver your feedback and context to your organization’s internal tool owners.

  • Reproduce, diagnose, and resolve reported issues.

  • Maintain security, prevent fraud/abuse, and comply with law.

  • Improve reliability and UX (e.g., performance tuning, crash fixes).

Under Limited Use, we limit use to the disclosed purpose(s), prohibit unrelated uses (e.g., advertising), and apply restrictions to both raw and derived/aggregated data.

4) When we share data

We do not sell your personal information. We share only:

  • With your organization’s internal recipients: The teams responsible for the relevant tool receive your feedback plus associated context.

  • Service providers (“processors”): Hosting, storage, and operational vendors bound by contracts and used solely to provide/improve the Service.

  • Legal/security: To comply with law, protect rights, or investigate abuse.

  • Corporate transactions: Merger/acquisition/asset sale, with appropriate protections and (where required) prior consent.

Transfers for advertising or unrelated secondary uses are not allowed.

5) Disclosures & consent

  • We disclose the categories of data collected and purposes prominently within the product and listing.

  • If we ever handle personal/sensitive data not closely related to the described feature, we will first present a clear in-product disclosure and obtain affirmative, informed consent before collection.

6) Secure handling

  • In transit & at rest: We transmit personal/sensitive data using modern cryptography (e.g., HTTPS/WSS) and protect it at rest with industry-standard controls. Chrome for Developers

  • Least access: Internal access is role-based and logged; human review occurs only with your explicit consent or where necessary for security, to comply with law, or in properly aggregated/de-identified form for operations, consistent with Limited Use. Chrome for Developers

  • Client storage: We minimize what we store locally and clear local caches when no longer needed (note Chrome’s guidance to be careful with client-side storage). Chrome for Developers

7) Data retention & deletion

  • Pre-submission navigation context: Retained only as long as necessary to batch and transmit to our backend and to associate with a ticket, then deleted within 30 days if no submission occurs.

  • Submitted feedback & screenshots: Retained for the life of the ticket and then retained according to customer’s policy.

  • Authentication tokens: Persist until sign-out, token expiry, or extension uninstall; you can clear them anytime via Complainer settings or by removing the extension.

You (or your admin) may request deletion at any time via privacy@revopsctrl.com

8) Incognito & enterprise settings

  • Incognito: Extensions run in Incognito only if you enable them. If enabled, we apply the same restrictions and secure handling described here. We support Chrome’s incognito behaviors (split/spanning) per manifest settings. Chrome for Developers

  • Managed environments: Your organization may pre-configure allowed domains, retention, and access controls through enterprise policies.

9) Your choices & rights

  • Controls in the UI: You can open the Complainer panel to submit feedback. You may review the message before sending.

  • Pause or limit collection: You (or your admin) can remove domains from Complainer’s allowed list or uninstall the extension at any time.

  • Access/Deletion: Contact privacy@revopsctrl.com

10) Children

The Service is for workplace use and not directed to children. We do not knowingly collect personal information from children under the age required by applicable law (e.g., under 13 in the U.S.).

11) International transfers

We may process data in countries other than yours. Where required, we use appropriate safeguards (e.g., Standard Contractual Clauses) to protect personal information.

12) Compliance statements required by Chrome Web Store

  • Privacy policy posted & accurate: We post an accurate, up-to-date policy and link it in our Chrome Web Store listing. Chrome for Developers

  • Limited Use: We limit our use of user data to providing/improving the single-purpose, user-facing feature; we do not allow unrelated uses (including advertising), and we do not transfer data except as necessary for the Service, legal/security, or with explicit user consent. We do not use/transfer data for creditworthiness or lending. We restrict human reading as outlined in Section 7. Chrome for Developers

  • Use of permissions: We request the minimum permissions needed when feasible; Chrome for Developers

  • Secure handling: We transmit sensitive data with modern cryptography and keep authentication information secure. Chrome for Developers

13) Changes to this policy

We may update this policy. If changes materially affect how we handle personal data, we will provide prominent in-product notice and update the effective date before the changes take effect.

14) How to contact us

Questions or requests about this policy or your data: privacy@revopsctrl.com