We connect with read-only tokens. We implement only what you approve. Credentials never touch a model context window. And we revoke every token the moment an engagement closes.
Every platform connection is documented before it's made. Here's the precise scope of what each token allows — and what it categorically cannot do.
Every audit, analysis, Leak Map generation, and ongoing monitoring runs entirely on read-only tokens. This phase never requires write access and we will never ask for it during auditing.
If you choose to engage for recovery, each approved fix requires a scoped write token — limited to the specific campaign being modified, granted only for the duration of the change, then revoked. There is no standing write access, ever.
Every API key and token flows through AWS Secrets Manager and CredentialProxy. The AI agents that run our audit pipeline are architecturally separated from the credentials they use — by design, not by policy.
We collect the minimum data required to run the audit and verify savings. Nothing is retained beyond its purpose. Nothing is used to train models or shared with third parties.
Campaign spend, ROAS, CPM, CTR, frequency, and audience data pulled from connected platforms. Used exclusively for waste analysis and geo-holdout measurement. Never retained after engagement close.
Order revenue, conversion counts, and channel attribution data. Used to reconcile platform ROAS against actual orders and verify geo-holdout savings. Revenue figures are aggregated — individual customer orders are never accessed or stored.
Name, work email, company name, and website submitted on the audit request form. Used to deliver the Leak Map, communicate during the engagement, and route the recovery report. Not sold, not shared, not used for any other purpose.
The agents that power AdLeakIQ are built with security constraints at the architecture level — not enforced through policy alone. Each agent has a strictly bounded scope it cannot exceed.
Each agent is initialized with only the tools it needs for its specific role. The Prospector agent has access to public enrichment tools and nothing else. The Audit Engine has read-only API access and nothing else. The Implementation Agent has scoped write access only while an approved fix is in progress.
Data fetching is deterministic — scripted API calls, not agentic decisions. LLM calls are single-pass with structured output schemas. No agent enters a loop that could make repeated API calls, compound errors, or trigger unintended account changes through iteration.
Every action with real-world consequences — deploying a fix, upgrading a token scope, generating an invoice, declaring an external event — requires explicit human sign-off before the agent proceeds. Approval is logged with timestamp, action, and approver identity.
A dedicated Security Sentinel agent runs independently from the audit pipeline. It monitors all active token permissions, checks for scope drift, validates that write tokens are revoked post-implementation, and alerts immediately on any anomaly. It has no ability to take action — only to alert and suspend.
A mutual NDA is available on request before any account connection is made. We treat your account data, business performance, and audit findings as strictly confidential by default — the NDA formalizes that commitment.
If you identify a security concern with AdLeakIQ's systems, data handling, or agent architecture, we want to know. We commit to acknowledging every report within 24 hours and providing a substantive response within 72 hours.
We're happy to walk through the architecture in detail before you connect any accounts. Security reviews and technical calls are available on request — no obligation required.
Connect your accounts with minimum-scope read tokens. Receive your Leak Map in 48 hours. Revoke access anytime — no lock-in, no obligation.
Get My Free Leak MapRead-only access only · NDA on request · Tokens revoked at engagement close