Data Security by Design: How CallCompute Protects Call Data

CallCompute is buyer-side software. We don't sell, route or broker calls. It was built from the ground up with one guiding principle: protect sensitive data without compromising performance. From how we ingest consumer information to how we track, store, and report conversions, our platform is designed around that principle.

This approach, often referred to as security and privacy by design, means buyers see consumer phone numbers only for calls they buy, which reduces how much sensitive data they hold. It does not replace your own HIPAA, TCPA or state privacy obligations.

Why We Ingest ANIs and How We Use Them

To support real-time bidding and intelligent decisioning, CallCompute can ingest the full ANI from your call suppliers. This allows us to:

• Detect duplicate calls across suppliers.

• Perform identity-based logic such as frequency capping or recency checks.

• Prepare for future enrichment to further improve the quality of call evaluations.

However, we do not share the ANI with the advertiser (our client) unless they win the bid and purchase the call. At that point, the call connects to their phone system, and the ANI is made available via standard caller ID, something they would receive naturally as part of the call itself.

Abstracted Tracking and Attribution via RTB IDs

All bid attempts, call evaluations, and outcomes are recorded and reported using an internal identifier known as the RTB ID. With this design:

• Advertisers only see performance data tied to RTB IDs, not consumer phone numbers.

• Conversion and revenue feedback is submitted by the advertiser referencing the RTB ID.

• ANIs are kept within our infrastructure and are not shown in client-facing reports unless the call was purchased.

In short, outcomes can be tied back to calls without exposing consumer phone numbers in reporting, which reduces unnecessary data exposure.

Handling Exceptions with Care

In rare, predefined scenarios, an advertiser may request the use of a service that requires the full ANI, such as a Do Not Call (DNC) suppression list or an existing customer database. When this occurs:

• The ANI is passed directly to the advertiser's service, not to the advertiser themselves.

• The transmission is encrypted and logged.

• The use of the ANI is limited in scope and agreed upon in advance.

These exceptions are the only instances where we intentionally pass an ANI prior to a call being purchased and even then, only for functional lookups under controlled terms.

Information Security Practices

CallCompute maintains information security practices, including:

• Defined controls for access, retention, encryption, and incident response.

• Secure infrastructure using cloud environments with strong authentication and monitoring.

• Clear policies governing the collection, retention, and secure deletion of data.

Our data retention practices set maximum storage periods for sensitive information, including ANIs, and require secure disposal using cryptographic erasure or other industry-standard sanitization methods.

Privacy-Forward, Performance-Driven

We've built a platform that:

• Is designed to limit exposure of sensitive consumer data.

• Reduces how much consumer data you hold.

• Enables actionable feedback loops using non-sensitive identifiers (RTB IDs).

• Gives you visibility into call performance without sharing consumer phone numbers for calls you didn't buy.

With CallCompute, privacy and performance go hand-in-hand

You get an automated way to buy calls, built with data protection in mind. Your own privacy and compliance obligations stay with you.