End-to-end encrypted communication, in the Absidion app and the web interface. Texts, files and forms — and groups with clear roles, in the platform's permission model.
The server carries ciphertext. The plaintext arises on the device — and nowhere else.
Secure communication is not a foreign body in the toolkit — it is a platform service. You can exchange texts, files and forms in one conversation, in the native Absidion app or in the web interface, with the same security model and the same identity as at any other point of the platform.
Groups, roles and permissions follow the model you know from the specialised processes — not a separate chat logic that would have to live somewhere on the side.
End-to-end encrypted, in app and web, for texts, files and forms — in groups with clear roles.
Messages, attachments and form responses are encrypted on the device and only decrypted at the recipient.
End-to-end encryption in the native Absidion app and in the web interface — both surfaces with a closed key path. Pick the channel that fits the situation.
A conversation can be a short message, a confidential attachment or a structured form. All in the same encrypted channel, with preview, versioning and audit trail.
Group chats with clear roles: who may read, who may write, who may invite, who may delete. Roles follow the platform's permission model — not a separate chat logic.
Internally, with external partners, with citizens — wherever content must not travel through someone else's inbox and the conversation should stay on the case, not in a private chat.
Two case workers clarify a sensitive matter directly on the case — without an external messenger or a plaintext email attachment.
A confidential dossier is handed over via the encrypted channel — with versioning and read receipt — rather than as a mail attachment.
An external person receives a link via the portal, answers a structured form, and can ask questions back at any time — encrypted.
Employees and external partners work in the same group — each with the rights their tenant and role provide.
A citizen writes from the portal to the responsible unit. The conversation stays on the case, not in someone else's inbox.
An operations cell coordinates in a closed channel — push to the phone, fully at the workstation too, all encrypted.
Six areas — from encryption itself through the two surfaces, the supported content and the role model to integration into the platform and the compliance frame.
End to end, with keys on the device — not on our server.
Content is encrypted locally; the server carries only ciphertext. Even we cannot read the plaintext.
Session keys are continuously rotated. A compromised key does not open old messages.
Every device has a visible security fingerprint. New devices on the counterparty's side are explicitly confirmed, with a warning on key change.
Private keys do not leave the device — neither in backups, nor in sync, nor in support cases.
Files, images, voice notes and form responses run on the same key path as the messages.
Built on proven, regularly audited algorithms — no home-grown crypto.
Secure conversation in the Absidion app and the web interface.
iOS and Android, with push, biometrics and background sync — plaintext arises only on the device.
In the browser, without a plug-in or separate install — end-to-end encrypted, with a closed key path.
Several devices per surface, with mutual device confirmation and a visible device list per identity (in the app).
What the app can do, the web can do — and vice versa. No second-class surface, no "PC only" notice.
Readable offline in the app; actions sync on connection — also encrypted at rest on the device.
Alerts for new messages via Apple Push, FCM and web push — the actual content does not travel in the push, but is decrypted locally.
Text, file, form — all in the same encrypted channel.
Direct messages, mentions, quotes, reactions — short and fast, without formal hurdles.
Attachments up to the configured tenant limit, with preview, versioning and optional expiry.
Forms from the form designer as a conversation element — responses land encrypted on the case, not in a mail inbox.
Reply to messages, quote histories, threads per topic — readably ordered even under encryption.
Fix typos or retract a message — visible to all participants, with an audit entry.
Who may see, write and invite — finely steerable, in the platform's permission model.
Closed groups with verified members, internally or across tenants.
Owner, moderator, write, read, guest — each role with clear rights and visible status.
Supervisory bodies read along without altering the conversation — without breaking the key path.
Members are invited with their identity and can be removed in a controlled way — new keys from joining onwards.
External people join via the portal, with their own account, identity and key.
Groups across tenant boundaries are possible — with separate tenant config and clear visibility rules.
A conversation belongs to a case, a project, a contact — not to an inbox.
Conversations hang on the record: case, project, contract, contact. Whoever opens the record sees the conversation — if entitled.
Every message is bound to an identity, with the same ACL checks as the record itself.
Who wrote, edited or read what when — traceable in the platform's audit trail.
A message can kick off a workflow — receipt of a reply, receipt of a form, approval step.
Your own conversations are full-text searchable locally — plaintext index on the device, not on the server.
Retention periods and automatic deletion per group are configurable — encrypted at rest, forgotten under control.
Security is the default — not a feature you have to switch on.
Hosting in Switzerland or the EU area, depending on tenant — encrypted storage at the chosen site.
The platform service runs in the same certified management system as the rest of the Absidion platform.
Key material and conversations are separated per tenant — no shared key space, no shared search basis.
Users can deposit encrypted recovery keys — controlled, without a backdoor master key.
Supervisory exports per tenant with a documented four-eye principle — not secretly, not centrally, but defined.
Regular external tests of the crypto and application stack, with a list of findings and a fix status per release.
Wherever content is exchanged between people, the platform service takes over — without every procedure inventing its own chat.
The Absidion app is the mobile surface for secure communication — end-to-end encrypted with a closed key path.
External attendees join via the portal and chime in encrypted in the same conversation.
Forms from the designer can be sent and answered as an encrypted conversation element.
Messages and form responses can trigger workflows — approval, escalation, automatic reply.
Conversations with contacts land on the record — not in a private inbox.
Confidential consultations and document exchange stay on the case — not in parallel email.
From any Absidion page, navigate to every other process and to the services that work across all of them.
A short demo where we're happy to answer your questions in person. No commitment, no sales theatre.