BlueLandscape · Files · Secure EU storage
A private EU bucket. Audited transit. Encrypted at rest.
Where your bytes actually live, and what we honestly do and don't promise about them. EU-resident by design — and clear about the one thing AI analysis rules out.
What we guarantee
Four things that are true for every file
Private bucket
A single private bucket in the EU (AMS3), block-all-public, with per-account key isolation. No file is ever served from a public URL.
Audited EU transit
Every byte proxies through our EU API — no presigned URLs are ever handed out — so the data path is provably EU-resident and auditable end to end.
Scanned inline
Uploads are virus-scanned on the path, before the object lands. Infected files are blocked, not quietly stored.
Encrypted at rest
Stored objects are encrypted at rest. Bytes sit on infrastructure that stays within EU borders.
What we will not claim
We do not say "we can't read your files"
That claim would be a lie. To run AI document analysis — the whole point of the product — our server has to decrypt and read the plaintext. So true zero-knowledge, client-side end-to-end encryption is off the table while those AI summaries exist.
What we promise instead is concrete and verifiable: audited EU infrastructure, encrypted at rest, scanned inline. That's the honest ceiling, and we'd rather state it plainly than market a guarantee we can't keep.
Same vault, every tool
The same EU-resident store backs the rest of the suite: supplier PDFs attached to your invoices, and research artifacts kept with your interviews — all under the same security posture.
Store on infrastructure you can reason about
Sign up for free. Questions about security? Email hello@bluelandscape.io.
Create an accountMore on Files: Overview · Pricing · AI document analysis