Security
How Factagora Enterprise handles your data.
This page describes what the product does today. If your review needs something that is not listed here, ask us and we will tell you where it stands.
Access
Who can get in.
- 01Isolated by organizationEvery request re-checks organization membership on the server before any data is read. People outside your organization get a not-found response, so they can't tell a collection exists.
- 02Roles and invitesThree roles: owner, admin and member. Only owners can delete collections, change roles or delete the organization. Invitations are emailed links that expire after 7 days and work only for the invited address.
- 03Sign-inSign in with Google or with email and password. Passwords are stored as bcrypt hashes, and sessions use an encrypted, HttpOnly, Secure cookie.
- 04Audit logChanges to members, invitations, collections, files, keys and integrations are recorded with who made them. Owners and admins can read the log.
Your data
Where it lives and how it leaves.
- 01Data locationFiles and graph data are stored in Google Cloud's us-east1 region, and the application database on Supabase in AWS us-east-1. The web app runs on Azure East US. All three are in the United States.
- 02Encryption at restStored files and databases are encrypted at rest by the cloud providers: Google Cloud by default, and Supabase with AES-256.
- 03No public file accessPublic access to the file bucket is blocked at the storage level. Files are reachable only through short-lived signed links.
- 04Database accessThe Enterprise database schema is not exposed to any public API role. Only the application servers connect to it.
- 05Uploads and downloadsUploads go straight to storage through signed links that expire in 15 minutes and enforce a file size limit. Download links expire in 5 minutes.
- 06DeletionDeleting a file removes the original and its extracted text from storage. The storage provider keeps a recoverable copy for 7 days, then erases it for good. Facts and index entries from the file are removed at the next graph rebuild.
- 07AI processingDocuments are parsed with Google Document AI. Fact extraction and chat use Gemini on Vertex AI. Embeddings and fact checks use Azure OpenAI.
- 08Model trainingThe AI providers we use, Google Cloud Vertex AI and Azure OpenAI, state that customer data is not used to train their models without the customer's permission.
Keys and limits
What you control.
- 01API keysRotate a collection key at any time and the old key stops working immediately. Personal tokens can be revoked and given an expiry date.
- 02IntegrationsIntegration credentials are encrypted with AES-256-GCM. Google Drive access is limited to the files you pick.
- 03Spend capWith the spend cap on, new indexing, chat, fact check and API search requests are refused once your included usage runs out. Stored documents stay in place.
- 04API logsAPI logs record method, path, status, duration, caller, IP address and user agent. They are deleted after 1, 7, 28 or 90 days depending on your plan.
Need a security review?
Send us your questionnaire or the controls your team requires. We'll answer with what is in place today.
PoC
Bring your messiest folder.
We'll run a PoC on it.
Send us the documents that keep changing. We'll set up a collection and show you the answers, version by version.