1. Who these terms are between
A finished agreement will identify the contracting entity, the customer organisation, and the relationship between them and the individual people who use the product. That identification is a matter for the executed agreement and is not stated here.
2. What the service is
Priveloq Chat is a browser-based communications application providing messaging, file and media sharing, voice notes, audio and video calling with screen sharing, temporary guest rooms, and administrative controls including account management, session control and a security audit trail.
It is not a native mobile or desktop application, it does not connect to the telephone network, and it does not record or transcribe calls.
3. Accounts and access
There is no public registration. Accounts are created by redeeming an invitation issued by an administrator of a deployment. Access is therefore granted by the customer organisation, and revoked by it: an administrator can suspend an account, revoke its sessions and require multi-factor authentication of the roles that need it.
Account holders are expected to keep their credentials and their second factor to themselves, and to tell an administrator promptly if either is lost or exposed.
4. Temporary guest rooms
A guest room invitation grants access to one conversation and nothing else, expires on its own, and is single-use. A host who creates a room is responsible for who they send the link to: before it is redeemed, anybody holding it can become the guest.
Room contents are deleted automatically when the configured retention window closes. That erasure is a property of the software rather than a promise made here, and the window is set by the deployment.
5. Acceptable use
The product must not be used to break the law, to harass anybody, to distribute malware, to infringe somebody else's rights, or to attempt to reach data or accounts you have not been given access to. Automated probing of another organisation's deployment is not acceptable use; responsible security research on your own is, and the security page says how to report what you find.
6. Content
Messages, files and recordings sent through the product belong to the people and organisations that created them. Nothing about operating the service transfers ownership of them.
7. Availability and change
The product is under active development, and its features change. Where a deployment is self-hosted, its availability is a function of the infrastructure the customer runs it on.
8. Security claims
The controls the product implements are described on the security page, together with what it does not provide. No claim of end-to-end encryption, of compliance certification, or of absolute security is made anywhere on this website, and none should be inferred from anything in this document.
9. Clauses this draft does not attempt
Warranties and disclaimers; limitation of liability; indemnities; fees, invoicing and taxes; service levels; data processing terms and sub-processors; confidentiality; termination and its consequences; export of data on termination; assignment; governing law and the forum for disputes.
Each of those is a commitment with legal consequences, and writing a plausible-looking version of one is worse than leaving it out.
10. Contact
Questions about these terms: hello@priveloq.local.