# Security questionnaire pack

Reusable answers for a prospect security review (GTM P1.4, cockpit
dev#1146). Copy from this file; do not invent a DPA, a SOC 2 report, or a
control the security page does not already label.

This pack describes current hosted-beta practice, not a certification.
Where a control is planned, unpublished, or a customer decision, the status
column on https://productionmaster.dev/security wins.

Last assembled: 2026-09-10.

## Architecture

Production Master is an evidence-first incident investigation product. Approved
production signals become a cited report. Proposed remediations stop at a human.

Two operating models exist today:

- Hosted closed beta: web UI and edge APIs on Vercel; Postgres and auth on
  Supabase; compute workers on a GCP GKE fleet. Available to closed-beta teams.
- Self-host via Helm: the same runtime installed into a Kubernetes cluster the
  customer operates. Available to closed-beta teams, not generally available.
- On-premises residency: region pin, offline model import, restore drill.
  Available to closed-beta teams.
- Air-gapped: fully disconnected install. Planned — not shipped.

The product depends on no single host. There is no marketplace / paid-components
seam in the shipped app.

## Data flows

1. Intake. An approved signal enters through a public API or webhook. Connector
   credentials are scoped per source; read-only is the default posture.
2. Investigation. The pipeline reads the agreed sources inside the agreed
   window, writes an append-only event log, and produces a cited report.
3. Action. Opening a pull request, paging on-call, or flipping a flag is a
   high-risk remediation. The matrix auto-approves none of those. A person
   clears each one, or issues a time-bounded capability grant. Draft-to-ready
   on a GitHub PR is a human GitHub action; the product has no path that flips
   it.
4. OSS dogfood (hosted). GitHub issues are ingested only from
   ProductionMasterAI/production-master and
   ProductionMasterAI/production-master-mcp. Private repos are out of scope.
   Public traces may keep issue text, code paths, stack traces, citations,
   model names, and costs. Tokens, secrets, env assignments, and account IDs
   are stripped.

Nothing in this pack claims that a customer incident has been published.

## Current hosted-beta operators

This is not a formal subprocessor register and not a notification process.
Those are unpublished. The names below are the operators of the current
hosted-beta deployment:

- Vercel — web app, marketing site, and serverless edge APIs
- Supabase — Postgres, auth
- Google Cloud — GKE fleet compute
- GitHub — source, webhooks, draft-PR proposal target for dogfood
- Customer-chosen LLM provider — BYO-LLM keys; provider terms are confirmed
  per deployment before evidence is connected

Self-host customers do not send investigation evidence through the hosted
operators above; the Helm install runs inside their cluster.

## Retention and deletion

No approved default retention, backup, deletion, or residency policy is
published. Do not quote a number of days. For a self-host install, retention
is the customer's. For hosted beta, agree the window for evidence copies
before the first investigation runs.

Encryption and key-management commitments are likewise unpublished. Do not
imply AES-at-rest, CMEK, or a KMS story.

## What we will not say

- We are SOC 2 / ISO 27001 / HIPAA certified. We are not.
- We have a signed DPA on this page. We do not.
- We publish a subprocessor-change notification SLA. We do not.
- Air-gap is available. It is planned.
- Dogfood runs against private product repos. It does not.
- Auto-fix merges its own PRs. It never does.