1. Current subprocessors
| Provider | Purpose | Data | Location / notes |
|---|---|---|---|
| Hetzner Online GmbH | Production hosting, network, compute, local storage, PostgreSQL, Redis, and backups for the Kanvly application. | Account data, workspace content, logs, uploaded avatars, operational metadata, and backups. | Germany / European Union. Kanvly currently runs on self-managed infrastructure hosted with Hetzner. |
| Stripe, Inc. | Payment processing, checkout, subscription management, invoices, tax calculation, and customer billing portal. | Billing contact details, payment metadata, plan, seat count, transaction status, and payment identifiers. | United States and other Stripe processing locations. Kanvly does not store full card numbers. Stripe handles payment details. |
| Apple Inc. | App Store distribution, in-app purchase processing, subscription management, receipts, refunds, and App Store account controls for iOS subscriptions. | App Store account and transaction metadata, subscription product identifiers, renewal status, refund status, and purchase verification details. | United States and other Apple processing locations. Apple processes App Store payments and manages App Store refunds and subscription settings. |
| Amazon Web Services, Inc. / Amazon SES | Transactional email delivery for password reset, account, billing, contact, and workspace invite messages. | Email address, message subject, message body, delivery metadata, and related operational metadata. | United States and other AWS processing locations. Used for email delivery, not for workspace storage. |
| OpenAI, L.L.C. | Optional Kanvly AI features and workspace copilot responses. | User prompts, selected chat history, and workspace context needed to answer an AI request. | United States and other OpenAI processing locations. Kanvly does not permit model training on customer data through Kanvly-controlled AI requests. |
| Google LLC | Google Analytics on marketing pages where allowed by jurisdiction or after consent, and Google OAuth when configured and selected by a user. | Analytics events and device/browser metadata for marketing analytics; OAuth profile data for Google sign-in. | United States and other Google processing locations. Google Analytics is blocked until consent in consent-required jurisdictions, and the footer preference control remains available for opt-out. |
| GitHub, Inc. | GitHub OAuth sign-in when configured and selected by a user. | GitHub account identifier, verified email, display name, and OAuth authentication metadata. | United States and other GitHub processing locations. Only used when the GitHub sign-in option is enabled and selected. |
| Customer-configured OIDC provider | Enterprise single sign-on when a customer configures its own OIDC identity provider. | OIDC identifier, verified email, display name, and authentication metadata. | Depends on the customer identity provider. Applies only to workspaces that configure OIDC/SSO. |
2. Self-hosted services
PostgreSQL, Redis, application runtime, local upload storage, and operational backups currently run on Kanvly-controlled infrastructure hosted with Hetzner Online GmbH in Germany. Those self-hosted components are not separate subprocessors beyond the hosting provider.
3. Changes and objections
Kanvly may update subprocessors as the product changes. If a new subprocessor materially changes how customer personal data is processed, Kanvly will update this page and take reasonable steps to notify affected customers where required. Customers may object through Kanvly supportwith a reasonable data protection basis.