Trust center
Subprocessors
This page names the companies that help WashRoute Pro run and makes clear which services are always used, used only when you choose an action, or used only after an optional feature is turned on.
A provider marked “Enabled when configured” does not receive customer data merely because it appears on this list. A “User-initiated service” receives only the stated fields when an authorized user chooses that action.
1. How to read this list
Core infrastructure supports the deployed Service. A user-initiated service receives its stated inputs only after an authorized user chooses that action. Configuration-dependent providers process information only for an enabled integration. A customer may use one, several, or none of those optional services depending on deployment and account configuration.
2. Current provider list
The table below is generated from the centralized legal provider inventory. Provider privacy terms are linked for transparency; our contracts and configurations govern their work for the Service.
3. Environment-specific providers
The current production environment uses Neon managed PostgreSQL in AWS US East and Cloudflare R2 for private object storage. Cloudflare also provides the Worker runtime, edge delivery, rate limits, and durable fallback capture. OpenStreetMap Foundation supplies best-effort public map tiles requested by the browser for saved coordinates; it is not a road-routing or geocoding provider. When an authenticated user chooses “Place this address on the map,” the server sends only the entered U.S. service address to the U.S. Census Geocoding Services API and returns an address-range estimate for review. A future environment must update this list before using a different database, storage, map, or geocoding provider.
Open-Meteo is named for location-based weather workability forecasts. When that feature is used for a scheduled job with saved coordinates, Open-Meteo receives the property latitude and longitude, account time zone, forecast variables requested, and request metadata, but not the customer name or street address. We will add any new routing, mapping, monitoring, analytics, support, or AI company to this page before it handles customer information. Test-only services do not receive live customer data and are not included as subprocessors.
4. Changes and objections
We update this page when a material provider begins or stops processing. Business customers may submit a reasonable data-protection objection using the Legal and contracts option on our Contact page. We will evaluate alternatives in good faith, but an integration may not function without its necessary provider.
Detailed provider inventory
| Provider | Status | Purpose and data | Location |
|---|---|---|---|
| Cloudflare, Inc. | Core infrastructure | Application hosting, edge delivery, request security, durable fallback capture, and private R2 object storage. Account requests, network and device data, application traffic, uploaded job files, and fallback request records. | Global network; processing location depends on request routing and configured services. |
| Neon, Inc. | Core infrastructure | Managed PostgreSQL database hosting for production application records. Account, customer, property, quote, job, billing-state, support, security, audit, and privacy-workflow records stored by the Service. | United States; the current production database is hosted in AWS US East. |
| OpenStreetMap Foundation | Core infrastructure | Map tiles displayed for saved properties, jobs, route planning, and field context. Browser network and device metadata, page referrer, and requested map-tile coordinates. Customer names and street-address text are not sent in the tile request. | Provider infrastructure locations described by the OpenStreetMap Foundation. |
| U.S. Census Bureau | User-initiated service | Convert a U.S. service address into an estimated map pin when an authenticated user chooses that action. The service-address fields entered by the user and server request metadata. Customer names, phone numbers, email addresses, job notes, and account credentials are not sent. | United States government infrastructure. |
| Twilio Inc. | Enabled when configured | Sending and receiving SMS and MMS communications. Phone numbers, message content, delivery status, and messaging metadata. | United States and other locations described by the provider. |
| Resend, Inc. | Enabled when configured | Transactional and product email delivery. Email addresses, message content, delivery status, and email metadata. | United States and other locations described by the provider. |
| Stripe, Inc. | Enabled when configured | Provider-hosted checkout and payment processing. Customer and transaction details needed to create checkout sessions and confirm payment status. | United States and other locations described by the provider. |
| Open-Meteo | Enabled when configured | Location-based weather forecasts for scheduled-job planning. Property latitude and longitude, account time zone, forecast variables requested, and request metadata. Customer names and street addresses are not sent. | European Union and other locations described by the provider and its infrastructure partners. |