Security
Security
Your manuals, contracts and drawings are in here. This is how we look after them.
Last updated November 18, 2026
This page describes the safeguards in MIDAAS as it is built today, in plain terms, and what we do not do. We are a small company and have not yet had an independent security audit; we would rather say so than imply otherwise.
Getting in
- No passwords. Sign-in is by a one-time link or six-digit code sent to the person's email. Codes expire quickly and are rate-limited.
- A required second step for administrators. Workspace administrators, the permanent administrator and our console staff must also use a passkey or an authenticator app, with recovery codes. A passkey is bound to MIDAAS's address and cannot be used on a look-alike site. Administrators can require it for everyone from a given email domain.
- Single sign-on (Google, Microsoft Entra ID, Okta) is available on the Enterprise plan, on request.
- Who may join. Each workspace admits people by invitation or by approved email domains, as its administrators choose.
- API keys for services and scripts belong to one workspace, are shown once, and are stored only as a fingerprint.
Who sees what
- Roles and permissions. Seven ready-made roles and 22 permissions, with overrides on any single collection, so the contracts folder and the service manuals need not be open to the same people.
- Workspaces are kept apart. Every record, search index entry and file belongs to exactly one workspace, and every request is limited to the workspace whose address it came to. Workspaces share our infrastructure; they do not share data.
- Support only by invitation. Our staff can enter a workspace only when its administrators allow it, for a time they choose. Each visit is recorded in both our records and the workspace's, and emailed to its administrators. An emergency access link goes only to the permanent administrator.
A record that cannot be quietly edited
Sign-ins, uploads, deletions, permission and role changes, support visits and settings changes are written to an append-only audit trail with who and when. Each entry carries a fingerprint that includes the one before it, so an entry cannot be altered or removed without the chain showing it, and the chain can be checked at any time.
In transit and at rest
- Encrypted connections only. Every request is served over HTTPS.
- Encrypted storage. The database and file storage are encrypted at rest by our providers. Secrets MIDAAS holds for you, such as authenticator secrets and the keys of a connected storage source, are encrypted again with a key kept outside the database, and are never shown back after they are saved.
- Files by expiring link. Original documents and page images are delivered through signed links that expire, not public addresses.
- Session cookies that scripts cannot read, that are not sent from other sites, and that only travel over HTTPS, with protection against requests forged by other sites.
Against abuse and runaway cost
- Rate limits on sign-in, codes, the workspace finder and the site assistant.
- Guardrails on every question. Oversized inputs and known prompt-injection attempts are stopped before they reach a model, and the answering model is instructed to answer only from your documents.
- Spending limits. Every AI call is metered per workspace, with a daily ceiling and automatic pauses for a failing model, so a script gone wrong cannot run up a bill.
- No half-finished states. Each step of reading a document commits fully or not at all, with a defined retry for every failure.
Deleting means deleting
- Deleting a document removes its text, page images, search index entries and the AI work made from it, from every collection it was in.
- A document removed from a connected source waits for an administrator's approval before it is deleted, unless the workspace turns that question off.
- Deleting a workspace removes every row, search index entry and file that belongs to it.
AI providers
- No training on your content. We use providers' commercial services, whose terms prohibit using what we send to train their models. Our privacy notice names them.
- Only what is needed. To answer a question, the model receives the question and the passages and page images retrieved for it, not your whole library.
- Our AI page covers this in more depth.
Run it in your own cloud
For organizations that need their documents to stay inside their own account, the MIDAAS Framework runs in your cloud, next to the data it reads. In that case your own security controls and provider agreements apply.
What we do not do
- We do not sell information or share it for advertising.
- We do not handle patient health records, payment card data or other regulated records unless a signed agreement covers them and says how.
- We do not claim certifications we do not hold. We have no SOC 2 or ISO 27001 report today.
If something goes wrong
If we learn of unauthorized access to a customer's information, we tell that customer without undue delay, and aim to within 72 hours, with what we know and what we are doing about it.
Reporting a problem
If you believe you have found a security problem, tell us through our contact page with "Security" in the subject. Please give us a reasonable time to fix it before telling anyone else, and do not access information that is not yours. We will acknowledge your report and tell you what we find.