Subprocessor & Connected-Service Disclosure Version: 2026-11-14-providers-v1 Effective 2026-11-14 ServicePace LLC 8 The Green, Ste B, Dover, DE 19901, US Service providers and connected services used to operate ServicePace, with the data and features involved. 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.