TTransparency centre

How security works

Each measure in plain words, with its current status.

Planned for launch

Google sign-in and profiles are available. Studio features require a connected, configured service; this page is not a claim that they are deployed.

Planned for launch

Encryption in transit

Every connection between your device and Kapsülle is encrypted (HTTPS/TLS). Unencrypted connections are refused.

Planned for launch

Encryption at rest

Studio text and recipient records use server-managed encryption; files have private access. Authorized services can process data. This is not end-to-end encryption.

Planned for launch

Sign-in

  • A second verification step (multi-factor) at sign-in.
  • A notification when a new device signs in.
  • Links sent to recipients are personal and expire.
Planned for launch

Access controls

  • Adding a trusted person opens nothing by itself.
  • You set access per category.
  • Staff access to content is minimised and logged.
Planned for launch

Activity log

Hosting may keep technical access logs. The studio records security and transaction events without private content. Enabled payment and notification providers receive only data needed for their service.

Planned for launch

Backups

Encrypted backups are kept separately and restores are tested regularly. Frequency and retention will be published here.

Planned for launch

Deletion

After identity verification, a deletion request suspends the account. Deletion jobs start after the waiting period shown in your account. Backup and legally required retention need a separate published policy.

Download a copy of your capsule. Keep this file somewhere private.

Planned for launch

When would your capsule be shared?

No automatic reminders or content sharing take place today. Sharing conditions and verification are still in development.

  1. Periodic reminders are planned. A response would keep your capsule on hold.
  2. No response will require further reminders and verification. Missing a notification is not permission to share.
  3. Death verification, recipient authorization and safeguards against accidental sharing must be completed before launch.
In effect today

This site today

  • Google sign-in and profiles are available. Studio features require a connected, configured service; this page is not a claim that they are deployed.
  • When you save in the connected studio, we process the recipients and contact details you enter, relationships, letters, notes, digital access instructions, files, recordings, assignments and plan preferences.
  • Hosting may keep technical access logs. The studio records security and transaction events without private content. Enabled payment and notification providers receive only data needed for their service.