by Wellreports.io
The third-party service providers we engage to help deliver the Well Ops platform, and where data is processed.
Effective July 12, 2026 · Provided by Wellreports LLC
We use a small set of trusted third-party providers to run the Well Ops platform. This page lists them, what each does, and where data is processed.
We engage the third-party providers below (“subprocessors”) to help deliver the Well Ops platform (the “Services”). We require each to protect information consistent with our Privacy Policy. This list may change as our infrastructure evolves; we will update it accordingly. Capitalized terms have the meanings given in our Terms of Service.
| Subprocessor | Purpose | Data Categories | Location |
|---|---|---|---|
| Anthropic | AI model provider powering AI Features (document/record extraction, insights, assistants) | Content submitted to AI Features, which may include Customer Data | United States |
| Amazon Web Services (AWS) | Cloud hosting and file/document storage | All hosted Customer Data and uploaded files | United States (us-east-2) |
| Vercel | Application hosting, delivery, and usage/performance analytics | Application requests, usage and performance telemetry | United States / global edge |
| Stripe | Subscription billing and payment processing | Billing contact and payment method details | United States |
| Twilio | SMS/MMS messaging (field, owner, and vendor communications) | Phone numbers and message content | United States |
| Mailgun | Transactional and notification email delivery | Email addresses, message content, and delivery/engagement events | United States |
| Mapbox | Maps and geospatial rendering | Map and location queries | United States |
| MQTT broker provider | SCADA / IoT telemetry ingestion | Device telemetry and connection metadata | Varies (customer-configurable) |
The Services also retrieve information from government and public-records providers on Customer’s behalf — for example, the Oklahoma Corporation Commission, the Oklahoma State Courts Network, county public-records providers, and (where enabled) the Texas Railroad Commission. These providers supply data used within the Services; they are data sources rather than subprocessors of Customer Data. Paid retrievals are billed as metered usage under the Terms of Service.
When Customer chooses to import data from an external system it controls (for example, a Microsoft SQL Server database or a Quorum accounting system), Customer directs that connection and is responsible for the source system and its credentials. Those external systems are not our subprocessors.
Questions about our subprocessors may be sent to privacy@wellreports.io.