Privacy Policy

§ 01 · SummaryWhat you should know in one minute.

This policy explains what data we collect, how we use it, and what choices you have. It applies to the Pisama Service — the open-source SDK / CLI, the hosted platform at pisama.ai, the marketing site, and our API endpoints.

§ 02 · Local-firstWhat stays on your machine.

SDK and CLI. When you pip install pisama and run detection locally, traces are analyzed on your machine. Pisama does not make outbound network calls to our infrastructure during local detection.

Tier-4 LLM judge. When the optional LLM-judge tier is invoked, the request goes from your machine directly to your configured LLM provider (e.g. Anthropic) using your own API key. Pisama is not in the path and does not see those requests.

MCP server. The MCP server process runs locally and serves clients you control (Cursor, Claude Desktop, Windsurf, etc.). Its configured client communicates with a selected Pisama backend, so request data leaves your machine when that backend is remote.

§ 03 · Data we collectWhat the hosted platform receives.

The hosted platform collects only the data you choose to send it:

• Account info. Email address, name, and authentication identifiers from your sign-in provider (Google OAuth).
• Traces and detections. Trace data you upload or push through a provisioned local or hosted integration, and the detections, diagnoses, and fix suggestions produced from it. Named framework lanes do not imply that every connector is publicly available.
• Account data. The email you sign up with, the tenant name you choose, your role within the tenant, and the timestamp + IP + user agent recorded when you accept the Terms of Service.
• Operational metadata. Standard server logs (IP, user agent, request path, timestamps) used for security, debugging, and abuse prevention. Essential client error reports may be sent to Sentry with default personal-data capture and session replay disabled.
• Registry subscriptions. When you subscribe to model registry emails, Brevo receives your email address and records your signup and confirmation. This subscription is separate from a Pisama account. RSS readers can follow the registry without providing an email address to Pisama.
• Analytics. When configured, PostHog, Google Analytics 4, and Vercel Analytics load on the marketing site or dashboard. These tools are not intended to include trace contents.

§ 04 · How we use itWhat we do with your data.

We use Customer Data only to:

• Provide the Service you requested (run detection, store results, generate fix suggestions)
• Communicate operational notices, security alerts, and product updates
• Send model registry updates to readers who confirm their email subscription
• Investigate abuse, debug failures, and maintain platform stability
• Comply with legal obligations

We do not use Customer Data to train machine learning models or sell it to third parties.

§ 05 · SubprocessorsWho else sees data on our behalf.

The hosted platform relies on a small set of subprocessors:

• Vercel — frontend hosting and edge delivery for pisama.ai.
• Fly.io — backend application hosting and managed Postgres (api.pisama.ai).
• Brevo: transactional email delivery (signup, password reset, alerts), and model registry email subscriptions, confirmation and unsubscribe handling.
• Resend — delivery of demo and contact form requests submitted on the site.
• Google (OAuth) — sign-in identity for the dashboard.
• PostHog, Google Analytics, and Vercel Analytics: when configured, product and site measurement loads automatically. PostHog receives account identifiers only when it is configured and you are signed in.
• X, LinkedIn, and Reddit: optional advertising measurement, active only when a corresponding pixel is configured.
• Anthropic — LLM-judge calls for the Tier-4 escalation tier (only when explicitly invoked using your own API key on the SDK; Pisama-internal LLM features call Anthropic from our backend).
• Sentry: when configured, error and security monitoring processed under our legitimate interest in keeping the Service secure and reliable. Default personal-data capture and session replay are disabled.

We update this list as the platform evolves. Notice of material changes will be provided where required by applicable law or the signed agreement.

§ 06 · RetentionHow long data is kept.

Account data. Retained while needed to provide the provisioned service and handled after closure according to the applicable agreement, legal obligations, and confirmed operational policy.

Traces and detections. The product manifest lists a 14-day reference allowance for the managed preview; this notice does not assert that an automated cleanup job currently enforces it. Actual retention and deletion behavior must be confirmed during provisioning and in any signed agreement.

Server logs and error-monitoring events. Retention depends on the configured hosting and monitoring services and must be confirmed for the provisioned deployment.

Backups. Backup retention and deletion timing are deployment-specific and must be confirmed in the applicable agreement.

§ 07 · SecurityHow we protect data.

Hosted endpoints are configured for TLS, and the application contains scoped-credential and rate-limit controls. Encryption at rest, secret management, log handling, and other controls depend on the provisioned infrastructure and should be validated before sensitive data is sent. This notice is not a security certification or audit report.

No system is perfectly secure. If you suspect a vulnerability or breach affecting your data, email security@pisama.ai.

§ 08 · Your rightsWhat you can ask us to do.

You can request to:

• Access the personal data we hold about you
• Correct or update inaccurate data
• Delete your account and associated data
• Export your data in a portable format
• Withdraw consent for processing where consent is the legal basis

Registry emails. Use the unsubscribe link in an update to stop receiving registry emails. Suppression and consent records may remain to honor that choice. For deletion requests, contact us using the address below.

Email privacy@pisama.ai with your request. Requests are handled within the timeframe required by applicable law and the provisioned agreement.

§ 09 · CookiesCookies and similar technologies.

The marketing site uses essential technologies for routing and authentication. When their corresponding environment configuration is present, Google Analytics, Vercel Analytics, and PostHog load to measure traffic or product usage. Google Analytics may set cookies (for example _ga, _gid); Vercel Analytics is designed to be cookieless; PostHog may use browser storage. Configured advertising pixels (X, LinkedIn, Reddit) may also load. You can block these with your browser’s tracking-protection or ad-blocking settings. The dashboard session cookie is essential for authentication and is separate from the above.

§ 10 · InternationalInternational transfers.

Pisama is operated from the United States. Hosted data may be processed where the configured subprocessors operate; location and any transfer requirements must be confirmed for the provisioned deployment and applicable agreement.

§ 11 · ChildrenChildren’s privacy.

The Service is intended for developers and engineering teams. It is not directed at children under 13, and we do not knowingly collect personal data from them.

§ 12 · ChangesChanges to this policy.

We may update this Privacy Policy from time to time. Notice will be provided where required by applicable law or a signed agreement. The “Effective” date at the top of this page identifies the published version.

§ 13 · ContactContact.

Questions about this policy or your data: privacy@pisama.ai. Security reports: security@pisama.ai. General legal matters: legal@pisama.ai.