DraftVersion 0.1 · 2026-11-03

Data Processing Agreement (DPA) — Annex to the Tender CRM Public Offer

DraftDraft v0.1 dated 2026-11-03. This text has not been reviewed by a lawyer and may change; values in [square brackets] are not yet defined. The Ukrainian version is the master text. Current prices and plan terms are on the Pricing page and take precedence over any mention of cost in these drafts.

ItemValue
Version[VERSION]
Effective dateFrom Acceptance of the Offer (automatically)
PartiesThe Customer (Controller) and Plenergy Europe PLC (Processor)

1. Subject matter, definitions, relationship to the Offer

1.1. This DPA is an Annex to the Public Offer (public-offer) and applies where the Provider processes personal data on behalf of the Customer in providing the Service ("Customer Data"). It complies with Art. 28 GDPR and the Ukrainian Law "On Personal Data Protection".

1.2. The terms "personal data", "processing", "controller", "processor", "data subject", "personal data breach" and "supervisory authority" have the meanings given in the GDPR. "Customer" = Controller (володілець), "Provider" = Processor (розпорядник). If the Customer itself acts as a processor for its own client, the Provider is a sub-processor and this DPA applies mutatis mutandis.

1.3. In case of conflict between this DPA and the Offer regarding processing of the Customer's personal data, the DPA prevails.


2. Details of processing (Art. 28(3) GDPR)

ElementDescription
Subject matterProvision of the Tender CRM cloud Service
DurationTerm of the Agreement + retrieval and deletion period (Offer clause 24)
Nature and purposeStorage, organisation, indexing, transmission, display, OCR and analysis of documents, AI Features, notifications, backup, support — solely to provide the Service to the Customer
Types of personal dataContact and business data (name, position, e-mail, phone) of Customer employees, counterparties, contracting authorities, bidders and winners, signatories of documents; any personal data contained in tender documents, e-mails, notes and chats uploaded by the Customer
Categories of data subjectsCustomer employees and Users; employees of counterparties, suppliers, contracting authorities, bidders; other persons whose data is in Customer Content
Special categoriesNot anticipated; the Customer must not enter them without a written agreement

3. Controller's instructions

3.1. The Provider processes Customer Data only on the Customer's documented instructions, which comprise: the Agreement (Offer, DPA), the Customer's settings and commands in the Service, and written instructions that do not contradict the Agreement.

3.2. The Provider may also process Customer Data where required by EU/Member State/Ukrainian law to which it is subject — informing the Customer unless the law prohibits it.

3.3. The Provider informs the Customer if, in its opinion, an instruction infringes data-protection law. The Provider may suspend performance of such an instruction.

3.4. The Customer is responsible for the lawfulness of instructions, legal bases, informing data subjects and for having the right to transfer data to the Provider and its sub-processors (including AI vendors).


4. Confidentiality

4.1. The Provider ensures that persons authorised to process Customer Data are bound by confidentiality (by contract or by law) and have access only on a need-to-know basis.


5. Security (Art. 32 GDPR)

5.1. The Provider applies the technical and organisational measures (TOMs) described in Annex 2, taking into account the state of the art, cost, nature of processing and risks.

5.2. TOMs may change provided the overall level of protection is not reduced.


6. Sub-processors

6.1. General authorisation. The Customer gives general authorisation for the engagement of the sub-processors listed in Annex 3 (and in the Privacy Policy) and for their replacement/addition under the procedure below.

6.2. Notice. The Provider notifies the Customer of an intention to add or replace a sub-processor at least [30] days in advance (e-mail to the Workspace administrator, notification in the Service and/or update of the list at https://[DOMAIN]/legal/subprocessors).

6.3. Objection. The Customer may object on reasonable data-protection grounds within [14] days. The parties will seek a solution within a reasonable time; if none is found, the Customer may terminate the Agreement in respect of the affected Service without penalty with a refund of the proportionate part of the amount paid in advance (no refund for AI Credits used). Continued use after the period expires means agreement.

6.4. The Provider concludes written contracts with sub-processors imposing data-protection obligations no less strict in substance than this DPA and remains liable to the Customer for their acts within clause 15.

6.5. Emergency replacement (e.g. failure or legal requirement) is permitted with immediate notice.


7. Assistance with data-subject requests

7.1. The Provider, taking into account the nature of processing, provides the Customer with reasonable assistance by technical and organisational means in responding to data-subject requests (access, rectification, erasure, restriction, portability, objection; Arts. 15–22 GDPR). Many actions the Customer can perform itself in the Service.

7.2. If a data subject contacts the Provider directly about Customer Data, the Provider (a) does not respond on the substance without instruction, other than acknowledging receipt, and (b) forwards the request to the Customer without undue delay.

7.3. Non-standard or labour-intensive assistance may be chargeable at the Provider's rates [owner decision].


8. Assistance under Arts. 32–36 GDPR

The Provider, taking into account the information available to it, assists the Customer in meeting obligations on security, breach notification, data protection impact assessments (DPIA) and prior consultation (Arts. 32–36) by providing information about the processing. Labour-intensive assistance may be chargeable.


9. Breach notification

9.1. The Provider notifies the Customer of a personal data breach concerning Customer Data without undue delay and, where possible, within [48] hours of becoming aware of it.

9.2. The notification contains, as far as known: the nature of the breach, categories and approximate number of data subjects and records, likely consequences, measures taken/proposed, and a contact point. Information may be provided in phases.

9.3. The Provider takes steps to remedy the breach and mitigate harm. A notification is not an admission of fault or liability.

9.4. The duty to notify the supervisory authority (Art. 33) and data subjects (Art. 34) lies with the Customer as Controller unless the law requires otherwise.


10. International transfers

10.1. The Customer authorises the Provider and sub-processors to transfer Customer Data outside the EEA/Ukraine only where safeguards exist under Chapter V GDPR (Arts. 44–49), in particular: an adequacy decision, the EU–US DPF (for certified recipients), or the European Commission Standard Contractual Clauses (Decision (EU) 2021/914).

10.2. SCCs: where a transfer of data of a Customer established in the EEA to the Provider (outside the EEA without adequacy) is restricted, the parties conclude the SCCs: Module Two (controller → processor), incorporated here by reference; for transfers from the Provider to a sub-processor outside the EEA — Module Three (processor → sub-processor). For the SCCs: Clause 7 (docking) — applies; Clause 9(a) — Option 2 (general authorisation, period [30] days); Clause 11(a) — optional wording does not apply; Clause 17 — law of [EU MEMBER STATE, e.g. Ireland/Poland]; Clause 18 — courts of [EU MEMBER STATE]; Annex I — section 2 of this DPA and Annex 1; Annex II — Annex 2 (TOMs); Annex III — Annex 3 (sub-processors). Supervisory authority under the SCCs — [SUPERVISORY AUTHORITY].

10.3. United Kingdom: where the UK GDPR applies, the ICO Addendum to the SCCs is used [if needed].

10.4. Ukraine: transfer is made under Art. 29 of the Law "On Personal Data Protection".

10.5. If a transfer mechanism is invalidated, the parties agree on an alternative mechanism; until then the Provider may suspend the relevant transfer.


11. Audits and information

11.1. The Provider provides the Customer on request with information necessary to demonstrate compliance with Art. 28 GDPR (including descriptions of TOMs, independent audit reports or certifications, if any).

11.2. Limited audit. If the information is insufficient or a supervisory authority requires it, the Customer (or an independent auditor bound by confidentiality and not a competitor of the Provider) may carry out an audit on these conditions: (a) written request at least [30] days in advance; (b) not more than once in 12 months, except following a security breach or a regulator's demand; (c) during business hours, without interfering with operations, without access to other customers' data, security systems and source code; (d) at the Customer's expense, including the Provider's costs of specialist time at its rates; (e) under NDA; (f) scope and plan agreed in advance, preferably remotely (documents, questionnaires, video interviews).

11.3. Audit results are the Provider's confidential information; the Customer shares the report with the Provider.


12. Return and deletion of data

12.1. After the Service ends, the Provider, at the Customer's choice: (a) provides an export of Customer Data during the retrieval period of [30] days (Offer clause 24); (b) thereafter deletes Customer Data from active systems within [30] days and from backups in the rotation cycle (up to [35–90] days), except where the law requires retention (then limited retention and protection).

12.2. The Customer may request written confirmation of deletion.

12.3. Deletion (on the Customer's request) of individual data in the Service is performed by the Customer itself or on request.


13. Customer's obligations

The Customer: (a) determines the purposes and means of processing; (b) is responsible for the lawfulness of Content and legal bases; (c) informs data subjects; (d) manages User access; (e) does not upload special categories of data without a written agreement; (f) is responsible for responding properly to requests of data subjects and regulators; (g) uses AI Features and integrations aware that relevant data is transferred to sub-processors (Annex 3).


14. Processor's data as controller

The Provider acts as a separate controller for account, billing, security, analytics and other data stated in the Privacy Policy (privacy-policy), and this DPA does not apply to such data.


15. Liability

15.1. Each party's liability under this DPA (including the SCCs within the limits permitted by law) is subject to the limitations and exclusions of the Offer (section 17), to the extent permitted by applicable law; the overall cap in the Offer applies cumulatively to the Offer and the DPA.

15.2. Nothing in this section limits data subjects' rights under the GDPR (Art. 82) or liability that cannot be limited by law, or limits the parties' direct liability to data subjects and regulators.

15.3. The Customer indemnifies the Provider for losses and costs arising from claims of data subjects or authorities caused by the Customer's instructions, the unlawfulness of Content or the lack of legal bases.


16. Term, changes, law

16.1. The DPA remains in force while the Provider processes Customer Data.

16.2. Changes to the DPA follow the procedure for changes to the Offer (section 26); changes required by a change in law, a regulator or a decision on the SCCs take effect on publication.

16.3. Governing law and dispute resolution — as in the Offer (section 28), without prejudice to the mandatory provisions of the SCCs.


Annex 1. Description of processing

See section 2 of this DPA. Changes — by updating the DPA.


Annex 2. Technical and organisational measures (TOMs)

The description is based on the Service's actual architecture (documents docs/architecture/*). Before publication each item must be verified by the owner/technical specialist against the real configuration. Items marked "[confirm]" are target or not yet confirmed.

AreaMeasures
1. System access controlMulti-factor authentication for administrator access to infrastructure [confirm]; server access by keys; action log; least privilege; separation of environments (dev/test/prod) [confirm]; secrets management outside Git, environment variables/secrets manager
2. Data access control / authorisationRole-based access control (RBAC) and granular server-side permissions checked on every request; permissions re-checked at execution time; deny by default; user authentication with passwords stored as strong hashes; limited token lifetime; MFA (TOTP) for users [status — confirm]
3. Tenant isolationAll repositories and queries bound to tenant_id; a foreign request returns "not found"; additional database row-level security (RLS); mandatory automated tests of tenant isolation and authorisation; search (including vector/RAG) limited to the tenant and tender
4. EncryptionTLS in transit; encryption of sensitive secrets in the DB (Fernet: AES + HMAC-SHA256, separate key; values are not returned through the API); [disk/storage and backup encryption — confirm]; passwords — hashes only
5. Loss protection / availabilityBackups of DB and storage on a schedule [specify frequency and retention]; recovery testing [confirm]; monitoring and alerts; incident-response procedure
6. Logging without contentLogs contain trace_id, tenant_id, user_id and technical events; documents, message/chat texts, file names, passwords, tokens and secrets are not logged; audit log of actions in the Service; log retention periods defined
7. File and document securityType verification by content (magic bytes); limits on size and complexity; antivirus scanning; rejection of macros and dangerous formats; safe file serving (nosniff, CSP isolation, forced download of risky types); quarantine of suspicious files
8. AI securityAll model calls through a single AI gateway; documents of third parties and texts from sources are treated as data, not instructions; no tenant/tender identifiers taken from the model; actions proposed by AI only after human confirmation, with permission checks; prohibited tools (deletion, payments, permission/settings changes); rate and budget limits; masking of sensitive patterns (phones, e-mails, cards) in user-uploaded files; "no training" — a requirement on vendors [confirm]
9. Network and infrastructureRestricted server access; browser automation isolated from the internal network; validation of outbound URLs (SSRF); rate limiting per tenant and per IP; OS and dependency updates; dependency licence checks
10. Secure developmentOWASP ASVS principles; code review; test pyramid with security tests; contract-first API; typed errors; dependency verification
11. Organisational measuresConfidentiality undertakings of employees and contractors; need-to-know access; security training [confirm]; access-revocation procedure on departure; incident-response policy; vendor assessment
12. Separation by purposeData of different Customers is logically separated; test data separate from customer data
13. Deletion and destructionProcedures for deleting Customer Content and backups (Offer clause 24; DPA clause 12); soft deletion of AI chats with final erasure after 30 days

Annex 3. Sub-processors (as at the version date)

Current list — https://[DOMAIN]/legal/subprocessors and section 12 of the Privacy Policy.

Sub-processorServiceDataLocationTransfer mechanism
OpenAI [legal entity — to be specified]AI (chat, extraction, embeddings)Text of documents, queries, uploaded filesUSA [/EU — verify]SCCs / DPF [verify]
Anthropic [to be specified; optional]AI (alternative vendor)SameUSA [specify]SCCs / DPF [verify]
[HOSTING PROVIDER]Hosting, storage, DBAll Service dataEU [country]DPA
[EMAIL PROVIDER]Sending e-maile-mail, name, message content[specify]DPA / SCCs
Stripe [Payments Europe, Ltd / Inc.] (to be connected later)PaymentsBilling dataEU / USADPA, SCCs/DPF
[MONITORING PROVIDER / self-hosted]Monitoring (no content)Technical data[specify]—