TracePoint defines data-processing terms for the exact deployment, parties, data and infrastructure in an executed agreement. This public summary identifies the subjects covered by that process and is not itself a signed DPA or assurance statement.
Deployment-specific DPA scopeThe public product environment uses local identity data, local operational scenario data, and ephemeral per-session state stored in the active application process. Visitors must not submit confidential customer records, credentials, regulated data, or production personal data.
An executed deployment agreement defines controller and processor roles, documented instructions, purposes, data categories, data subjects, retention, deletion, processing locations and sensitive-data restrictions.
Technical and organizational measures are documented from the identity, access, tenancy, encryption, logging, backup, recovery, incident-response and connector controls selected and verified for the deployment.
Any applicable subprocessor inventory, processing locations, transfer mechanisms and supplementary safeguards are established for the selected deployment before relevant processing begins.
The executed DPA defines assistance, notification, return, deletion and audit obligations appropriate to the agreed processing scope.
Enterprise teams may discuss deployment-specific data-protection requirements through legal@tracepoint.tech.