Legal
Subprocessors
Kintex AIS runs on Google services. This page lists every subprocessor we use, what it does, the data involved and where it is processed.
Last updated: 8 October 2026
| Service | Purpose | Data | Location |
|---|---|---|---|
Firebase Authentication Google | Sign-in and account identity | Name, email address, authentication identifiers | Global |
Cloud Firestore Google | App database and backups (point-in-time recovery 7 days; daily backups kept 7 days; weekly backups kept 14 weeks) | All Customer Data except photos | europe-west2 (London) |
Cloud Functions for Firebase and Cloud Scheduler Google | Server logic and scheduled jobs | Customer Data in transit | europe-west2 (London) |
Web server-side rendering (Firebase Hosting frameworks backend) Google | Renders web pages | Request data | europe-west1 (Belgium) |
Firebase Hosting Google | Static site and content delivery network | Request data, including IP address | Global edge |
Cloud Storage (photos) Google | Inspection photos | Photos, which may show people | europe-west2 (London) |
Cloud Storage (app downloads) Google | Pilot Android app files | No personal data stored | United States (us-east1) |
Firebase App Check with reCAPTCHA Enterprise (web) and Play Integrity (Android) Google | Abuse prevention | Device and browser signals | Global |
Firebase Cloud Messaging Google | Push notifications | Device push tokens | Global |
Google Workspace (Gmail) Google | Service emails (account verification, password reset, welcome) and delivering website enquiries | Name, email address, organisation name, enquiry form contents | Global |
Google ML Kit (on-device, via the QR scanner) Google | QR scanning on the phone | Camera images are processed on the device and not uploaded; Google may collect limited device and performance diagnostics | On-device |
- Firebase AuthenticationGoogle
- Purpose
- Sign-in and account identity
- Data
- Name, email address, authentication identifiers
- Location
- Global
- Cloud FirestoreGoogle
- Purpose
- App database and backups (point-in-time recovery 7 days; daily backups kept 7 days; weekly backups kept 14 weeks)
- Data
- All Customer Data except photos
- Location
- europe-west2 (London)
- Cloud Functions for Firebase and Cloud SchedulerGoogle
- Purpose
- Server logic and scheduled jobs
- Data
- Customer Data in transit
- Location
- europe-west2 (London)
- Web server-side rendering (Firebase Hosting frameworks backend)Google
- Purpose
- Renders web pages
- Data
- Request data
- Location
- europe-west1 (Belgium)
- Firebase HostingGoogle
- Purpose
- Static site and content delivery network
- Data
- Request data, including IP address
- Location
- Global edge
- Cloud Storage (photos)Google
- Purpose
- Inspection photos
- Data
- Photos, which may show people
- Location
- europe-west2 (London)
- Cloud Storage (app downloads)Google
- Purpose
- Pilot Android app files
- Data
- No personal data stored
- Location
- United States (us-east1)
- Firebase App Check with reCAPTCHA Enterprise (web) and Play Integrity (Android)Google
- Purpose
- Abuse prevention
- Data
- Device and browser signals
- Location
- Global
- Firebase Cloud MessagingGoogle
- Purpose
- Push notifications
- Data
- Device push tokens
- Location
- Global
- Google Workspace (Gmail)Google
- Purpose
- Service emails (account verification, password reset, welcome) and delivering website enquiries
- Data
- Name, email address, organisation name, enquiry form contents
- Location
- Global
- Google ML Kit (on-device, via the QR scanner)Google
- Purpose
- QR scanning on the phone
- Data
- Camera images are processed on the device and not uploaded; Google may collect limited device and performance diagnostics
- Location
- On-device
Changes to this list
We give 30 days’ notice by email to each Organisation’s system administrators before adding or replacing a subprocessor. Customers may object to the change, and if we cannot resolve the objection they may terminate.