Subprocessors and Service Providers

Function: Database and backend hosting for CRM records, authentication-linked application data, and server functions.

Data categories: Account, team, customer, contact, scheduling, billing, message, voice, file, location, integration, and operational records stored in the application.

Function: Authentication and account identity management.

Data categories: Names, email addresses, profile and authentication identifiers, session information, and sign-in provider data.

Function: Platform subscriptions, customer payments, billing, and payment-device services.

Data categories: Payment and billing details, customer identifiers, transaction and invoice data, and Stripe account or payment-method identifiers; full card numbers are handled by Stripe rather than stored by the application.

Function: Application hosting where configured for a deployment.

Data categories: Application runtime, request, and operational data processed by the hosted application. Production use of Railway depends on deployment configuration.

Function: R2 file and object storage plus application-edge, CDN, Bot Fight Mode, and WAF services.

Data categories: Uploaded photos, documents, attachments, signatures, PDFs, voice recordings, and other stored files; request IP addresses, headers, URLs, and security or traffic metadata processed at the application edge.

Function: SMS/MMS delivery and inbound messaging.

Data categories: Sender and recipient mobile numbers, SMS/MMS message content and media metadata, delivery status, message identifiers, and account or webhook metadata. The registered application routes do not currently send voice calls or call recordings to Twilio.

Function: Email delivery, including transactional messages and Account Owner-created campaign and drip messages.

Data categories: Recipient email addresses, subjects, message bodies, rendered template output, attachments when used, and delivery or engagement metadata.

Function: Application log and event storage.

Data categories: Redacted request and event metadata, account and organization identifiers, counts and timing or performance data, and redacted error context emitted by the application. Sensitive phone, email, token, address, transcript, and payment fields are replaced with a redaction marker before ingestion.

Function: Error, performance, replay, and reliability diagnostics.

Data categories: Redacted application error and performance data, stack traces, request/device/browser metadata, wide-event breadcrumbs, mobile user or account context, and replay data when Sentry is configured. Sensitive event fields and user email addresses are replaced with a redaction marker while operational identifiers and counts are retained.

Function: Background job and workflow execution.

Data categories: Workflow event payloads, record identifiers, and data needed for notifications, billing, voice, booking, and synchronization jobs.

Function: Rate limiting and request-protection services.

Data categories: Raw portal access tokens used as Redis keys, user and organization identifiers used as keys, IP addresses, rate-limit counters, and request-protection metadata.

Function: AI features, including live voice conversations, onboarding assistance, transcription, intent parsing, generation of CRM tool requests, message generation, and document/image upload and extraction.

Data categories: Live or stored microphone audio and voice conversations; transcripts; prompts and conversation content; CRM tool requests and results; contact names and other identifiers; account and profile information; job notes and descriptions; uploaded document images and PDFs; bulk customer and business records extracted from those documents, including names, contact details, addresses, account information, invoices, job information, and other records contained in the documents; and text submitted for or generated by AI features.

Function: Address autocomplete, maps, routing, and route optimization.

Data categories: Addresses, customer or job coordinates, route stops, and mapping or routing request data.

Function: Optional calendar connection and synchronization.

Data categories: Google account and calendar identifiers, OAuth tokens, event details, and appointment-related data.

Function: Optional Google identity sign-in on mobile.

Data categories: Identity and profile information, authentication responses, and account identifiers returned through Google sign-in.

Function: Optional CRM contact synchronization.

Data categories: Integration credentials or tokens and synchronized contact data: contact names, email addresses, phone numbers, company names, tags/source values, and GoHighLevel/Humboldt contact mapping identifiers.

Function: Optional accounting integration for contacts, invoices, estimates, expenses, and time entries.

Data categories: Integration credentials or tokens; contact and billing-address data; invoices and estimates with customer references, amounts, currencies, and line items; expenses/purchases with vendor, account, category, notes, and amounts; and time-entry data with employee references, hours, dates, and notes.

Function: Optional mobile push-notification delivery.

Data categories: Device push tokens, app/device metadata, and notification payloads.

Function: Map embeds on public tracking pages.

Data categories: Tracking-page coordinates and browser/request metadata needed to load the map embed.

Function: Sign in with Apple and optional Apple Maps navigation.

Data categories: Identity and profile information used for Apple sign-in, and customer or job destination coordinates when Apple Maps is selected.

Function: Mobile speech recognition through the operating system speech service selected by the device.

Data categories: Microphone audio and interim or final transcripts; on-device mode may process audio locally, while network mode sends audio to Apple Speech, Google Speech Recognition, or another speech service selected by the device.

Function: Public API documentation asset delivery.

Data categories: Browser and network request metadata associated with loading Swagger UI assets; the application code does not send CRM records to unpkg.