Cordice
Open Cordice (opens in a new tab)
← All legal documents

Privacy Policy

Last updated: [PUBLICATION DATE]

Русская версия (имеет юридическую силу)

This Privacy Policy (the "Policy") sets out the personal data processed when the Service is used, the purposes, legal bases, periods and methods of processing, the recipients of data, the procedure for cross-border transfer, the protective measures applied, and the rights of data subjects and how they are exercised. The Policy forms an integral part of the Terms of Service and applies together with the Consent to the processing of personal data and the Cookie notice. This English version is a translation provided for convenience; the Russian and Uzbek versions are equally authoritative.

Key principles

This section is for information only and does not replace sections 1–16 of the Policy.

  • Minimisation. The Operator stores only the data necessary for the Service to work and stay secure, and only for the periods set out in section 9. Sign-in uses an email address with a one-time code, without a password.
  • No advertising profiles. The Operator does not sell personal data, does not use trackers or advertising identifiers, does not build interest profiles and does not train neural networks on messages. No ads are shown in the Service (2.19). No third-party counters or trackers — neither in the apps nor on the site (2.18).
  • Encryption. Calls are end-to-end encrypted: the Operator does not hold the keys and cannot listen to or record a call (2.8). Cloud chats and files are stored encrypted; the keys are kept outside the database and the file storage and are not accessible to storage providers. The running Service can technically decrypt cloud chats, which is necessary for search, sync, bots and the handling of reports. Secret chats with end-to-end encryption have not been implemented as of the date of this version.
  • Free of charge. The Service is free; no payments are accepted and no payment data is processed (2.20).
  • Staff access is restricted. Messages are opened only while handling a report or for a recorded reason, and every access is logged (section 8).
  • Third-party applications and services are not the Operator. Bots, Mini Apps and app stores process the data they receive on their own and at their own responsibility (2.12, 6.6).
  • The User is in control. The account can be deleted and a copy of data obtained (section 10); data subject rights are set out in section 11.

1. Operator, scope and definitions

1.1. The operator (controller) of personal data is CORDICE LLC (in Russian ООО «CORDICE», in Uzbek «CORDICE» MChJ), Republic of Uzbekistan, Tashkent (the "Operator").

DetailValue
Taxpayer ID (STIR)[STIR]
Registered address[ADDRESS]
General questions[email protected]
Personal data questions and data subject requests[email protected]
Person responsible for organising personal data processing[NAME / POSITION]

1.2. The Policy applies to the processing of personal data when the Cordice apps are used (web at app.cordice.org, Android, iOS, Windows, macOS and Linux), the sites cordice.org, developers.cordice.org and crdc.xyz, and when the Operator's support is contacted (together, the "Service").

1.3. Definitions:

  • User — a natural person who has registered with or uses the Service;
  • personal data — any information relating to an identified or identifiable natural person (the data subject);
  • processing — any operation or set of operations performed on personal data, including collection, organisation, storage, alteration, use, transfer, anonymisation, blocking and destruction;
  • Content — messages, files, media, stories and other material posted or transmitted by Users through the Service;
  • Space — a server, group or channel in the Service;
  • Space Owner — a User who created a Space or obtained the right to manage it, and the moderators and administrators appointed by them;
  • Third-Party Services — bots, Mini Apps, payment systems, app stores and other services provided by persons other than the Operator;
  • Third Parties — any persons other than the Operator and the User concerned;
  • processor — a person processing personal data on the Operator's behalf.

1.4. Other terms have the meanings given in the Terms of Service and applicable law.

2. Data processed

2.1. Account and sign-in

DataPurposeProcessing and storage details
Email address; phone number — if provided by the User [VERIFY: whether a number can be added as of publication]signing in, recovering access, being found by contacts (if the User allows it)stored encrypted, separately from the rest of the profile data
One-time sign-in codesconfirming that the number or address belongs to the Useronly a hash of the code is stored. A code is valid for 10 minutes; 5 entry attempts are allowed. The code is not included in the email: the email contains a link to a page on cordice.org where the code is shown when a button is pressed. For that page the code is stored encrypted with a key contained in the link in the email and cannot be read without the email
The code page: information on requesting and opening the codeinforming the User which device and place requested sign-in, detecting attempts at unauthorised accessdevice and browser, approximate city and country by IP address, time; every press of "Show code" and "This wasn't me", with the IP address and browser information. Deleted one day after the link expires (a link is valid for 15 minutes)
IP address that requested a codeprotection against code guessing and mass sendingdeleted one day after the code expires
"Not a robot" check at sign-in and registrationprotection against automated registration and guessingperformed by Cloudflare Turnstile (section 6)
Old and new number or address when changedsecurity: a notice is sent to the old addressdeleted after 90 days
Authenticator app secret (when two-step verification is on)verifying the app's codestored encrypted
Backup codessigning in without the authenticator apponly hashes are stored
Passkeyssigning in without a codeonly the public key, its name and the time of last use are stored
Version and time of acceptance of the documentsevidencing acceptance of the documents and consentfor as long as the account exists
Re-sign-in tokens (Android and iOS apps only)signing in again without a code after signing outa random token is kept in the device's secure storage, the Operator keeps only its hash; the token is single-use and valid for 30 days; deleted on "End all sessions", "This wasn't me" and on blocking
The code for the next delivery channelresending the same code by email (by SMS — once sign-in by phone number is enabled) if it did not reach the appstored encrypted with a server key together with the sign-in attempt and deleted with it (after one day)
Confirmation of a new sign-inasking "Is this you?" on a device where the User is already signed ina mark on the session; absent an answer, the sign-in is deemed confirmed after 7 days
Request to reset two-step verificationturning two-step verification off after 7 days when access to the app and backup codes is lostthe time of the request, until it is executed or cancelled
Account countrycompliance with the laws of the User's country (data storage location, age restrictions, availability of content), choice of SMS operator — once sign-in by phone number is enableddetermined from the country code of the phone number and, until one is added, from the country of the IP address at registration; may be corrected by the Operator's staff at the User's request; not chosen by the app. Kept with its history of changes for as long as the account exists. The IP country of each sign-in is not recorded

2.2. Profile

2.2.1. The following are processed: username (@username), display name, "About", status and custom status, avatar, cover, nameplate, server tag, last-seen time and the chosen presence mode, and marks set by the Operator: "bot", subscription flag, account restrictions.

2.2.2. Where the User has confirmed being 18 or older (to access a Space marked "18+"), the fact and time of that confirmation and the "show 18+ spaces on iOS" setting are stored. The date of birth is neither requested nor stored.

2.2.3. Username, display name, avatar and "About" are publicly available: anyone with a link to the profile (crdc.xyz/@username) can access them, including without signing in to the Service. The last-seen time is available to those designated by the User in privacy settings.

2.3. Devices and sessions

2.3.1. For each session the following are stored: device name and platform; app version, device model, operating system version and language; IP address and User-Agent (the information the browser or app reports about itself); sign-in and last-activity times.

2.3.2. This information is available to the User under Settings → Devices, where any session can be ended. The User is notified of every new sign-in in the Cordice service chat.

2.3.3. A session ends automatically after 180 days regardless of use. The data of an ended session is deleted after 90 days. QR sign-in data (device name, IP address, User-Agent) is deleted one day after the code expires.

2.4. Contacts and connections

2.4.1. The following are processed: friends, friend requests, contacts (with labels assigned by the User), favourites, close friends, blocked users.

2.4.2. Address book sync is available only in the Android and iOS apps, only with the User's separate permission, and may be skipped. The address book is not sent to the server: the app computes a SHA-256 hash of each phone number and email address and sends those hashes. The server looks for matches among users who have allowed being found by number or email and does not keep the hashes received. The users found are added to contacts. A hash of a phone number is not encryption and can be guessed; for this reason hashes are not stored and lookups are limited to 2,000 a day.

2.4.3. Privacy settings are processed: who may send the User requests, find the User by number or email, see the last-seen time, call, add the User to groups, and see read receipts.

2.5. Messages and other Content transmitted

2.5.1. Messages: text, attachments, voice and video messages, stickers and GIFs, polls and votes, reactions, replies, forwards, mentions, pins, threads, scheduled messages (until sent) and reminders.

2.5.2. Service data (metadata): sender, recipient, chat, time of sending, read receipts, information on views of a channel post, the typing indicator. Metadata is not encrypted, since messages cannot be delivered without it.

2.5.3. Search. For message search the server keeps a search index made of keyed hashes of words (a blind index). The text cannot be recovered from the index without the key.

2.5.4. Deletion. When a message is deleted for all participants, its text and attachments are destroyed; an empty record indicating the sender and time of sending is kept to preserve the integrity of the chat. "Delete for me" only hides the message for the User. Edit history is not kept.

2.5.5. Disappearing messages. When a timer is on in a chat, messages are deleted automatically when it runs out.

2.6. Files and media

2.6.1. Files are encrypted on the Operator's server, each with its own key, and stored encrypted in the Cloudflare R2 object storage in the EU (6.1, section 7); the keys are kept by the Operator and are not transferred to the storage provider. Stored with a file: the User who uploaded it, the chat, file name, type, size, dimensions and duration, and a small preview. The server makes smaller copies of an uploaded photo for the feed.

2.6.2. Metadata is removed from photos (EXIF and XMP), including GPS coordinates, camera model and time of capture; the orientation is preserved. Removal is performed for JPEG, PNG, WebP, AVIF and HEIC. The metadata of files sent "as a document" is not changed, and the recipient receives the original file.

2.6.3. Avatars, covers, group photos, stickers, server emoji and saved GIFs are publicly available (they can be opened by a direct link) and are therefore stored without encryption.

2.7. Stories

The photo, video or text of a story, its caption, the chosen audience (contacts, friends, selected persons, close friends), the display time (6 to 48 hours), and information on who viewed the story and what reactions they left are processed. Stories and view information are deleted one day after the display ends, except stories pinned by the User to the profile.

2.8. Calls

2.8.1. All calls in the Service are end-to-end encrypted: one-to-one and group calls, server voice channels, stages, screen sharing.

2.8.2. On joining a call, the device creates a temporary key pair. One participant creates the call key and sends it to the others encrypted. The Operator's server and the media server relay this data but cannot read it.

2.8.3. The key changes when a participant joins, leaves or is removed. A new participant has no access to the earlier part of the call, and a departed participant has none to the later part.

2.8.4. Verification. Tapping the lock icon in a call shows four emoji. Matching emoji for all participants confirm that no outside person, including the Operator, is present in the call.

2.8.5. The Operator does not record calls and has no technical means of recording them.

2.8.6. The server processes call metadata: caller and callee, whether it was a video call, times of start, answer and end, reason for ending, participants of a voice channel. The server also receives information on whether the microphone and camera are on. Call history is stored; microphone and camera state is not. The LiveKit Cloud media server (6.1) relays encrypted media streams without access to their content and processes technical connection data: IP address, time, traffic volume.

2.8.7. The User's IP address is not disclosed to other participants: the connection goes through the media server (LiveKit Cloud).

2.9. Voice message transcription

Transcription of voice and video messages to text is not provided as of the date of this version. Once enabled: a voice or video message is recognised, when the User taps "Transcribe", on the Operator's own server; the recording is not transferred to third parties and no third-party speech recognition services are used; the transcript is stored encrypted for as long as the message exists and is available to all chat participants. The accuracy of transcription is not guaranteed.

2.10.1. Link previews. When a link is sent, the Operator's server opens the page itself and saves its title, description and image. The site receives the request from the Operator's server, not from the User.

2.10.2. GIFs. A GIF sent by the User is copied to the Operator's servers and stored with the message. Saved GIFs are shown in the "My GIFs" tab. Third-party GIF catalogues (Tenor, KLIPY and the like) are not used.

2.10.3. Gifoteka. The Gifoteka GIF catalogue — a separate catalogue of CORDICE LLC with its own rules ([GIFOTEKA DOMAIN]) — is not provided as of the date of this version. Once enabled: the search query is sent to Gifoteka from the Operator's server, without the User's name, phone number or IP address; images in search results load from Gifoteka's site, which does not keep IP addresses in its logs, but Cloudflare receives them; when the User publishes their own GIF, Gifoteka receives the GIF, its title, tags and a random identifier that does not allow the User to be identified in the Service, and the User's name only if the User so decides.

2.11. Servers, channels and groups

For each server the following are stored: members, their nicknames and roles, time of joining, settings, channels, invites, emoji, automod rules, bans and timeouts (with the reason and the person who issued them), and the moderators' action log. Public servers are shown in the Discover catalogue. For broadcast channels, anonymised statistics are kept: numbers of subscriptions and unsubscriptions, forwards and views.

2.12. Bots and Mini Apps

2.12.1. Bots and Mini Apps ("Third-Party Applications") are created by Users and third-party developers, not by the Operator. Developers of Third-Party Applications are not affiliated with the Operator and act independently of it; the Operator does not review, support or guarantee Third-Party Applications. A developer must ask for the User's consent where it is required to obtain or use the User's data.

2.12.2. A bot in a private chat receives the messages the User addresses to it and the User's public profile data: ID, name, @username, language.

2.12.3. A bot added to a group or Space receives all messages in it within the permissions granted to the bot and its event subscriptions (the app platform: REST, WebSocket, events), and the bot's owner receives them on their own server. Updates not collected by the bot are kept by the Operator for up to 24 hours, but no more than 10,000 per bot. When a bot is added, the Service shows a corresponding warning. A User who adds a bot to a Space is solely responsible for that decision.

2.12.4. A Mini App is a third-party website opened inside the Service. A Mini App receives (in its launch data) the User's ID, name, @username and language, the type of chat it was opened from, and the launch parameter. Clipboard access is granted only after the User's permission. Mini Apps do not receive the phone number, email address, location, or camera and microphone access from the Operator. Since a Mini App and the sites that a bot's links and buttons lead to are third-party sites, the site owner may receive the User's IP address and browser and device information when they are opened, as with visiting any website.

2.12.5. Processing of data by a Third-Party Application is determined by its owner under its own policy; the owner is an independent controller of personal data (6.6). Developers are required to comply with the Developer Terms. The Operator is not responsible for the content and operation of Third-Party Applications or for their processing of personal data.

2.13. Notifications

Push tokens, the "Do not disturb" schedule, the User's time zone (so the schedule fires on time) and per-chat notification settings are stored. How notifications pass through Google and Apple is set out in section 6.

2.14. Reports, moderation and child safety

2.14.1. When a report is made about a message, user, chat or server, the report (reporter, object, reason, explanation) and a snapshot of the reported content are stored. The snapshot is stored encrypted and is necessary to review the report, since offenders typically delete messages. The decision on the report, the moderator's note and any restrictions placed on the account (with the reason) are also stored.

2.14.2. The Operator does not automatically check uploaded images: images are not compared, by hash, with databases of known material and are not checked by a classifier. Images are reviewed by the Operator's staff only when a report is received (2.14.1). If child sexual abuse material is identified while a report is being reviewed, the Operator reports it to the competent authorities where required by law.

2.14.3. Automated checking means. The Operator may in future use automated means to check images in Public Spaces (profile avatars and covers, server icons and banners, photos of public groups and channels, photos in public servers and channels) by supplementing this Policy with a description of such means and of the data they process. Private chats, closed groups and private servers are not checked by such means; any decision to apply measures to a User is taken by a person.

2.14.4. Restrictions applied by moderators (hiding a message, profile, channel or server, marking media as sensitive) are stored with the reason, author and time; when a restriction is lifted, the record remains in the log.

2.14.5. Moderation is a right, not an obligation, of the Operator; the Operator does not carry out pre-moderation or monitoring of Content except as described in this subsection.

2.15. Support

When support is contacted (at support@ or other @cordice.org addresses), the person's address and name, the correspondence, its subject, attachments (up to 10 MB) and internal staff notes are stored. Texts and attachments are stored encrypted. If the address matches an account in the Service, the request is linked to the account. The Operator may keep a record of the person contacting support: name, email address, phone, organisation, notes.

2.16. Data stored only on the User's device

2.16.1. Web and desktop apps: interface settings and recent searches, the User's private notes about other users (not sent to the server), a hash of the local passcode. One required cookie is used for sign-in. Account data is removed from the browser on sign-out. Details — the Cookie notice.

2.16.2. Android: session keys are stored encrypted in the Android keystore; settings and an image and voice message cache are also stored. Backup of app data to Google's cloud is disabled.

2.16.3. iOS: session keys are kept in the Keychain and available only on that device; a media cache and settings are also stored.

2.16.4. Call keys exist only in the device's memory for the duration of the call.

2.16.5. The User is responsible for the safekeeping of data stored on the device.

2.17. Logs and technical information

2.17.1. Service request log: request ID, method, path without parameters, response code, processing time. The IP address is not written to the log, phone numbers and email addresses are masked, tokens are removed. Retention — 14 days.

2.17.2. Edge proxy log: may contain the IP address and User-Agent. Retention — no more than 14 days.

2.17.3. Service metrics (load, errors, number of connections) are processed only in aggregate form, without data on individual Users.

2.17.4. Crash reports. When an app or server crashes, a technical report (stack trace, version, device) is sent to the Operator's own crash reporting server. No third-party services are used; message texts, numbers and tokens are removed from reports.

2.17.5. Rate limits are calculated by IP address and account in memory and are not written to the database.

2.18. Processing the Operator does not carry out

The Operator:

  • does not use advertising identifiers, pixels, interest profiles, third-party counters, trackers or third-party analytics, whether in the apps, on the site or in the web app;
  • does not request location; the Service has no location sharing feature;
  • does not request date of birth or identity documents;
  • does not analyse messages for advertising, profiling or training neural networks;
  • does not sell, rent or transfer personal data for advertising purposes;
  • does not receive or store bank card numbers or CVV.

2.19. Cordice Ads

2.19.1. No ads are currently shown in the Service, and no personal data is processed for the purpose of showing ads. The Operator may introduce advertising in the future; if it does, the Policy will be supplemented before the relevant processing begins.

2.19.2. Promotional posts that Space Owners publish on their own in their channels and groups are not the Operator's advertising; the Operator is not responsible for their content or for the processing of data by the advertisers of such posts.

2.20. Payments

2.20.1. The Service is currently provided free of charge: no paid features are provided, no payments are accepted and no payment data is processed. There are no built-in payments in bots and Mini Apps. The Operator does not receive or store bank card data.

2.20.2. The Operator may introduce paid features in the future; if it does, the Policy will be supplemented before any payment data is processed.

2.21. Personal data of Third Parties provided by the User

2.21.1. By posting in or transmitting through the Service personal data of Third Parties (including in messages, files, contact labels, address book sync, reports and support requests), the User represents that they have a lawful basis for such transfer (including the consent of the persons concerned where required by law) and is solely responsible for its lawfulness.

2.21.2. In respect of such data, the Operator carries out technical processing to the extent necessary for the Service to function and does not determine the purposes for which the User posts it. The User settles Third Party claims relating to such data on their own; the Operator's rights under the Terms of Service are unaffected.

2.22. Publicly available data

Data the User has made publicly available (2.2.3, public Spaces and channels, public images under 2.6.3) may be accessible to an unlimited number of persons, including outside the Service. The Operator does not control and is not responsible for the copying, storage and further use of such data by Third Parties.

3. Device permissions

3.1. The apps request access to device functions only when performing an action that requires it. Refusing a permission does not prevent use of other functions.

PermissionWhen requestedPurpose
Microphonea call, voice message, video messagerecording and transmitting sound
Cameraa video call, video message, taking a photo, scanning a QR codecapturing or transmitting video
Photos and media library (iOS)choosing or saving a photosending or saving media
Contactsaddress book syncfinding users the User knows (2.4)
Notificationsafter sign-innotifying of messages and calls
Bluetooth (Android)a callrouting sound to a headset
Display over the lock screen, full-screen notificationsan incoming callshowing the call screen
Screen recordingscreen sharing in a callsharing the screen with participants
Installing apps (Android, build from the site, not from Google Play)an updateinstalling a new version of Cordice
Local network (iOS)connecting to a server on the local networkfor developers

4.1. The Operator processes personal data for the following purposes and on the following bases:

PurposeDataLegal basis
Running the messenger: account, delivering messages, calls, files and stories, sync across devices2.1–2.13the data subject's consent; performance of the contract (Terms of Service)
Account security: codes, two-step verification, sessions, sign-in and contact-change notices2.1, 2.3performance of the contract; the Operator's legitimate interest in protecting accounts
Protection against spam, fraud and attacks: rate limits, the registration check, logs2.1, 2.3, 2.17the Operator's legitimate interest
Moderation, handling reports, child safety2.14 and the reported contentthe Operator's legitimate interest; performance of the contract; compliance with a legal obligation
Contact syncaddress book hashesthe data subject's separate consent (may be withdrawn)
Push notifications through Google and Apple2.13, message previewthe data subject's consent (notification permission)
Support2.15performance of the contract; the Operator's legitimate interest
News and tips by emailemail addressthe data subject's separate consent. No such emails are sent as of the date of this version
Complying with lawful requests from public authoritiesdata to the extent required by lawcompliance with a legal obligation
Account country: data storage location, age restrictions, availability of content, choice of SMS operator (once sign-in by phone number is enabled)account country (2.1)compliance with a legal obligation; performance of the contract

4.2. Processing is carried out on the basis of the consent given at registration (Consent to the processing of personal data) and other bases provided by applicable law. As a person registered in the Republic of Uzbekistan, the Operator processes data in accordance with the Law of the Republic of Uzbekistan "On Personal Data" No. ZRU-547 of 2 July 2019. For data subjects in the European Union, the European Economic Area or the United Kingdom, the bases in the table correspond to Article 6 of the General Data Protection Regulation (EU) 2016/679 (GDPR): consent — point 1(a), performance of a contract — point 1(b), legal obligation — point 1(c), legitimate interest — point 1(f).

4.3. Providing the data necessary for registration and operation of the Service (email address, technical session data) is a condition of entering into the contract; the Service cannot be provided without it. Providing other data is voluntary.

5. Access to data within the Service

5.1. Other Users have access to Content the User sends them and to the User's profile and status within the User's privacy settings.

5.2. Space Owners (including moderators) have access to messages in their Spaces, may delete them and have access to their server's moderation log. Calls in voice channels are end-to-end encrypted and are not accessible to anyone other than participants.

5.3. Bots and Mini Apps receive data to the extent set out in 2.12.

5.4. The Operator's staff have access to data within the limits set by section 8.

5.5. Space Owners, other Users, and owners of bots and Mini Apps process the data they receive on their own and at their own responsibility. The Operator does not control and is not responsible for their actions, including copying, forwarding and storing Content received.

6. Transfer of data to third parties

6.1. The Operator entrusts processing of personal data to, or transfers it to, only the following persons and only for the stated purposes:

RecipientData accessiblePurposePlace of processing
Cloudflare, Inc. — delivery networkweb, API and WebSocket traffic passes through Cloudflare: the encrypted connection terminates on its servers, so it can technically access cloud-chat data in transit. Call media does not pass through Cloudflare. Also: DNS, the tunnel to the Operator's server, the cordice.org site, inbound support emaildelivery, DDoS protection, DNS, receiving emailglobal network
Cloudflare, Inc. — TurnstileIP address and browser characteristics"not a robot" check at sign-in and registrationglobal network
Cloudflare, Inc. — R2Users' files and database backups — encrypted only; Cloudflare does not hold the encryption keysobject storageEU
LiveKit, Inc. (LiveKit Cloud)encrypted call media streams (without access to content); technical connection data: IP address, time, traffic volumecall media serverUSA
Resend, Inc.the recipient's address, the time and the service email (including one with a link to the code page). Codes are not included in emailssending service emails (sign-in, confirming actions)EU (eu-west-1)
Google (Firebase Cloud Messaging)on Android: the sender's name and the start of the message text (up to 100 characters), unless the User has hidden previewsdelivering notifications to AndroidUSA and other countries
Apple (APNs)on iOS: the same; for calls only the fact of an incoming call and the caller's namedelivering notifications to iOSUSA and other countries
The User's browser push service (Google, Mozilla, Apple, Microsoft)only the fact that a notification exists and the target browser; the content is encrypted for the User's browserweb notificationsvarious countries
Google Playthe fact of an update check (if the app was installed from Google Play)updates—
Bot and Mini App developersdata under 2.12running the bots and Mini Apps the User usesany country

6.1.1. No SMS messages are currently sent. Once sign-in by phone number is enabled, the phone number and the text with the code will be transferred to an SMS provider, and the Policy will be supplemented. The Operator may use a fallback email sending provider to the extent stated for Resend, supplementing the list of recipients.

6.2. Notifications. The Android and iOS operating systems allow an app to be woken in the background only through Google's and Apple's services. With previews on, Google or Apple receive the sender's name and the start of the message. The User may turn on "Hide message text in notifications", in which case the notification contains only "New message". The content of web notifications is encrypted before it leaves the Operator's server.

6.3. Requests from public authorities. The Operator discloses personal data to public authorities only on a request binding under the law and to the extent set by that request. The content of calls cannot be disclosed, as the Operator does not hold it. The Operator may notify the User of a request received unless prohibited by law. The procedure is set out in Requests from authorities.

6.4. The Operator does not sell personal data.

6.5. Succession. On reorganisation of the Operator or transfer of the Service to another person, personal data may be transferred to the successor in compliance with the law. The Operator notifies Users of such transfer in advance by a means of its choice. The successor is bound to process personal data in accordance with this Policy unless otherwise agreed with data subjects as provided by law.

6.6. Independent controllers. Space Owners, owners and developers of bots and Mini Apps, app stores (Apple, Google) and other Third-Party Services receiving personal data in connection with use of the Service are not the Operator's processors and process such data as independent controllers — under their own policies and at their own responsibility. The Operator is not a party to the relationship between the User and such persons and is not responsible for their processing of personal data, including its lawfulness, security and respect for data subjects' rights. Data subject requests concerning such data are to be addressed to the person concerned.

7. Storage location and cross-border transfer

7.1. The Operator's main server (database, API, data processing) is located in Tashkent, Republic of Uzbekistan. Users' personal data, including that of citizens of the Republic of Uzbekistan, is stored in the database on this server in accordance with Article 27¹ of the Law "On Personal Data". [VERIFY: registration of the database in the State Register of Personal Data Databases]

7.2. Users' files and database backups are encrypted on the Operator's server and transferred encrypted for storage to the Cloudflare R2 object storage located in the EU. The encryption keys are kept by the Operator separately from the storage and are not transferred to Cloudflare. Such storage constitutes a cross-border transfer of personal data in encrypted form.

7.3. Cross-border transfer also takes place: through Cloudflare's network (traffic delivery, Turnstile — global network); to the LiveKit Cloud media server (technical call data and encrypted media streams — USA); to Resend (service emails — EU); to Google's and Apple's push notification services and browser push services (USA and other countries); to the developers of bots and Mini Apps the User uses (any country).

7.4. Cross-border transfer is carried out on the basis of the data subject's consent given at registration (Consent, item 6) and other bases provided by law. The User is informed that in some recipient countries the level of personal data protection may differ from that in the User's country.

8. Access by the Operator's staff to messages

8.1. Cloud chats are stored encrypted on the servers, but the running Service can decrypt them; technical access to them therefore exists. The Operator applies the following restrictions to such access:

  • viewing messages is available only to staff with the moderator role or above, signed in with two-step verification;
  • messages are opened only within a specific report or with a written reason (for example, a fraud investigation or compliance with a legal requirement);
  • every view is recorded in a log stating the staff member, object, time and reason;
  • the number of pages that can be viewed is limited;
  • access to servers and keys is limited to [POSITIONS], and every server sign-in is logged;
  • messages are not viewed for advertising, statistics or any other reason not listed above.

8.2. Listening to calls by the Operator's staff is technically impossible.

9. Retention periods

9.1. Personal data is kept for the following periods:

DataRetention period
Account, profile, contacts, settingsfor as long as the account exists
Messages and filesuntil deleted by the User, a chat moderator or a disappearing-message timer; after account deletion — under section 10
Sign-in codes and the IP address that requested themone day after the code expires
The code page: request information, log of code revealsone day after the link expires
Account country and its history of changesfor as long as the account exists
QR sign-in dataone day after expiry
Sessions (IP address, User-Agent)while the session is active (no more than 180 days) and 90 days after it ends
Phone number or email change records90 days
Service change logs for sync30 days
Unfinished uploads24 hours
Files not attached to any message7 days
Storiesone day after the display ends (except those pinned to the profile)
Uncollected bot updatesup to 24 hours (no more than 10,000 per bot)
Call keysonly on devices, for the duration of the call
Data export archive7 days after it is prepared
Reports and decisions, staff action log3 years, unless a longer period is required to resolve a dispute or by law
Support requests3 years after the request is closed; earlier at the data subject's request, unless otherwise required by law
Service and edge proxy logs14 days
Database backupsstored encrypted in Cloudflare R2: daily — 14 days, weekly — 8 weeks, monthly — 12 months

9.2. On expiry of the retention periods or achievement of the purposes of processing, personal data is destroyed or anonymised, unless longer storage is required by law or for the establishment, exercise or defence of the Operator's rights in a dispute.

10. Account deletion and a copy of data

10.1. Obtaining a copy of data: Settings → Account → Download my data. The Operator prepares an archive containing the User's profile, contacts, messages and files and sends a link to it in the service chat. The link is valid for 7 days.

10.2. Deleting the account: Settings → Account → Delete account. Deletion is confirmed with a code. A User who owns servers must transfer them to another member or delete them before deleting the account.

10.3. Deletion proceeds as follows:

  1. Deferred deletion (14 days). The account is marked for deletion. Signing in to the account during this period cancels deletion.
  2. Permanent deletion. On expiry of the period, the following are destroyed: phone number and email address, profile, sessions and devices, contacts, subscriptions, push tokens, two-step verification settings, stories. The username (@username) is released.
  3. Data retained. Messages the User sent to chats with other persons and files attached to them remain with the other participants; "Deleted account" is shown instead of the User's name. To remove their messages, the User may delete them for all participants before deleting the account. Reports, the moderation log and support requests are retained, unlinked from the account, for the periods in section 9.
  4. Backups. Deleted data is removed from the running Service immediately and remains in encrypted backups until their retention period expires — no more than 12 months (section 9).

11. Rights of the data subject

11.1. Every User, to the extent provided by applicable law, has the right to:

  • obtain information on the processing of their personal data and a copy of it (including through "Download my data");
  • require rectification of inaccurate data (most data can be changed in Settings);
  • require erasure of data and delete the account (section 10);
  • withdraw consent, including the separate consents to contact sync, notifications with message text and newsletters;
  • object to processing or require its restriction;
  • receive data in a machine-readable format to transfer it to another service;
  • challenge the Operator's actions or omissions before the competent authority or in court (section 15).

11.2. Data subjects in the Republic of Uzbekistan, under the Law of the Republic of Uzbekistan "On Personal Data" No. ZRU-547, also have the right to:

  • obtain information on whether the Operator holds their personal data, its composition, the purposes, bases, methods and periods of processing, and the third parties to whom it is transferred;
  • require rectification, blocking or destruction of personal data that is incomplete, outdated, inaccurate, unlawfully obtained or not necessary for the stated purpose of processing;
  • challenge the Operator's actions or omissions before the competent public authority or in court;
  • exercise other rights provided by that Law.

11.3. Data subjects in the European Union, the European Economic Area or the United Kingdom have, under the GDPR, the right:

  • of access (Article 15), to rectification (Article 16) and to erasure (Article 17);
  • to restriction of processing (Article 18);
  • to data portability — receiving data in a structured, machine-readable format (Article 20);
  • to object to processing based on legitimate interest (Article 21);
  • not to be subject to a decision based solely on automated processing which produces legal effects or similarly significantly affects the data subject (Article 22); decisions to apply measures to a User are taken by a person (2.14.3);
  • to withdraw consent at any time without affecting the lawfulness of processing before withdrawal (Article 7(3));
  • to lodge a complaint with a supervisory authority (Article 77).

11.4. Withdrawal of consent to processing of data without which the Service cannot be provided (4.3) entails termination of the contract and deletion of the account. Withdrawal of consent does not prevent processing carried out on other lawful bases (compliance with a legal obligation, legitimate interest, defence of rights in a dispute).

11.5. How to submit a request. A request is sent to [email protected] from the email address or phone number linked to the account, or through support in the app. The Operator may request information necessary to verify the requester's identity and ownership of the account and may decline to act on the request until it is verified.

11.6. Response time. The Operator considers the request and responds within the periods set by applicable law; for data subjects covered by the GDPR — within one month, extendable by a further two months taking into account the complexity and number of requests, with the data subject informed of the extension and the reasons for it.

11.7. The Operator may refuse a request in whole or in part in the cases provided by applicable law, including where compliance would infringe the rights and freedoms of others, and in respect of manifestly unfounded or excessive requests, stating the reasons for refusal.

12. Persons under 16

12.1. The Service is intended for persons aged 16 and over. Age is confirmed by the User at registration; no document check is carried out. The User is responsible for the accuracy of the confirmation.

12.2. On receiving information that an account belongs to a person under 16, the Operator closes the account and deletes its data. Parents and legal guardians may report such an account to [email protected].

13. Security

13.1. The Operator applies the following legal, organisational and technical measures to protect personal data:

  • in transit: connections encrypted with TLS 1.2 or higher; calls — end-to-end encryption;
  • at rest: messages, files, reports, support requests, phone numbers and email addresses (and, once the feature is enabled, voice transcripts) are encrypted with AES-256-GCM. The data keys are themselves encrypted with a root key that is kept outside the database and the file storage and is not accessible to storage providers, so neither a copy of the database nor the contents of the file storage can be read on their own. As of the date of this version the root key is kept on the same Operator server as the database, and the server's disk is not encrypted; moving the keys to a separate key server is planned. Database backups are encrypted and stored in Cloudflare R2;
  • codes, backup codes and tokens are stored only as hashes;
  • session keys on mobile devices are kept in the operating system's secure storage;
  • staff access to servers and the admin panel requires two-step verification and is logged.

13.2. The Operator takes reasonable and proportionate protective measures having regard to the nature of the data, the state of the art and the risks of processing. No method of transmitting or storing data is absolutely secure, and the Operator does not guarantee absolute protection of data against unauthorised access. The Operator is not liable for the consequences of unlawful acts of third parties who have overcome the protective measures taken, or for the loss or disclosure of data resulting from the User's acts or omissions, including sharing sign-in codes or losing control of a device, phone number or email address — to the extent permitted by law.

13.3. The User must keep their devices, phone number, email address, sign-in codes and backup codes secure and promptly notify the Operator of any unauthorised access to the account.

13.4. Vulnerability reports are sent to [email protected] (Vulnerability disclosure policy).

13.5. Incidents. In the event of a security breach that may affect Users' personal data, the Operator notifies the competent authority and the affected data subjects in the cases, manner and periods established by applicable law, without undue delay; for data subjects covered by the GDPR — notification of the supervisory authority within 72 hours of the Operator becoming aware of the breach, where required by Article 33 of the GDPR.

14. Changes to the Policy

14.1. The Operator may amend the Policy unilaterally. A new version takes effect on publication in the Service unless it specifies a different date.

14.2. The Operator notifies Users of material changes affecting their rights by a means of its choice (including in the Cordice service chat) before the changes take effect, as a rule at least 14 days in advance, except for changes required by law, decisions of public authorities or the need to address security threats, which may take effect immediately. Editorial changes that do not affect Users' rights take effect on publication without separate notice.

14.3. Where a change in the data processed or the purposes of processing requires new consent of the data subject under the law, the Operator requests such consent; until it is obtained, no processing for the new purposes is carried out.

14.4. Continued use of the Service after a new version takes effect means acknowledgement of it. If the User does not agree with the new version, the User may stop using the Service and delete the account, and exercise the rights set out in section 11.

14.5. The date of the current version is stated at the beginning of the Policy. Earlier versions are provided on request.

15. Enquiries and complaints

15.1. Questions and requests relating to the processing of personal data are sent to the Operator at [email protected]. Contacting the Operator is not a precondition for applying to the competent authority or a court.

15.2. The data subject may apply to the competent authority:

  • in the Republic of Uzbekistan — the State Personalisation Centre under the Cabinet of Ministers of the Republic of Uzbekistan;
  • in the European Union — the supervisory authority of the place of habitual residence, place of work or place of the alleged infringement;
  • in another country — that country's data protection authority.

16. Final provisions

16.1. The Policy is drawn up in Russian and Uzbek; both versions are equally authoritative. The English version is a translation provided for convenience.

16.2. Relations connected with the processing of personal data are governed by the legislation of the Republic of Uzbekistan and, for data subjects in the European Union, the European Economic Area or the United Kingdom, also by the mandatory rules of the data protection legislation applicable to them. The rights of the data subject provided by law cannot be limited by this Policy.

16.3. If any provision of the Policy is held invalid, this does not affect the validity of the remaining provisions.

16.4. Matters not governed by the Policy are governed by the Terms of Service and the law. In the event of conflict between the Policy and the Terms of Service on matters of personal data processing, the Policy prevails.