Privacy-Safe by Design

When a client asks “is my data safe with you?”, the correct answer is not a policy statement. It is an architectural one: their sensitive data never touches Consumr.AI’s servers. This is a consequence of how the system is built.

How the data flow actually works

Clients typically have a customer list: phone numbers, email addresses, loyalty card data, CRM records. That list represents people who have bought from them, visited their stores, or interacted with their brand. It is first-party data in the traditional sense of the word.

Here is what Consumr.AI does not do: ingest that list directly.

Instead, the client uploads their customer list to the ad platform (Meta, for example). Meta already holds the identity graph that connects phone numbers and email addresses to behavioural profiles across Facebook, Instagram, and WhatsApp. Meta generates lookalike audiences and behavioural signals from that upload. Those signals, audience patterns, interest clusters, behavioural tendencies, are what Consumr.AI works with.

The raw CRM data goes to Meta. Consumr.AI sees only what Meta surfaces: the audience signals, not the underlying records.

No first-party data enters Consumr.AI’s systems.

Why Consumr.AI still calls it “first-party data”

In client-facing conversations, the platform refers to this as “first-party data”; that language is intentional. The data originated from the client’s first-party relationship with their customers. It is not third-party panel data or scraped information. Clients understand “first-party” and it accurately describes the provenance of the signals, even though Consumr.AI does not receive the raw records themselves.

This distinction matters for how you explain it. Do not say “we don’t use first-party data”; that contradicts the product’s own framing. Say instead: “We work with first-party-derived signals, but the raw data stays on your side and on the platform. It never flows into our system.”

Compliance posture

As stated in the training, the platform is described as “IDSS ISO every bit compliant.” The IDSS reference in the transcript is ambiguous; see the Open Questions page for the precise certification name. What is clear from the training is that compliance was not bolted on after the fact. It was a design requirement from the start.

The reason it works structurally: you cannot have a data breach involving data you never stored. The architecture removes an entire category of risk.

Answering the client question

When a prospect or client raises data safety as a concern, the response has two parts:

Structural: Their sensitive records, phone numbers, email addresses, CRM data, are uploaded directly to the ad platform (e.g., Meta), not to Consumr.AI. Consumr.AI receives the audience signals that the platform generates, not the underlying records. There is nothing to breach on Consumr.AI’s side because the sensitive data was never there.
Compliance: The platform is built to meet applicable data and privacy standards. For the specific certifications, refer to the Reference section.

Privacy safety here is not a policy pledge that depends on good intentions or vigilant staff. It is a consequence of the architecture. The data never arrived, so it cannot leave.