Privacy Policy & Data Security
Effective Date: August 20, 2026 | Product: BPO Helper (Chrome Extension) | Publisher: DevHatchery
1. Introduction & Privacy Commitment
DevHatchery operates BPO Helper, a specialized browser productivity suite built for call center agents, BPO representatives, and CRM operators. DevHatchery is committed to data minimization, transparent security practices, and user privacy. BPO Helper operates locally inside the browser sandbox and adheres to strict Zero Data Selling and Zero PII Harvesting principles.
2. Chrome Web Store User Data Policy Compliance
In accordance with Google Chrome Web Store Developer Program Policies and Limited Use requirements:
- DevHatchery does NOT sell, transfer, rent, or monetize user data, customer records, lead names, phone numbers, or browsing histories.
- DevHatchery does NOT utilize or transfer user information for personalized advertisements, lead broker networks, credit determination, or cross-site tracking.
- Data accessed by the extension is strictly utilized to provide client-side productivity features (real-time phonetic pronunciation mapping, telephone number formatting, and local call note drafting).
3. Requested Permissions & Technical Justifications
BPO Helper requests only the minimal set of browser permissions required to perform its functions:
• storage: Allows the extension to store non-sensitive configuration parameters (such as whitelisted CRM domains, custom checklist items, temporary call note drafts, and the activated license key) locally in chrome.storage.local. This data never leaves the user workstation.
• activeTab & scripting: Required exclusively to scan visible lead name strings and telephone numbers on authorized dialer tabs to display the phonetic overlay. No page content is ever recorded, logged, or sent to remote servers.
• host_permissions (<all_urls>): Call centers utilize proprietary intranet IPs, internal subdomains, and custom Vicidial installations. The extension stays entirely inert and dormant until the agent explicitly clicks '+ Enable on this Site'.
4. Data Handling & Verification Architecture
A. Lead & Customer Information (Zero Transmission): While an agent is on a live call, name evaluation and string parsing occur in the local computer's volatile memory against an offline bundled phonetic database. No customer names, phone numbers, or customer notes are ever uploaded or transmitted to any external server.
B. License Verification & Device Binding: To validate active subscriptions and enforce workstation limits (Single PC vs Unlimited Team), the extension communicates over encrypted TLS/HTTPS with the official DevHatchery Licensing Server (https://license.devhatchery.com/verify-license.php). The payload consists solely of the user-provided License Key, Product Identifier, and an anonymous browser-generated UUID. No personal web browsing history or unassociated data is transmitted.
5. Payment Processing & Subscription Management
All order processing, billing operations, taxes, and subscription lifecycle management are securely handled by Paddle, serving as the official Merchant of Record (MoR). DevHatchery does not receive, store, or process payment card numbers or banking credentials. Customers may manage, update, or cancel their subscriptions at any time via the Paddle Customer Portal or through the DevHatchery License Hub at https://license.devhatchery.com/get-license.php.
6. Data Retention & User Erasure Rights
Agents and organizations maintain total ownership of their data. Clicking "Reset Values" in the extension interface or uninstalling the extension from Google Chrome immediately and permanently removes all stored local configurations, checklist notes, and active session tokens.
7. Compliance & Contact Inquiries
For technical support, privacy inquiries, or enterprise compliance requests, contact:
Publisher / Organization: DevHatchery
Official Platform: https://devhatchery.com
Product Portal: https://devhatchery.com/bpo-helper/
License & Billing Hub: https://license.devhatchery.com/get-license.php