Provider change register
New provider changes recorded here follow the notice review process. Existing provider disclosures remain in the inventory below. Business owners: view your delivery dates and objections.
Loading change register…
| Provider | Purpose and data | When used / scope |
|---|---|---|
| Floot | Hosting, database, storage, queues, real-time, managed email and analytics interfaces Business records, uploads, account/security and delivery data; website measurement depending on mode | Core platform and selected features Published infrastructure and downstream-provider documentation reviewed. Actual project connection boundaries, DPA acceptance and isolated restoration remain separate evidence; see disclosure source links. |
| Stripe | Subscription billing and connected business payment services Billing identities, payment details collected in Stripe fields, transaction references and dispute information | Checkout, billing or authorized client payment workflows Source integration observed; processor/independent-controller roles and applicable terms require confirmation |
| Twilio | SMS delivery, inbound messages and delivery callbacks Phone numbers, message bodies, consent/delivery metadata | Configured SMS features and authorized sends Source integration observed; carrier registration, countries, contractual entity and retention unverified |
| OpenAI | AI assistance, extraction, plan processing and transcription Submitted prompts, relevant business context and selected documents/images/audio | When supported AI features are invoked Owner confirms connection; provider publishes API training/retention controls. Account-specific settings, endpoint persistence and contract coverage still require confirmation; no blanket zero-retention promise. |
| Cloudflare Turnstile | Abuse and automated-request protection Browser, connection and verification information | Protected forms and authentication flows Verification endpoint observed; role, location and contractual coverage require confirmation |
| Maps/address features and optional Google identity or business-profile connections Requested addresses/location context or selected identity/business-profile data, depending on feature | Only relevant enabled/authorized Google features Multiple services with potentially different roles; Google Business features may be disabled or gated | |
| Apple | Optional Sign in with Apple Provider identifier and permitted email/name, relay and authorization information | When Apple sign-in/linking is chosen Identity integration observed; not every business uses it; independent-provider terms apply |
| Intuit / QuickBooks Online | Customer-authorized accounting connection and supported exports Selected customer, invoice and payment records and authorization references | Enabled, authorized accounting features Source integration observed; connection alone does not prove export capability or completion |
Scope
This disclosure describes ServicePace’s application providers and optional connected services. Data shared depends on the feature, permissions, configuration and authorized action. Core platform processing and customer-selected integrations have different roles under their applicable agreements. Planned Google Ads, Meta and TikTok advertising is not active; no advertising pixels have been installed.
Processors versus connected services
A provider can act as a subprocessor, an independent controller, a customer-selected integration, or a browser asset supplier depending on its contract and the feature. Payment, identity, maps and accounting providers may determine some purposes independently. The DPA annex must distinguish those roles. No provider receives every data category simply because it is listed.
Data minimization and optional features
Core hosting supports the application and stored business records. Messaging, AI/OCR, maps, identity and accounting processing depend on the feature, permissions, configuration and authorized action. Do not send raw card details, passwords or unrelated sensitive records to optional processing tools. Provider privacy notices do not replace ServicePace’s own contractual diligence.
Locations, contracts and downstream providers
Floot’s public database documentation identifies its hosted-app infrastructure region and explains recovery/file limits. Its downstream-provider list is available at https://floot.com/subprocessors; that catalog includes conditional and builder-only services and must not be treated as a list of every ServicePace data recipient. Exact account agreements, customer-selected provider roles, non-hosting processing locations and any transfer mechanisms remain subject to the actual feature and contract. Public documentation is not proof of a restore drill or execution of Floot’s DPA.
Changes and requests
Contact privacy@servicepace.com for the provider disclosure or an objection. The owner-approved rule is 30 days’ advance notice for a new covered subprocessor and a concurrent 15-day reasonable objection period. Business owners can view their notices and submit concerns at /provider-notices. The register saves confirmed delivery dates, calculates deadlines on the server, blocks normal activation before the notice period ends and blocks unresolved objections. Failed or uncertain delivery does not start the clock. Existing-provider changes, urgent security/legal exceptions and providers’ independent downstream changes require documented review outside this new-provider workflow. The DPA forms part of the applicable accepted ServicePace agreement.
Receipt and document extraction
ServicePace’s supported receipt scanner sends the selected receipt image to OpenAI vision for editable extraction results. Users must verify the extracted details before saving or using them. No separate receipt-text extraction provider or browser OCR asset service is used by the active receipt-scanning path. Optional AI processing is described in the Privacy Policy and AI Usage Terms.
Published evidence links
Floot infrastructure/security: https://floot.com/docs/platform/security-and-data ; database/recovery: https://floot.com/docs/platform/database ; downstream inventory: https://floot.com/subprocessors . Stripe roles depend on the applicable account agreement: https://stripe.com/legal/dpa . OpenAI API processing controls: https://developers.openai.com/api/docs/guides/your-data . Owner-confirmed direct integrations remain subject to their actual accounts and contracts; no new credentials or provider agreements were created by this disclosure.