BankID, locked to a person
The recipient verifies their identity with BankID. The link opens only for the personal identity number you have entered.
Send sensitive content.
From your own address.
Qlave Mail is your everyday email with a secure mode. When you choose Secure message, the message and attachments stay protected and are shown only once the recipient has verified their identity.
Product overview · PilotChoose secure mode
One choice before Send.
You write the message and add attachments as usual and choose Secure message. For the recipients you choose the protection: BankID locked to a person, a one-time code or a personal link.
In secure mode the content does not travel in the email itself.
AT THIS STEP
You also choose how many days the link is valid.
An illustration of the flow in Qlave Mail. No accounts are connected and no emails are sent here.
01 / SEND SECURELYThe content stays.
The content stays.
The invitation goes.
In secure mode the content is not sent in a regular email. The message and attachments are stored in Qrona’s Secure File Sharing, and each recipient gets an invitation from your own mailbox with a personal link. The content is shown only once the recipient has verified their identity.
- The same compose window
- You write and attach files as usual. One choice decides whether the email goes as usual or as a secure message.
- One invitation per recipient
- Each recipient gets their own invitation and their own link. Cc and Bcc are not used in secure mode.
- An optional greeting
- A short text can be included in the invitation. It is visible before verification, so it should not contain anything sensitive.
- A time limit
- You choose how many days the link is valid. Once that time has passed, the content can no longer be opened.
02 / PROTECTION TO MATCH THE CONTENTThree levels.
Three levels.
Your choice.
One-time code
The recipient gets a one-time code by text message or email and enters it to open the content.
Personal link
The simplest level. The link is personal to the recipient and valid for the time you have chosen.
Choose BankID when the content is at its most sensitive, such as personal data, contracts or financial documents.
03 / THE RECIPIENT’S PATHVerify.
Verify.
Read and download.
The recipient does not need a Qlave Mail account. The invitation comes from your address, and the link leads to Secure File Sharing, where the recipient verifies their identity in the way you have chosen.
- The invitation
- Comes from your mailbox, with you as the sender and without the protected content.
- Verification
- BankID, a one-time code or a personal link, as you choose.
- The content
- The message is shown and the attachments can be downloaded for as long as the link is valid.
- Traceability
- The sending is recorded in the organisation’s audit log in Qlave Mail.
04 / TWO WAYS TO SENDRegular when that is enough.
Regular when that is enough.
Secure when it is needed.
Not everything needs to be sent securely. In Qlave Mail you choose for each email, based on what it contains.
Your email takes
the usual route.
Qlave Mail hands the email to your email service. From there it is handled as a regular email by the provider and the recipient.
Microsoft 365 · Google WorkspaceThe content stays
in a protected space.
The recipient gets an invitation from your address and verifies their identity before the message and attachments are shown.
Built on Qrona’s Secure File Sharing. Requires Qrona with the Secure File Sharing package, and each user connects Qlave Mail in Qrona once.05 / WHO SENDS IT?You remain
You remain
the sender.
Qlave Mail prepares the email, or the invitation when you send securely, and hands it over to your connected mailbox. Microsoft 365 or Google Workspace handles delivery from there. You keep your email address and do not need to move your mailbox.
Microsoft 365
Email is handed over through Microsoft Graph with the connected user’s permission.
Google Workspace
Email is handed over through the Gmail API after the user has approved the connection.
The integrations must be enabled and approved for your organisation. Support for other providers through IMAP/SMTP is part of the future plan.
06 / ACCESS WITH A PURPOSEThe right permissions.
The right permissions.
A clear purpose.
Qlave ID handles sign-in to the app. You approve the mailbox connection separately with Microsoft or Google, and you choose what Qlave Mail may do. You do not give your mailbox password to Qlave Mail.
- Send on your behalf
- Always included. Access is tied to the user’s connected mailbox.
- Find recipients
- Contact permissions are used to suggest addresses as you type.
- Read and organise email
- Optional. Turned on only if you choose it when connecting the mailbox, for the inbox, folders and search in Qlave Mail.
- Calendar
- Optional in the same way, to view and book in the calendar.
- Disconnect
- A connection can be removed. Its stored access credentials are then deleted from Qlave Mail.
07 / PROTECTION IN THE APPContent and history.
Content and history.
Each in its own place.
Encrypted storage
Email content, attachments and archive copies are encrypted with the organisation’s key. A file is encrypted before it is sent to the app’s storage.
Events you can follow
The audit log links events in a hash chain, allowing changes to the chain to be detected. Log details describe events, not the content of your emails.
A choice of file storage
An organisation can use an approved storage profile or connect its own compatible storage. Email content and attachments are not distributed through a public CDN.
Storage encryption protects information in the app’s storage, but it does not make a regular email encrypted all the way to the recipient. Content that should not travel in a regular email is sent securely.
08 / UNDERSTAND THE STATUSSent is
Sent is
one step along the way.
A clear status should reflect what the system knows. That is why there is a difference between an email waiting in the queue, being handed to the email service and being read by a person.
- Queued
- The message is waiting to be handed over. A temporary error may trigger another attempt later.
- Sent
- The email service has accepted the handover. This is not a guarantee of inbox delivery or a read receipt.
- Needs attention
- For example, a connection may need to be approved again, an attachment may be too large or a sending attempt may have failed.
If sending is interrupted and the outcome is unclear, the user may need to check Sent in their mailbox before sending again.
START WITH THE RIGHT APPROACHYour requirements.
Your requirements.
Our next conversation.
Tell us about your email environment and the information you need to send securely. We will work through integrations, protection levels and storage together.
Talk to us about Qlave Mail Back to Qlave Mail