Data handling and security
Organization boundaries
Section titled “Organization boundaries”API requests resolve organization membership and permissions on the server. Organization-scoped database tables use PostgreSQL row-level security, and the application role does not bypass RLS. A guessed ID from another organization returns Not found rather than exposing its data.
These controls do not make it safe to share your session, runtime tokens or exports with unauthorized people.
Evidence
Section titled “Evidence”Repository analysis stores source-backed evidence with credential redaction. Restricted evidence requires Analyst or higher. Redaction is a defensive control, not a license to commit secrets or submit arbitrary sensitive text.
If a source credential was exposed, remove it from the source and rotate it at the issuing system. Resolving a ModelFence finding does not revoke that credential.
Runtime ingestion
Section titled “Runtime ingestion”Ingestion tokens are integration-scoped and stored as hashes by the application. Rotate or disconnect a source when its token is no longer trusted. Prompt and completion bodies are not supported runtime content. An attribute allow-list drops unsupported fields and reports how many were dropped.
You remain responsible for what your instrumentation puts in allowed fields, URLs, asset names and metadata. Send the least information needed for the investigation.
Sessions and requests
Section titled “Sessions and requests”The production application uses an OIDC code flow with PKCE and a server-managed cookie session. State-changing browser API calls require the application’s CSRF header. CORS is not a mechanism for granting arbitrary third-party access.
The docs website is public and static. It has no session or access to your ModelFence organization. Never post tokens, raw private evidence or customer data as documentation examples.
Reports and retention
Section titled “Reports and retention”Exports remain sensitive organization artifacts even when evidence is redacted. Apply your storage, distribution and deletion policies. The current UI does not provide retention configuration; deployment operators must review their database, backup and logging policies separately.
This page describes implemented controls. It does not claim SOC 2, ISO certification, a particular regulatory status or independent audit assurance.