Skip to content
CiThreeCiThree

CiThree legal

Privacy Policy

Account and workplace data, confidential ratings, communications, service providers, device storage and deletion.

Version 2026-11-07.1 · Effective 2026-11-07 · English

Download document (.txt)

1. Operator and privacy contact

CiThree is operated by CiThree LIMITED LIABILITY COMPANY (CiThree LLC, Armenian «ՍԻԹՐԻ» ՍՊԸ), registered in the Republic of Armenia on 10 October 2026 under registration number 999.110.1616996. Its registered address is 34 Karakhanyan St., Apt. 5, Nor Nork, Yerevan 0092, Armenia. Contact the company at [email protected].

CiThree LLC determines the purposes and means of processing for its platform. Send privacy questions and data-rights requests to [email protected]. Signed-in Contact us is an additional route. The same email address is available to people who cannot sign in.

Organizations independently decide which membership requests to approve and how they use information in their activities. Their responsibilities and decisions operate alongside CiThree LLC's responsibilities for the platform.

2. Information and its sources

Account and profile information includes your name, email address, phone number, account and public profile IDs, profile photo or organization logo, company description, verification status and account preferences. A phone number is required by the current personal-registration form and optional for company registration. Passwords are stored as password hashes.

Relationship and workplace information includes organization and team memberships, applications, approvals, membership dates and history, Circle contacts, organization partnerships, work schedules, availability and notes when those features are used. Information can come from you, an organization representative or another participant.

Content includes publications, links, selected audiences, ratings, message text and participants, timestamps, reactions, reports, support conversations and selected attachments. Support attachments can include images, PDF, Word and spreadsheet files. Profile, publication and support files can be stored by the service.

Security records include session IDs, refresh-token hashes, IP addresses, user-agent information, sign-in attempts, email-verification and password-reset records, notification registrations and operational logs. Search requests leave your device to obtain results.

Website and app activity reports include sign-in time, account reference, platform and a country inferred from the connection. Country information can be approximate or unavailable. The service also keeps aggregate guest page-view statistics. This processing uses connection information and is independent of a GPS permission.

Android notifications use push tokens and Firebase installation information. Embedded services can also receive browser, device and connection information as described below.

When you affirmatively accept an active agreement, the evidence includes your account, document version and content hash, acceptance time, selected confirmations and a web or mobile client label. The legal-acceptance record adds no separate IP field. Session and network systems can process IP addresses for their own purposes.

3. Purposes and applicable grounds

We process information to provide accounts, verification and recovery, organization and membership features, eligible ratings and limits, publications and chosen audiences, messages, schedules, notifications, support, moderation, security and operation of the service.

Where applicable law requires a legal basis, we use the basis appropriate to the specific processing. This can include your consent, processing objectively necessary to provide the service you request, an applicable legal obligation, or a legitimate interest permitted by the relevant law after the required necessity and rights assessment.

Optional processing that requires consent is offered with the required choice. You can withdraw a consent-based choice through the available control or by contacting [email protected]. Withdrawal applies to that processing going forward and is assessed alongside any separate applicable ground for retaining specific information.

Organization membership and employment do not authorize an organization to compel ratings or demand proof of a person's submitted rating. Agreement to service terms and acknowledgment of a privacy notice are recorded separately from any optional consent.

4. Audiences and confidential ratings

Profile information, relationship information, aggregate scores and publications are available according to the feature and applicable settings. Organization representatives can access information needed to manage their applications, memberships, teams and schedules.

Personal publication audiences can include C1, C2, C3 or All. C1 and C2 publication audiences use current relationships by default. An author can also include former colleagues whose qualifying membership periods overlapped. The C3 publication audience is fixed from the relevant Circle contacts when the publication is first created. Organization feeds can show All and C2-selected publications by their current members.

Hiding a publication or source controls your own feed. An author can pause and resume their own publication. Publication and advertising expiry dates continue to run while a publication is paused. Recipients can independently keep information they were permitted to access.

Ordinary rating displays show aggregates and permitted count labels. Other participants and organization management do not receive an itemized list of who gave each individual score. General submission responses and delayed personal-rating application reduce the information available from the timing of a score change.

Pending personal ratings can temporarily contain the individual numerical inputs needed to apply the rating. Under the deployed minimized-retention model, processed, immediately applied and suppressed ratings do not retain the individual numerical history used by earlier versions. Account and target references, time, scale, relationship, processing status and duplicate-prevention records can remain for limits and service integrity. Current aggregate scores remain.

These retained references remain protected personal information. Authorized personnel may access relevant records for a necessary operational, security or lawful purpose. Requests for contributor information are assessed under applicable law and the rights of everyone affected. Earlier recovery copies and external observations can have different information from the current minimized records.

Ratings summarize participant opinions. CiThree supplies information and does not itself decide whether an employer hires, dismisses or promotes a person. Consider relevant independent information when making consequential decisions. Contact [email protected] about inaccurate information, manipulation or an allegedly unlawful use.

5. Messages, files and device copies

Message text, participants, timestamps and related records are stored by the service. Images sent through the device chat-image feature pass through the server as a relay and are kept in the participating devices' application storage. The server can retain attachment metadata. Image availability depends on the relevant device copies and transfer conditions.

Profile photos, publication and sponsored images, and support attachments use separate storage processes and can remain in the database or private file storage. Photo and camera access is used when you select or capture an image. Notification sounds use audio playback. The present application has no voice-message recording feature.

Your device can contain cached profiles, offline action queues, preferences and chat images. Signing out, removing the application and clearing device storage affect different records. Copies exported to a gallery or independently saved by a recipient are controlled through the relevant device or recipient.

Operating-system backup and device transfer can keep preferences or files according to their configured rules. Protected credential storage has separate controls. Copies exported to a gallery, retained by recipients or included in independent device backups follow the relevant device and provider settings.

6. Service providers and recipients

Hetzner supplies the platform's primary hosting infrastructure for the server, database and private files. Cloudflare provides DNS, network protection and website traffic handling. Cloudflare also routes messages sent to the company's public email address to a company-monitored Google mailbox.

Resend delivers verification, password-reset and configured operational email. Delivery involves the destination address, message content and any temporary link needed for that message. Keep verification and reset messages private.

Google Firebase Cloud Messaging and Firebase installation services support Android notifications. The platform's push payload contains routing identifiers, unread counts and notification settings. Conversation text and sender names are omitted from that push payload. Provider services also process installation, application and connection information.

Expo/EAS supplies application-build infrastructure. The inspected Android release uses native Firebase tokens and direct server-to-FCM delivery. Its configuration disables Expo over-the-air application updates.

Selected publication and message recipients, relevant organization representatives and necessary service personnel receive information through the features they use. Information may also be disclosed where a valid legal requirement applies.

Providers, their infrastructure and authorized operations can process information in countries outside Armenia and your home country. Applicable transfer requirements and the arrangements relevant to a particular service or request must be assessed for that processing. Contact [email protected] for information about relevant recipients and transfers.

7. YouTube and external links

Linked YouTube videos can load a preview image from Google before you play the video. Loading an embedded player also makes requests to YouTube. Those requests can include IP address, browser or application information, the requested video, player interactions and cookies or similar identifiers according to Google's processing and your settings.

Video autoplay settings offer Always, Wi-Fi only and Never. The current default is Always. Autoplay preferences control automatic playback, while preview images can still make an external request. Required choices for optional third-party processing must be provided for the relevant processing and jurisdiction.

Google describes its handling of information in its Privacy Policy at https://policies.google.com/privacy and its partner-services notice at https://policies.google.com/technologies/partner-sites. Embedded YouTube features are subject to https://www.youtube.com/t/terms. The player may display advertising supplied by YouTube. CiThree's present integration does not request access to your YouTube account.

Opening an external link allows the destination to handle the connection under its own practices. Review that destination's notice when deciding whether to use its service.

8. Storage and security measures

The website uses authentication cookies and browser storage. The app uses protected device storage for session credentials. Preferences, offline features and relevant images also use device storage. Embedded third-party media can use additional identifiers or storage.

The deployed client uses HTTPS for the public website and API and secure WebSocket connections. The service uses password and token hashing, authenticated access checks, restricted private-file handling and encrypted recovery archives. Appropriate access and security controls are maintained for their respective purposes.

Communication and relay features require the service to process the information needed for delivery. Independent provider storage, recipient copies, earlier archives and live storage have their own controls. Contact [email protected] if you believe an account or information has been exposed.

9. Retention and deletion

Account, profile, membership, schedule, message, support and publication information is kept while needed for the live account and the relevant service records, subject to a valid deletion request and any specific lawful retention requirement. Archived publications, hidden items, ended memberships and blocked conversations can remain stored. The service has no general automatic deletion rule triggered solely by account inactivity.

Detailed sign-in and country records, website account-activity records and aggregate guest page-view records are retained on a rolling 30-day basis. A scheduled cleanup removes older records.

Individual rating inputs follow the minimized-retention process described in section 4. Pending inputs remain available while required for processing. Limited action records and identifiers support cooldowns, quotas, duplicate prevention, abuse handling and the integrity of the service.

Session and recovery credentials expire according to their access limits. Expiry, replacement or revocation ends validity and can leave limited database records. These records and operational logs are retained for necessary access management, security, abuse investigation or an applicable legal requirement, with deletion or minimization when their continuing purpose ends.

Completed scheduled server-backup pairs older than 30 days are removed after a fresh encrypted backup is verified. Separately retained manual, downloaded and historical recovery archives follow their recorded recovery or incident purpose and review process. Recipient, gallery and provider copies have their own controls.

Account erasure leaves a restricted ledger with retired account, profile and public identifiers, account type and deletion time. Retired public IDs are reserved permanently to prevent their reuse. File storage keys remain in the cleanup queue while removal is pending and are cleared after successful cleanup. The erasure ledger supports reliable deletion and recovery handling.

Where a specific legal obligation, security incident or dispute requires keeping particular records, the retained scope and duration must be appropriate to that purpose. You can contact [email protected] to ask about the retention applying to your information.

10. Deleting your personal or company account

Use the account-deletion option in the website or app settings, or visit https://cithree.com/delete-account. The self-service flow asks for the account password and the confirmation DELETE. If you cannot sign in, use password recovery or contact [email protected] for a verified request.

Successful self-service deletion removes the live account and linked profile, authored messages and publications, relevant memberships, related rating and agreement records, account sessions and associated notification registrations. A company account's deletion also removes its owned teams, memberships, schedules and content. Members' separate personal accounts remain independent.

An administrator-scheduled account deletion has a 30-day recovery period. The moderation process records its status, deadline and recovery options separately from immediate self-service deletion.

Other participants' aggregate scores can remain at their existing values. Shared conversation objects, other people's contributions and independently retained copies can remain. Private-file cleanup runs asynchronously and retries failures. Recovery archives follow the retention arrangements above.

Before a restored backup is reopened to users, the operator must reconcile the current erasure records and reapply recorded deletions. A deletion request is assessed for any limited records that must be retained under a specific lawful reason.

11. Requests, controls and complaints

Email [email protected] to ask about access, correction, deletion, restriction, objection, withdrawal of consent or a portable copy where the applicable law provides that right. Describe the request and provide enough information to identify the account or event. Use Contact us as an additional route when signed in.

We may request proportionate information to verify identity or authority. Avoid sending passwords or unnecessary identity documents. We assess the request and the rights of other people affected, communicate the outcome and follow the response periods and permitted extensions under applicable law.

Available controls include supported profile editing, publication audiences, membership-visibility settings, notification preferences, video autoplay, session revocation, password recovery and account deletion.

You may complain to the competent data-protection or other supervisory authority and seek the remedies available under the law applicable to your situation. The company can provide its response and relevant information through [email protected].

12. Adults and child safety

CiThree is for people who are at least 18 and have reached legal adulthood where they live. New-account agreement controls require an affirmative adulthood confirmation. A confirmation records the user's declaration and has practical verification limits.

If you believe a child has supplied information or may be at risk through CiThree, use Contact us or email [email protected]. Provide the relevant public ID or content reference and the reason for concern. The operator will assess the report, restrict or remove relevant content or access when appropriate, and follow the reporting and protective obligations required by law.

13. Updates to this policy

Published versions carry their publication and effective dates. Material changes to purposes, recipients, storage, retention or rating confidentiality will be explained with the notice and any advance notice or fresh choice required by applicable law.

Previous versions remain available through the legal-document archive. A new acceptance or acknowledgment record is created only for an actual affirmative action against the version presented to the user.

Document fingerprint (SHA-256): 176b28605c2fc2e41a04fd96251bc63f49dab8feeab96a64310343bede5488d1