AxXtori / AxXtori Data Processing Agreement

AxXtori Data Processing Agreement

Last updated: November 8, 2026

Platform: rtedhub.space


1. Parties and Definitions

1.1 Parties

This Data Processing Agreement (the "Agreement" or "DPA") is entered into between:

  • The Processor: Olha Rubtsova, operating the platform rtedhub.space as RtedHub, a natural person established in Ukraine, contactable at [email protected] (the "Processor"); and
  • The Controller: the customer of the rtedhub.space platform - the natural or legal person who registers an account, deploys the Software Agent on machines under their administration, and determines what data is collected and from which managed machines (the "Controller").

1.2 Background

This Agreement supplements and forms part of the Terms of Service governing the Controller's use of the rtedhub.space platform (the "Principal Agreement"). It governs the processing of personal data by the Processor on behalf of the Controller and is intended to satisfy the requirements of Article 28(3) of Regulation (EU) 2016/679 (the "GDPR") where applicable, and to allocate responsibilities between the Parties under applicable data protection law.

1.3 Definitions

  • "Software Agent" means the executable software component provided by the Processor through the platform, which the Controller installs and configures on Windows machines under its control (owned by it, or administered by it with the authorization of their owner) in order to manage and operate those machines remotely. It is an administration and convenience tool. As part of remote administration, the Agent can report machine information (hostname, username, operating system information, running processes, IP addresses) and, only when the administrator issues an explicit command, provide a live screenshot or retrieve a specific file. The Agent does not passively record user input or continuously capture activity, other than the device performance statistics described in Sections 4 and 5.
  • "Personal Data", "Data Subject", "Processing", "Data Controller", "Data Processor", "Sub-processor", "Supervisory Authority" and "Personal Data Breach" have the meanings given to them in the GDPR. Where Ukrainian law applies, equivalent terms under the Law of Ukraine "On Personal Data Protection" shall be construed accordingly.
  • "Collected Data" means any data, including any Personal Data, gathered by the Software Agent from managed machines as instructed by the Controller and processed through the platform. Some Collected Data (machine metadata, device performance statistics, and the Administrator Audit Log) is stored in the platform database; other Collected Data (on-command screenshots and file contents) is relayed in real time to the Controller and is not stored by the Processor, as further described in Sections 4 and 5.
  • "Administrator Audit Log" means the record of administrative actions performed by the Controller and its Technicians through the platform - that is, which commands were issued to a managed machine, by whom and when - maintained for accountability and security purposes. It is a log of the administrators' own actions, not a record of End User keystrokes or input.
  • "Technician" means a person whom the Controller invites, by e-mail, to work in the Controller's account with that person's own platform account, within the rights the Controller assigns (which groups of managed machines and which modules the Technician may use). A Technician is an Administrator acting on behalf of the Controller.
  • "End User" means any individual using, operating, or otherwise present on a managed machine on which the Controller has deployed the Software Agent.
  • "Applicable Data Protection Law" means all laws and regulations applicable to the Processing of Personal Data under this Agreement, including the GDPR (where applicable) and the Law of Ukraine "On Personal Data Protection" No. 2297-VI.

2. Roles of the Parties

2.1 The Parties acknowledge and agree that with respect to the Processing of Collected Data:

  • (a) the Controller is the Data Controller and solely determines the purposes and means of the Processing, including which categories of data are collected, from which managed machines, with what frequency, and for what purpose; and
  • (b) the Processor is the Data Processor and Processes Collected Data only on behalf of, and under the documented instructions of, the Controller.

2.2 The Controller alone configures the Software Agent and issues the commands that determine what is collected, itself or through its Technicians within the rights it assigns. The Processor does not initiate, select, or direct any collection of data from any managed machine.

2.3 The Processor accesses Collected Data only to the minimum extent necessary to deliver, maintain, and secure the Service - never for independent purposes. The Processor's role is limited to transmitting and storing Collected Data for the Controller and making it accessible to the Controller through the platform, together with any access strictly necessary to support the platform or to comply with a binding legal obligation.

2.4 No operator access to session content. Live screenshots and file contents handled during a remote session are streamed directly to the authenticated Administrator's browser session and are never stored on, nor accessible to, the Processor. From the Processor's side, apart from the stored data described in Section 4, the only information observable is that an Agent has connected and its display name. The Processor cannot view enrollment tokens (stored only as cryptographic hashes), per-agent keys (encrypted at rest), or any captured screen or file content.

2.5 Where the Controller administers machines on behalf of their owner (for example, as that owner's IT service provider), the Controller is responsible for its own agreement with that owner, and in relation to such data the Processor acts as the Controller's sub-processor under the terms of this Agreement.

2.6 Technicians. Technicians act on behalf of and under the authority of the Controller, and the commands they issue are instructions of the Controller. The Controller alone decides whom to invite, which machines and modules each Technician may use, and when to remove a Technician. Technicians are not engaged by the Processor and are not Sub-processors.

2.7 If the Processor is of the opinion that an instruction from the Controller infringes Applicable Data Protection Law, the Processor shall inform the Controller without undue delay. The Processor is not obliged to perform a comprehensive legal review of the Controller's instructions.


3. Subject Matter and Duration

3.1 Subject matter: the Processing of Collected Data by the Processor on behalf of the Controller in the course of providing the rtedhub.space platform and the Software Agent.

3.2 Duration: this Agreement takes effect on the date the Controller first accepts the Principal Agreement or first uses the platform and remains in force for as long as the Processor Processes Collected Data on behalf of the Controller.


4. Nature and Purpose of Processing

4.1 Nature: The Processor's processing activity differs by data type:

  • Agent connection identity and audit record (display name in the form username@hostname, as reported by the Agent on connection, plus the Administrator Audit Log): stored in the platform database. The full list of running processes is not stored in the application database, and operating system information is stored only as part of the Windows policy data, the protection and update status and the monthly report data described below; the database also retains the device performance statistics described below. For each installed Agent, the database keeps the IP address and time of its last connection, and the IP address each installation request came from, so the Controller can tell its devices apart and recognise an unexpected installation; IP addresses may also appear in server operational logs.
  • Device performance statistics (CPU, GPU, memory, disk and network utilisation sampled over time, together with the names of the top few running applications recorded approximately once per hour): stored in the platform database and retained for a period of up to thirty (30) days so that the Controller can view performance statistics for its managed machines and configure threshold alerts.
  • Protection and update status (once a day, for each managed machine: the antivirus and third-party firewall products that Windows Security Center lists, with whether each is on and up to date; whether Windows Firewall is on for each network profile; the name, type, size and health status of each physical disk; the Windows updates installed in the preceding sixty-two (62) days, as update numbers with their installation dates; the Windows build and edition; and the installed memory size): stored in the platform database. Only the latest report is kept; a daily summary of it is part of the monthly report data.
  • Monthly report data (for each managed machine and each day: the minutes it was online and in use during the Controller's work hours, its average and peak processor and memory load, how full its system drive was, the threshold alerts that started that day and how long each took to clear, the name of the program that led processor use for the most hours, the state of its antivirus, firewall and disks, its Windows build and edition, its installed memory size and the numbers of the updates installed that day; on plans that include Windows policies, also its update status and policy state): derived automatically from the device performance statistics, the protection and update status and the Windows policy data, stored in the platform database and retained for up to thirteen (13) months so that the Controller can make monthly reports for its clients and compare months. A note that the Controller or a Technician writes for a report's first page (plain text of up to six hundred (600) characters, one for each group of machines and month) is stored with these data. A report is built on request from these data, End User reports, the Administrator Audit Log and the log of policy changes; reports made by a Technician leave out End User reports. The report itself is not stored by the Processor, and its PDF file is made in the Controller's browser.
  • Report delivery data (for the Controller's clients: the e-mail addresses of up to five (5) recipients for each group of machines and how often its report is due; the company name, contact line, reply address and logo the Controller puts on its reports (the logo received as bare pixels and stored as a PNG image the Processor makes from them); the links a client opens a report by, with how many times each was opened and when last, never by whom; and a log of when a report was sent and to how many addresses, not to which): stored in the platform database to send the Controller's reports to its clients and to remind the Controller when one is due. A report e-mail is sent only when the Controller or a Technician presses Send in the panel; it carries a summary of the report, a link to it and the report as a PDF file that the Processor makes from pictures of the report's pages sent by the sender's browser (as bare pixels, never as a file), goes out through the Processor's e-mail provider (Section 10) from the Processor's address under the Controller's name, with replies going to the Controller, and carries a link by which its recipient stops further e-mails to that address. The Processor keeps neither the e-mail nor the PDF after sending. A report opened by its link shows only that report, without the Windows user names or the identifiers of the machines.
  • Team data (where the Controller invites Technicians): the e-mail address an invitation was sent to; for each Technician, the account they use, the name the Controller gives them, the groups of managed machines and the modules they may use, and when they joined and left; and a record of team events (invitations sent, re-sent or cancelled, Technicians joining, declining, leaving or being removed) with the e-mail addresses involved and the IP address the action came from. Stored in the platform database. The names the Controller gives to groups of managed machines are stored with them.
  • Windows policy data (on plans that include Windows policies): for each managed machine, its Windows edition and build number, the number of Windows updates waiting and whether a restart is pending, as last reported by the Agent; where the Controller sets Windows policies, the settings it chooses for a group of managed machines or for a single machine, the state of each chosen setting on each machine (for example applied, restored, not applicable, or held by another tool, with a short reason), and a log of policy changes recording who made each change, when, for which group or machine, and which settings changed. Stored in the platform database. So that a setting can be put back when it is turned off, the Agent keeps the value each setting had before it first changed it in a local file on the managed machine; that file is not sent to the Processor.
  • On-command captures (live screenshots, file contents): transmitted in real time from the Agent directly to the Controller's browser session and not stored on the Processor's servers. The Processor acts as a transient relay only; no copy of screenshot or file content is retained after the session ends.

4.2 Purpose: to provide the Controller with remote administration, monitoring, and management functionality for the Controller's own managed machines through the platform and the Software Agent, solely as configured and instructed by the Controller.

4.3 Retention: stored Collected Data (the Agent display name, its last connection IP address and time, and installation request IP addresses) is retained for the duration of the Controller's account and is deleted in accordance with Section 14 thereafter. The Administrator Audit Log and End User reports are kept for twelve (12) months from their creation (Section 14.4). Entries of the Administrator Audit Log naming a Technician are kept for the same twelve (12) months, also after the Technician leaves. Team data is kept while the Technician is in the Controller's team; an invitation expires after seven (7) days and is deleted thirty (30) days after it was sent (an expired one, thirty (30) days after it expired), and the record of team events is kept for twelve (12) months. Device performance statistics (Section 4.1) are retained only for a period of up to thirty (30) days to provide the performance-statistics functionality and are deleted automatically thereafter. Monthly report data (Section 4.1) is retained for up to thirteen (13) months and deleted automatically thereafter, and is deleted together with the machine it describes; a report note is deleted together with its group of machines. The protection and update status (Section 4.1) keeps only the latest report and is deleted together with the machine. Report delivery data (Section 4.1): a recipient's address is kept until the Controller removes it or the recipient stops the e-mails by their link, and is deleted together with its group of machines; a link works for sixty (60) days, can be withdrawn at any time and is deleted seven (7) days after it expires or is withdrawn; the log of sent reports is kept for twelve (12) months; the branding is kept until the Controller changes it. Windows policy data is kept while the Controller uses it: the settings chosen stay until the Controller changes them, a machine's reported state and its own policy are deleted together with that machine, and the log of policy changes is kept for twelve (12) months. On-command captures are not retained after the session ends (Section 4.1).


5. Type of Personal Data and Categories of Data Subjects

5.1 Types of Personal Data that may be Processed (as determined by the Controller's configuration):

  • Agent connection identity: the display name (username@hostname) reported by the Agent at the time of connection, stored as part of the connection event record and as the device's last known name;
  • Network data: the IP address and time of each Agent's last connection, and the IP address of each installation request;
  • Device performance statistics: CPU, GPU, memory, disk and network utilisation sampled over time, and the names of the top few running applications recorded approximately once per hour on each managed machine, retained for a period of up to thirty (30) days for the performance-statistics functionality and deleted automatically thereafter. This is primarily technical data describing the machine but may incidentally reflect the activity of an End User of that machine;
  • Protection and update status: as described in Section 4.1. This is technical data describing the configuration of a managed machine;
  • Report delivery data: as described in Section 4.1. The recipients' e-mail addresses are personal data of the people at the Controller's clients who get its reports, provided by the Controller;
  • Monthly report data: as described in Section 4.1, retained for up to thirteen (13) months. This is primarily technical data describing the machine but may incidentally reflect the activity of an End User of that machine (for example, the hours it was in use and its most used program). A report note contains whatever the Controller or a Technician writes in it;
  • End User reports: the reason and optional description a person at a managed machine submits through the on-screen notice, with the device it came from. Reports are sent to the Processor for review, together with who worked on that machine in the preceding fifteen (15) minutes, and, except reports of unauthorized access, are also shown to the Controller (not to its Technicians);
  • Administrator Audit Log: the record of administrative commands the Controller and its Technicians issued to a managed machine, with who issued each;
  • Windows policy data: as described in Section 4.1. This is technical data describing the configuration and update status of a managed machine; the log of policy changes names the Controller or Technician who made each change;
  • Team data: as described in Section 4.1, about Technicians and the people invited to become Technicians. While a Technician (or, once the account has Technicians, the Controller) works on a managed machine, the on-screen notice on that machine shows that person's name in front of the module in use: the name the Controller gave, or the part of the e-mail address before "@";
  • On-command captures: live screenshots and file contents retrieved from a managed machine in response to an explicit administrator command. These are streamed directly to the Controller's browser in real time and are not stored on the Processor's servers. They may incidentally contain Personal Data present on the machine at the time of the command, but no copy is retained by the Processor after the session ends.

5.2 The Software Agent is an administration tool intended for the Controller to manage its own machines, not a tool for monitoring people. Any Personal Data relating to an End User is incidental and arises from the operating environment of the managed machine rather than being a purpose of the Service. The Controller nonetheless acknowledges that an on-command screenshot or file may incidentally contain special categories of Personal Data (Article 9 GDPR), and the Controller is responsible for ensuring a valid legal basis where this occurs.

5.3 Categories of Data Subjects: where any Personal Data is processed, it relates to the Controller's own administrators, its Technicians and the people it invites to become Technicians, and, incidentally, to any End User present on a managed machine on which the Controller has deployed the Software Agent, as determined by the Controller's deployment decisions.


6. Obligations and Rights of the Controller

6.1 The Controller shall:

  • (a) comply with Applicable Data Protection Law in its capacity as Data Controller;
  • (b) ensure it has a valid legal basis and, where required, has provided all necessary notices and obtained all necessary consents for the deployment of the Software Agent on each managed machine;
  • (c) warrant the lawfulness of each deployment of the Software Agent and of each category of data collected;
  • (d) issue instructions to the Processor that comply with Applicable Data Protection Law;
  • (e) be solely responsible for informing End Users of any monitoring to the extent required by law;
  • (f) use the Software Agent only on machines under its control (owned by it, or administered with the authorization of their owner) and only for lawful purposes; and
  • (g) not use the platform or the Software Agent for any unlawful purpose, including unauthorised access to machines; and
  • (h) invite as Technicians only persons it authorises to administer the machines concerned, give each Technician only the access they need, remove access that is no longer needed, bind its Technicians to confidentiality, and be responsible for their actions in its account as for its own.

7. Processor Obligations - Documented Instructions

7.1 The Processor shall Process Collected Data only on documented instructions from the Controller, unless required to do so by applicable law; in such a case, the Processor shall inform the Controller of that legal requirement before Processing, unless prohibited from doing so.

7.2 The Controller's instructions are constituted by: (a) this Agreement; (b) the Principal Agreement; (c) the configuration and commands the Controller selects within the platform; and (d) any further written instructions agreed by the Parties.


8. Confidentiality

8.1 The Processor shall ensure that any person authorised to Process Collected Data is bound by an appropriate obligation of confidentiality and Processes Collected Data only as necessary to perform the services.

8.2 Collected Data is accessible only to the Processor and to the developer who builds and maintains the platform and the Software Agent on the Processor's behalf. The Processor ensures that the developer is bound by confidentiality obligations equivalent to this Section. Should the Processor engage further personnel, the same obligations shall be imposed on them.


9. Security - Technical and Organisational Measures

9.1 The Processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk. The Parties acknowledge that the Processor runs the platform as a team of two and that such measures are proportionate to a focused service of this size.

9.2 Measures implemented by the Processor include, as applicable and proportionate:

  • (a) Transport security with pinned certificate authorities: the Software Agent and its installer connect to the platform only over TLS and accept the server's certificate only if it is issued for the platform's host name by one of a fixed set of certificate authorities built into the Agent (currently ISRG Root X1/X2 and Google Trust Services GTS Root R1-R4); a certificate from any other authority, including that of an interception proxy, is rejected. TLS is terminated at Cloudflare's edge (Section 10) before traffic reaches the platform;
  • (b) Per-command authentication: every command issued to a Software Agent, including stop commands, is signed with a per-agent HMAC-SHA256 key and carries a timestamp and a one-time nonce; unsigned, altered, expired or replayed commands are rejected by the Agent;
  • (c) Approved, one-time enrollment: an Agent is enrolled only after the account holder approves the installation request in the dashboard, which shows the IP address the request came from. The Agent's credentials are then delivered once, over the TLS connection described in (a), to the installer that made the request, and cannot be collected a second time;
  • (d) Signed modules: platform modules (plugins) are cryptographically signed (Ed25519) and verified against a public key embedded at build time; unsigned or tampered modules are rejected;
  • (e) Protection at rest: agent tokens are stored only as SHA-256 hashes (a newly issued token is held encrypted with AES-GCM only until the installer collects it, and is then erased); per-agent keys are encrypted (AES-GCM) in the database; on the Managed Machine, agent secrets are protected using Windows DPAPI bound to the user account and are readable only by administrators of that machine;
  • (f) Tamper-evident audit log: administrative actions (commands sent to Agents, installation approvals and denials, install-key and device changes) are recorded in a hash-chained log whose integrity can be verified end-to-end; a copy is kept outside the main server in an append-only store (Cloudflare D1, Section 10), so records cannot be silently altered or deleted. Uploaded file contents and long command arguments are recorded by size only;
  • (g) Operational controls: the RMM signing key is isolated from the website key; failed authentication attempts are rate-limited by IP; the real-time channel accepts connections only from the platform origin; tokens are masked in logs; the server refuses to start if known-bad or default secrets are detected; and access to modules is restricted by subscription tier;
  • (h) Technician access: a Technician can open the Controller's panel only after adding two-step sign-in (an authenticator app or a passkey) and only from a session that passed it; rights are closed by default, so a Technician sees and commands only the groups of machines and the modules granted, and every command is checked against those rights on the server, an attempt outside them being refused and recorded; answers from a managed machine reach only the person who sent the command and the Controller; rights are confirmed again at least every minute, so removing a Technician or changing their rights takes effect within that time; and each Technician's actions are recorded under their own name in the Administrator Audit Log described in (f);
  • (i) routing of platform traffic through Cloudflare to mitigate common network-level threats; and
  • (j) application of available security updates within a reasonable time.

9.3 The Controller is responsible for the security of the managed machines on which it deploys the Software Agent and for the security of its own account credentials.


10. Sub-processors

10.1 The Controller provides general authorisation for the Processor to engage Sub-processors, subject to this Section 10.

10.2 The Processor currently engages the following Sub-processors for the Processing of Collected Data:

  • Cloudflare, Inc. - network, CDN, reverse proxy/tunnel, DDoS mitigation, and storage of the append-only copy of the Administrator Audit Log (Cloudflare D1) (United States / global edge network).
  • Oracle Corporation (Oracle Cloud Infrastructure) - cloud hosting: compute and database storage (Frankfurt, European Union, eu-frankfurt-1).
  • Google LLC (Gmail) - delivery of e-mail notifications to the Controller, of invitations to the people the Controller invites as Technicians (the invitation carries the Controller's e-mail address) and of the Controller's reports to the recipients it names (a summary of the report, a link to it and the report as a PDF file), including performance-statistics threshold alerts, which contain the managed machine's display name, its group, load figures and, where available, the name of its most active program (United States).

Freemius, Inc. acts as Merchant of Record for account billing and processes payment and account data under the Privacy Policy. Freemius does not process Collected Data from managed machines and is therefore not a Sub-processor of Collected Data under this Agreement.

10.3 The Processor shall impose on each Sub-processor data protection obligations substantively equivalent to those in this Agreement. The Processor remains fully liable for each Sub-processor's performance.

10.4 The Processor shall inform the Controller of any intended changes regarding Sub-processors, giving the Controller the opportunity to object within fourteen (14) days on reasonable data-protection grounds. If no resolution is reached, the Controller may terminate the affected services and request deletion of Collected Data under Section 14.


11. Assistance with Data Subject Rights

11.1 Taking into account the nature of the Processing, the Processor shall assist the Controller by appropriate technical and organisational measures, insofar as possible, in fulfilling the Controller's obligation to respond to requests for exercising Data Subject rights.

11.2 Where a Data Subject contacts the Processor directly, the Processor shall forward the request to the Controller and shall not respond itself. The Controller is primarily responsible for handling all Data Subject requests.


12. Personal Data Breach Notification

12.1 The Processor shall notify the Controller without undue delay after becoming aware of a Personal Data Breach affecting Collected Data.

12.2 Such notification shall, to the extent known, describe the nature of the breach, categories and approximate number of Data Subjects and records concerned, likely consequences, and measures taken or proposed.

12.3 Responsibility for notifying any Supervisory Authority and affected Data Subjects rests with the Controller.


13. Assistance with Compliance Obligations

13.1 The Processor shall assist the Controller in ensuring compliance with the obligations under Articles 32 to 36 GDPR (security, breach notification, DPIAs, and prior consultation), taking into account the nature of the Processing and the information available to the Processor.


14. Return or Deletion of Data

14.1 Upon termination of the services, or at the Controller's earlier documented request, the Processor shall, at the Controller's choice, delete or return all Collected Data and delete existing copies, unless retention is required by applicable law.

14.2 Active Collected Data is deleted promptly, and in any event within fourteen (14) days of termination or of the Controller's deletion request. Residual copies remaining in routine backups are purged on the ordinary backup-rotation cycle and in any event within thirty (30) days.

14.3 The Controller may export Collected Data through the platform's available functionality prior to termination.

14.4 Security records. When the Controller's account is deleted, its devices, agent credentials, install keys and installation requests are deleted at once, its Technicians lose access, and its team data is deleted, except the record of team events, which is kept for twelve (12) months from each event. Notwithstanding Sections 14.1 and 14.2, the Administrator Audit Log (including its off-site copy, Section 9.2(f)) and End User reports are security records: they are kept for twelve (12) months from their creation, also after termination, so that misuse of the Software can be investigated, and are then deleted automatically. When a Technician's own account is deleted, only that person's memberships end; the entries naming them in the Controller's Administrator Audit Log stay for their twelve (12) months.


15. Audit

15.1 The Processor shall make available to the Controller information reasonably necessary to demonstrate compliance with this Agreement and Article 28 GDPR.

15.2 Recognising that the Processor runs the platform as a team of two, audits shall be conducted primarily by means of the Processor responding to reasonable written questionnaires. On-site audits are not generally available; where the Controller demonstrates a specific legal requirement, the Parties shall agree in good faith on a proportionate alternative at the Controller's expense.


16. Lawfulness of Deployment and Warranties of the Controller

16.1 The Controller represents and warrants that:

  • (a) it has the lawful right and authority to deploy the Software Agent on each managed machine on which it is installed;
  • (b) it has established a valid legal basis for all Processing it instructs, including any on-command screenshots and files;
  • (c) it has provided all notices and obtained all consents and authorisations required from End Users and any other relevant persons; and
  • (d) its instructions and use of the platform do not and will not infringe Applicable Data Protection Law or the rights of any third party.

17. Indemnification

17.1 The Controller shall defend, indemnify, and hold harmless the Processor from and against any and all claims, demands, investigations, fines, penalties, losses, damages, liabilities, costs, and expenses (including reasonable legal fees) arising out of or in connection with:

  • (a) the Controller's deployment, configuration, or use of the Software Agent or the platform;
  • (b) the Controller's collection, use, or disclosure of Collected Data;
  • (c) any breach by the Controller of Applicable Data Protection Law or of this Agreement; or
  • (d) any claim brought by an End User, employee, contractor, Data Subject, third party, or Supervisory Authority relating to the Processing instructed or carried out by or on behalf of the Controller.

18. Suspension

18.1 The Processor may suspend all or part of the Processing and/or the Controller's access to the platform where the Processor has a reasonable suspicion that the Controller is using the platform or the Software Agent unlawfully, abusively, or in breach of this Agreement or Applicable Data Protection Law.

18.2 Where reasonably practicable, the Processor shall give the Controller notice of such suspension and shall lift it once the relevant concern is resolved.


19. International Transfers

19.1 The Controller acknowledges that Collected Data may be Processed in or transferred to countries outside the Controller's jurisdiction through the Processor's infrastructure and Sub-processors. Where Applicable Data Protection Law requires a transfer mechanism, the Parties shall rely on an appropriate safeguard recognised under that law, and the relevant Standard Contractual Clauses (Module Two: Controller to Processor) are deemed incorporated by reference to the extent required.

19.2 Where a transfer of Collected Data is subject to a statutory transfer mechanism, the Parties rely on the relevant Standard Contractual Clauses, which are incorporated by reference and completed by the details set out in this Agreement (the parties, the categories of data and Data Subjects in Sections 4 and 5, and the technical and organisational measures in Section 9).


20. Liability

20.1 Each Party's liability under this Agreement is subject to the limitations and exclusions set out in the Principal Agreement. Nothing in this Agreement limits any liability that cannot be limited under Applicable Data Protection Law.


21. Governing Law and Jurisdiction

21.1 This Agreement is governed by the laws of Ukraine, without prejudice to any mandatory provisions of the GDPR or other Applicable Data Protection Law.

21.2 Disputes shall be referred to and finally resolved by binding individual arbitration under the laws of Ukraine, seated in Ukraine, conducted in English by a sole arbitrator, consistent with the dispute-resolution mechanism in the Platform Terms of Service. The Processor may seek injunctive or equitable relief in any competent court where necessary to prevent irreparable harm. Nothing in this clause prejudices any mandatory rights of a Data Subject under Applicable Data Protection Law.

21.3 Consumer carve-out. Where the Controller is a consumer habitually resident in the European Union, the European Economic Area, or the United Kingdom, this Section does not apply to the extent that mandatory consumer-protection law provides otherwise: the choice of law does not deprive that Controller of the protection of provisions that cannot be derogated from by agreement under the law of their country of habitual residence, they retain the right to bring proceedings before the courts of that country, and they are not required to arbitrate.


22. Miscellaneous

22.1 Order of precedence: in the event of any conflict between this Agreement and the Principal Agreement regarding the Processing of Personal Data, this Agreement prevails.

22.2 Severability: if any provision is held invalid or unenforceable, the remaining provisions remain in full force.

22.3 Entire agreement: this Agreement, together with the Principal Agreement, constitutes the entire agreement between the Parties regarding the Processing of Collected Data.

22.4 Contact: all notices to the Processor under this Agreement shall be sent to [email protected].


Processor: Olha Rubtsova (RtedHub) - Ukraine - [email protected]

Controller: the customer of rtedhub.space accepting this Agreement, as identified by its platform account.

By deploying the Software Agent or otherwise using the rtedhub.space platform, the Controller accepts and agrees to be bound by this Data Processing Agreement.