ComplianceData SecurityPrivacy
Privacy by Design: Bidding on Calls with Pseudonymous IDs
How CallCompute uses pseudonymous RTB IDs for reporting and conversion feedback, so buyers see consumer phone numbers only for calls they buy.
At CallCompute, privacy is a design principle of our platform. We've designed our workflows around the idea that consumer information should only be accessed when necessary, and not exposed beyond what's operationally required. Reporting and optimization rely on pseudonymous (RTB ID) data, which reduces unnecessary exposure of consumer phone numbers. This does not replace your own HIPAA, TCPA or state privacy obligations.
Why We Ingest ANIs and What We Do With Them
CallCompute is buyer-side software. We don't sell, route or broker calls. We ingest consumer Automatic Number Identification (ANI) data when your call suppliers submit call opportunities to you. We use this information to:
-
Detect duplicate calls from the same or different suppliers.
-
Prepare for future enrichment models that could improve bidding precision.
-
Enhance the performance of our proprietary decision engine.
However, we do not expose the ANI to advertisers unless the call is purchased.
If an advertiser wins the bid and the call is transferred, the consumer's phone number is naturally revealed to the advertiser via standard caller ID. This is the only scenario in which an advertiser gains access to the ANI.
Reporting Through RTB IDs, Not Phone Numbers
Our system uses a unique internal identifier called an RTB ID to track every call attempt and its outcome. These identifiers are used for:
-
Tracking performance across publishers and campaigns.
-
Reporting ping attempts and call activity to clients.
-
Mapping conversion data returned from the advertiser.
When a call is not purchased, client-facing reporting reflects the ping attempt using the RTB ID, not the consumer's phone number. This means consumer phone numbers are not shared with the advertiser unless they purchased the call.
Conversion Reporting Without Sensitive Data
Advertisers send us conversion and revenue data after the fact using the RTB ID as a reference. This structure enables:
-
Tying outcomes to calls without exposing the underlying ANI in reporting.
-
A feedback loop keyed on RTB IDs rather than phone numbers.
-
Less consumer data held by the advertiser.
Limited Exception: Advertiser-Supplied Lookup Services
If an advertiser provides a service such as a DNC API or existing customer database, we may pass the full ANI to that specific tool in order to determine whether the advertiser wants to bid. This is the only exception to our RTB ID approach and is:
-
Controlled through contractual agreement.
-
Logged and monitored.
-
Scoped to that lookup process.
Less Consumer Data, Same Performance
Because advertisers only see RTB IDs for calls they did not buy, CallCompute reduces how much consumer data you hold. It is not a substitute for your own HIPAA, GDPR or CCPA obligations.
By assigning RTB IDs to all activity, we enable:
-
Client-facing reporting keyed on pseudonymous IDs rather than phone numbers.
-
Separation between consumer phone numbers and the performance data you work with.
-
Actionable insights with less consumer data in your systems.
Performance and privacy can work together
A feedback loop keyed on pseudonymous RTB IDs lets us learn from outcomes and adjust bidding while reducing how much consumer data is exposed.
Frequently asked questions
What is privacy by design in call data processing?
Privacy by design at CallCompute means privacy is a core principle of our platform architecture, not just a feature. We've designed our workflows around the idea that consumer information should only be accessed when necessary, and not exposed beyond what's operationally required. Reporting and optimization rely on pseudonymous (RTB ID) data, which reduces unnecessary exposure of consumer phone numbers. This does not replace your own HIPAA, TCPA or state privacy obligations.
Why does CallCompute ingest ANIs and how are they used?
CallCompute ingests consumer Automatic Number Identification (ANI) data when call suppliers submit call opportunities to a buyer. We use this information to detect duplicate calls from different suppliers, prepare for future enrichment models to improve bidding precision, and enhance our proprietary decision engine. However, we do not expose the ANI to advertisers unless the call is purchased.
What are RTB IDs and how do they protect privacy?
RTB IDs are unique internal identifiers used to track every call attempt and its outcome. They're used exclusively for tracking performance across publishers and campaigns, reporting ping attempts and call activity to clients, and mapping conversion data returned from advertisers. Using RTB IDs means consumer phone numbers are not shared with advertisers unless they have purchased the call.
How does CallCompute handle conversion reporting without sharing sensitive data?
Advertisers send conversion and revenue data back to CallCompute using only the RTB ID as a reference. This lets outcomes be tied to calls without exposing the underlying ANI in reporting, and means the advertiser holds less consumer data.
Are there any exceptions to CallCompute's RTB ID approach?
In limited cases, if an advertiser provides a service such as a DNC API or existing customer database, we may pass the full ANI to that specific tool to determine whether the advertiser wants to bid. This exception is controlled through contractual agreement, logged and monitored, and scoped to that lookup process.