A private communications platform, built deliberately.
Priveloq Chat is being built as a private browser-based communications platform focused on controlled access, privacy and secure collaboration. It carries messages, files, voice notes and calls between people who already have a reason to be talking — and it is designed around the assumption that who may see a conversation is the most important question in the product, not an afterthought bolted to the side of it.
It is a working application rather than a plan: messaging, media, calling, temporary guest rooms, the hidden chat vault, multi-factor authentication, session control and an administration area with an audit trail all exist today. What it is not yet is finished, and the security page is candid about which of the things people ask for it does not do.
Four decisions everything else follows from
Invitation, not registration
Anybody with the address can create an account on most products. Here there is no registration endpoint at all, so who is inside the deployment is a decision somebody made rather than a consequence of who found the URL.
The server decides
Nothing is protected by the interface declining to draw a button. The application requires an authenticated caller by default, and a page that is meant to be public has to say so - so forgetting a rule fails closed.
Temporary means temporary
A guest room that says it will be erased is erased by a background service, on a schedule, whether or not anybody remembers. A promise about retention is worth exactly what enforces it.
Say only what is true
This site does not claim end-to-end encryption, a compliance certification or an absolute guarantee, because the application does not provide them. A security claim that cannot be checked is worse than none.
Boring technology, deliberately.
A server-rendered ASP.NET Core application with a PostgreSQL database, a realtime connection for messages and presence, object storage for files and a conference server for calls. No native mobile application, no desktop client, and nothing a visitor has to install.
That is a choice about maintenance as much as about architecture. Every additional client is another place a permission check can be forgotten, and a browser is the one runtime everybody already has.
Where it runs
A deployment can be hosted for you, or run entirely on your own infrastructure — the application, its database, its object storage and its conference server. It scales to more than one node with a shared realtime backplane and shared rate-limit counting, so limits stay limits rather than becoming one allowance per node.
Who it is for
Organisations where the membership list is deliberate, conversations involve people outside it from time to time, and somebody has to be able to answer for who had access to what.
Talk to us
The fastest way to find out whether Priveloq Chat fits is to describe what you need it to do. Write to hello@priveloq.local, or use the contact form.
Contact usPrivate communication without public signup.
Request access or sign in to your existing account. Accounts are created by invitation, so there is no public registration to work through.