Trust
Designed so you never hand your data over
A data security product shouldn't become the biggest copy of your sensitive data. Ligurian is built so that it never holds your files at all.
What we keep, and what we don't
| Data | Kept by Ligurian | Where and how |
|---|---|---|
| File and message content | Never | Read in memory to classify, then discarded |
| Snippets and evidence | Never | Written to storage you own: SharePoint, OneDrive, Azure Blob or Amazon S3 |
| Content of cloud workloads | Never | Classified inside your own cloud account; only results leave it |
| Files blocked on a laptop | Never | Held encrypted on that laptop for up to 72 hours so they can be restored, then deleted. Never uploaded |
| Facts about your data | Yes | What it is, where it lives, who can reach it, labels and actions taken. AWS Sydney, backed up in Melbourne |
| Fingerprints of content | Yes | One-way keyed hashes, used to spot copies of the same file. They can't be turned back into content |
| Audit log | Yes | Every action by Ligurian, your MSP or an automated rule. AWS Sydney |
Every event also records where protection took effect. We only call something blocked if it was stopped before it happened. A file removed after the fact is reported as removed, and a detection as a detection.
Where it runs, and who can get in
Onshore by default
The platform runs in AWS Sydney. When Ligurian uses an AI model, the request stays in Australia.
Least privilege
Every connection asks only for the access it needs, and you can review exactly what it was granted.
Logged, in your view
Support access is time-limited and tied to a reason. What we and your MSP do shows up in your audit log.
Gone when you go
Leave, and your tenant is fully purged within 30 days, not kept in a long-term archive.
Your call on automation
Ligurian monitors, suggests or acts at the level you choose, and every automated action can be traced.
No proxy
Your traffic isn't routed through us. Protection uses the platforms' own controls and a light endpoint agent.
Report a security issue
If you think you've found a vulnerability in Ligurian or this website, email security@ligurian.ai. We'll acknowledge it, keep you updated and credit you if you'd like.
Our security.txt has the same details in machine-readable form.
Before launch
- Our list of sub-processors
- Our independent assurance plans
- The test set behind our Australian identifier detection
We'll publish these here. We won't claim a certification we don't hold.
This website, too
This site sets no cookies, runs no analytics or advertising scripts, and loads nothing from third parties. Waitlist details are stored with our hosting provider, Cloudflare, in its Oceania region. Read the privacy policy.
Be first in the hive
We're building Ligurian with a small group of MSPs.