Privacy Policy
Last updated: July 2026
1.0 Overview
Wemacx ("we", "us", or "the Company") operates an enterprise contact centre platform ("the Service"). This Privacy Policy explains how we collect, process, store, and protect information in connection with our platform. It applies to enterprise clients, their agents and supervisors, and end consumers who interact with contact centres powered by Wemacx.
2.0 Data Collection
We collect information necessary to provide the Service, including: (a) Identity Data — names, email addresses, phone numbers, and biometric data where applicable; (b) Interaction Data — call recordings, chat transcripts, email content, and session metadata; (c) Telemetry Data — platform usage metrics, performance logs, and system diagnostics; (d) Contract Data — billing information, service agreements, and support records. We do not sell personal data to third parties under any circumstances.
3.0 Interaction Fabric Privacy
All customer interaction data processed through the Wemacx platform is governed by our Data Processing Agreement (DPA) with the enterprise client. Wemacx acts as a Data Processor on behalf of the enterprise (the Data Controller). Interaction recordings, transcripts, and analytics remain the property of the enterprise client and are stored according to the retention policies configured by them.
4.0 Data Sovereignty
Wemacx is designed for sovereign deployment. Enterprise clients may deploy the platform entirely within their own infrastructure (On-Premise or Private Cloud), ensuring no interaction data is transmitted to Wemacx or any third-party service. For managed SaaS deployments, data is stored within the geographic region selected by the enterprise client, with encryption at rest (AES-256) and in transit (TLS 1.3).
5.0 GDPR & CCPA Compliance
For clients operating in the European Economic Area or California: (a) We support all data subject rights including access, rectification, erasure, and portability; (b) Our AI systems are designed for GDPR Article 22 compliance — no solely automated decisions are made without human oversight where required; (c) We maintain appropriate Standard Contractual Clauses for international data transfers; (d) A Data Protection Officer (DPO) is available at privacy@wemacx.com.
6.0 SOC2 & Security
Wemacx maintains SOC2 Type II certification, ISO 27001 compliance, and PCI DSS Level 1 certification for payment interaction handling. Security controls include: role-based access control, multi-factor authentication, penetration testing (quarterly), vulnerability management, and 24/7 security monitoring. Full security documentation is available under NDA for enterprise clients.
7.0 Contact Information
For privacy enquiries, data subject requests, or security concerns, contact: sales@wemacx.com · +91 80 3730 7830. Registered address and DPO contact available upon request.
Verbiq Chrome Extension
Privacy Policy for Verbiq, an AI-powered page-translation Chrome extension developed and maintained by the Wemacx team.
Overview
What Verbiq does and what this policy covers
Verbiq is a Chrome extension developed by Wemacx that translates the text content of web pages into a target language using AI translation providers. Translation is controlled by a license issued by your organisation — it only activates on domains your administrator has explicitly permitted.
This policy explains what data Verbiq accesses, how it is used, where it goes, and what rights you have. It applies to all users of the Verbiq Chrome Extension.
No data sold
Your data is never sold, rented, or shared with advertisers or data brokers.
Translation only
Page text is sent to AI providers solely to produce a translation. Nothing else.
Stored locally
All cached translations are stored on your device only, never on Wemacx servers.
Keys never leave memory
AI provider API keys are held only in the extension's volatile runtime memory.
Data we access
What information Verbiq accesses and why
Verbiq accesses two categories of data: the text content of web pages you visit (on permitted domains only), and extension configuration data stored locally on your device.
| Data | Purpose | Stored? | Sent to third party? |
|---|---|---|---|
| Page text content Visible text nodes on permitted web pages | Sent to AI translation provider to produce translated output | Device only | Yes — AI provider |
| Form field input Text typed into input and textarea fields | Translated back to the page's source language on blur (focus-out) | Device only | Yes — AI provider |
| Current page URL | Checked against the license's allowed domain list before translation begins. Sent to the licensing server only when a translation failure is logged. | Not stored | Yes — licensing server (on failure only) |
| License key & session token | Authenticates the extension with the licensing server. Stored locally to survive browser restarts. | Device only | Yes — licensing server |
| Translation cache SHA-256 hash → translated string | Avoids re-sending identical text to the AI provider. Expires after 7 days. | Device only | No |
| Machine ID Anonymous SHA-256 derived identifier | Enforces the one-seat-per-device license model. Cannot be used to identify you personally. | Device only | Yes — licensing server |
Third-party services
Who receives your data and under what conditions
Page text is sent to one or more AI translation providers. Your organisation's administrator configures which providers are used. Verbiq supports the following:
| Provider | Data sent | Privacy policy |
|---|---|---|
| OpenAI | Page text (as JSON array) | openai.com/policies/privacy-policy |
| Anthropic | Page text (as JSON array) | anthropic.com/privacy |
| Google (Gemini) | Page text (as JSON array) | policies.google.com/privacy |
| Groq | Page text (as JSON array) | groq.com/privacy-policy |
| Wemacx Licensing Server | License key, machine ID, session token, page URL (on failure only) | This policy |
Page text is transmitted to AI providers over HTTPS. It is used solely to produce a translation response and is governed by each provider's own terms of service and privacy policy. Wemacx does not control how AI providers handle data on their infrastructure — we recommend reviewing their policies linked above.
What we do not collect
Data Verbiq never accesses
Verbiq does not access, collect, store, or transmit any of the following:
Passwords
Input fields of type password are explicitly excluded from translation and are never read by the extension.
Browsing history
Verbiq only reads the current active page URL to check domain permissions. It has no access to your browsing history.
Personal identity
No name, email address, IP address, or other personally identifiable information is collected by Wemacx.
Financial data
No payment information or financial data is collected or processed by this extension.
Location
Verbiq does not access your geographic location. Domain matching uses the page URL only.
AI provider keys
API keys for AI providers are decrypted in the extension's volatile Service Worker memory only. They are never written to disk, browser storage, or sent to Wemacx servers.
Chrome permissions
Why each browser permission is required
Stores the session token, license key, allowed domain list, exclusion list, and translation cache on your device. No data is stored on Wemacx servers.
Reads the URL of the current tab to verify it matches the license's allowed domain list before initiating any translation.
Injects the extension's own bundled content script into permitted web pages to collect text nodes and apply translations. No external scripts are injected.
Schedules a heartbeat every 15 minutes to validate the active license session and prune expired translation cache entries. Required because Manifest V3 Service Workers do not support setInterval reliably.
Required to inject the content script into web pages. Translation only executes if the current page URL matches the license's configured allowed domain patterns. Pages outside those patterns are never translated.
Data retention
How long data is kept and how to delete it
| Data | Retention period | How to delete |
|---|---|---|
| Translation cache | 7 days from last access | Automatically pruned. Also cleared on sign-out or extension uninstall. |
| Session token | Until sign-out or license expiry | Click Sign Out in the extension popup. |
| License key | Until sign-out or uninstall | Click Sign Out or uninstall the extension. |
| Translation failure logs | 90 days (server-side) | Contact your organisation's administrator. SuperAdmin can purge logs manually. |
| AI provider keys | Session only (volatile memory) | Cleared automatically when the Service Worker restarts or the extension is reloaded. |
Security
How your data is protected
All communication between the extension and the licensing server, and between the extension and AI providers, is encrypted using HTTPS (TLS 1.2 or higher).
AI provider API keys are stored on the licensing server encrypted at rest using AES-256-GCM. When delivered to the extension at activation, they are re-encrypted with a one-time transit key. Inside the extension they are held only in the Service Worker's volatile runtime memory — they are never written to chrome.storage, localStorage, or any other persistent store.
The extension does not execute remote code. All JavaScript is bundled locally at build time. No code is fetched or evaluated at runtime.
Your rights
What you can request
Depending on your location, you may have rights under applicable data protection law (including the GDPR, CCPA, and India's DPDP Act) to access, correct, or delete personal data held about you.
Because Verbiq does not collect personally identifiable information, most requests can be fulfilled by signing out of the extension (which clears all locally stored data) and contacting your organisation's administrator for server-side log deletion.
To exercise any data rights or to raise a concern, contact us at sales@wemacx.com. We will respond within 30 days.
Children
Use by minors
Verbiq is an enterprise tool intended for use by adults in professional and organisational settings. It is not directed at children under the age of 13 (or the applicable age in your jurisdiction). We do not knowingly collect data from children.
Changes
Updates to this policy
We may update this policy from time to time. When we do, the effective date at the top of this page will be updated. Significant changes will be communicated through the Chrome Web Store listing or by email to the registered administrator contact for your organisation.
Continued use of Verbiq after changes are posted constitutes acceptance of the updated policy.