Data processing
Effective
This page explains the processing scope of the existing detection service and what needs to be defined for a migration assessment. It also explains how to request a data processing agreement (DPA). This page is not itself a DPA.
Request a data processing agreement
To ask whether a DPA can cover a proposed deployment or assessment, email with your company name, account email and proposed scope. A request does not itself establish GDPR compliance or guarantee that a DPA will be available for the requested scope.
What the processing scope covers
Detection service. Pisama processes LLM agent traces you submit via the API or SDK. These may contain conversation content, tool calls, and metadata. We process this data solely to provide the Pisama failure-detection service.
Migration assessments. The proposed engagement must identify which request logs, model outputs, tool responses and metadata are needed, where they will be processed and which providers will receive them. Those details must be defined for the assessment. The detection-service description above does not establish the processing terms for a migration assessment.
Retention and deletion
For the detection service, the product manifest lists 14 days as a managed-preview reference allowance; this page does not assert operational enforcement. Actual retention, deletion, and backup behavior must be defined for the provisioned deployment. You may request deletion by emailing .
Retention, deletion and backup terms for a migration assessment must be defined for that engagement. The managed-preview reference allowance does not establish those terms.
Configured subprocessors
The existing product lists the providers below, subject to the configurations described. The applicable providers and subprocessors for a migration assessment must be identified for its agreed scope; this list does not establish which model or serving routes an assessment will use.
- Vercel (frontend hosting and edge delivery)
- Fly.io (backend application hosting and managed database)
- Brevo and Resend (configured transactional or request email delivery)
- Google (configured sign-in identity)
- PostHog, Google Analytics, and Vercel Analytics (when configured)
- Anthropic (only for configured model-assisted processing)
- Sentry (when configured for error and security monitoring)