MIDAAS

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

Who sees what

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

Against abuse and runaway cost

Deleting means deleting

AI providers

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

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.