DATA PROCESSING AGREEMENT (DPA)

Status and Acceptance of the DPA

This DPA forms part of the NN Agent Terms of Service and applies when the User transfers or provides the Platform with access to third parties’ personal data.

"User" under this DPA is the Controller; Individual Entrepreneur Tatiana Reznikova is the Processor. If applicable law characterises the roles differently in a specific operation, the parties fulfil the obligations corresponding to their actual role.

Acceptance of the DPA is effected simultaneously with the Terms of Service or by a separate electronic action in the interface. The current version may be published at https://nexifyneo.com/policy/dpa/en.

Subject Matter and Documented Instructions

The Processor processes Customer Data solely for the purpose of providing the functionality of NN Agent in accordance with the Terms of Service, the Platform settings, and the Controller’s documented instructions.

Instructions include, in particular: uploading a database, connecting a Telegram account, selecting campaign recipients, enabling the AI function, configuring CRM/funnel, connecting an integration, requesting export/deletion, and other actions performed by the Controller’s authorised person in the interface.

If the Processor has reasonable grounds to believe that an instruction is unlawful, it may suspend its execution and request clarification. This does not relieve the Controller of the obligation to maintain a legal basis for processing.

Description of Processing

Obligations of the Controller

  • to maintain a legal basis for the collection, use, transfer, and outbound communications in relation to each relevant set of data;
  • to provide data subjects with mandatory information and to ensure the exercise of their rights;
  • to comply with direct marketing rules and to maintain evidence of consent/opt-out where the Controller is the sender of marketing communications;
  • not to upload excessive data or special categories of data without necessity and a separate legal basis;
  • to lawfully connect Telegram accounts, AI providers, CRM and other third-party services;
  • not to instruct the Processor to carry out processing that is manifestly contrary to mandatory law;
  • to independently determine whether a DPIA or the designation of a DPO is required, having regard to the scale and nature of its processing.

Obligations of the Processor

  • to process Customer Data solely in accordance with the Controller’s documented instructions and to the extent necessary for providing the service;
  • to ensure the confidentiality of individuals who have access to the data;
  • to implement appropriate technical and organisational measures;
  • to maintain legally required records of processing operations and incidents;
  • to provide the Controller with reasonable assistance in fulfilling data subject requests, DPIA, consultations with the supervisory authority, and demonstrating compliance;
  • to notify the Controller without undue delay upon identifying an incident affecting their data;
  • upon termination of processing, to delete or return data in accordance with Section 10;
  • to provide information reasonably necessary to demonstrate compliance with this DPA.

Security

Minimum measures are set out in Annex B. They may be updated as the Platform evolves, provided that the overall level of protection is not reduced without justified reason.

The Controller is solely responsible for the security of its devices, Telegram accounts, API keys, passwords, employee access rights, and third-party integrations selected and managed by the Controller.

Sub-processors and Third-party Services

The Processor does not transfer processing to a sub-processor without the Controller’s prior written consent to the extent required by the Law of Georgia. Electronic consent to the list of sub-processors and updates thereto shall be deemed written if it enables verification of the Controller’s consent.

Prior to engaging a new sub-processor, the Processor shall ensure that obligations of confidentiality, security, processing only on instructions, and deletion/return of data are extended to such sub-processor by contract, to the extent applicable to its services.

Services that the Controller connects using its own account or API key and independently selects as data recipients do not become sub-processors of the Processor solely by virtue of technical integration. The Controller is responsible for the lawfulness of such transfer and for its contractual relationship with such service.

International Transfers

International transfer is permitted only after a mechanism permitted by Article 37 of the Law of Georgia has been identified and implemented.

Where the parties rely on contractual safeguards as the basis for transfer to a country without an adequate level of protection, the Processor shall ensure that authorisation from the State Audit Service of Georgia is obtained in cases where such authorisation is required by law, prior to commencing the relevant transfer.

Where the lawful mechanism is the data subject’s written consent, the Controller must ensure its validity and inform the data subject in advance that the destination country has not been recognised as providing adequate safeguards, and inform them of the possible risks. For bulk Customer Data, this mechanism is not considered operationally preferable where a more robust mechanism exists.

The Controller authorises only those cross-border transfers in respect of which the requirements of this Section and Annex A.

Data Subject Requests, Supervision, and DPIA

If the Processor receives a data subject request in relation to Customer Data, it does not take a substantive decision in place of the Controller, unless the law requires otherwise, and forwards the request to the Controller without undue delay.

Taking into account the available functionality, the Processor provides reasonable assistance with the search, export, rectification, restriction, and deletion of data.

At the Controller’s request, the Processor provides information on its security measures, sub-processors, incidents, and cross-border transfer mechanisms, as required for DPIA and engagement with the supervisory authority.

Return, Export and Deletion

Following the end of the Subscription, outbound campaign reports provided for under the Terms of Service may be exported within 14 calendar days.

Account Data and Customer Data, including saved conversations, outbound campaign databases, connected account information, and settings, are retained for 30 calendar days following the end of the Subscription, after which they are deleted or anonymised, except for mandatory retention and temporary backups within the rotation cycle.

Upon a justified request by the Controller during the term of the agreement, the Processor deletes data within the limits of technically available functionality, unless further retention is required by law.

Incidents

The Processor notifies the Controller of a confirmed incident affecting Customer Data without undue delay following its identification and provides available information: the nature of the incident, the categories/volume affected, likely consequences, and measures taken.

The Controller is responsible for notifying the State Audit Service and data subjects where such obligation falls on it. The Processor provides reasonable assistance.

Audit and Evidence of Compliance

The Controller may, no more than once every 12 months, request information reasonably necessary to verify compliance with this DPA, unless a more frequent request is necessitated by an incident, a requirement of the supervisory authority, or a material change in processing.

The parties shall first use documentary review. Access to systems and premises is permitted only where objectively necessary, with prior arrangement, subject to confidentiality requirements, and without creating undue risk for other users.

Governing Law and Order of Priority

DPA is governed by the law of Georgia. Disputes are resolved in the manner established by the Terms of Service, unless mandatory law requires otherwise.

In the event of conflict: for Customer Data processing — DPA; for the commercial terms of Platform use — the Terms of Service; for NN Agent’s own data processing — the Privacy Policy.

  • TLS/SSL and other secure protocols for data in transit;
  • password hashing using bcrypt;
  • role separation and least-privilege access;
  • action logs/server logs and incident investigation;
  • network security controls and vulnerability management;
  • regular backups and recovery;
  • employee access controls and confidentiality obligations;
  • incident response procedures and management of data subject rights;
  • periodic review of the relevance of measures when the architecture changes.