For privacy-first organisations
Collaboration that meets your compliance officer's standards.
Every conversation is end-to-end encrypted before it leaves your devices, and the whole platform can run on hardware you control when SaaS isn't an option.
The pain
Your tooling answers to your vendor — not your compliance officer.
SaaS vendors that "could" decrypt your data
Your collaboration vendor holds the keys. The privacy policy says they won’t look — but the architecture says they could.
Data residency uncertainty
Multi-region SaaS makes it hard to prove where regulated data actually lives, or which sub-processors have transient access.
No on-prem option for daily-driver tools
You can self-host an issue tracker from 2009 or accept full SaaS for the modern one. Nothing in between for teams that need on-prem.
Compliance forms that take months
Every new SaaS vendor triggers a security review, a DPA negotiation, and another row on the data-flow diagram.
How New Journey approaches it
Encryption you can audit. Data you actually own. An on-prem option when SaaS isn't one.
Private channels are sealed on members' devices before they reach us. We move sealed bytes; we don't hold the keys. The protocol is an open IETF standard — verifiable on our security page.
Every device holds a full copy of the workspace. Your data is on machines your team controls. We relay sync — we don't curate your records.
On Enterprise, run the whole stack on your own infrastructure. Same product, same encryption, no third-party processor in the path.
Features that matter for privacy-first orgs
Where to dig in next.
Conversations only your team can read. The encryption story your compliance team can actually audit.
Architecture, threat model, key management — and exactly what we can and cannot see.
Self-host, SSO, audit logs, and the procurement details for regulated teams.
Privacy & compliance FAQs
Can the vendor read our messages?
No — and not because we promise. Because we can't. Conversations are sealed on your devices before they leave; we move bytes we can't unseal.
Where does our data live?
On your devices, first. The cloud relays sealed bytes for sync. On Enterprise you can self-host the relay inside your own perimeter.
Do you support SSO and audit logs?
Yes. SSO, SCIM provisioning, and audit logs are part of Enterprise. The pricing page has the procurement detail.
How do we evaluate the encryption claims?
The cryptography is an open IETF standard with an open implementation — both auditable. Our security page covers the threat model, what the relay can and cannot see, and which parts your team can verify themselves.
Bring it to your compliance officer.
Ship faster without rewriting the data-flow diagram every quarter.