G-Control Sign in
TEMPLATE. NOT LEGAL ADVICE. Prepared by an AI assistant (not a licensed lawyer) on 2026-11-18, modelled on Article 28 GDPR. For EU customers the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) must be attached in full, unchanged. A licensed lawyer must review before use. Fill in [...], then delete this box.

Data Processing Agreement (DPA)

Between the Customer (controller, "Customer") and [KOMPANIYA], [MANZIL], tax ID [STIR] (processor, "Provider"). This DPA forms part of the Terms of Service for G-Control, G-Market and G-Agronom. If this DPA conflicts with the Terms, this DPA prevails for personal data.

1. Subject matter and duration

The Provider processes Customer Personal Data only to provide the Services ordered by the Customer, for the term of the Terms and the deletion period in section 11. Details are in Annex I.

2. Customer instructions

  1. The Provider processes Customer Personal Data only on documented instructions from the Customer: the Terms, this DPA, the Order and the settings the Customer chooses in the Services (including the data region and whether AI agents and Telegram are enabled).
  2. If the Provider is required by law to process otherwise, it informs the Customer first, unless the law forbids that.
  3. The Provider tells the Customer immediately if, in its opinion, an instruction breaks data protection law.
  4. The Provider does not sell Customer Personal Data, does not use it for its own purposes, and does not combine it with other data, except as needed to provide and secure the Services (CCPA "service provider" terms, Cal. Civ. Code §1798.140(ag)).

3. Confidentiality

Everyone at the Provider who can access Customer Personal Data is bound by a confidentiality obligation and gets access only when needed.

4. Security (Art. 32 GDPR)

The Provider applies the technical and organisational measures in Annex II and may improve them, but not reduce the overall level of protection.

5. Sub-processors

  1. The Customer gives general authorisation to use the sub-processors in Annex III.
  2. The Provider informs the Customer at least [30] days before adding or replacing a sub-processor (email to the account owner and the list at [SAYT]/subprocessors). The Customer may object on reasonable data protection grounds; if no solution is found, the Customer may terminate the affected Service and receive a pro-rata refund of prepaid fees.
  3. The Provider signs a written contract with each sub-processor with data protection obligations no weaker than this DPA and remains responsible for it.
  4. Customer-directed services (Anthropic when the Customer uses its own API key; Telegram, WhatsApp, payment or fiscal operators the Customer connects) are chosen and contracted by the Customer. The Provider only transmits data to them on the Customer's instruction and is not responsible for their own processing.

6. International transfers

  1. The Provider stores Customer Personal Data in the data region chosen in the Order. It does not move it to another country except to the sub-processors in Annex III or on the Customer's instruction.
  2. Where a transfer needs a legal mechanism, the parties use: for EU/EEA data — the EU SCC (Module 2 controller→processor; Module 3 for onward transfers to sub-processors), with the annexes of this DPA as the SCC annexes; for Turkey — the KVKK standard contract, notified to the KVKK Board within 5 business days; for Russia — the operator's prior notice to Roskomnadzor (152-FZ Art. 12) and data localisation in Russia; for Kazakhstan — storage in Kazakhstan (Law 94-V Art. 12) and transfer only under Art. 16; for Uzbekistan — the safeguards under Law ZRU-547 Art. 15 and 27-1; for the UK — the UK Addendum to the SCC; for Saudi Arabia / UAE — the transfer rules of their PDPLs.
  3. The Provider's staff in Uzbekistan may access data remotely for support and maintenance only. [TEKSHIRILSIN: whether remote access from Uzbekistan counts as a transfer under each law — it does under GDPR.]

7. Help with data subject requests

The Services let the Customer find, export, correct and delete data. If the Provider receives a request directly, it forwards it to the Customer without undue delay and does not answer it on its own unless authorised.

8. Personal data breach

  1. The Provider notifies the Customer without undue delay and in any case within [24] hours after becoming aware of a personal data breach affecting Customer Personal Data. (24 hours is chosen so the Customer can meet the strictest deadline: Russia 24 hours to Roskomnadzor; EU/Turkey/Saudi Arabia 72 hours.)
  2. The notice includes, as far as known: what happened, categories and approximate number of people and records, likely consequences, measures taken, and a contact person. Information may be provided in phases.
  3. The Provider helps the Customer notify authorities and individuals. Notification by the Provider is not an admission of fault.

9. Help with impact assessments

The Provider gives reasonable information for the Customer's data protection impact assessments and prior consultations.

10. Audits

The Provider makes available information needed to show compliance with this DPA: security description, policies, [certificates or audit reports when available]. On-site audits: once a year, with [30] days' notice, at the Customer's cost, by an auditor bound by confidentiality, or more often if required by a supervisory authority or after a breach.

11. End of processing

After the contract ends the Customer may export its data for [30] days. Then the Provider deletes Customer Personal Data from live systems within [30] days and from backups within [N] days, unless law requires longer storage. On request the Provider confirms deletion in writing.

12. Liability

Liability under this DPA follows the limitation of liability in the Terms, except where applicable data protection law does not allow it.


Annex I — Description of processing

ItemG-ControlG-MarketG-Agronom
Data subjectsCustomer's employees, contractors, clients, leads, partnersCustomer's employees/cashiers, buyers, debtors, suppliersCustomer's employees, agronomists, field workers, farmers/partners, suppliers
Personal datanames, phones, emails, messages, files, tasks, deals, HR records (position, attendance, salary), documentsnames, phones, purchase history, receipts, debt (nasiya) amounts and due dates, loyalty data, cashier PIN logsnames, phones, field boundaries and coordinates, device GPS during scouting, photos, voice notes, warehouse/chemical records
Special categoriesnot intended; Customer must not enter health/biometric data without legal basis and written noticenot intendednot intended (no voice biometrics)
Nature of processinghosting, storage, display, search, backup, sending notifications, AI agent requests (if enabled), Telegram delivery (if connected)samesame + map display, offline sync from devices
Purposeproviding the Services to the Customersamesame
Durationterm of the Terms + section 11samesame
Frequencycontinuouscontinuouscontinuous

Annex II — Technical and organisational measures (summary)

  1. Encryption in transit (TLS 1.2+). Encryption at rest provided by the hosting provider [TEKSHIRILSIN per provider]. Customer API keys encrypted in the application.
  2. Passwords stored only as salted hashes; cashier PIN logins limited to registered terminals.
  3. Role-based access; new users have zero permissions; server checks permission on every request.
  4. Logical separation of each Customer's data (tenant ID on every record); tests for cross-tenant access.
  5. Access logs and admin action logs kept [90] days.
  6. Daily backups, kept [N] days, restore tested [quarterly].
  7. Security updates; dependency and code scanning (e.g. semgrep) before releases.
  8. Staff: confidentiality obligation, least-privilege access, two-factor authentication on admin accounts.
  9. Incident response plan with a 24-hour customer notification target.
  10. AI agents: off by default; use only Customer's key; read data with the requesting user's permissions; cannot change data without human confirmation.

Annex III — Sub-processors and Customer-directed services (as of [SANA])

#NameServiceLocationDataWhen usedSafeguard
1Railway CorporationCloud hosting, database, backupsUSA; region [US / EU-West] [TEKSHIRILSIN]all Customer Data in that regionalways (current region)DPA with Railway [TEKSHIRILSIN: railway.com/legal]; SCC
2[UZ-HOSTING-PROVAYDER]Local hosting for Uzbekistan regionUzbekistanCustomer Data of UZ regionwhen UZ region selectedlocal contract
3[KZ-HOSTING-PROVAYDER]Local hosting for Kazakhstan regionKazakhstanCustomer Data of KZ regionwhen KZ region selectedlocal contract
4[RU-HOSTING-PROVAYDER]Local hosting for Russia regionRussiaCustomer Data of RU regionwhen RU region selectedlocal contract
5[EU-HOSTING-PROVAYDER]EU hostingEU member stateCustomer Data of EU regionwhen EU region selectedGDPR Art. 28 contract
6[EMAIL-PROVAYDER]Transactional email (log-in codes, notifications)[DAVLAT]name, email, message content of notificationsalwaysDPA + SCC
C1Anthropic PBCAI model (Claude API) for AI agentsUSAthe user's prompt and the Customer Data needed to answer itonly if the Customer enables AI agents with its own API keyCustomer-directed: Customer's own contract with Anthropic (commercial terms + Anthropic DPA) [TEKSHIRILSIN]
C2Telegram (Telegram FZ-LLC / Telegram Messenger Inc.) [TEKSHIRILSIN entity]Bot messages, notifications, chat integrationUAE / globalnames, Telegram IDs, message content sent through the botonly if the Customer connects a Telegram botCustomer-directed; Telegram Terms of Service / Bot Platform terms; Telegram does not sign individual DPAs [TEKSHIRILSIN]
C3Open-Meteo (G-Agronom)Weather dataEU (Switzerland/Germany) [TEKSHIRILSIN]field coordinates only, no namesonly if the Customer turns weather on (off by default)no personal data sent; check commercial licence
C4[TO'LOV-PROVAYDER], [FISKAL-OPERATOR]Payments, fiscal receiptsCustomer's countryas required by that serviceonly if connected by the CustomerCustomer's own contract