Requests from Authorities
Last updated: [PUBLICATION DATE]
Русская версия (имеет юридическую силу)
This English text is a translation provided for convenience. The Russian and Uzbek versions are equally authoritative.
1. General Provisions
1.1. This Procedure sets out how CORDICE LLC (the "Operator") handles requests from government and other competent authorities for information about Users, and informs Users of that procedure.
1.2. The Procedure is for information purposes. It is not a contract with any authority or third party, creates no rights for them and does not limit the Operator's rights under the law. Terms have the meaning given in the Terms of Service; the data held and its retention periods are defined in the Privacy Policy.
2. Grounds for Disclosure
2.1. The Operator discloses information about Users solely on the grounds and in the manner provided for by the laws of the Republic of Uzbekistan and the international treaties of the Republic of Uzbekistan, upon a request that is binding on the Operator and made by a competent authority in the prescribed form.
2.2. Requests from authorities of foreign states are handled in the manner provided for by the international treaties of the Republic of Uzbekistan on legal assistance. The Operator may decline to act on a request from a foreign authority made outside that procedure.
2.3. The Operator carries out a legal assessment of every request and discloses information to the minimum extent necessary to comply with it.
3. Rights of the Operator
3.1. The Operator may:
- verify the authenticity of the request and the authority of the body and official;
- ask for clarification or narrowing of a request it considers overly broad or vague;
- challenge a request, refuse to comply with it or comply in part, in the manner provided for by law, if the request does not meet legal requirements, is made by an improper authority, lacks a proper legal basis or is excessive;
- not respond, pending verification, to requests from free email services and to requests whose authenticity has not been confirmed through official channels.
3.2. The Operator does not build hidden means of access ("back doors") into the Service and does not grant anyone standing access to Users' data.
4. Information the Operator Holds
4.1. The Operator's main server (database, API and processing) is located in Tashkent, Republic of Uzbekistan; Users' data is stored on it. Users' files and database backups are kept in encrypted form in Cloudflare R2 object storage in the European Union; the encryption keys are kept by the Operator separately from the encrypted data and are not available to the storage provider.
4.2. The Operator can provide only information it actually holds at the time of complying with the request, as described in the Privacy Policy:
- email address, or phone number if provided, and profile data;
- session data (IP address, device);
- call history (who, whom, when) without content;
- messages and files that have not been deleted.
4.3. Deleted messages, files and data of deleted accounts may remain in encrypted backups: daily backups for 14 days, weekly for 8 weeks and monthly for 12 months. Backups are intended for restoring the Service after failures; the Operator may decline to extract individual information from them on request unless expressly required by law. After these periods, deleted data cannot be recovered or provided.
4.4. The Operator does not hold the content of calls. Calls are end-to-end encrypted and the keys exist only on participants' devices. Call media is relayed through LiveKit Cloud (LiveKit, Inc., USA), which processes technical connection data (IP address, time, traffic volume) but cannot obtain the content of a call. The Operator is technically unable to record a call or to add an outside participant unnoticed: key substitution is detected by participants through the emoji check. The Operator is technically unable to comply with requirements to intercept or listen to calls.
4.5. The Operator is not obliged to create, recover, decrypt or obtain information it does not hold, or to modify the Service for that purpose, unless expressly required by law.
5. Emergency Requests
5.1. Where there is an immediate threat to a person's life or of serious harm to their health, a request may be sent to [email protected] with the subject "EMERGENCY" and a description of the threat. In such a case the Operator may, but is not obliged to, disclose limited information at its discretion before receiving a formal request, where permitted by law.
6. Data Preservation
6.1. On a reasoned request from a competent authority, the Operator may preserve specific account data for up to 90 days while a formal request is prepared. Preservation does not constitute disclosure.
7. Notice to the User
7.1. The Operator may, but is not obliged to, notify a User at its discretion of a request concerning them, including before disclosure, unless such notice is prohibited by law or a court decision. As a rule, the Operator does not notify the User where such a prohibition exists, or where there is a threat to a person's life or a threat to a child.
8. How to Submit a Request
8.1. A request must be sent to [email protected] and must contain:
- the name of the authority, the position and name of the official, and contact details for verification;
- the legal basis for the request;
- the account identifier (@username or a link to a profile, message or server);
- the information requested and the period it covers.
8.2. A request lacking this information may be left unprocessed until it is provided.
9. Transparency
9.1. The Operator may publish aggregate statistics on requests (number, countries, number granted) to the extent permitted by law; the frequency and form are determined by the Operator.
10. Final Provisions
10.1. The Operator may amend this Procedure unilaterally; a new version takes effect upon publication unless it states otherwise.
10.2. This Procedure is governed by the laws of the Republic of Uzbekistan. The Russian and Uzbek versions are equally authoritative.