Legal
Sub-processors
Last updated: August 1, 2026
Kipper Inc. (“Kipper”) engages the third-party sub-processors below to help provide the Kipper conversational finance intelligence platform (the “Service”). Each sub-processor is engaged under written terms requiring data-protection obligations materially consistent with our Data Processing Agreement or as required by applicable law.
This page is the source of truth for our current sub-processors. It is referenced by our Data Processing Agreement.
Current sub-processors
| Sub-processor | Purpose | Personal data processed | Primary location |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting, compute, and storage (customer data logically separated with application-level access controls); AI inference via AWS-managed Amazon Bedrock — interprets queries and generates responses without sharing data with model providers or using it for model training. | Customer data hosted in Kipper’s AWS environment; query text and data used for LLM inference | United States |
| Stripe, Inc. | Subscription billing and payment processing. | Billing contact and account data; full card numbers and security codes are handled by Stripe and not stored by Kipper | United States |
| Twilio Inc. | Delivery of SMS messages for the SMS interface. | Phone numbers and SMS message content | United States |
| Sentry (Functional Software, Inc.) | Application error and performance monitoring. | Diagnostic and error data, which may include limited personal data present at the time of an error | United States |
| PostHog, Inc. | Product analytics and session recording (for logged-in platform users); all text input fields are configured to be masked. | Product usage data, identifiers, and session-recording data (text inputs masked), which may include personal data | United States |
| Google LLC (Google Workspace) | Business email, productivity, and internal/support communications. | Business contact details and any personal data contained in communications | United States |
| Conductor Labs, Inc. (Conductor.is) | API integration layer used exclusively to connect to QuickBooks Desktop and QuickBooks Enterprise (not used for QuickBooks Online, Xero, or NetSuite); data passes through in transit and is not permanently retained by Conductor. | Financial data read from connected QuickBooks Desktop/Enterprise company files (e.g., customers, invoices, payments, vendors, bills), which may include personal data | United States |
Primary location reflects where customer data is principally processed; sub-processors may process data in other locations under their own transfer terms.
Customer-directed integrations. Services you connect at your own direction — such as your source systems and the messaging, chat, or AI assistant interfaces you choose (e.g., Slack, Microsoft Teams, Claude, ChatGPT) — are not Kipper sub-processors; your use of them is governed by your agreements with those providers. (Kipper-provided SMS is delivered through Twilio, which is a sub-processor listed above, not a customer-directed integration.)
A note on AI and your data
AI inference runs through AWS-managed Amazon Bedrock, within our own AWS account and infrastructure — not a separate third-party AI vendor. Under AWS’s published Amazon Bedrock documentation, AWS states that Bedrock does not store your input or output data, does not share it with the third-party model providers whose models it hosts, and does not use it to train models. Each model provider runs in a dedicated deployment account it cannot access, and model-invocation traffic stays within the AWS network. Only the data needed to answer a given query is sent for inference, and Bedrock’s automated abuse-detection mechanism involves no human access to input or output data. See Section 7 of our Data Processing Agreement for details.
Questions: legal@kipper.com.