Unit 2A, 17/F, Glenealy Tower, No.1 Glenealy, Central, Hong Kong S.A.R
Privacy & security
Nothing collected. Nothing readable.
Two halves of one answer: the data TalkRidge refuses to hold in the first place, and the encryption that protects everything it necessarily does — with a relay that can read none of it.
The principle
Privacy by refusal, not by policy
A policy can change with an acquisition, a subpoena or a bad quarter. An architecture cannot. TalkRidge protects you with what it refuses to build.
Every messenger says your privacy matters. The question worth asking is: what do they hold that could hurt you? For TalkRidge the answer is a pseudonymous mailbox, a queue of sealed envelopes deleted on delivery, and — if you opt in — a backup blob only your keys can open. That is the whole list.
By design
What TalkRidge refuses to collect
Six deliberate absences. Each one removes a whole category of risk — breach, sale, subpoena or mistake — by making the data itself not exist.
No phone number or email
Identity is a keypair created on your phone at first launch. Registration does not exist, so neither does the database of identities that every breach starts with.
No address-book upload
TalkRidge never reads or uploads your contacts. The people you talk to are stored on your device — and, at your option, in a backup only your keys can open.
No directory, no search
You cannot be found, browsed or enumerated. The only way into your contact list is a QR code scanned in person — spam has no door to knock on.
No ads, analytics or trackers
No advertising identifiers, no analytics SDKs, no crash-reporting that exfiltrates your usage. The app phones home for messages — nothing else.
Content-free notifications
Push notifications say “New message” and stop there. Apple’s and Google’s notification pipelines never see a word, a name or a picture.
Two modes, your call
Convenience mode keeps an encrypted, key-locked backup so a new phone can recover your contacts. Privacy mode keeps everything device-only — nothing exists anywhere else.
The test that matters
What our servers could never tell anyone
Imagine every TalkRidge server seized and every disk read. Here is what would still be missing.
Who you are
No name, number, email or account. Your mailbox is a hash of a public key — a pseudonym even we cannot resolve to a person.
What you said
Every payload is ciphertext sealed on your device. There is no server-side key, no escrow and no “lawful access” copy — nothing on our side opens it.
Who your friends are
Sender identity rides inside the encryption, and there is no directory to cross-reference. The social graph lives on your phone, not in our database.
Your address book
It is never uploaded in readable form. Even the optional backup is a sealed blob we store without being able to look inside.
The model
Assume the server is watching. Design for it.
TalkRidge doesn’t ask you to trust its infrastructure — it is engineered so the infrastructure has nothing worth trusting it with.
Keys are generated on your device and never leave it. Messages are sealed before they are sent, addressed pseudonymously, stored only until delivered, and readable only on the recipient’s phone. If our servers were breached tomorrow, the attacker would find queues of ciphertext — and no key, anywhere, to open them.
On your device
The cryptography, in plain words
A hybrid post-quantum protocol composed from vetted, unmodified open-source primitives — conservative where it counts, modern where it matters.
End-to-end, always on
Every message, voice note, photo, file and call-setup is encrypted on your device with XChaCha20-Poly1305 authenticated encryption. There is no plaintext mode to fall back to.
Hybrid post-quantum keys
Key agreement combines X25519 with ML-KEM-768, the NIST-standardised post-quantum KEM — in the initial handshake and again at every ratchet step, so “record now, decrypt later” has nothing to wait for.
Forward secrecy & self-healing
A double ratchet rolls the keys forward with the conversation: a key that leaks tomorrow cannot unlock yesterday, and a compromised session heals itself as messages flow.
Signed identities
Your identity is an Ed25519 signing key exchanged in person by QR code and confirmed with a fingerprint on both screens — there is no key server that could hand out a fake one.
Vetted primitives, unmodified
All cryptography uses well-reviewed open-source implementations, byte-for-byte unmodified. The custom engineering lives in the protocol composition — never inside a cipher.
Encrypted at rest
Keys live in the iOS Keychain or Android Keystore, and session state is sealed on disk under a device-held wrap key — locking the data even against other apps and backups.
On our servers
The relay is not trusted — on purpose
The server’s only job is to hold sealed envelopes until they can be delivered. Everything about it is designed around that being all it can do.
A blind mailbox
The relay stores sealed envelopes addressed to a hash of the recipient’s public key. It cannot open them, and it does not know your name, number, or anything else about you.
Nothing to phish
There are no passwords and no server-side accounts. Fetching your mailbox is authorised by a signature over a fresh timestamp, bound to the request it accompanies.
Minimal metadata
Sender identity travels inside the encryption rather than on the envelope, and padding blurs message sizes — the relay is designed to learn as little as physics allows.
Delete on delivery
A message is removed from the server the moment your device confirms receipt, and undelivered mail expires on a timer. The relay is a postbox, not an archive.
At a glance
The privacy properties, listed
If a future version of TalkRidge ever walks one of these back, this page is where it would have to say so.
No registration, ever
No phone number or email collected
No contact-book access or upload
No user directory or search
No advertising or tracking SDKs
No message content in notifications
Sender identity sealed inside the encryption
Messages deleted from the relay on delivery
Optional backup encrypted with your keys only
Privacy mode: strictly device-only data
Local data encrypted at rest
Keys generated and held on-device
The stack
The building blocks
Standard, well-studied algorithms — IETF and NIST standards implemented by widely reviewed open-source libraries, composed carefully and left unmodified.
XChaCha20-Poly1305 authenticated encryption
X25519 elliptic-curve key agreement
ML-KEM-768 post-quantum KEM (NIST FIPS 203)
Double ratchet with hybrid PQ steps
Ed25519 identity signatures
HKDF-SHA256 key derivation
Signed, replay-bound API requests
iOS Keychain / Android Keystore key storage
DTLS-SRTP encrypted call media
Who we are
A software house, not a data company
HKMSP designs, builds and operates custom software and cloud-native products. TalkRidge is its answer to a simple frustration: every mainstream messenger asks for a phone number and a leap of faith.
25+
years of IT, cloud & security background
2
platforms: iOS and Android
0
ads, trackers or data sales
1
job: private conversations, done properly
Conservative cryptography
Standard algorithms, widely reviewed open-source implementations, zero modifications. The interesting engineering is in the composition — being clever inside a cipher is how messengers get broken.
Built and operated by one team
The engineers who design TalkRidge also run its infrastructure. There is no hand-off between “delivery” and “support” — the product is a living system, not a project artifact.
Deliberately small
Every feature is a new attack surface and a new data flow to reason about. TalkRidge grows slowly and on purpose — the essentials, hardened, beat a feature list.
Honest claims only
No borrowed trust, no “military-grade” theatre. What the protocol does is documented plainly — and what hasn’t been independently verified yet is stated just as plainly.
Honest limits
What we won’t claim
Security marketing is full of borrowed trust. Here is where TalkRidge’s guarantees end — written down, on the website.
The applications have not yet been independently audited — until they are, our claims are design claims, stated plainly.
A relay necessarily sees traffic timing and approximate sizes. We minimise what that reveals; no messenger can honestly claim to erase it.
End-to-end encryption protects the channel, not the endpoints: a compromised or unlocked phone reads its own messages. Use a device lock.
The fingerprint check at pairing is your guarantee against swapped codes — take the two seconds to compare it for contacts that matter.
TalkRidge’s encryption is built exclusively from vetted, unmodified open-source cryptographic primitives, and the protocol design is documented openly. The applications have not yet undergone an independent external security audit — we say so plainly rather than borrow trust, and independent review is on the roadmap.
Contact
Questions? Talk to a human.
Questions about TalkRidge, feedback on the app, or press and partnership enquiries — send a message and it lands with the team that builds the product.
Headquarter
Unit 2A, 17/F, Glenealy Tower, No.1 Glenealy, Central, Hong Kong S.A.R
Email us
TalkRidge
TalkRidge is a private, end-to-end encrypted messenger: no phone number, no user directory, no ads. Contacts are added in person by QR code, and the servers only ever see ciphertext — designed, built and operated by HKMSP.
CONTACT US
Unit 2A, 17/F, Glenealy Tower, No.1 Glenealy
Central, Hong Kong S.A.R
Office Hours: 9AM - 7PM HKT
NEWSLETTER
Stay up to date with our latest news and products.
TalkRidge is designed, built and operated by HK Managed Services Provider Limited. Messages are end-to-end encrypted on your device before they are sent; TalkRidge’s servers store only ciphertext in transit and cannot read your conversations. The applications have not yet undergone an independent external security audit.
© 2026 HK Managed Services Provider Limited. TalkRidge is a product of HK Managed Services Provider Limited.