Privacy Policy
QC Dashboard Annotator — Chrome Extension (v0.2) · Last updated: February 11, 2026

1. Overview
   QC Dashboard Annotator ("the Extension") is an internal, unlisted Chrome extension built by HyperVerge for use exclusively by its internal quality-control teams. It adds an annotation overlay to the internal QC Dashboard web application, allowing team members to review and annotate KYC/OCR API responses directly within the dashboard interface.
2. Data We Collect
   The Extension collects and stores the following data locally on the user's device only, using Chrome's local storage API:

Annotator profile: A self-entered display name and an auto-generated anonymous annotator ID (e.g., "A-X7K2F9").
Annotation data: Field-level correctness judgments, ground-truth corrections, and 422-response validity assessments tied to request IDs already visible on the QC Dashboard.
Session metrics: Timer state (elapsed seconds), sample counts, and annotation pace — used to track productivity within a session.
User preference: A custom download-directory subfolder name.
All of the above data is stored exclusively in chrome.storage.local on the user's own device. No data is transmitted to any external server or third-party service, except the Slack webhook described below.
3. Data Shared Externally
The Extension sends a pace-alert message to a private HyperVerge Slack channel via a Slack Incoming Webhook when an annotator's average pace exceeds the configured threshold (120 seconds per sample). This alert contains:

The annotator's self-entered name and auto-generated ID.
Average annotation pace, sample count, and elapsed time.
No KYC data, personal identification information, document images, or API response content is ever included in these alerts or transmitted externally by the Extension.

1. Data Retention and Deletion
   All annotation data is stored temporarily and is automatically deleted from local storage when the user exports annotations (via the "Export JSON" button). Users can also manually clear all stored data at any time using the "Clear All Annotations" button in the Extension popup. No data persists on any remote server.
2. Permissions and Their Purpose
   storage: Used to persist annotations, annotator profile, timer state, and user preferences locally on the device between sessions.
   activeTab: Used to inject the annotation toolbar and overlay UI into the currently active QC Dashboard tab when the user clicks the extension icon.
   downloads: Used to save exported annotation JSON files and to download document images from the QC Dashboard to the user's local machine for quality-control review.
3. Host Permissions
   The Extension's content script is restricted to a single host: https://qc-internal-prod.hyperverge.co/*. This is HyperVerge's internal QC Dashboard. The extension does not run on any other website. Additionally, the content script performs a guard check on page load (document.querySelector('ol > li.border')) and immediately exits if the expected dashboard structure is not found.
4. Remote Code
   The Extension does not use any remote code. All JavaScript and CSS is bundled within the extension package. There are no external <script> tags, no dynamically loaded modules, and no use of eval() or equivalent runtime code evaluation.
5. Third-Party Services
   The only external service contacted by the Extension is the Slack Incoming Webhook API (hooks.slack.com), used solely for internal pace-monitoring alerts as described in Section 3. No other third-party services, analytics, or tracking tools are used.
6. User Rights
   Users can view all stored data via the Extension popup at any time. Users can delete all stored data instantly using the "Clear All Annotations" button. Since this is an internal tool distributed only to HyperVerge employees, users may also contact the internal development team for any data-related requests.
7. Children's Privacy
   This Extension is an internal workplace tool and is not intended for use by children under 13. It is distributed exclusively to HyperVerge employees.
8. Changes to This Policy
   This privacy policy may be updated as the Extension evolves. Any changes will be reflected on this page with an updated date.