Built for scrutiny.
All in one place.

What Forge actually implements, grouped by the three properties it is built for. For security reviewers, IT and anyone who has to sign off on a tool before it touches company material.

Security and data handling Talk to our team

Each row is marked built, coming or not offered. The last of those is included on purpose. A list that only shows what exists tells a reviewer nothing about where the edges are, and they will find the edges anyway.

Confidential

What leaves, what is kept, and who can reach it.

Your data. Your control.
Designed for regulated environments.

Feature	Details	Status
PII redaction before egress	Email addresses, phone numbers, payment card numbers (Luhn-checked), Indian PAN and Aadhaar are replaced with placeholders before the request leaves for a model.	Built
Reversible masking	Real values are re-inserted into the answer the user reads, so the reply stays usable without the provider having seen them.	Built
Redaction across table cells and page wraps	Column-aware masking for tabular documents, and reconstruction of values split across a PDF line break.	Built
Organisation policy floor	An admin can require redaction across the organisation. A member may be stricter, never looser.	Built
Pre-upload PII report	A count of what was detected is shown before ingestion completes, with the option to cancel.	Built
Public personal-data scan	An open MCP endpoint, usable from Claude and other assistants, that reports and locates personal data in a document so the caller can mask its own file before it goes anywhere. Nothing sent to it is stored or logged.	Built
Names and addresses	US social security numbers, Indian PAN and Aadhaar, email, phone and card numbers are detected today, selectable by region. Names and addresses need a model-based tier, which is built and not yet enabled.	Coming
Original files discarded after extraction	Text is extracted on upload and the original file is deleted immediately. No provider ever receives a file.	Built
Ephemeral chat attachments	A file attached to a single conversation is not indexed and is deleted with the thread.	Built
Access granted per project	Membership is per project rather than per organisation. Being in the organisation grants nothing by itself.	Built
Private threads	Conversations are per member. No administrator query returns another person’s messages.	Built
Retention and deletion	A daily sweep enforces the retention window you set, with a server-side ceiling. Scope is conversation history; documents are removed when deleted.	Built
Encryption	Provider-managed encryption at rest; AES-256-GCM for stored secrets such as API keys.	Built
No training on your data	Commercial no-training terms with every provider in the path. Contractual rather than observable.	Built
Subject access and erasure	Export or erase everything held about one person, run by the operator on request.	Built
Data residency	Data and application compute are in the United States. Program runs execute on a separate provider, constrained to Eastern North America. One region serves every customer; a specific region or compliance boundary is a dedicated deployment.	Built

PII redaction before egressBuilt: Email addresses, phone numbers, payment card numbers (Luhn-checked), Indian PAN and Aadhaar are replaced with placeholders before the request leaves for a model.
Reversible maskingBuilt: Real values are re-inserted into the answer the user reads, so the reply stays usable without the provider having seen them.
Redaction across table cells and page wrapsBuilt: Column-aware masking for tabular documents, and reconstruction of values split across a PDF line break.
Organisation policy floorBuilt: An admin can require redaction across the organisation. A member may be stricter, never looser.
Pre-upload PII reportBuilt: A count of what was detected is shown before ingestion completes, with the option to cancel.
Public personal-data scanBuilt: An open MCP endpoint, usable from Claude and other assistants, that reports and locates personal data in a document so the caller can mask its own file before it goes anywhere. Nothing sent to it is stored or logged.
Names and addressesComing: US social security numbers, Indian PAN and Aadhaar, email, phone and card numbers are detected today, selectable by region. Names and addresses need a model-based tier, which is built and not yet enabled.
Original files discarded after extractionBuilt: Text is extracted on upload and the original file is deleted immediately. No provider ever receives a file.
Ephemeral chat attachmentsBuilt: A file attached to a single conversation is not indexed and is deleted with the thread.
Access granted per projectBuilt: Membership is per project rather than per organisation. Being in the organisation grants nothing by itself.
Private threadsBuilt: Conversations are per member. No administrator query returns another person’s messages.
Retention and deletionBuilt: A daily sweep enforces the retention window you set, with a server-side ceiling. Scope is conversation history; documents are removed when deleted.
EncryptionBuilt: Provider-managed encryption at rest; AES-256-GCM for stored secrets such as API keys.
No training on your dataBuilt: Commercial no-training terms with every provider in the path. Contractual rather than observable.
Subject access and erasureBuilt: Export or erase everything held about one person, run by the operator on request.
Data residencyBuilt: Data and application compute are in the United States. Program runs execute on a separate provider, constrained to Eastern North America. One region serves every customer; a specific region or compliance boundary is a dedicated deployment.

The security overview at /security covers the same ground for a procurement review, including the data processing agreement. Why Forge is built this way is argued on the thesis page.

Built for scrutiny.All in one place.

Confidential

Built for scrutiny.
All in one place.