Privacy & Trust
Privacy isn't a footnote.It's the architecture.
CrowdScout measures engagement on aggregates, keeps every tenant's data strictly separated, stores it in the EU, and is built so the AI can never reach a single recipient. Here's the plain-language version — the formal documents are linked at the bottom for your DPO.
Strict tenant isolation
Your data lives in your tenant and is never mixed with another publisher's. Every query is scoped to you, server-side — not by a filter we could forget.
EU data residency
Built for the European market. Your data is stored and processed in the EU — no transatlantic round-trips, no surprises for your DPO.
The AI never sees recipients
A hard, deny-by-default boundary keeps recipient identifiers, raw IPs and user-agents away from the AI. It reasons over aggregates only — by design, not by policy alone.
GDPR Art. 28 processor
You stay the controller; CrowdScout is your processor, under a Data Processing Agreement. We process only what you instruct, for as long as you instruct.
The AI egress boundary
Deny by default.Aggregates only.
The assistant is read-only and bound by a data-egress boundary: it can request aggregated metrics, segment rollups and campaign summaries — and nothing else. Recipient-level data simply isn't on the menu, so it can't leak through a clever prompt.
AI egress boundary
deny by defaultNever leaves your tenant
- Recipient identifiers
- Raw IPs & user-agents
- Your tenant's own ID
What the AI sees
- Aggregated metrics
- Segment rollups
- Campaign summaries
Questions for your DPO?
See it for yourself.
A 30-minute walkthrough — and straight answers to your compliance questions. We'll reply within one business day.