Compliance Registry

Privacy Policy

Last Updated: June 2026

At Wennio, we recognize that data security and transparent collection practices are foundational to engineering global cloud networks. This policy outlines how your business information and end-user data are handled across our routing nodes.

1. Information We Collect

Wennio collects information through system logs and account configurations to maintain security and ensure reliable API routing. This includes:

  • Account Registration Data: Full names, billing details, verified business email addresses, and active API credentials.
  • Messaging Metadata Logs: Destination mobile phone numbers, sending timestamps, carrier routing tags, and message delivery statuses.
  • Usage & Technical Data: Originating IP addresses, API endpoint performance metrics, system error logs, and client software request variables.

2. How We Use Data & Core Payload Policy

We process your data purely to maintain, evaluate, and scale critical infrastructure. To ensure developer security:

The Payload Safeguard: The actual text content of your SMS communications, verification OTPs, and WhatsApp payloads is transmitted through transient memory buffers. It is immediately discarded or securely hashed after passing downstream to Tier-1 carriers. We do not inspect, monetize, or permanently store message body payloads on long-term data disks unless explicitly required by local law enforcement.

3. Data Retentions & Archiving

To support programmatic billing audits, fraud detection, and delivery monitoring, transactional tracking records and metadata (such as destination phone numbers and timestamps) are archived inside encrypted database environments for a maximum period of ninety (90) days. Following this lifecycle window, data patterns are completely anonymized or permanently deleted from our primary servers.

4. Data Sharing & Third-Party Carrier Nodes

Wennio will never sell, lease, or distribute your corporate or end-user identity profiles to advertising brokers. To route message data successfully to its destination, data paths must necessarily traverse global downstream telecommunication networks, regional gateways, and authorized mobile carrier nodes. These operators process tracking information solely to complete the transmission request under explicit carrier compliance laws.

5. Global Security Architectures & Encryption

All inbound and outbound API requests hitting Wennio endpoints are encrypted in transit using industry-standard Transport Layer Security (TLS 1.3). Static backend system resources, dashboard balances, and configuration values are secured at rest using AES-256 bit encryption algorithms. Access to our internal production infrastructure is guarded by zero-trust architecture parameters and strict multi-factor authentication controls.

6. Your Regulatory Rights & Compliance (GDPR / CCPA)

Depending on your geographic location or corporate operational region, you and your users retain specific legal control rights over collected variables. This includes the right to request access to archived metadata files, rectify inaccurate telemetry tracking fields, or demand the permanent erasure of account infrastructure details from our systems. You can initiate a deletion workflow via the developer console at any time.

Privacy Operations Desk

Have questions about how our transient data cache works, or need a custom Data Processing Agreement (DPA) signed for your enterprise enterprise software requirements?