Your Data Stays Yours. Period.
Built for ISPs who handle CPNI and subscriber data every day. We take security as seriously as you do.
How Your Data Flows
Multi-tenant architecture with customer-isolated data stores. Encryption at every boundary.
Your VoIP System
RingCentral, 3CX, Five9 and more
QueSee Processing
US / EU Data Centers, Private Network
Encrypted Storage
AES-256 at Rest, Tenant Isolated
Diagram is illustrative. Full technical architecture documentation available upon request for Enterprise evaluations.
Security Controls. ISP-Specific Compliance.
Encryption
- AES-256 encryption at rest for all stored data
- TLS 1.2 or higher, or SSH, for all data transfers
- Cloud-native secrets management with encrypted credential storage
- Dedicated encryption controls (Enterprise, on request)
- Encryption in transit (TLS 1.2+ or SSH) and at rest (AES-256) across the entire pipeline
Access Controls
- Role-based access control (RBAC) with granular permissions
- Multi-factor authentication through Google or Microsoft sign-in
- SSO via Google and Microsoft - your team signs in with accounts they already have.
- Staff admin sessions time out after 60 minutes of inactivity
- Centralized audit logging of security events (30-day retention)
CPNI & Data Handling
- Supports your FCC CPNI (Customer Proprietary Network Information) compliance
- Strict tenant isolation - no data commingling between customers
- US and EU data residency available. Data of customers outside the US and EU may be processed in other countries unless they request US-only processing
- Data fully exportable in standard formats; custom retention periods by agreement
- After contract termination, a 30-day export window, then data deleted within 30 days
- Card numbers, security codes, social security and bank account numbers redacted automatically before anything is stored
Infrastructure
- Hosted on Google Cloud infrastructure with US and EU data center options
- 99% uptime target
- DDoS mitigation at the network edge, built into our cloud infrastructure
- Zone-redundant hosting with automatic database failover and continuous backups
- Private network for internal services, with a fixed outbound IP; the database accepts connections only from our own fixed addresses
Single Sign-On & Access Management
No separate credentials. Your team signs in with Google or Microsoft accounts they already have.
Supported Identity Providers
Essential Plan
SSO (Google/Microsoft) + MFA. Your team signs in with accounts they already have.
Pro Plan
PopularSSO (Google/Microsoft) + MFA. One-click login through accounts your team already uses. JIT (Just-In-Time) user provisioning supported.
Enterprise Plan
SSO via Google and Microsoft + MFA. Dedicated encryption controls on request.
Security Features by Plan
Every plan includes enterprise-grade encryption, MFA, and SSO. Higher tiers add dedicated controls and advanced audit logging, on request.
| Security Feature | Essential$70/agent/mo | ProPopular$120/agent/mo | Enterprisefrom $0.20/sub/mo |
|---|---|---|---|
| Security Controls | |||
| Encryption at rest (AES-256) and in transit (TLS) | |||
| MFA via Google or Microsoft Sign-in | |||
| Role-Based Access Control (RBAC) | |||
| Standard Audit Logging | |||
| SSO (Google/Microsoft) | |||
| Advanced Audit Logs (extended retention, export) - on request | - | ||
| Custom Retention Periods (by agreement) | - | ||
| Dedicated Encryption Controls - on request | - | - | |
| Dedicated Instance Option - on request | - | - | |
| Data Residency (US- and EU-based customers) | US | US | US & EU |
| Custom DPA | - | - | |
| Business Associate Agreement (BAA) - on request | - | - |
Subprocessor Disclosure
Full transparency on who handles your data and why. We notify customers 30 days before adding new subprocessors.
Zero data retention for call audio.
Call audio is analyzed in isolated infrastructure (in the US or EU for customers there) and deleted once processing ends. Our model provider's automatic caching and logging are turned off. Short-lived caches that hold your data are used only for your account and expire within an hour of last use; the only caches shared across customers hold QueSee's own processing instructions, never customer data. The insights we generate are kept in your QueSee environment for the term of your subscription.
Your Data Stays Where You Choose
US customers' data is stored and processed in the US, and EU residency is available. For customers outside the US and EU, data is stored in the US and may be processed in other countries; ask us and we limit processing to the US. E-commerce support-ticket review may be processed outside the US for any customer.
| Category | Purpose | Data Location |
|---|---|---|
| Cloud hosting and databases | Application hosting, compute, storage and databases | United States |
| Language-model processing | Analysis of calls and chats | United States; for customers outside the US and EU, may be other countries |
| E-commerce support-ticket review | Reviewing e-commerce support tickets and drafting replies (never used for calls) | United States, or other countries |
| Authentication | Sign-in for your team | United States |
| Telephony for the voice agent | Voice agent calls and text messages | United States |
| Email delivery | Service emails, including the alerts you configure | United States |
| Shipment tracking | Tracking lookups for e-commerce support-ticket review (tracking numbers only) | Not stated by provider |
| Processing-quality evaluation | Checking the quality of the Service's processing, for customers outside the United States only (no data retention) | United States |
| Engineering and support tooling | Tools our engineers use to support the Service; may process customer data for support and quality checks (no model training) | United States |
| Product analytics | Usage analytics and session replay (on-screen text masked) | United States |
| Payment processing | Billing | United States |
Customers see every provider by name in QueSee under Settings. Anyone else can request the named list at security@quesee.ai. Tools that run only on our marketing website are listed in our Privacy Policy.
Rolling Out QueSee to Your Team?
Here's what your agents need to know. Share this with your team before rollout.
No new recordings
QueSee analyzes call recordings you already have. It doesn't record anything new, and nothing needs installing on agent workstations. Optional live hints run in the agent's browser and listen only when the agent starts them.
Agents see their own data
Agents can see their own scores, coaching insights, and performance trends. It's a coaching tool, not a surveillance tool.
Controlled visibility
Individual agent data is visible to authorized managers only - not broadcast to the whole company. Permissions are role-based.
Coaching, not punishment
The purpose is coaching and continuous improvement, not surveillance or punitive action. We recommend transparent rollout communication.
“Introducing QueSee to Your Team” One-Pager
A ready-to-share document explaining what QueSee does, what agents can see, and how their data is handled.
Security & Compliance FAQ
Answers to the questions your IT and security teams will ask.
What security controls does QueSee have in place?
Where is my data stored?
Do humans access my call recordings?
What should our call greeting say?
How do you handle CPNI?
Can I submit a security questionnaire?
What's the uptime SLA?
Can I export my data if we leave?
Do you support SSO?
What subprocessors do you use?
Is a BAA or custom DPA available?
Can I run my own penetration test against QueSee?
Security-First. ISP-Built. Ready for Your Review.
14-day free trial. No credit card. Documented security controls. CPNI aware. Your security team will thank you.