PRIVACY NOTICE
Version dated 1 November 2026. Website: https://sargo.uz.
Current operation
The website operates as a catalogue and accepts requests for advice and quotations. Enquiries are stored on the website server, sent to Google Sheets CRM and accompanied by brief notifications in the SARGO SALES Telegram work chat. These functions support enquiry handling; purchases and payments cannot be completed directly on the website. You can also contact the company using the published phone number and email.
1. Website owner and contact details
The website owner and company responsible for processing data is «SARGO» MAS’ULIYATI CHEKLANGAN JAMIYAT («SARGO» MCHJ), tax identification number (STIR) 312472902.
Registered address: Republic of Uzbekistan, Samarkand Region, Samarkand City, XAZORA MFY, SPITAMEN KO‘CHASI, 270-UY.
Data-related enquiries: Info@sargogroup.com, +998702240004. Contact person: Parviz Sobirov Murodilloevich.
2. Enquiries: information, purposes and recipients
When you submit an enquiry, «SARGO» MCHJ processes information to respond, advise you about products and discuss cooperation terms. Your consent is the basis for processing the enquiry. Submitting an enquiry does not subscribe you to advertising.
Depending on the form, the information processed includes your name, phone number, comment, company and email, country/region/city, products and quantities of interest, project or cooperation details you provide, enquiry source and tags, language, creation time, and consent details and version. Phone numbers are normalized. If you attach a project, the PDF file of up to 5 MiB and its metadata are retained. Do not include unnecessary information about yourself or other people in your enquiry or file.
Enquiries are stored in PostgreSQL on an aHOST server in Germany. Google Sheets CRM receives the enquiry identifier and date, name, phone number, product, area/volume, source and information used to handle the enquiry. Notes may include company, email, location, project, timing, technical requirements, delivery details and comments you provide, together with calculations and enquiry-source tags. For an attached PDF, the CRM receives its identifier and a restricted link requiring staff sign-in, not the file itself.
The SARGO SALES work chat in Telegram receives a brief notification: enquiry identifier, decor, area, city, and a CRM link or a pending-record status. Your name, phone number, comment and PDF are not included in this notification. These services support enquiry tracking and responses; their use involves transfers outside the website infrastructure.
Public enquiry records do not store IP addresses or browser information. This does not mean that no technical information is processed when the website operates or by infrastructure providers. Meta Pixel loads only after the visitor gives separate, voluntary consent and records views of public pages. Declining consent does not restrict access to the catalogue or forms. Meta may receive the page and referrer URLs, IP address, browser and device information, and cookie identifiers. We do not add names, phone numbers, form contents or enquiry identifiers to events.
The visitor’s choice is stored separately in the browser without automatic expiry. Consent can be withdrawn. After withdrawal, events stop being sent; data previously received by Meta is not automatically deleted.
2.1. Cookies, browser storage and technical records
The sargo_locale cookie stores your selected language for 365 days. Browser local storage contains the animation preference sargo.motion.preference (off/auto) and, if already present, sargo.analytics.consent: the consent choice, version and recording time. These local records have no automatic expiry. No new consent interface is displayed while analytics are disabled; an existing record does not mean analytics are running.
Tab storage holds up to three decor identifiers for comparison, enquiry receipt details (identifier, mode and time), and up to 100 identifiers of viewed receipts. A receipt is valid for 30 minutes, but its storage record is not deleted by a timer. sessionStorage records are limited to the tab session. You can remove these records using your browser controls.
Names, phone numbers and comments are not saved in these browser stores; while a form is being completed, they are held in page memory.
Application error logs contain events, request identifiers, statuses and error codes, but not enquiry contents; background-task logs contain identifiers and statuses. This describes application logs, not every log maintained by the hosting provider.
2.2. Separate staff access
Staff access to the CMS uses an eight-hour __Secure-better-auth.session_token cookie with HttpOnly, Secure, SameSite=Lax and Path=/. Server-side staff session records include user identifiers, tokens, dates, browser information and IP addresses where available. The CMS audit log records staff, actions, objects and times. This access is separate from browsing the public catalogue.
2.3. Staff Google Sheets connection
SARGO Website CRM records enquiries in the Google Sheets spreadsheet selected by the company. The owner of the staff console configures this connection. Catalogue visitors do not need to sign in to Google or grant access to their Google Drive.
After the owner's separate consent, the application requests drive.file permission and access that can operate while the owner is not present in the browser. This permission type covers files the user authorizes for the application; the SARGO implementation additionally limits operations to the preselected CRM spreadsheet. It does not request full access to Google Drive, Gmail or contacts.
During setup, the application reads the selected file's identifier, type, ownership and editability information, sheet structure and column headers. During operation, it reads registry rows, including existing contact details, notes and statuses, to detect duplicates, avoid overwriting occupied rows and assign the responsible staff member correctly. It writes the enquiry information listed in section 2 and updates the assignee and status. These data are used to record and handle SARGO enquiries.
The selected spreadsheet identifier, connection confirmation information and authorization state are stored on the server outside the website's public files. Stored Google tokens are protected by encryption and access restrictions. This describes token storage, not encryption of all data or provider backups. Tokens allow the application to call Google on behalf of the authorizing owner. A temporary access token is also provided to the file-selection page only for the signed-in owner; the application does not write it to browser localStorage or sessionStorage. The contents of read rows are processed on the server; the website database stores enquiry information, identifiers and delivery state. Tokens themselves are not shared with visitors, with managers through Telegram or with other enquiry recipients.
Spreadsheet access depends on permissions configured in Google. On the date of this version, CRM access is limited to the company owner and the company’s technical service connection; managers’ individual accounts have not yet been connected. Staff receive separate access within their responsibilities when onboarded. Notifications are received by the SARGO SALES work group; membership of that group does not provide access to the spreadsheet. aHOST provides infrastructure and Google provides the APIs and spreadsheet service. The application does not use Google data for advertising, sale or other purposes not described in this notice. Brief Telegram notifications are generated from website enquiries as described in section 2, not by exporting the registry read from Google.
The owner can revoke SARGO Website CRM access in their Google Account settings. To disconnect it on the SARGO side and request deletion of stored tokens or related data, contact Info@sargogroup.com. Revoking permission stops further authorized access through Google, but does not itself delete previously stored enquiries, spreadsheet records or backups. Requests to delete those data are considered separately under sections 3 and 5. This notice does not promise automatic deletion of tokens or all copies of data.
3. Retention
The company’s retention period for ordinary enquiries is 12 months after the last contact concerning the enquiry. This period applies to ordinary enquiries; records relating to concluded contracts are subject to separate periods taking legal requirements into account. Retention periods for technical logs and backups are determined separately.
You can request deletion or withdraw consent by writing to Info@sargogroup.com. If processing must continue on another lawful basis, the company will explain that basis to you.
The retention period is applied through manual review of enquiries by the company owner. The last actual contact is established from verified communication records, not the scheduled date of the next contact. When the period expires or a justified deletion request is received, the company checks whether continued retention is necessary and removes data that no longer need to be retained from the active website database, CRM and company-controlled messages and attachments. Automatic deletion is not configured. Deleting active records does not mean that every backup or technical log is immediately erased; exact provider-log and backup periods are not specified in this notice. Information about a particular enquiry and its deletion can be requested through the stated email.
4. Processing outside Uzbekistan
The website and database are hosted by aHOST in Germany. Google and Telegram also process data within the services used. Their processing and backup storage are not represented as being limited exclusively to Germany or Uzbekistan. This notice does not replace assessment of applicable data-transfer and processing requirements.
5. Your rights
You can write to Info@sargogroup.com to request information about the processing of your data, correction, cessation of processing or deletion, or to withdraw consent previously provided. Please identify the enquiry concerned. To protect your data, the company may request information needed to verify your identity. Requests are considered under applicable Uzbekistan law. You may seek protection of your rights from the competent public authority or a court.
6. Changes
The company will update this notice when the way the website operates changes.