Архівна редакція 1.0.0 від 19 листопада 2026. Чинна редакція може відрізнятися.
Data Processing Agreement (DPA)
Дата набрання чинності: 19 November 2026
Version of 19 November 2026.
This Data Processing Agreement (the "Agreement") forms an integral part of the Terms of Service of FOPilot and is entered into between the Business Customer (the "Controller", "you") and Sole proprietor Bohdan Ovsiienko (the "Processor", "we") when the Terms are accepted. It applies to personal data that we process on your behalf when providing the Service and contains the terms required by Article 28 of Regulation (EU) 2016/679 (GDPR) and Article 4(4)–(5) of the Law of Ukraine "On Personal Data Protection". This Agreement, concluded electronically, is equivalent to a written agreement.
1. Definitions
1.1. Customer Personal Data — personal data that the Processor processes on behalf of the Controller when providing the Service (Annex 1).
1.2. Data Protection Law — the GDPR (where it applies), the Law of Ukraine "On Personal Data Protection" and other laws applicable to the processing of Customer Personal Data.
1.3. Subprocessor — a person engaged by the Processor to process Customer Personal Data.
1.4. Incident — a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
1.5. SCCs — the standard contractual clauses for the transfer of personal data to third countries adopted by Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
1.6. Other terms have the meanings given in the Terms and the GDPR. The terms "controller" and "processor" correspond to "володілець" and "розпорядник" under Ukrainian law.
2. Roles and Subject Matter
2.1. For Customer Personal Data you are the controller and we are the processor.
2.2. If you process data on behalf of your own clients (for example as an agency), you are a processor and we are your subprocessor. In that case you warrant that your contracts with your clients allow you to engage us on the terms of this Agreement, and you pass their instructions on to us.
2.3. The subject matter, duration, nature and purpose of processing and the categories of data subjects and personal data are set out in Annex 1.
2.4. This Agreement does not cover data for which we are an independent controller (Account data, payment data); that processing is governed by the Privacy Policy.
3. Controller's Instructions
3.1. We process Customer Personal Data only on documented instructions from the Controller, including with regard to transfers to a third country, unless required to do so by law applicable to us. In that case we inform the Controller of that legal requirement before processing, unless that law prohibits such information.
3.2. Documented instructions are: the Terms and this Agreement; the settings the Controller configures in the Service; Tool calls initiated by the Controller, Organization members it authorizes or AI assistants to which it has granted access; and other written instructions of the Controller agreed with us.
3.3. We immediately inform the Controller if, in our opinion, an instruction infringes Data Protection Law.
4. Confidentiality
4.1. Only persons who need access to Customer Personal Data to provide the Service have such access, and they have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
5. Security
5.1. We implement the technical and organizational measures set out in Annex 2, taking into account the state of the art, the costs, the nature, scope, context and purposes of processing and the risks to data subjects' rights.
5.2. We may update the measures provided that the overall level of protection is not reduced.
6. Subprocessors
6.1. The Controller gives general authorization to engage the subprocessors listed on the Subprocessors page.
6.2. We notify Organization owners by e-mail and update the Subprocessors page at least 14 days before a new or replacement subprocessor starts processing Customer Personal Data.
6.3. The Controller may raise a reasoned objection within 14 days after the notice. We will make reasonable efforts to address the objection. If this is not possible, the Controller may terminate the Contract for the Service and receive a refund for the unused part of the paid period.
6.4. We impose on subprocessors contractual data protection obligations no less protective than those in this Agreement and remain fully liable to the Controller for the performance of their obligations.
7. Assistance to the Controller
7.1. Data subject requests. The Service provides features for finding, exporting, rectifying and deleting data. We forward to the Controller without delay any data subject requests we receive and do not respond to them ourselves unless the Controller instructs us to.
7.2. Other obligations. Taking into account the nature of processing and the information available to us, we assist the Controller in meeting its obligations regarding security of processing, notification of breaches, data protection impact assessments and prior consultation with the supervisory authority (Articles 32–36 GDPR).
8. Incidents
8.1. We notify the Controller of an Incident without undue delay and in any event within 48 hours after becoming aware of it.
8.2. The notice contains, as far as available: a description of the nature of the Incident, the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken or proposed; and a contact person. We provide missing information in phases.
8.3. Notifying an Incident is not an acknowledgement of fault or liability.
9. Return and Deletion
9.1. While the Contract is in force, the Controller can export its data using the Service's features.
9.2. After the Contract ends, we delete Customer Personal Data within 30 days, and from backups within their overwrite cycle (up to 30 days), unless the law requires us to keep it. Shorter retention periods (Annex 1) apply throughout the term of the Contract.
10. Information and Audits
10.1. On the Controller's request we provide the information necessary to demonstrate compliance with Article 28 GDPR, including a description of security measures, the list of subprocessors and answers to reasonable data protection questionnaires.
10.2. If that information is insufficient, the Controller may carry out an audit, including an inspection, itself or through an independent auditor bound by confidentiality: no more than once every 12 months, with at least 30 days' notice, during business hours, without access to other customers' data and without compromising the security of the Service, at the Controller's expense. The frequency limit does not apply after an Incident or where a supervisory authority requires an audit.
11. International Transfers
11.1. We are located in Ukraine. Where the Controller is established in an EEA state and transfers Customer Personal Data to us, the transfer is governed by the SCCs (Module Two: transfer controller to processor), which are incorporated into this Agreement by reference. The Controller is the data exporter and the Processor is the data importer.
11.2. For the SCCs the parties choose the following: Clause 7 (docking clause) does not apply; Clause 9(a) — Option 2 (general written authorisation) with 14 days' prior notice; the optional wording in Clause 11(a) does not apply; the competent supervisory authority under Clause 13 is determined by the data exporter's establishment; Clause 17 — Option 2, the law of the EU Member State in which the data exporter is established (where that law does not allow for third-party beneficiary rights, the law of Ireland); Clause 18 — the courts of the EU Member State in which the data exporter is established. Annex I to the SCCs consists of the party details in the Terms and Annex 1 to this Agreement; Annex II is Annex 2; Annex III is the Subprocessors page.
11.3. Where the GDPR applies to the processing but the Controller is not established in the EEA, the parties apply the SCCs with the minimum changes needed for that situation.
11.4. We transfer Customer Personal Data to our subprocessors outside the EEA on the basis of an adequacy decision of the European Commission or the SCCs (Module Three: transfer processor to processor). For Controllers in Ukraine, cross-border transfers are made in accordance with Article 29 of the Law of Ukraine "On Personal Data Protection".
11.5. In the event of a conflict between the SCCs and this Agreement or the Terms, the SCCs prevail.
12. Controller's Obligations
12.1. The Controller ensures a lawful basis for processing and transferring Customer Personal Data to us, proper information of data subjects and their consent where required by law (including for sending review requests).
12.2. The Controller does not send special categories of personal data to the Service unless needed to perform its request, and minimizes such data in replies and messages published or sent through the Service.
12.3. The Controller is responsible for the third-party accounts it connects, the settings of the Service and the actions of AI assistants to which it has granted access.
13. Liability
13.1. The parties' liability under this Agreement is governed by section 16 of the Terms, except where the SCCs or mandatory provisions of Data Protection Law do not allow it to be limited, including with regard to the rights of data subjects.
14. Term and Changes
14.1. This Agreement remains in force for the term of the Contract and until Customer Personal Data is deleted in accordance with section 9.
14.2. We may change this Agreement in accordance with section 18 of the Terms, including to comply with Data Protection Law. Changes may not reduce the level of protection of Customer Personal Data.
14.3. On matters of personal data protection, this Agreement prevails over the other provisions of the Terms.
Annex 1. Description of Processing
| Item | Description |
|---|---|
| Subject matter | Performing the Controller's requests to retrieve, display, create and change data in the Controller's accounts in connected services (Nova Poshta, Prom.ua, Horoshop, Rozetka, KeyCRM, Checkbox, monobank), preparing daily summaries and reconciling incoming payments |
| Duration | the term of the Contract and the periods in section 9 |
| Nature of processing | retrieval from connected services, structuring, temporary storage (cache), transmission to connected services (creating waybills, updating orders, creating receipts), passing results to the Controller's AI assistant, masking, deletion |
| Purpose | providing the Service to the Controller |
| Categories of data subjects | the Controller's buyers and customers; recipients of shipments; sender contact persons (the Controller's staff); counterparties in the Controller's bank statements |
| Categories of data | first and last name; phone number; city, address and delivery branch; order contents, amount, payment method and status; waybill number and status, cash-on-delivery amount; fiscal receipt data (goods, amounts, form of payment, contact for sending the receipt where given); bank transactions (date, amount, description, counterparty name and account where provided by the bank) |
| Special categories | none intended |
| Retention | short-term cache — no longer than 24 hours; action log and daily summaries — without personal data |
Annex 2. Technical and Organizational Measures
- Encryption: data is transmitted only over secure connections (TLS); credentials of connected services are stored encrypted with support for key rotation; access tokens and API keys are stored only in hashed form.
- Access control: each Organization's data is logically separated and permissions are checked on every request; staff access follows the least-privilege principle; access to servers and the admin panel is limited to designated persons using strong authentication.
- Minimization: Tools return only the data needed; phone numbers are masked unless needed for an action; short cache periods; contact details are hashed when their retention period ends.
- Logging and monitoring: a log of Tools that change data (without full parameters); logs contain no secrets and no personal data from request bodies; error monitoring with personal data scrubbed.
- Availability and recovery: daily backups overwritten within 30 days; restore tests.
- Secure development: automated tests, code review, timely dependency updates, secrets kept outside the code, a procedure for handling vulnerability reports.
- Incident response: a defined procedure for detecting, assessing, containing and notifying Incidents (section 8).
- Personnel: confidentiality obligations; data protection briefings.
- Deletion: data export and Account deletion features; automatic deletion when retention periods expire.
- Physical security: provided by the hosting provider (Hetzner Online GmbH, Finland) in a data centre with controlled access.
Annex 3. Subprocessors
The current list of subprocessors is on the Subprocessors page.