TLS 1.3 encrypted signalling, ephemeral call audio that is never recorded or stored, encryption at rest, and compliance-by-design - built directly into the core of Jingle Plug-In.
Encryption Performance Metrics
Encryption Stack
Call signalling is encrypted in transit with TLS 1.3, and data stored on our servers is encrypted at rest with AES-256. For users who have explicitly opted in, call audio is processed in real time for routing only - never recorded or stored - and calls hand off to Tier 1 carrier networks (PSTN) beyond our edge.
All call signalling traffic is encrypted with TLS 1.3, the current industry standard for transport security.
Every internal service authenticates with mutual TLS - no implicit trust between services inside the network.
Plug-in-to-server communication runs over HTTPS (TLS), with real-time call signalling handled over SIP.
Data stored on our servers is encrypted at rest with AES-256.
Call audio is processed ephemerally for real-time call routing only. It is never recorded and never stored.
For users who have explicitly opted in, calls terminate on the public telephone network (PSTN) via Tier 1 carrier interconnections. The encryption described here applies between your device and our network edge.

Transparency
We believe in radical transparency. Here is exactly what we process, why we process it, and how long we keep it.
| Data Point | Purpose | Retention Period |
|---|---|---|
| Call Audio | Real-time call routing (processed ephemerally) | Never stored |
| Call Duration | Billing and usage metering | 90 Days, then anonymised |
| Call Quality Metrics | Service quality monitoring | 30 Days |
| Network Type | Route optimization and call quality | Session only |
| Country (from verified number) | Country / region only, derived from the user's verified phone number, for geographic routing - no GPS or location permission | Session only |
| Plug-In Error Logs | Debugging plug-in integration issues | 7 Days (aggregated) |
| Anonymous Session Token | App functionality and fraud prevention | Expires within 7 days |
Zero Access Policy
Trust is built on boundaries. Our plug-in is architected to minimize data footprint - it is built so it cannot access this data, ensuring privacy by design.
Our servers automatically reject data payloads containing these identifiers.
Never recorded or stored
Never collected or uploaded - optional on-device caller-name display only
Zero message access
Never collected - only coarse, country-level region, derived from the verified number, for call routing
Completely isolated
No file system access
Infrastructure
Multiple layers of defense protect every component of our platform, from the edge network to the database layer.
Multi-region deployment across geographically isolated data centers. Automatic failover keeps the service available during transitions.
Edge-level traffic analysis and rate limiting. Volumetric, protocol, and application-layer attacks are mitigated automatically.
Every internal service authenticates via mTLS. No implicit trust between services. All inter-service communication is encrypted and verified at every hop.
All data at rest is encrypted with AES-256, in line with the data minimisation and retention commitments in our Privacy Policy.
Automated monitoring flags anomalies and abusive traffic patterns in real time, protecting partners and the integrity of the network.
The platform undergoes ongoing security review and vulnerability assessment, and findings are prioritised for remediation.
Compliance
Our platform is designed to meet the highest standards for data protection and privacy regulation worldwide.
European Union Privacy
Full support for right to erasure, data portability, and consent management APIs.
United Kingdom Standards
Compliant with post-Brexit data protection standards and ICO guidelines.
Google Data Safety
Pre-filled Data Safety form responses and prominent-disclosure templates for Google Play submission.
Join the partner network built on the international carrier interconnects with Jingle Plug-In.