Legal
Subprocessor Exhibit
Effective date: July 24, 2026 *(update on material changes)*
Effective date: July 24, 2026 *(update on material changes)* Provider: Kraken Services LLC, d/b/a Service Velocity Incorporated into: DPA Cover Page · CSA Framework Terms Engineering review: 2026-07-24 — see counsel-review-checklist.md §Internal #4
Provider uses the following subprocessors to deliver the Service Velocity platform. This list is authoritative for security questionnaires and DPA notices once counsel-reviewed.
Change notification: Provider will notify Customer of material subprocessor changes at least 30 days in advance via email to Customer's account administrator and by updating this exhibit.
Infrastructure & core platform
| Subprocessor | Processing location | Purpose | Data processed |
|---|---|---|---|
| Microsoft Azure | United States (primary: Central US / `centralus`) | Cloud hosting — compute, database, storage, identity, monitoring | All platform data |
| Microsoft Entra ID | United States | Authentication and SSO | Identity, credentials metadata, session tokens |
| GitHub (Microsoft) | United States | Source control and CI/CD (no production customer DB content) | Configuration metadata only |
SaaS subscription billing (Layer A)
| Subprocessor | Processing location | Purpose | Data processed | Status (2026-07-24) |
|---|---|---|---|---|
| Stripe, Inc. | United States | Primary SaaS subscription billing | Billing contact, payment method tokens, subscription metadata | Implemented on `feature/v1-commercial`; not yet on `develop`/production |
| Paddle.com Market Ltd. | United States / EU (per Paddle) | Secondary SaaS subscription billing (abstraction proof) | Billing contact, payment method tokens, subscription metadata | Stub only — not processing live SaaS fees in V1 |
In-product payments (Customer's end-customer payments — Layer B)
| Subprocessor | Processing location | Purpose | Data processed | Status (2026-07-24) |
|---|---|---|---|---|
| Helcim | Canada / United States | Default invoice payment processing | Payment tokens, transaction metadata | Production path |
| Square, Inc. | United States | Secondary invoice payment processing | Payment tokens, transaction metadata | Stub only — not processing live invoice payments in V1 |
*Service Velocity does not store full card PANs.*
Communications
| Subprocessor | Processing location | Purpose | Data processed |
|---|---|---|---|
| Azure Communication Services | United States | Transactional email delivery | Recipient addresses, message content |
| JustCall (where Customer enables integration) | United States / per vendor | SMS and voice | Phone numbers, message/call metadata and content |
Artificial intelligence
| Subprocessor | Processing location | Purpose | Data processed |
|---|---|---|---|
| Microsoft Azure OpenAI Service | United States | LLM inference for AI-assisted features | Tenant-scoped prompts and completions per AI Data Use Policy |
No subprocessor may use Customer Personal Data for model training except as prohibited by Provider's agreements with subprocessors and the AI Data Use Policy. Additional LLM providers will be disclosed here before enablement.
Optional customer integrations (when Customer enables)
These process Customer data only when the Customer connects/configures the integration (often Business-plan features).
| Subprocessor | Processing location | Purpose | Data processed |
|---|---|---|---|
| Jobber | United States / per vendor | Import and migration of field-service data | Customers, jobs, quotes, schedules, related records |
| Intuit QuickBooks Online | United States / per vendor | Accounting sync (invoices, payments, customers) | Financial and customer records Customer authorizes |
| ATTOM | United States | Property / address enrichment | Addresses and property attributes submitted by Customer |
| Apify | United States / per vendor | Outreach / enrichment automations (where enabled) | URLs and scraped public data Customer configures |
| Mapbox | United States | Maps, geocoding, routing | Addresses and coordinates |
Observability & support tooling
| Subprocessor | Processing location | Purpose | Data processed |
|---|---|---|---|
| Microsoft Azure Monitor / Application Insights | United States | Application telemetry, logs, metrics, alerting | Operational telemetry (may include user IDs, request metadata) |
| Azure Managed Grafana | United States | Ops dashboards over Azure Monitor metrics/logs (IaC-managed) | Operational telemetry (may include user IDs) |
Data residency note
Production customer data is stored and processed primarily in Azure Central US (`centralus`) for US latency. Provider does not offer EU-only or customer-selectable region hosting at V1. Resources are only placed outside Central US when a service is unavailable in that region (document any exception here).
Customer authorization
By executing the DPA or using the Service after notice of an updated subprocessor list, Customer authorizes Provider to engage the subprocessors listed above subject to the DPA Standard Terms.
Last reviewed: 2026-07-24 — Engineering draft verification (#1168 / #1184 checklist)
Product legal
- Product Privacy Policy
- Terms of Service (CSA)
- Acceptable Use Policy
- AI Data Use Policy
- Support Policy & SLA
- Subprocessors
- Data Processing Agreement
- Cookie Notice (Product)
- Privacy Rights & Requests
- Client Portal Notice
- Mutual NDA Standard Terms 1.0
Marketing site: Website Privacy · Website Terms · info@servicevelocity.ai
Draft templates published to stabilize product links. Counsel review in progress (Service-Velocity/servicevelocity#1168).