Identity sits in a vault
Real identities live in a schema the client cannot read directly. They come out through one guarded function, and only after both people have agreed.
08 / Zalo Mini App · solo · not released
A dating Mini App inside Zalo. Everyone is verified as a real person behind the scenes but anonymous to each other, and a name or number only appears when both people agree. Recipients control their own inbox, and everyone gets the same daily limit on showing interest. This is a prototype: the Zalo verification is still simulated.

Verified behind the scenes, anonymous up front.
Real identities live in a schema the client cannot read directly. They come out through one guarded function, and only after both people have agreed.
A staged reveal from voice to name to photo to number was cut. Both agree and both are revealed, otherwise nothing is, and a block during a reveal stops it too.
Zalo only gives an app-scoped ID, so an Edge Function turns it into a Supabase JWT. Without that bridge the row-level rules protect nothing. The real token check is not finished, which is why this cannot go to production yet.
A database trigger enforces the daily limit using server time, so changing the clock on a phone does not get around it. It applies equally to everyone.



Build a product together, distribute one that exists, commission software, or join in — write a few lines and NYX will get back to you.
Send an invitation →