Hosting in London
OmniaGraph runs on Amazon Web Services in the London region (eu-west-2). Uploaded files are stored in a private Amazon S3 bucket in the same region, with public access blocked.
Investors and lenders put private documents next to public evidence. This page sets out where OmniaGraph runs, how those documents are protected and which companies process data for us.
Public research is shared by every client. Your watchlists, monitors, findings and private documents belong to your workspace alone.
OmniaGraph runs on Amazon Web Services in the London region (eu-west-2). Uploaded files are stored in a private Amazon S3 bucket in the same region, with public access blocked.
Each uploaded file is encrypted by the application before it is stored, and its extracted text, sections and summaries are encrypted in the database. S3 adds its own encryption at rest.
Every document belongs to one workspace. It can be attached only to that workspace's monitors, and searches only reach that workspace's documents and the public research every client shares.
CSV and JSON exports leave private material out by default. It is included only when someone with permission to use private documents asks for it explicitly.
The site, the app and the API are served over TLS 1.2 or 1.3, and plain HTTP is redirected to HTTPS. Browsers are told to use HTTPS only for a year (HSTS). Session cookies are marked Secure and HttpOnly.
Every webhook is signed with HMAC-SHA256 over its timestamp and body, so your system can check that it came from OmniaGraph and was not changed.
To read a document and extract findings from it, OmniaGraph sends its text to an AI model. Embeddings, the numeric index used to search your documents, are made the same way.
Monitor runs, document reading and search send model requests through OpenRouter to the providers listed below.
Each of those requests tells OpenRouter to use only providers that do not collect the data they are sent.
A monitor sends the sections of a document that match its questions, not the whole workspace.
Access is granted by your workspace owner, and the strongest permissions are off until they are needed.
Nobody can create an account. A workspace owner invites each user.
OmniaGraph stores no passwords. Users sign in with a six-digit code sent by email. Codes expire after 10 minutes and allow five attempts.
Where it is switched on, a user who already has an OmniaGraph account can sign in through a Rodan account, a login operated by Rodan Analytics Limited. It creates no accounts, accepts no invitations and sets no roles, and the emailed code stays available.
Owners, members and viewers. Viewers can read findings but cannot use private documents.
A workspace must have private documents turned on, and a user must have permission to use them.
API keys and access tokens are stored as SHA-256 hashes, never as the key itself.
A small number of OmniaGraph operators can open a workspace to support it. Each time they do, it is logged.
For a security questionnaire, or to ask us to export or delete your workspace's data, email [email protected].