Data processing addendum

DPA terms are scoped before customer data processing.

This route explains the current public-beta boundary. It is not an executed data processing addendum.

Effective: 2026-08-08 Public-beta boundary: product terms are quoted before onboarding

Signed status

No executed public DPA is published from this website. DPA terms are handled before customer data processing.

Processing scope

Data categories, purposes, roles, subprocessors, geography, retention, deletion, and assistance obligations belong in the customer scope.

Security schedule

Controls, audit rights, incident notice, backup, encryption, and access commitments belong in the customer scope.

Current public-beta status

Current public-beta status

The public website collects working-session inquiries but does not process customer CRM records, prospect lists, outreach content, or opportunity data in a logged-in product environment.

Availability scope

Availability scope

A signed DPA is handled before customer data processing. It names controller/processor roles, processing purposes, subprocessor list, transfer terms, security measures, breach notice, deletion/export obligations, assistance duties, and contact path.

Public-beta boundary

This page states current website behavior.

Publish or sign a DPA only after the actual product data flow, subprocessors, and security controls are confirmed.