TERMS / PRIVATE BETA

Terms of Service

These beta terms explain how access, credits, provider credentials, approvals, refunds, and public proof exports work before general availability.

Status: legal review placeholder; last updated 2026-05-18

Private beta terms

Access is invite-only. Proof Foundry can limit features, pause runs, revoke invites, or change beta caps while the product is under controlled launch review.

Proof Credits

Included, trial, and purchased Proof Credits are budget controls for eligible provider/model/compute usage. Credits do not guarantee a provider is available, allowed, or suitable for a project.

Refunds

Unused purchased top-ups can be manually credited or refunded after billing review. Consumed provider spend is not automatically refundable; support can review exceptions with billing evidence and approved manual adjustment.

Provider keys

You are responsible for keys you connect. Proof Foundry must keep keys server-side, scoped, redacted, and revocable, but you should revoke provider-side credentials if you suspect compromise.

Deletion and export requests

Lab admins can request export, deletion, or redaction from the account data-retention surface. Proof Foundry may retain records needed for security, billing, abuse review, legal hold, or already-approved public proof exports.

Public proof exports

You control whether a proof export leaves the lab. Public exports must omit raw secrets, hidden reasoning, private dataset rows, and private repository contents unless you explicitly approve disclosure.

Human approval

High-cost compute, risky provider actions, GitHub writes, and public proof publication can require approval receipts. The system may block actions when approval, budget, or connector scope is missing.