Kleerr Subprocessors
Last updated: October 3, 2025
Contact: privacy@kleerr.com
Kleerr engages the third-party Subprocessors listed below to support delivery of the Services. Each Subprocessor is bound by written data-processing terms. Kleerr remains responsible for their performance.
Customer Data processed by or through these providers is not used to train generalized or third-party AI/ML models.
How we use Subprocessors
- Scope: Infrastructure hosting, security/CDN, front-end hosting/caching, payments processing, transactional email delivery, and AI model invocation.
- Safeguards: Encryption in transit/at rest where applicable, least-privilege access, logging/monitoring, and contractual confidentiality.
- Change notifications: We update this page for material changes. If your DPA provides an objection right, we’ll notify the Customer admin via email 30 days before a change where feasible.
Entity | Purpose/Role | Data Categories Processed | Processing Location(s) |
---|---|---|---|
Amazon Web Services, Inc. | Cloud infrastructure (compute, storage, networking); managed platform services | Customer Data (as configured), and Service Data ( operational logs/metrics ) | United States (primary) |
Cloudflare, Inc. | Content delivery and security (CDN, DDoS/WAF, edge proxy) | Network telemetry (IP addresses, headers, request metadata) and cached content as configured | Global edge network with primary processing in the United States |
Vercel Inc. | Application hosting and content delivery | Rendered application assets and responses; limited request metadata | United States (primary) with global edge delivery |
Stripe, Inc. | Payment processing and subscription billing | Account/billing identifiers, payment tokens, transaction metadata | United States (primary) with global processing as needed for payment routing |
Brevo (Sendinblue) | Transactional email delivery | Recipient identifiers and message metadata/content for service communications | European Union (primary) with global email delivery |
Render, Inc. | Managed hosting for selected third-party integrations | Integration metadata and Customer Data processed by the enabled integration as configured by Customer | United States (primary) |
Definitions
Customer Data: Data submitted to or collected by the Services on Customer’s behalf (e.g., event/attribution data, identifiers).
Service Data: Operational data generated by the Services (e.g., logs, metrics).
Subscription to changes
To receive Subprocessor change notifications, email privacy@kleerr.com with subject “Subscribe to Subprocessor updates,” and include your company name and admin contact.
This page reflects current usage. Historic updates and removals are tracked below.
Subprocessor change log
Date | Change Type | Vendor | Locations | Notes |
---|---|---|---|---|
2025-10-03 | other | Initial publication | N/A |