Skip to content
Invite-only · browser-based

Private communication.
On your terms.

Priveloq Chat brings secure messaging, browser-based voice and video calls, temporary guest conversations, private media sharing, and conversations you can keep out of sight into one controlled communications platform.

What it does

Everything a private conversation needs

One application for messages, calls, files and the people you bring in from outside — with the controls to decide who reaches any of it.

Secure messaging

Direct and group conversations with real-time delivery, read state, presence, typing indicators and private media.

Priveloq Calls

Private browser-based audio and video calling with screen sharing and group call support.

Priveloq Guest

Invite external guests into temporary conversations without creating permanent accounts.

Priveloq Vault

Keep selected conversations out of the normal conversation list, behind a separate session-specific vault lock.

File and media sharing

Images, documents, audio, video and voice notes recorded in the browser, delivered only to authorised readers.

Cross-device access

Use it from current desktop and mobile browsers. There is no native application to install, and nothing to keep updated.

Privacy

Private conversations can stay out of sight.

Selected conversations can be hidden from the normal conversation list and unlocked separately for the current browser session. Nothing announces that there is anything to unlock.

  • Hidden conversations are absent from the list, from search and from notifications until the vault is open.
  • The vault is unlocked with a secret separate from the account password, and unlocking one browser opens nothing on another.
  • An open vault closes itself again after a period of inactivity, and can be closed on every device at once.
  • Too many wrong attempts pause the vault without touching the account, so guessing at somebody's hidden chats cannot lock them out.
Said plainly: this is an access-control feature, not end-to-end encryption. It decides what is shown and to which session; it does not put message content beyond the server's reach.
Hidden from the list Absent from search A separate secret Per browser session Locks itself again Lock every device

  1. Open a room

    Somebody inside your organisation creates a temporary room and gets a single-use invitation link.

  2. The guest joins

    They choose a display name. No account, no password, no email confirmation.

  3. Talk

    Messages, files, voice notes, audio, video and screen sharing — in that one room only.

  4. It disappears

    When the retention window closes, the room and everything in it is removed.

Guest access

Invite someone without creating a permanent account.

Create a secure temporary guest room for messaging, voice notes, media sharing, audio calls, video calls and screen sharing. The guest sees that conversation and nothing else in the product.

  • Each invitation is single-use, expires on its own, and can be revoked before it is redeemed.
  • A guest credential is valid for one room. It reaches no other conversation, no directory and no account.
  • Temporary room history is removed automatically according to the configured retention policy — on this installation, 30 minutes after the call ends.
  • Administrators can see that rooms exist and end them, without a route into what was said in one.
How guest rooms work
Calls

Calling that happens in the browser

Ring somebody from the conversation you are already in. No dial-in numbers to distribute, no meeting client for the other side to install.

Audio calls Video calls Group calls Screen sharing
Who may join a call is decided by the server, not by whoever holds the link: each participant is issued a short-lived credential for that one room. Removing somebody from a conversation therefore takes effect on a call already in progress. There is no telephone dialling, no recording and no transcription.
Media

Files that are not simply sitting on a public URL.

Attachments are stored outside anything a web server hands out by path, and every read is authorised against the conversation the file was sent to.

  • Images, documents, audio, video, and voice notes recorded in the composer.
  • Authenticated access on every fetch and every download — a copied link is not a key.
  • Playback and preview in the conversation, without the file leaving the authorisation check behind.
  • Photographs have their embedded metadata removed before they are stored, so a shared picture does not carry its location with it.
Images Documents Audio Video Voice notes Authorised downloads
Administration

Controls for the people who answer for it

Everything an administrator can do is a permission granted to a role, and every consequential action is recorded.

Invitations

Issue, track and revoke the invitations that create accounts. There is no other way in.

Accounts and roles

Assign roles, suspend an account, and require multi-factor authentication of the roles that need it.

Session control

See where an account is signed in and revoke a session, which takes effect on the next request rather than at the cookie's expiry.

Guest room oversight

See which temporary rooms are open and end one, with no route into what was said inside it.

Security auditing

Sign-ins, role changes, suspensions, invitations and session revocations are written to an audit trail an administrator can review.

Deployment policy

Retention windows, media limits, multi-factor requirements and guest capabilities are configuration, enforced on the server rather than by hiding a button.

Architecture

The server decides, every time.

Authorisation is not something the interface does by drawing fewer buttons. Every request is checked where it is answered, and the application refuses by default: a page that does not state that it is public is not public.

  • Multi-factor authentication, and a policy that can require it of a role.
  • Sessions that can be revoked, and a revocation that is observed on the next request.
  • Attachments stored outside the web root and served only to authorised readers.
  • Short-lived, per-participant credentials for the conference provider.
Read about security

  1. The browser

    No application to install and no plug-in to trust. Messages, files, voice notes and calls all run in a current desktop or mobile browser.

  2. Priveloq Chat

    Every request is authenticated and then authorised on the server. A page that forgets to say who may see it is refused rather than served: the application requires a signed-in caller by default, and each public page states its exemption explicitly.

    • Messaging Conversations, delivery and read state
    • Media Uploads stored outside the web root
    • Security Sessions, roles, permissions and the audit trail
    • Calling Who may join, and for how long

  3. The conference server

    Audio and video run through a conference service the deployment operates or contracts. It never decides who may join: Priveloq Chat checks that, and issues each participant a short-lived credential for one room, which is what makes removing somebody take effect on a call already under way.

Private 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.

Contact us Sign in
FAQ

Questions people actually ask

Including the ones with an answer we would rather be able to give differently.

No. Priveloq Chat is a browser-based web application designed for current desktop and mobile browsers. There is nothing to install from an app store, and nothing to keep updated on a device.

Not publicly. Accounts are created by invitation: an administrator issues one to an address, and redeeming that invitation is what creates the account. There is no public registration page, which is why this site asks you to get in touch rather than offering a sign-up form.

Yes. A temporary guest room gives an outside party one conversation and nothing else: they choose a display name, they can message, share files, record voice notes and join a call, and they never see anything beyond that room. The room and everything in it is removed automatically when its retention window closes.

Selected conversations can be kept out of the ordinary conversation list and unlocked separately, for the current browser session only. It is an access-control feature rather than an encryption one: unlocking on a laptop does nothing to a phone, and the vault closes itself again.

Yes, directly in the browser: one-to-one and group audio, video and screen sharing. There is no dialling of telephone numbers, no recording and no transcription.

Images, documents, audio, video and voice notes recorded in the composer. Files are served only to people authorised to see the conversation they were sent to - a link on its own is not enough to open one.

Yes. A deployment can run the application, its database, its object storage and its conference server itself. Get in touch and we will talk through what that involves.

No, and this site will not claim otherwise. Traffic is encrypted in transit and messages and files are served only to authorised callers, but the server can read message content - which is what makes server-side search, administration and the guest-room purge possible. If end-to-end encryption is a requirement for you, say so when you get in touch.