Trust centre
Trust is specificor it is nothing.
This is where a careful advertiser, publisher or procurement team can read how we work before signing anything. We say what we do, and we say plainly what we have not yet published.
Brands we run campaigns for
Standards and technology we build on
Measurement partners we work with
Built on open standards
- OpenRTB 2.6Real-time bidding protocol
- PrebidHeader bidding and server-side auctions
- app-ads.txtAuthorised sellers, declared by the app
- sellers.jsonWho is selling, declared by the seller
- SupplyChain objectEvery hop in the path, named
- TCFConsent strings in Europe
- Global Privacy PlatformPrivacy signals across regions
Standing commitments
Six rules that applyto every campaign.
These are defaults of the platform. They do not depend on the size of the account or on who is asking.
A holdout group by default
Every campaign keeps a randomised group of people who are never shown the ad, so results are reported as lift and not as credit claimed.
How measurement worksReports down to app level
You see every app where your ads ran, with spend and outcomes for each, and you can block any of them.
What you can seeA working opt-out
Anyone can ask to stop being retargeted, and the request is honoured across the platform.
Opt outPermission before precision
Where a platform or a law requires consent, we address only the people who gave it and fall back to context for everyone else.
Privacy and identityNo audiences on sensitive categories
Audiences are not built from health, finance hardship, sexuality, religion or similar categories, whatever the advertiser asks.
Read the policiesNo retargeting on children's apps
Apps directed at children are excluded from audiences and from delivery, in line with COPPA and the platform rules.
Compliance and standardsEvery trust page
Find the pagethat answers you.
Security
Principles, what we do not hold, and how to report a vulnerability.
OpenCompliance and standards
How the platform responds to each privacy regime and platform rule.
OpenData handling
What data we touch, what we never need, and what happens when an agreement ends.
OpenTransparency
What advertisers and publishers can see, and how we are paid.
OpenPrivacy and identity
How identifiers, consent and contextual fallbacks fit together.
OpenQuality
Invalid traffic, supply vetting and brand suitability.
OpenAd and supply policies
The rules for advertisers, publishers and creative.
OpenOpt-out
How a person stops being retargeted.
OpenData processing addendum
A summary of the terms for processing data for advertisers.
OpenPrivacy policy
How we handle personal data on this website and in the platform.
OpenBrand
How our name and marks may be used.
OpenStatus
What we publish andwhat we do not yet.
A trust page that lists only strengths is a brochure. This table shows where each item stands today.
| Item | Status | Where |
|---|---|---|
| Privacy policy | Published | Privacy policy |
| Opt-out | Published | Opt-out |
| Ad and supply policies | Published | Policies |
| Data processing summary | Published | Data processing addendum |
| Sub-processor list | On request | Data handling |
| Security overview | Published in principle | Security |
| Independent audit report | Not available. We will say so plainly until one exists | Security |
| Service level terms | In customer agreements | Ask us |
Procurement
Questions procurementteams ask.
Do you hold a security certification?
No. We hold no third-party security certification today. If that changes, we will publish it on the security page, and until then we describe our practice and nothing more.
Can we see an independent audit report?
There is none to show at present. We would rather say so than imply otherwise. Where a customer needs assurance, a security questionnaire or a conversation is the route.
Are you a processor or a controller?
For data an advertiser sends us about its own app users, we act as processor. The data processing addendum summary explains the terms, and some activity such as bid request handling is covered in the privacy policy.
Where is the list of sub-processors?
It is not published yet. The categories we use are described on the data handling page, and the list will appear there. Customers are told of changes under the agreement.
What happens to our data when we leave?
It is deleted or returned at the end of the agreement, as you choose, unless the law requires us to keep something. The retention periods are not yet published.
Can we see which apps our ads ran in?
Yes. Reporting runs down to the app bundle, with spend and outcomes for each, and any app can be blocked.
Can we speak to a current customer?
You can ask. A reference is arranged only with that customer's consent. See the customers page for how it works.
Where do we send a security questionnaire?
Through the contact page. Say what you need and who will review it, and we will route it to the right person.
Documents
Ask for whatyou need to see.
How to request documents. Use the contact page, name the document, and tell us whether you are an advertiser, a publisher or a partner. The full data processing addendum, security questionnaires and agreement terms are handled there. We will tell you if something you ask for does not exist yet.
Get started