TrustLayer
☾ Book a demo
← Part of TrustLayer Mail

Every email. Kept as evidence.
Found in seconds.

The Compliant Email Archive journals a copy of everything your organisation sends or receives, as it happens, into a tamper-evident store that the right people can search in seconds.

The problem

An archive only matters on the day somebody asks.

And on that day, producing the email is the easy half.

The hard half is proving it is the original. That nothing was altered. That nothing was quietly deleted the week before anyone thought to ask. That the person who left in 2023 has a record too, even though you stopped paying for their mailbox.

Search that takes an afternoon has already failed. So has a retention policy nobody has looked at since it was set.

One email, end to end

What happens between sent and searchable.

1
Sent
Journalled

A copy taken as it happens, not swept up later.

2
Stamped
Fingerprinted

Sequential number, timestamp, digital fingerprint.

3
Sealed
Encrypted

AES-256 on ingestion, before it reaches storage.

4
Read
Indexed

Body, headers, attachment names and extensions.

5
Asked
Found

Lucene search. Wildcards, Boolean, fuzzy. Seconds.

The fingerprint is the point. It is what turns a pile of stored email into something you can put in front of a regulator and say: this is the whole record, and none of it has been touched.

Three things people confuse

A backup is not an archive.
Nor is Microsoft 365.

All three are worth having. They answer different questions, and only one of them answers a regulator.

What you need it forBackupM365 archivingThis archive
Restore the estate after an outageYes——
Prove an email was never altered—PartlyYes
Prove an email was never sent—PartlyYes
Find one message across years, in seconds—PartlyYes
More than two eDiscovery searches at once——Yes
Read mail that is under litigation hold——Yes
Keep a leaver's mail without their licence——Yes
Audit who opened what, as it happens——Yes
Take your data out as .eml, .pst or .pdfPartlyPartlyYes

Microsoft 365 archiving is capable, and for some organisations it is enough. The limits above are its published ones: two simultaneous eDiscovery searches, no access to mail on litigation hold, no retention for a leaver without an active subscription, and audit that can be switched off without notification, which is what makes tamper-evidence hard to demonstrate. Microsoft publishes its eDiscovery limits.

Who can see what

The archive watches the people watching it.

Administrators see nothing

An admin account has no access to archive content at all. If somebody needs it for their role, that is a separate, deliberate grant.

Opening someone else's mail is logged

Any access by a person who was not a sender or recipient is audited in real time, and your nominated Data Guardians are told.

Shortening retention takes two

A reduction needs a second approver holding the Data Guardian role. No single account can quietly shrink what you keep.

Moving your archive

Leaving the old one is the hard part.

Which is why most comparisons skip it, and why we scope it before you sign anything.

Years of mail sitting in a system you have outgrown is not a technical problem so much as a risk you are being asked to accept sight unseen. We would rather show you the plan first. It runs as a managed migration through a specialist partner, scoped, assessed and reported before a single message moves.

01
Nothing stops

New mail starts archiving with us on day one, while the history moves in the background. The old archive stays readable throughout. There is no window where you are between two systems with neither of them complete.

02
History from wherever it lives

Historic mail can be pulled straight from live mailboxes on any platform - Microsoft 365, Google Workspace, Exchange, Outlook.com, anything speaking IMAP or POP3 - including shared mailboxes and Exchange Online archives. Exports from an old archive come in as .pst or .eml.

03
Scoped before it is priced

The first conversation covers your volumes, your retention obligations and who does what. You get a plan and a report before you commit, and we will tell you up front if the volume makes the import chargeable.

Two things worth knowing before you start

Getting data out of your current archive is your vendor's job, not ours. We can often help with tools and professional services, and which of those apply depends entirely on what you are leaving. It is the first thing to establish, because it is the part with the longest lead time.

Imported history is not the same as journalled mail. Anything we pull from a live mailbox arrives with its metadata intact, but nobody can prove it was unaltered before it left that mailbox. Mail journalled from the day you switch on carries the full tamper-evident chain. If a regulator's window reaches back before your start date, that distinction matters and you should plan for it.

The detail, without the meeting.

Ask us something specific →
How it is sold

An add-on to Email Security, within the Mail layer. Not a standalone product, and not something you have to take to get Mail.

Retention

Indefinite by default. Configurable shorter, deletes automatically at the age you set. No ceiling to negotiate.

Mail systems

Microsoft 365, Google Workspace, Exchange, and hybrid estates running cloud and on-premise at once.

Connections

IMAP, POP3, EWS and Microsoft Graph. Many-to-one and one-to-many tenants.

Also archived

Microsoft Teams messages. Outlook calendar items. Folder replication for Exchange and Exchange Online.

Search

Apache Lucene. Wildcard, Boolean, proximity and fuzzy. Attachment names and extensions indexed.

Where you search

Browser, or the Outlook add-in. Same interface in both.

Encryption

TLS in transit. AES-256 on ingestion and at rest, applied before storage.

Sign-in

Multi-factor, via ADFS, Microsoft 365, Okta or another OAuth provider.

Getting data out

Restore into the live mailbox, or export as .eml, .pst or .pdf. Per user, or across the whole archive.

Getting data in

Historic mail pulled from live mailboxes. .eml exports from an old archive imported.

Storage

Deduplicated, so one copy is held however many people received it.

Migration

Managed through a specialist partner. Scoped and reported before anything moves, run in parallel so nothing stops.

Where the answer is no

Things we would rather you heard from us.

You will find out anyway. It is cheaper for both of us if you find out now.

01
It is not a backup

A backup is a point-in-time copy for disaster recovery. This is a continuous, tamper-evident record for compliance and eDiscovery. A backup cannot prove an email was unaltered before it ran, and it misses anything sent and deleted between two of them. We do not sell backup.

02
It will not keep you working through an outage

You can read archived mail during a Microsoft 365 outage. You cannot send and receive from it. If riding one out is a board-level requirement, that is email continuity - a different product, and we would rather say so now.

03
It cannot search inside encrypted mail

If a message is encrypted by the mail client, it is archived encrypted. We index what is readable - sender, recipient, subject, date, headers - and the message can be downloaded and decrypted to read.

04
It does not supervise Slack or Zoom

Teams messages are archived. Our CASB shows who is using Slack and Zoom and controls access and file movement. Supervising what is said inside them is a different job, and other products do it properly.

Bring your
volumes.

Thirty minutes with someone who has moved an archive before. We will tell you what your incumbent will and will not hand over, and roughly what the move looks like, before you commit to anything.

Book a demo
Live platform, your questions.
Book a demo
Already with BT, an MSP or a reseller?
It can be switched on through them.
How →