Software you actually own

Most software is rented, not owned. You sign up, your data flows into someone else's systems, and over time you're locked in — not because the product is the best, but because leaving has quietly become impossible. For a lot of teams that trade-off is fine. For teams handling sensitive information, it isn't.

SafeChat was built by our team specifically for OSP Rhein-Neckar. It isn't a product sold to anyone else — it's a bespoke messaging platform made for one organisation, on their terms. The people who use it are athletes, coaches, physiotherapists, and administrative staff at a German Olympic Training Centre — a context where data sensitivity isn't a legal checkbox, it's part of the daily reality of the work.

01What SafeChat actually does

At its core SafeChat is a secure internal messaging platform — but built for the specific shape of an OSP, not for a generic office. Users can send one-to-one messages, create group chats for casual coordination, and use structured channels for permanent team and department spaces. Voice and video calls are built in, hosted on EU infrastructure with no data leaving the European Economic Area. Files, voice notes, and media can be shared within conversations. Everything is end-to-end encrypted.

The navigation was designed mobile-first, because athletes and coaching staff live on their phones. The web version — used more by administrative staff and coaches at their desks — shares the same design system, the same components, and the same behaviour. Same product, different screen.

What makes the structure distinct from off-the-shelf tools is the separation between channels and chats. Channels are permanent spaces tied to teams, sports groups, or departments — they exist independently of who's in them at any given moment, and new members can be added with admin approval. Group chats are lighter, short-term, casual. The difference is visible at a glance and reinforced throughout the interface, so staff don't have to think about which one to use.

02A safety feature built into the product, not bolted on

OSP Rhein-Neckar operates under SafeSport obligations — the framework that governs athlete welfare and safeguarding in German sport. That shaped one of SafeChat's most distinctive features: a built-in compliance reporting mechanism.

Any user can flag a message they find offensive, abusive, or inappropriate, directly from within the app. When a message is flagged, the report — including the message content, the sender and recipient, the timestamp, and the stated reason — is written immediately to a secure incident log. A designated Compliance Officer within the organisation receives a notification and can access a dedicated dashboard where flagged incidents appear in full context: the reported message, surrounding conversation, all participant details. The officer can review, escalate, or archive each incident. Every action they take is itself logged, with a timestamp and their account ID. Nothing in the incident log can be edited or deleted.

The reason this matters is not just legal compliance — it's that the alternative is an offline process, which means someone has to remember to report something, find the right person, describe what happened from memory, and hope the relevant messages haven't been deleted in the meantime. SafeChat makes the reporting the same gesture as any other interaction in the app: a single tap, from wherever the conversation happened.

03Controlled connections — no open directory

One of the more considered decisions in SafeChat's design is that users cannot contact each other freely by default. There is no open directory. No user can search for, find, or message another user unless a connection has already been established between them.

To connect with someone, you share a Personal ID or an Invite Link — which can also be displayed as a QR code on screen for in-person sharing, or included in an email or printed document. The other person sends a connection request; you receive a notification showing their name, role, and department; you accept or decline. Only after acceptance can messages be sent in either direction.

Groups work the same way. A group admin shares an invite link; anyone who wants to join submits a request; the admin approves or declines. Being in the same group does not automatically grant members the ability to message each other privately — that still requires a separate connection. The admin also controls whether new members can see prior conversation history or only messages from their join date.

This isn't just a privacy measure. In a sports safeguarding context, an open directory where any registered user can initiate contact with any athlete is exactly the kind of exposure that SafeSport frameworks exist to prevent.

04Your data stays with you

The most important feature of SafeChat is the one you never see: your data never leaves your control. Messages are encrypted and they live inside your own environment — not on our servers, not on a third party's. There is no copy of your conversations sitting somewhere you cannot see, and no arrangement where we could hand your data to anyone, because we simply do not hold it. Voice and video calls are routed through Digital Samba Embedded, an EU-hosted provider operating under a signed data processing agreement, with no media leaving European infrastructure.

05Hosting on your terms

SafeChat runs on your infrastructure, in your jurisdiction, under your rules. That means you decide where the data sits, who can reach it, and how it is governed — not a vendor whose priorities might change next quarter. For an organisation with real compliance obligations, "on your terms" isn't a preference; it's the whole point.

06No lock-in, by design

We think good software should be easy to leave. Nothing in SafeChat is engineered to make you dependent — no proprietary traps, no data you can't export, no switch you can't flip. The relationship lasts because it works, not because you're stuck. That confidence only comes from building it that way from the start.

07Built for one, built to last

Because SafeChat was made for a single organisation, every decision could be the right one for them — not a compromise averaged across a thousand customers. The compliance reporting workflow exists because OSP Rhein-Neckar needs it. The controlled connections model exists because their safeguarding obligations require it. The channel structure exists because that's how their teams actually work. That's the kind of work we like: a tool that fits one team exactly, that they own outright, and that keeps working long after we've handed it over.