Your own database
Each customer receives a separate PostgreSQL database. Customer business data is not stored in a shared table with a tenant identifier.
Security and data residency
Your contracts stay separated, controlled and accountable.
Fratera separates customer data at database level and enforces access inside the database. EU and US deployment regions are available, with the same core security architecture in every edition.
Separate databasefor every customer
EU or USdeployment region
Database-enforcedaccess control
Encryptedat rest and in transit
Security by design
Isolation is the starting point.
Not an enterprise add-on.
Contract repositories contain commercial terms, personal data and documents that should never cross a customer boundary. Fratera therefore gives every customer a separate PostgreSQL database rather than separating tenants with an application filter inside one shared database.
Inside that database, row-level security applies the signed-in user’s permissions to direct data access as well as the application. Physical separation and database authorization solve different problems; Fratera uses both.
EU or US deployment
Your region is selected when the workspace is created. The customer database, document storage and regional application services are deployed for that region.
Encryption at rest and in transit
Data is encrypted at rest using AES-256 and protected in transit with TLS 1.2 or later. Database connections and document storage are encrypted.
Identity and access
Compose access from reader, contributor, approver, procurement and administrator capabilities. Restricted visibility groups protect sensitive records, while delegation-of-authority rules control approval thresholds.
Use email sign-in or OpenID Connect SSO with Microsoft Entra, Okta or another OIDC provider. Your administrator can make SSO the only way in, self-serve from Settings. A pre-flight check first lists anyone who would be locked out, and outside approvers and signers keep their links. Roles remain controlled inside Fratera; directory sync through SCIM is planned, not presented as a current capability.
Audit trail and data lifecycle
Approval decisions, access changes and key contract and vendor record changes are written to the audit trail. A deleted record stays recoverable for 30 days before it is purged, and an administrator can keep it longer, up to a year. Administrators can export customer data and arrange deletion at the end of the relationship.
Database-enforced authorization
Row-level security is default-deny and evaluates requests as the signed-in user. The same authorization boundary applies when data is accessed through the interface or through direct API requests.
Sign-in activity and access changes
Settings › Compliance shows who signed in, when, from which IP address and on which device, including sign-outs and timed-out sessions. Sign-in records are kept for a year.
The access-change log records every change to roles, permissions and approval rules, with who made it and when.
Signing evidence
When the last person signs, Fratera adds an evidence page, seals the PDF with a trusted timestamp and files it on the contract. Fratera signatures are simple electronic signatures. They are not advanced or qualified signatures.
AI with boundaries
AI can assist. It cannot grant access or make the decision.
Fratera keeps model output outside authorization, workflow, money and record-changing decisions. Read-only questions run through controlled product tools under the signed-in user’s existing permissions.
Contract answers are bounded to documents the user can already access and include source-page evidence so the answer can be checked.
When the AI reads a document, the document goes to our AI provider, Mistral AI, through its endpoint in your region. Mistral is listed in our sub-processors, and an administrator can switch AI reading off for the whole workspace.
Neither Fratera nor our AI provider uses your content to train models.