Subprocessors
Last updated: September 24, 2026
Isles Mechanical LLC uses the following subprocessors to deliver ServiceRunner. This list forms part of the Data Processing Addendum. It is updated before any new subprocessor begins processing customer personal data.
1. Current Subprocessors
Locations below are where each provider processes the data we send it. Several are global companies; the location given is the one that applies to this Service, not the full list of places that provider operates in.
| Subprocessor | Purpose | Data involved | Location |
|---|---|---|---|
| Sentry (configured diagnostics provider) | Optional browser error reporting on the website, only when enabled for the deployment and after the visitor opts in. Disabled in the mobile app. | Error messages, stack traces, app version and technical context; network IP address. No account identity fields, request headers, cookies or session recordings. | Depends on the configured Sentry endpoint and hosting region; contact us for deployment-specific details. |
| Cloud infrastructure provider (region selected by customer) | Hosting of the application, PostgreSQL database, Redis cache and queue, and S3-compatible object storage for photos, plans and files; backups. | All Customer Data and account data | Customer-selected region |
| Stripe, Inc. | Our subscription billing and, when a Customer enables its connected merchant account, end-client invoice card collection and recurring agreement payments; payment security and fraud prevention. | Billing contacts and organization details; for Customer collections, end-client and invoice identifiers, amounts, authorization and payment references, limited card details, and payment events. Full card details are entered into Stripe's secure fields and held by Stripe. | United States |
| Resend, Inc. | Transactional email delivery (invitations, verification, password reset, notifications, quotes and reports sent by customers). | Recipient email address, name, message content | United States |
| Telnyx LLC | Business phone calls and SMS/MMS delivery through configured ServiceRunner phone lines. | Phone numbers, call metadata, message content and attachments; recordings and voicemail when enabled. | United States |
| AI model provider: OpenAI, L.L.C. or Anthropic, PBC, whichever is selected for the task | Reading receipt photos attached to expenses; transcribing and summarising phone recordings when enabled; drafting review replies when a user asks. Only the selected provider receives the data; there is no automatic fallback to the other. | Receipt images (which can show a name, card last four digits or store location); call audio and transcripts; review text. Sent through the provider's business API; not used to train its models, and kept by the provider only for a limited abuse-monitoring period. | United States |
| Google LLC (Firebase Cloud Messaging) | Push notification delivery to iOS and Android devices and browsers. | Device push token, notification title and body | United States |
| Google LLC, Microsoft Corporation, Apple Inc. (single sign-on) | Identity verification when a user chooses to sign in with that provider. Engaged only if the deployment enables SSO and only for users who use it. | Name, email address, provider subject identifier | United States |
| Map tile provider (default: OpenStreetMap Foundation tile servers; a keyed provider such as MapTiler, Stadia Maps or CARTO may be configured) | Map tile imagery for site and dispatch maps, built on OpenStreetMap data. The browser or app fetches tiles directly. | IP address and the tile coordinates requested (which reveal the map area viewed) | United Kingdom / Netherlands (OSMF) or the configured provider's region |
| Apple Inc. (App Store) and Google LLC (Google Play) | Distribution of the mobile apps, crash reporting through the platform, and in-store account handling. Acting as independent controllers for store accounts. | Store account identifiers, app diagnostics as configured by the device owner | United States |
Customer-selected integrations can also disclose Customer Data directly to another provider. When a Customer connects QuickBooks Online and separately enables accounting sync, Intuit may receive customer contact details and issued invoices, payments and supported credits, and return company and transaction data for reconciliation. Intuit is identified here as a Customer-selected integration, not as our blanket DPA Subprocessor. Stripe, when processing for the Customer's connected merchant account, and Intuit may act as independent controllers for some activities and processors for others under their own terms and privacy notices: Stripe Privacy Policy; Intuit Privacy Statement.
Isles Mechanical affiliates and contractors who provide engineering or support may access Customer Data under confidentiality obligations and the DPA; they are not listed individually. Where a Customer self-hosts or chooses a dedicated deployment, the hosting provider and region are those selected by the Customer and stated in its Order.
2. Safeguards
Each subprocessor is bound by a written agreement that imposes data protection obligations no less protective than the DPA, including confidentiality, security measures and assistance with data subject rights. The Service is offered in the United States and Canada only (Terms Section 1.3). Personal information transferred from Canada to the United States for processing is covered by those contractual obligations, which is the comparable protection PIPEDA and Quebec Law 25 require of a transferring organization; we remain accountable for it, and Section 11 of the DPA sets out the commitment in full. We review each subprocessor's security documentation before onboarding and periodically thereafter.
3. Change Notifications and Objections
We will publish changes on this page and notify Organization Owners and billing contacts by email or in-app notice at least 30 days before a new subprocessor begins processing Customer Personal Data. To receive notices at an additional address, or to object to a new subprocessor on data-protection grounds, email privacy@servicerunner.app. The objection procedure and remedies are set out in Section 5 of the DPA.
4. Change History
- September 27, 2026: Listed the AI model provider (OpenAI or Anthropic, as selected), which reads receipt photos for expenses and already handled phone-recording transcription and review-reply drafts.
- September 21, 2026: Updated the phone and messaging subprocessor to Telnyx.
- September 24, 2026: Initial publication of this page. Added the map tile provider (previously undocumented), Resend and the messaging provider; replaced the informal "SMTP email providers" description; named the hosting provider category and region.