Sub-processors
These are the service providers ZeroBadge uses to run the platform and badges. Each one is bound by a written contract that limits it to providing its service to us and requires it to protect the data. None of them may use our customers' data for its own purposes. We post a change to this list at least 30 days before a new provider starts processing customer personal information. Customers may object as described in the Data Processing Addendum (Terms of Service, Part 4).
| Provider | What it does for us | Data involved | Location |
|---|---|---|---|
| Amazon Web Services | Badge connectivity (IoT), processing and backups | Badge data including location readings, device identifiers | United States |
| Supabase | Database, file storage and sign-in | All account, worker, time and location records | United States |
| Vercel | Application hosting | Data passing through the web application | United States |
| Hologram | Cellular connectivity for badges; cell-based location estimates | SIM identifiers, connection records, cell tower identities | United States |
| Google (Geolocation API) | Estimating badge location from nearby Wi-Fi networks | Wi-Fi network identifiers and signal strengths from a badge scan | United States |
| Mapbox | Maps and address lookup | Map views; addresses and coordinates looked up | United States |
| Stripe | Payments | Customer billing contacts and payment details | United States |
| Resend | Names and email addresses of message recipients, message content | United States | |
| Twilio | Text messages (when enabled) | Phone numbers, message content | United States |
| Sentry | Error monitoring | Technical error details | United States |
| Anthropic | ZeroBadge AI assistant, only where a customer enables it | Questions and the account data needed to answer them | United States |
To be told about changes, or to object, write to contact@zerobadgetechnologies.com.
