Sub-processors
Last updated June 2026
Draft. This document is being finalized with our policy
tooling and is pending legal review. Questions? Email support@briefqr.com.
To deliver BriefQR we rely on the vetted providers below, each acting as a sub-processor under our agreement with you. A Data Processing Agreement covering this list is available to business customers on request at support@briefqr.com. We will update this page before adding or replacing a sub-processor.
| Sub-processor | Purpose | Data processed |
|---|---|---|
| Supabase | Database, authentication, file storage, edge functions | Account, operators, sessions, scans, location, evidence photos |
| Netlify | Static hosting & CDN for the marketing site and app | Standard web request/log data |
| Plunk | Transactional & marketing email (verification, reset, invites, inquiries, newsletter) | Recipient email address & send metadata |
| Creem | Payments as Merchant of Record | Billing & payment data (card data never reaches BriefQR) |
| OpenFreeMap | Map tiles for the geofence picker & session maps | IP address & requested map-tile coordinates (no cookies, no login) |
| Photon (komoot) | Address search & reverse geocoding in the geofence picker | IP address, typed search text & pin coordinates (no cookies, no login) |
For details of what each provider processes and on what basis, see our Privacy Policy.