Private early access
Service providers and optional integrations
This disclosure describes the current technical service roles. It is not a representation that every integration is enabled for every carrier. Before customer activation, the signed provider schedule must confirm the actual parties, processing roles, services, agreements and hosting regions.
Updated October 26, 2026
Base44 — website and application platform
Base44 provides website/application hosting, application authentication and database services, and can serve site images. Depending on the enabled workflow, it processes account, prospect and carrier operational records and technical request information. Its own upstream providers and contractual terms require review for the agreed customer service.
Base44 DPASupabase — private evidence storage and processing support
Supabase provides private evidence storage and associated processing support. Approved files, metadata and related technical requests may pass through it. A project’s selected region does not establish the location of every other provider or support activity. Confirm the actual project region, access arrangements and applicable terms before an order is signed.
Supabase DPACloudflare — public network delivery
The public website is delivered through Cloudflare infrastructure. Network requests can expose technical information such as IP address and request metadata. This observation does not establish that Cloudflare is the storage location for carrier records or evidence.
Google — sign-in, fonts and optional carrier integrations
Google Sign-In handles account authentication when used; web fonts make technical requests to Google. Mapping or routing may process addresses and permitted operational location for requested features. A carrier may separately authorize its own Google Drive or mailbox connection. Those customer-controlled integrations must be distinguished from Provider-selected core processing in the signed schedule. A Google logo or code path is not proof that any particular integration is enabled.
Regions, optional billing and future changes
There is no blanket U.S.-only data-residency commitment on this website. Confirm regions, enabled optional billing or other providers, and any required transfer terms before activation. A provider mentioned in source code but not configured is not automatically part of the customer’s active service. The provider list and order schedule must be reviewed when services change; notice and objection handling for engaged subprocessors are governed by the agreed DPA.
Review the proposed DPAAsk for the applicable provider schedule
For the provider schedule relevant to a proposed pilot, contact carrierhelm.admin@gmail.com. We must confirm the actual processing arrangement before access is granted; this public list does not replace the signed order or provider due diligence.
Request provider information