Why echoBOS?

Learn in detail why conventional cloud services are problematic for emergency service organisations – and how echoBOS solves these problems.

Why conventional cloud services are problematic

Authorities and emergency service organisations are subject to special requirements for data protection and information security

CLOUD Act & Third-Country Access

Messengers from US providers are subject to the CLOUD Act: US authorities can demand the disclosure of stored data – even from servers in Europe and without the knowledge of those affected.

EU Servers Alone Are Not Enough

The physical server location alone does not guarantee data sovereignty. What matters beyond that are organisation-wide policies, automated structures and a separation of organisations directly in the database.

Metadata Analysis

Even with encrypted content, metadata is collected: who communicates with whom, when, how often and from which location. This data has high informational value.

Missing Data Isolation at Organisation Level

Conventional messengers are not designed for organisation-wide data isolation. Official and private communication takes place on the same devices – without technical separation at database level.

No Audit Logging

Without traceable logging, it cannot be proven who accessed which data and when. This is a compliance risk for authorities.

No Device Access Protection

Consumer messengers offer no way to enforce biometric unlock organisation-wide. Each member decides for themselves – a security risk with lost devices.

Our Security Architecture

echoBOS was designed from the ground up for the requirements of emergency service organisations

German Servers

All data is stored and processed exclusively on servers in Germany. German data protection law applies.

Tenant Separation

Row Level Security separates the organisations' data directly in the database. Each organisation only sees its own content.

Transport Encryption

All data transmission between app, web interface and server is encrypted via TLS. Unencrypted requests are redirected to HTTPS.

Protected Files and Passwords

Files from chat and file storage can only be retrieved via time-limited, signed links that are issued only after the permission has been checked. Passwords are stored exclusively as cryptographic hashes.

Roles & Permissions

Roles for members and admins, plus individual permissions – such as creating events or approving reservations – and responsible persons for departments and groups.

Your Content Stays in Germany

Your organisation's data is stored exclusively in Germany and never shared with third parties. No tracking services and no advertising in the app or the web application. The only exception is the delivery of push notifications — it necessarily runs via Google and Apple, and carries neither names nor content.

Biometric Access Control

Administrators can enforce biometric app unlock organisation-wide. echoBOS does not store any biometric data – verification occurs exclusively on the device.

Device Security at Organisation Level

With echoBOS, the organisation – not the individual member – determines which security policies apply to every device. Administrators can mandate biometric app unlock via fingerprint or Face ID.

  • Global security policies set by administrators
  • Enforceable biometric app unlock
  • Cannot be disabled by individual members
  • Uses native device security (Face ID, fingerprint)
  • No biometric data stored by echoBOS

echoBOS and private messengers

Feature
echoBOS
Private messengers
Admin enforces app lock
User cannot bypass protection
Organisation-wide policy
No biometric data with provider
Biometric data remains exclusively on the end device.

Your organisation controls access

With echoBOS, the organisation decides who gets access to the app – not the individual member. No self-registration, no uncontrolled invitations.

  • Admin creates users and generates personal invitation codes
  • No self-registration – only invited persons receive access
  • Device connections revocable by admin at any time
  • Connection status in the app shows managed access
  • A new invitation code disconnects all previous app devices

Secure onboarding flow

1
Admin creates user
2
Invitation code generated
3
Member activates app
Connected & managed
App access can be cut instantly
The admin can disconnect app devices instantly – without physical access to the device, for example when a duty phone has been lost.

Convinced? Get started now!

Get a free consultation on how echoBOS can support your organisation.

Get in touch