Subprocessors

This page lists the third-party providers ("subprocessors") that may process personal data on behalf of Kasper Automation when providing services.

If you have questions about subprocessors, data residency, or vendor risk requirements, contact: security@kasperautomation.com

Last updated: 2025-12-12  |  Effective date: 2025-12-12

What is a subprocessor?

A subprocessor is a third party that may process customer personal data on our behalf to support delivery of the services (for example: hosting, monitoring, support tooling, and payment processing).

When this list applies

This list applies when Kasper Automation is acting as a processor for customer personal data, including when:

  • We are operating a managed hosting model (if offered)
  • We use third-party tools for support, monitoring, logging, or analytics (where applicable)
  • We process customer requests via email or customer support channels

If you use a client-hosted model and choose not to share production credentials or data with us, subprocessor exposure can be reduced. Your exact setup will be documented per project.

Subprocessor update policy

We may update this list from time to time.

  • We will provide notice of material changes where contractually required.
  • If you object to a new subprocessor on reasonable data protection grounds, we will work with you to find a suitable alternative where feasible, or you may terminate the impacted services as described in the DPA.

To request notifications of changes, email: hello@kasperautomation.com with subject line "Subprocessor Notifications".

List of subprocessors

Below is the current list of subprocessors. Items marked "Optional" are used only when applicable (for example, if you choose a managed hosting model or specific tooling).

Subprocessor Purpose Data potentially processed Processing location / region
Amazon Web Services (AWS) Website hosting & delivery Website traffic metadata Global
Microsoft 365 (Microsoft) Business email Names, emails, message content, attachments Global
EmailJS Website contact form delivery Form submissions (name, email, message) Global
n8n Cloud (n8n GmbH) Automation runtime Workflow data and related metadata routed through the platform Germany

Notes on common categories

The exact data processed depends on your workflow and tool stack. Typical categories include:

  • Contact details (name, email, phone)
  • CRM fields (lead/customer records)
  • Operational messages (email/Slack/Teams content you route through workflows)
  • Files you intentionally pass through workflows (documents, exports)
  • Identifiers and metadata needed to run workflows (record IDs, timestamps)
  • Support communications (email/tickets)
  • Logs and diagnostic data (limited error information)

Customer options

If you have strict requirements, we can usually design around them.

Examples:

  • Client-hosted delivery (recommended for strict client requirements)
  • Reduced logging and shorter retention windows
  • Region-specific hosting (where applicable)
  • Avoiding specific tooling when feasible

To request a tailored approach, contact: hello@kasperautomation.com

Related documents