Menu
OurSub-processors
A sub-processor is a company we engage to process data on our instructions, for our services and for the purposes we carry out on our own account. This is the list Section 5.1 of our Data Processing Addendum refers to.
We update this list when we engage a new sub-processor. Microsoft Azure (production hosting since September 2026), IPinfo and PostHog were added on 25 September 2026, after they had begun processing data. If you object to a new sub-processor, contact us at the address below within 15 days of the update that adds it.
Current sub-processors
| Sub-processor | Service | Processing location | Data processed |
|---|---|---|---|
| Microsoft Corporation (Microsoft Azure) | Cloud hosting, databases, data storage, compute infrastructure, operational logging | United States: Central US region (Iowa); database backups replicated to the East US 2 region (Virginia); operational logs and application telemetry in the South Central US region (Texas) | All categories described in Section 2.1 of the DPA; operational logs, which include screen IP addresses and screen identifiers |
| Amazon Web Services, Inc. | Data storage (Amazon S3); backups (AWS Backup) | United States (US-East-1, N. Virginia); a backup copy in US-West-2 (Oregon) | Files delivered to and received from data partners (DPA Sections 4.3 and 4.4); copies of measurement data, including the copies data valuation partners read; locked snapshots of our former Postgres database and server volumes, taken before the move to Microsoft Azure and kept until 1 April 2027 at the latest (DPA Section 6.2) |
| Google LLC (Google Cloud: Vertex AI and BigQuery) | AI/ML inference and model evaluation, embedding generation; data warehousing | Vertex AI: any Google Cloud region, as Vertex AI is called through its global endpoint; BigQuery: United States (US multi-region) | Camera frames selected for cloud analysis under Section 2.3.2, including images of venue interiors and the people in them; speech transcripts, for extraction of purchase intent, brand mentions and sentiment; request-level ad data with device identifiers, and hourly audience measurements for each screen, for model training (BigQuery); ad creative analysis |
| Stripe, Inc. | Payment processing and Connect payouts | United States | Account data, revenue data, payment information |
| IPinfo, Inc. | IP geolocation | United States | Public IP addresses our local geolocation file cannot place, including the IP addresses of screens, ad events and measurement SDK requests; the public IP address of the phone or browser that registers a screen without coordinates |
| WeatherAPI.com | Environmental data enrichment | United States / EU | The screen's coordinates (latitude and longitude), and the screen's IP address when the screen requests weather itself |
| API-Sports | Live sports scores and event data | Europe (France) | No personal data, sports event identifiers only |
| PostHog, Inc. | Product analytics | United States | Screen device fingerprints, screen identifiers and screen error events |
This list was last updated on 25 September 2026.
Not the same as a data partner
Sub-processors process data on our instructions, for our services and for the purposes we carry out on our own account (for example, Amazon S3 holds the files we deliver to and receive from data partners). They are different from data partners, described on the Data Partners page, which receive data for their own purposes under Section 4.3 of our Data Processing Addendum. Engaging a sub-processor never by itself authorizes any sale or sharing of your data. /legal/data-partners
Questions about this list
Write to us and we will respond. support@trillboards.com