Open-sourced the mobile auth layer (no personal data, looking for feedback)
Summary: Anton Minin Baranovskii announced the open-sourcing of the mobile client for Toqen.app, an access-first authentication system that avoids collecting personal data. They provided details on how user access is verified using device-bound identifiers and cryptographic keys. Feedback on whether open-sourcing such systems increases trust was requested, along with any other critiques. The system is aimed at various digital access scenarios, including SaaS platforms and event access systems.
Hey everyone,
I recently open-sourced the mobile client of Toqen.app - an access-first authentication system I am building.
One thing that matters to me here: the app does not collect personal or sensitive user data (no email, phone number, location, etc.).
It only uses device-bound identifiers and cryptographic keys required for authorization - you can verify this directly in the code.
This mobile layer is where access actually gets confirmed:
- user decision
- device signature
- real-time verification
The app itself does not grant access - everything is verified on the backend after the device signs a short-lived challenge.
Repository: https://github.com/toqenapp/mobile-react-native
Product access:
iOS (App Store): search for “toqen.app”
Android (closed testing): https://forms.gle/f9FcbHyHJiajmFWV7
Typical use cases include:
SaaS platforms
gated digital content
memberships
online education environments
event access systems
other products requiring time-bound and policy-defined authorization
I would really appreciate any feedback or honest critique.
Muhammad Haris
Anton, from my side as a founder, open-sourcing the auth layer does increase trust, but only for the small group of people who actually read code, and for everyone else it is the story around it that matters. What I take from your approach is the discipline of collecting no personal data at all, because that is a promise I can explain to a user in one sentence, and it is much harder to argue with than a long privacy policy. I also think the real test is not whether people praise the idea, but whether a platform owner is willing to depend on it for real access, and that is where a simple, honest demo would help you more than more features. My honest answer to your question is that trust comes in layers: the open code convinces the technical few, and their recommendation then convinces everyone else, so I would keep the code open and focus on making the first integration painless.
Anton Minin Baranovskii
OPOne thing I am still trying to understand:
Does open-sourcing something like the auth layer actually increase trust, or do most people decide based on other signals anyway?
Would be interesting to hear how you approach this.