Data Map — Where Your Data Lives
Last updated: August 19, 2026
This page is a plain-language inventory of the personal data ProBelt handles, the systems it lives in, who can access it, and how long it is kept. It supports our Privacy Policy and Data Processing Agreement. We do not use a third-party CRM, ad network, or data broker.
1. Systems That Hold User Data
| System | Location | What it holds |
|---|---|---|
| Supabase — Postgres database | United States (managed cloud) | All structured app data: accounts/profiles, businesses (tenants) and members, clients, leads, jobs, estimates, invoices, expenses, timesheets, calls & SMS records, booking requests, consent records, push tokens, analytics tables |
| Supabase — Auth | United States | Email addresses, credential data, sign-in sessions for app users |
| Supabase — Storage (private buckets) | United States | Job-site photos, receipts, FieldNote media — served only through short-lived signed URLs |
| Supabase — Edge Functions | United States | Server-side logic: the AI proxy (calls OpenAI), SMS/voice handling, payments/webhooks, the weekly retention purge |
| OpenAI API | United States | Photos/text you submit to AI features — transmitted via our server-side proxy to generate your result; not used to train OpenAI models; we keep only minimal usage metadata |
| TypeSafe API | United States | Bank transaction descriptors (merchant names, amounts) for expense categorization — transmitted via our server-side proxy; TypeSafe states inputs are not used to train its models and are not disclosed beyond its service providers; we keep only minimal usage metadata |
| Twilio | United States | Phone numbers, SMS message content and metadata, call records for the calling features |
| Mapbox | United States | Addresses and coordinates sent for mapping/geocoding |
| Apple (TestFlight/App Store) & RevenueCat | United States | Beta distribution and crash logs (Apple); subscription entitlement data (RevenueCat) |
| Hostinger (this website) | US/EU | Web-server logs only — no app data |
2. Personal Data Inventory (PII)
| Data | Examples | Stored in |
|---|---|---|
| Identity & contact | Name, email, phone, company name/role | Supabase Auth + profiles/tenant tables |
| Client/lead contact data | Names, phones, emails, service addresses | Clients/leads tables (tenant-isolated) |
| Location | GPS clock-in/out points, geofence events (opt-in) | Geofence/time-entry tables |
| Communications content | Call transcriptions, voicemail, SMS bodies | Calls/call_messages/sms_messages tables + Twilio |
| Photos & media | Job-site photos, receipts (may incidentally capture people) | Private storage buckets + metadata tables |
| Financial records | Estimates, invoices, expenses, payment status | Estimate/invoice/expense tables (payment processing itself via Apple/RevenueCat) |
| Device & usage | Push tokens, device type/OS, feature analytics events | Push-token and analytics tables |
3. Who Can Read It
- You and your business: every table that holds business data is protected by row-level security (RLS) — a database-level rule set that blocks access by anyone who is not a member of your business. Members see your business's data; field workers see what their role permits.
- ProBelt support/engineering: scoped service-role access used only to operate and support the service (for example, restoring data you ask us to help with). Support access to your business content is request-driven, not ambient browsing.
- Subprocessors: only the providers listed above, only for their stated purpose (Section 1), under the safeguards in the Privacy Policy and DPA.
- Media files: not publicly listable or downloadable — private buckets with expiring signed URLs.
4. Retention at a Glance
An automated job runs weekly to purge expired data. Current periods — with the rationale — are maintained in Section 7 of the Privacy Policy: granular analytics events are purged after 90 days; call logs and transcriptions after 365 days; aggregate metrics after 2–3 years; business records are kept while your account is active and deleted within 30 days after confirmed account deletion.
5. Keeping This Map Honest
Whenever we add a new system that holds user data or change where data lives, we update this page and the subprocessor list in the Privacy Policy. Questions or corrections: support@probelt.app.