Security & Compliance
Proofwork is designed so you can adopt AI skills without introducing new data-handling risk. Here's exactly how it works.
Proofwork is never in the inference path
Your documents, prompts, and conversation history stay between you and your AI provider (Anthropic, OpenAI, etc.). Proofwork provides reference data and reasoning scaffolds — we never see, process, or store the content of your queries.
Architecture
What Proofwork returns
Structured reference data: tariff schedules, CBP ruling precedents, chapter notes, and classification instructions. These are pre-compiled from public government sources and frozen at build time. No live scraping, no customer data in the response.
What Proofwork never sees
The full conversation between you and your AI assistant. The AI calls Proofwork's tools with a product description (the tool input), receives reference data back, and reasons over it locally. Proofwork doesn't see the surrounding conversation, attached documents, or the AI's final output.
What Proofwork stores
User accounts (email, display name), organization memberships, subscription state, and aggregate usage counts (calls per period, per tool). We do not store tool inputs, tool outputs, product descriptions, or classification results. Tool calls are stateless — nothing from the request body is persisted.
Infrastructure
Google Cloud Platform
All services run on GCP in
us-central1
(Iowa). Google Cloud is SOC 1/2/3, ISO 27001, ISO 27017, ISO 27018,
and FedRAMP certified.
Cloud Run (serverless)
Both the web app and MCP servers run on Cloud Run — fully managed, auto-scaling, with Google-managed TLS. No persistent VMs, no SSH access to production.
Cloud SQL (Postgres)
User accounts and usage data are stored in Cloud SQL with automated backups, encryption at rest (Google-managed keys), and encryption in transit.
Secret Manager
API keys, signing keys, and service credentials are stored in Google Secret Manager — never in code, environment files, or container images.
Authentication
Identity Platform
User authentication is handled by Google Cloud Identity Platform with email/password, Google, and Microsoft sign-in. Proofwork never stores or handles raw passwords — Identity Platform manages credential verification, MFA, and session security.
OAuth 2.0 for MCP connections
MCP clients (Claude, ChatGPT) connect using standard OAuth 2.0 Authorization Code + PKCE. Access tokens are JWT-based, RS256-signed, and scoped to the specific MCP server being accessed. Tokens expire after one hour.
API keys for programmatic access
Developer API keys are bcrypt-hashed before storage. Keys are user-bound and participate in the same usage metering and freemium gating as OAuth tokens. Keys can be revoked instantly from the account page.
Data handling
| Data type | Collected | Stored |
|---|---|---|
| Product descriptions (tool input) | Processed in-memory | Not stored |
| Classification results (tool output) | Returned to caller | Not stored |
| Conversation context | Never received | N/A |
| User account (email, name) | At sign-up | Yes (Cloud SQL) |
| Usage counts (calls per period) | Per tool call | Yes (Cloud SQL) |
| Payment info | At checkout | Stripe only (PCI DSS Level 1) |
Development practices
Automated CI/CD
Every code change runs through automated lint, format checks, and 160+ tests before deployment. Database migrations are applied atomically via Alembic before new code goes live.
Monitoring & alerting
Cloud Run 5xx errors and Stripe webhook failures trigger immediate email alerts. Application logs are retained in Google Cloud Logging with structured correlation IDs.
Secrets management
No secrets in code or environment files. All credentials are stored in Google Secret Manager and injected at deploy time. JWT signing keys are persistent and managed.
Dependency management
Python dependencies are pinned via
uv.lock
for reproducible builds. Docker images use multi-stage builds
with minimal runtime surfaces.
Compliance
Proofwork runs entirely on Google Cloud Platform infrastructure that is independently audited and certified:
SOC 1/2/3
GCP infrastructure
ISO 27001
GCP infrastructure
ISO 27017/27018
GCP cloud security
PCI DSS Level 1
Stripe payments
FedRAMP
GCP infrastructure
HTTPS everywhere
Google-managed TLS
Proofwork does not yet hold its own SOC 2 Type II certification. Given our architecture — no customer data retention, stateless tool calls, GCP-managed infrastructure — the compliance surface is narrow. If your organization requires a formal attestation, please contact us to discuss your specific requirements.
Questions?
For security inquiries, vulnerability reports, or compliance documentation requests:
[email protected]