Data handling and security.
BidTrim runs inside your infrastructure and makes every decision there. This page lists what the model uses and what is sent to BidTrim for training.
| Data | Used by the model | Sent to BidTrim for training |
|---|---|---|
| Request context: environment, app or site, publisher ID, format, pod fields, floor | Yes | Yes |
| Device type, OS, country | Yes | Yes |
IP address (ip, ipv6) | No | Never |
Device and user IDs (ifa, buyeruid, eids) | Only whether one is present | Never the value |
Precise location (geo.lat, geo.lon) | No | Never |
| Consent and privacy strings | No | Never |
| Bid price | No | Never |
| Outcome of each forwarded request | Yes, for training | Bid, no-bid or timeout, without the bid price |
The agreement lists every field
The agreement lists, field by field, what is sent to BidTrim for training. Nothing outside that list is sent.
Privacy signals are untouched
BidTrim does not create, change or send bid requests. Your platform sends each request as it built it, so TCF and GPP strings, US privacy strings and the COPPA flag reach your demand partners exactly as you set them.
Data handling, version 1.1. Last updated 16 November 2026.
Separation
BidTrim's operator also buys and trades media, so the agreement states it plainly: data from a customer's platform is used only to provide BidTrim to that customer. It is not used for the operator's own buying or trading and is not disclosed to any other customer.
Agreement
Before any traffic is connected, a data processing agreement is signed. Request context and outcome records may be personal data, depending on their contents and on how they can be linked. For that processing, BidTrim's operator acts on the customer's behalf, under the customer's documented instructions and the data processing agreement.
Retention and location
How long training data is kept, the region where it is processed and every subprocessor involved are written into the agreement. The current subprocessor list is sent with the draft agreement, before signing.
Security
The platform calls the container over the customer's internal network, and a decision requires no external network call. The container image is signed and runs as a non-root user, and the customer's team can inspect it before deployment. BidTrim holds no SOC 2 or ISO 27001 certification today. Security questionnaires are answered before deployment, and security issues can be reported to security@bidtrim.com.
Demos for supply platforms.
A demo covers training data, processing locations and the data processing agreement. Each request is reviewed before the time is confirmed.
Book a demo