Trust
Security & data handling
Placement terms and revenue figures are commercially sensitive by nature. Pecker is built on the assumption that the data proving a compliance breach shouldn't create a second compliance problem of its own.
Two ways to run it, one answer either way
Deploy Pecker on your own infrastructure and nothing about your placement contracts, revenue figures, or probe history ever reaches us. Prefer not to run it yourself? We host it for you on infrastructure dedicated to your account - not a shared multi-tenant database. Either way, the data your account managers rely on stays under your control.
Probes see only what a player sees
Every probe loads the public-facing page of an operator site the same way a visitor would. Pecker never authenticates into an operator system, never touches credentials that aren't yours, and never scrapes anything behind a login.
Evidence you can stand behind
Timestamps and screenshots are written once, at scan time, and retained as individual records rather than overwritten summaries. If a position record needs to hold up in a renegotiation, it hasn't been quietly edited since.
Minimal collection, by default
The public site itself collects only what's needed to answer an enquiry - see the Privacy Policy for the specifics. No analytics profiling, no third-party ad trackers, one cookie for your display preference.
Questions about a specific deployment or data residency requirement? Get in touch - a real question about your setup gets a real answer, not a compliance PDF.