Registered delivery, by API
Delivered,
and provable.
Email tells you a message left. Perlata tells you it arrived, to whom, and at what moment, recorded so it can be checked when disputed.
-
Identified recipient
The recipient completes a verification step before the content is released, and the record states exactly what that step established.
-
Tamper-evident record
Every step is written to a record that cannot be altered without the change showing. The whole is then sealed and anchored outside the system.
-
Evidence that stands alone
You end up with one evidence package, kept in an archive that only appends, readable years later without us in the room.
Frequently asked questions
What does Perlata record for every message?
On what ground this was the right address, with the substantiation and the weight of it. You have to supply that substantiation as the sender anyway, whichever provider you use. The other side can check the evidence package themselves, with standard tools, without us and without an internet connection. And the record is anchored externally every hour with two independent timestamp authorities, so we cannot rewrite history either.
Is the content of the message in the email?
No. The email announces the message; the content is released only after the recipient has completed the verification step, and that step cannot be switched off. If you ask for a lighter check as the sender, we raise it to at least a check of the address, because opening a link establishes nothing.
One thing is yours to decide: the subject you supply does appear in the announcement, so the recipient knows what they are identifying for. So do not put in it what you would rather keep out of an ordinary email. The content itself is stored encrypted, including inside the evidence chain.
How long is the evidence kept?
Seven years by default, and a sender can agree a longer term for their own messages, which matches the longest limitation periods. The archive is write-once: a retention period can only be extended, and not even we can shorten it.
If you stop using Perlata the evidence stays for the full term. The public keys travel inside every package, so you can verify your files years later without us.
What does the data processing agreement cover?
You sign a data processing agreement under article 28 GDPR, listing the sub-processors, the storage location and the notification chain in case of a breach.
All data stays within the European Union, in Frankfurt. Amazon Web Services is the sub-processor for archive storage, key management and mail delivery. Personal data is stored encrypted, including inside the evidence chain, so an erasure request can be carried out without the evidence losing its verifiability.
What is Perlata liable for?
We limit our liability up front, as article 13(2) of the eIDAS Regulation allows, and that limitation will be set out in the terms of service. Those terms do not exist yet: we will draw them up before the first customer signs, and you will see them before you commit to anything. Ask us now and we will send you the draft.
One thing belongs on the table with it, because it allocates risk: with a qualified service, intent or negligence is presumed under article 13(1), and with us you have to prove it.
Is Perlata a qualified service under eIDAS?
No. Perlata is not on any EU trusted list, so the legal presumption of receipt in article 43(2) of the eIDAS Regulation does not apply here. What you get instead is a file the opposing party can verify for themselves, and the ground for the address, which that presumption does not cover anyway.
Join the waitlist
Leave your address and we will get in touch when early access opens.
Early access in Q4 2026.
Rather write to us? [email protected]