Skip to main content
Security & Compliance

Your Data Stays Yours. Period.

Built for ISPs who handle CPNI and subscriber data every day. We take security as seriously as you do.

Security ControlsAES-256CPNI AwareGDPR Terms AvailableSSO Included
Architecture

How Your Data Flows

Multi-tenant architecture with customer-isolated data stores. Encryption at every boundary.

Your VoIP System

RingCentral, 3CX, Five9 and more

TLS 1.2+ / SSH

QueSee Processing

US / EU Data Centers, Private Network

TLS 1.2+

Encrypted Storage

AES-256 at Rest, Tenant Isolated

Edge DDoS Mitigation
PII Detection + Handling
Dedicated Encryption Controls (Enterprise, on request)
Automatic Database Failover

Diagram is illustrative. Full technical architecture documentation available upon request for Enterprise evaluations.

Security Pillars

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
Identity & Access

Single Sign-On & Access Management

No separate credentials. Your team signs in with Google or Microsoft accounts they already have.

Supported Identity Providers

Google SSO
Available now
Microsoft SSO
Available now

Essential Plan

SSO (Google/Microsoft) + MFA. Your team signs in with accounts they already have.

Pro Plan

Popular

SSO (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.

Plan Comparison

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 FeatureEssential$70/agent/moProPopular$120/agent/moEnterprisefrom $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)USUSUS & EU
Custom DPA--
Business Associate Agreement (BAA) - on request--
Transparency

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.

CategoryPurposeData Location
Cloud hosting and databasesApplication hosting, compute, storage and databasesUnited States
Language-model processingAnalysis of calls and chatsUnited States; for customers outside the US and EU, may be other countries
E-commerce support-ticket reviewReviewing e-commerce support tickets and drafting replies (never used for calls)United States, or other countries
AuthenticationSign-in for your teamUnited States
Telephony for the voice agentVoice agent calls and text messagesUnited States
Email deliveryService emails, including the alerts you configureUnited States
Shipment trackingTracking lookups for e-commerce support-ticket review (tracking numbers only)Not stated by provider
Processing-quality evaluationChecking the quality of the Service's processing, for customers outside the United States only (no data retention)United States
Engineering and support toolingTools our engineers use to support the Service; may process customer data for support and quality checks (no model training)United States
Product analyticsUsage analytics and session replay (on-screen text masked)United States
Payment processingBillingUnited 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.

Team Rollout

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.

FAQ

Security & Compliance FAQ

Answers to the questions your IT and security teams will ask.

What security controls does QueSee have in place?
QueSee implements documented security controls covering security, availability, and confidentiality. You can request a copy of our security controls documentation using the form above - we'll verify your identity and send it to you.
Where is my data stored?
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.
Do humans access my call recordings?
Call recordings are processed by automated systems. Authorized QueSee staff may access a recording only to provide support, investigate a security incident, check the quality of processing, or meet a legal obligation, and every access is logged.
What should our call greeting say?
Callers should hear that a call may be analyzed by your service providers, not only that it is recorded. A line that covers it: "This call may be recorded and analyzed, including by our service providers, for quality and training purposes." Your phone system plays the greeting, so the wording is yours to set.
How do you handle CPNI?
QueSee is fully CPNI-aware. We follow FCC guidelines for handling Customer Proprietary Network Information. All subscriber data is tenant-isolated, access-controlled, and encrypted. We do not share, sell, or commingle customer data across tenants.
Can I submit a security questionnaire?
Yes. Send it to security@quesee.ai and we'll complete it with you. We can also provide pre-filled Shared Assessments SIG Lite and CSA CAIQ questionnaires on request, which usually saves your team a round trip.
What's the uptime SLA?
We target 99% monthly uptime. Formal uptime commitments are available on Enterprise agreements. We announce planned downtime in advance.
Can I export my data if we leave?
Yes. You can export your data in standard formats (JSON, CSV). Upon contract termination, you have a 30-day export window, after which your data is deleted within 30 days. Copies in routine backups expire on their own schedule. We provide written confirmation of deletion on request.
Do you support SSO?
Yes. SSO via Google and Microsoft is included on all plans - your team signs in with accounts they already have.
What subprocessors do you use?
The categories of providers that process customer data are listed in the Subprocessor Disclosure section above. Customers see every provider by name in QueSee under Settings, and anyone else can request the named list. Call audio is 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. We don't store full call transcripts, except a redacted transcript of each voice agent call, kept for 14 days so we can check how the agent handled it, and no customer data is used to train models. We retain the insights we generate and subscriber profile data in our database in your data region for the term of your subscription.
Is a BAA or custom DPA available?
A standard Data Processing Addendum (DPA) is available on request above. Custom DPAs and Business Associate Agreements (BAAs) are available on request on the Enterprise plan. Contact our security team to discuss your specific requirements.
Can I run my own penetration test against QueSee?
Yes, with coordination. Enterprise customers may conduct their own penetration testing against their QueSee instance. We require 14 days advance notice, a defined scope, and a signed testing agreement. Contact security@quesee.ai to arrange.

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.

Documented security controls
AES-256 Encryption
CPNI Aware
SSO Included
ROI by Week 5