DraftVersion 0.1 · 2026-11-03

Privacy Policy (Tender CRM)

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 date[DATE]
Forms part ofPublic Offer (public-offer), clause 1.9

1. Who we are and what this Policy covers

1.1. This Policy explains how Plenergy Europe PLC ("we", the "Provider"; tax number 16341022; Vesivärava tn 50-201, 10152 Tallinn, Harju maakond, Estonia; r.latypov@plenergy.co.uk) processes personal data in operating the Tender CRM service (https://[DOMAIN], https://[APP_DOMAIN]) in accordance with Regulation (EU) 2016/679 (GDPR) and the Ukrainian Law "On Personal Data Protection" (and, where applicable, other laws of [GOVERNING LAW]). It fulfils the information duties under Arts. 12, 13 and 14 GDPR.

1.2. Our roles.

  • (a) We are the controller for: account and authentication data, billing data, support communications, marketing and business contacts, technical logs and security data, records of acceptance of terms, and analytics of Service use.
  • (b) We are the processor for personal data contained in Customer Content (documents, contract records, counterparty contacts, e-mails, chat texts, etc.). The Customer is the controller, and processing is governed by the Data Processing Agreement (DPA) — data-processing-agreement.

1.3. If you are a user invited by your employer (the Customer), then for data in Customer Content your employer is the first point of contact.

1.4. The Service is for business (B2B) and is not intended for consumers or persons under 18.


2. Principles (Art. 5 GDPR)

We process data lawfully, fairly and transparently; for specified purposes; limited to what is necessary; accurately; no longer than needed; with integrity and confidentiality; and we can demonstrate compliance (accountability). The privacy-by-design and by-default measures (Art. 25) are described in section 10.


3. What data we process, purposes and lawful bases (Arts. 6, 13/14 GDPR)

#Categories of dataSourcePurposeLawful basis (GDPR / Ukrainian law)
1Account data: name, e-mail, phone (optional), position, language, settings, password hash, MFA settings, roles and permissionsyou / the CustomerCreating and maintaining the account, authentication, providing the ServicePerformance of contract (Art. 6(1)(b)) — for sole-proprietor Customers; for Customer employees — legitimate interest (6(1)(f)) in providing the Service to a business customer
2Customer data: name, registration and tax numbers, address, contacts of responsible persons, rolesthe CustomerConcluding and performing the Agreement, communication6(1)(b), 6(1)(f), 6(1)(c)
3Billing data: plans, seat counts, amounts, payment dates, status, payment token, last 4 digits and card type, country, VAT IDCustomer; payment providerInvoicing, payments, accounting, taxes, fraud prevention6(1)(b), 6(1)(c) (accounting, tax), 6(1)(f) (fraud prevention). We do not receive or store full card data — the payment provider holds it
4Logs and technical data: IP address, session/device identifiers, user-agent, time, trace_id, tenant_id, user_id, security events, action log (audit). Without the content of documents and messages.automaticSecurity, abuse detection, diagnostics, debugging, audit6(1)(f) (security and stability of the Service); 6(1)(c) where needed
5Integration credentials and settings: credentials for third-party platforms (e.g. Zakupivli), API keys for AI vendors (if the Customer enters them), mailbox settingsthe CustomerPerforming integration functions as instructed by the Customer6(1)(b)/(f); here we act as processor (see DPA); credentials are stored encrypted
6Service use and product analytics: UI actions, features, AI usage volume (token counts, model, cost, no content), limitsautomaticEnforcing AI Credit limits/billing, preventing abuse, improving the Service6(1)(b) (credit counters); 6(1)(f) (improvement, aggregated)
7Support requests: contact data, content of the request, attachmentsyouSupport and problem resolution6(1)(b), 6(1)(f)
8Terms-acceptance records: document version, time, IP address, user identifierautomaticEvidence of contract conclusion and consents6(1)(f), 6(1)(c)
9Marketing contacts: name, e-mail, company, industry, e-mail-open history (with consent)you / public business sourcesInformational and marketing messages, events, offersConsent (6(1)(a)) or, for B2B business addresses where local law allows, legitimate interest (6(1)(f)) with an easy right to opt out
10Website data: cookies/storage, IP, pages (only with consent for non-necessary categories)automaticOperation, analytics, marketing — see cookie-policyNecessary — 6(1)(f)/ePrivacy exemption; others — consent (6(1)(a))
11Customer Content (including personal data in tender documents, e-mails, counterparty contacts, chat messages)Customer/SourcesProviding the Service (storage, document processing, OCR, analysis, AI)We are the processor; the basis is determined by the Customer as controller
12Public tender data from Sources (names of contracting authorities, bidders, winners — legal entities; in some cases officials, contact persons)public platforms (Prozorro, Zakupivli, e-Zamówienia/BZP, TED, Baza Konkurencyjności)Monitoring, analysing and displaying tenders for the CustomerFor us — legitimate interest (6(1)(f)) in aggregating public data; to the extent kept in a Workspace — as processor for the Customer. We limit display to the minimum needed and strip unneeded fields (e.g. data of other bidders)
13Data for compliance and defence of rights: requests from authorities, claimsvariousDefence against claims, compliance with law6(1)(c), 6(1)(f)

3.2. Special categories of data (health, political/religious views, biometrics, criminal records, etc.) the Service is not intended to process. The Customer must not enter such data without a separate agreement.

3.3. Whether providing data is mandatory. Data in items 1–3 is needed to conclude and perform the Agreement; without it we cannot provide the Service. Other data is voluntary.

3.4. Legitimate interests. Where we rely on 6(1)(f), we have carried out (or will carry out — [lawyer: confirm]) a balancing test (LIA). You may object (section 8).


4. Recipients of data (Art. 13(1)(e))

We disclose data to: (a) our sub-processors (section 12); (b) the payment provider; (c) professional advisers (lawyers, auditors, accountants) under confidentiality; (d) public authorities as required by law; (e) successors in a reorganisation/sale of the business (with notice); (f) you and your administrators (within Workspace access rights). We do not sell personal data and do not pass it to advertising networks.


5. Cookies and similar technologies

The main application uses only necessary storage (authentication token, theme, interface settings). The marketing site may use other categories only with your consent. Details are in the Cookie Policy (cookie-policy).


6. Automated decisions and AI (Art. 22 GDPR)

6.1. AI Features analyse documents, extract requirements, classify and propose actions. We do not make decisions producing legal or similarly significant effects for an individual solely on the basis of automated processing. AI outputs are supporting; actions in the Service are performed only after confirmation by a human.

6.2. We do not profile Users to evaluate personal characteristics. Accounting of AI use (tokens, cost) serves limits and billing.

6.3. AI vendors process data to produce a response; we require them not to use such data to train their models (stated as a requirement to be verified against vendors' current terms) — see ai-and-data-sources-notice.

6.4. Third-party documents and texts from Sources are treated as data, not instructions; we apply technical measures against prompt injection.


7. Retention periods

CategoryPeriodNote
Account dataFor the term of the Agreement + up to [30] days after the retrieval period ends, then deletion/anonymisationMay be longer in a dispute
Customer ContentUntil deleted by the Customer or [30] days after termination (retrieval period), then deletion from active systems within [30] days; from backups — up to [35–90] daysAI chats deleted manually — "soft" deletion, final erasure after 30 days
AI chats, chat filesUntil deleted by the user/Customer; after deletion — 30-day "bin", then final erasureChat content does not enter logs
AI usage ledger (tokens, model, cost — without content)[24] monthsBilling, limits, abuse prevention
Accounting and tax documents (invoices, payments)[5 / 3] years or longer if the law requires [lawyer: specify for the Provider's jurisdiction; PL — 5 years from end of year, UA — per accounting law]Legal obligation
Terms-acceptance records (version, time, IP)Term of the Agreement + [3–6] years (limitation period)Legitimate interest — evidence
Security and access logs[90–180] days; the audit log of actions in a Workspace — within the retention of Customer Content
Application technical logs[30–90] daysWithout document/message content
Support requests[3] years from closure
Marketing contactsUntil consent is withdrawn/objection; inactive — [24] months
BackupsRotation cycle [35–90] daysIsolated, encrypted [verify]
Data of trial Workspaces without conversion[30] days after the trial ends

8. Your rights (Arts. 12–22 GDPR; Art. 8 of the Ukrainian Law)

8.1. You have the right to: access (Art. 15); rectification (16); erasure ("right to be forgotten", 17); restriction of processing (18); notification to recipients (19); data portability (20); object to processing based on legitimate interest and to direct marketing (21); not to be subject to solely automated decisions (22); withdraw consent at any time without affecting prior processing (7(3)); lodge a complaint with a supervisory authority (Art. 77) — [SUPERVISORY AUTHORITY, e.g. UODO (Poland) / the Ukrainian Parliament Commissioner for Human Rights / ICO (UK) — depending on where you are]. Ukrainian law also grants the right to access, to an explanation, to demand that data be changed or destroyed, and to apply to the Commissioner or a court.

8.2. How to exercise them: write to r.latypov@plenergy.co.uk with the subject "Data request"; we may ask you to verify your identity (including through the Workspace administrator). We respond without undue delay and at the latest within 1 month (extendable by 2 months for complexity; we will tell you). The request is free of charge, except manifestly unfounded or excessive requests (Art. 12(5)).

8.3. Data in Customer Content: if you contact us about data we process as processor, we will forward the request to the controller (the Customer) and help it comply (DPA).

8.4. Unsubscribing from marketing: the "unsubscribe" link in every e-mail or r.latypov@plenergy.co.uk.

8.5. There are exceptions (e.g. the right to retain data for compliance with law or defence of rights).


9. International transfers (Arts. 44–49 GDPR)

9.1. The main processing of Service data takes place on a server in [EU: country/region — to be specified]. Certain sub-processors (in particular AI vendors and payment services) may process data outside the EEA, including in the USA.

9.2. For transfers outside the EEA we apply one of the safeguards: (a) an adequacy decision (e.g. the EU–US Data Privacy Framework for certified recipients — [verify for each]); (b) the European Commission Standard Contractual Clauses (SCCs) adopted by Decision (EU) 2021/914, with a transfer impact assessment (TIA) and supplementary measures where needed; (c) absent those — other Art. 49 grounds only in exceptional cases. For transfers from the UK — the IDTA / Addendum to the SCCs [if applicable].

9.3. For users in Ukraine: transfer is made having regard to Art. 29 of the Law "On Personal Data Protection" (states ensuring adequate protection — the EEA and parties to Convention 108; otherwise on the basis of the data subject's consent, a contract or other legal grounds) [lawyer: confirm].

9.4. A copy of the relevant safeguards may be requested at r.latypov@plenergy.co.uk.


10. Security (Art. 32 GDPR; technical and organisational measures)

We apply measures proportionate to the risk. In particular (described according to the Service's actual architecture; the full list of TOMs is in the Annex to the DPA):

  • Tenant isolation: every data request is bound to tenant_id; repositories and APIs check that records belong to the Customer (a foreign request is answered as "not found"); database row-level security (RLS) is used as an additional (not the sole) defence; automated tests of isolation between tenants are a mandatory part of development.
  • Access control: a role model and granular server-side permissions (client-side authorisation is never trusted); permissions are re-checked at execution time; user confirmation of actions proposed by AI; MFA (TOTP) [in beta — confirm status before publication].
  • Authentication: passwords are stored only as strong hashes; tokens have a limited lifetime.
  • Encryption: TLS in transit; sensitive secrets kept in the database (e.g. credentials for third-party platforms, AI vendor keys) are encrypted (Fernet / AES with HMAC) with a key that is not stored in code and are not returned through the API; [disk/storage and backup encryption — confirm actual configuration].
  • Logging without content: logs contain identifiers and technical events; the content of documents, message/chat texts, names of uploaded files, passwords and tokens are not written to logs.
  • File handling: type checked by content, size limits, malware scanning, rejection of dangerous formats, safe file serving (nosniff, content isolation).
  • AI security: text of documents and third-party sources is treated as data; model outputs are validated; identifiers proposed by the model are not trusted; AI has no access to payments, deletion or permission changes; rate limits and budget limits.
  • Network and infrastructure: browser automation isolated from the internal network; restricted server access; dependency updates; licence control.
  • Monitoring and response: metrics, tracing (OpenTelemetry), alerts, incident-response procedure.
  • Backup and recovery — per schedule [to be specified].
  • Organisational measures: least-privilege staff access, confidentiality undertakings, training [to be specified].

No system is 100% secure; we cannot guarantee absolute security.


11. Personal data breaches (Arts. 33–34 GDPR)

11.1. We will notify the competent supervisory authority of a breach concerning personal data within 72 hours of becoming aware of it, where the breach is likely to result in a risk to the rights and freedoms of individuals (Art. 33).

11.2. If the risk is high, we will notify affected individuals without undue delay (Art. 34), and where we act as processor we will notify the controller Customer without undue delay (and no later than [48] hours) so that it can fulfil its obligations (DPA).

11.3. We maintain a breach register.


12. Sub-processors and recipients

The list is current as at the version date. We may change it in accordance with the DPA (notice and right to object). [Values in brackets need to be specified.]

Sub-processorPurposeCategories of dataProcessing locationTransfer safeguards
OpenAI ([OpenAI, L.L.C. / OpenAI Ireland Ltd — to be specified])AI Features (chat, extraction, classification), embeddings (document indexing)Text of tender documents, user questions, texts of files uploaded to the chat; tender metadata (see ai-and-data-sources-notice)USA / [EU — verify regional data residency]DPA, SCCs / DPF [verify]
Anthropic (if needed, optional) ([Anthropic PBC — to be specified])AI Features (chat, structured output) — as an alternative vendorSame as OpenAI (if activated)USA [specify]DPA, SCCs / DPF [verify]
Hosting provider ([HOSTING PROVIDER])Server, network, storage (PostgreSQL DB, object storage, cache)All Service dataEU ([country — to be specified])DPA; processing in the EEA
Object storageFiles and documents — in the current architecture the S3-compatible storage runs on the same server; if moved to an external provider it is added here ([PROVIDER])Documents, attachmentsEU—
E-mail / SMTP ([EMAIL PROVIDER])Sending system e-mails, notifications, invoicese-mail, name, subject/body[EU/USA — specify]DPA, SCCs [if needed]
Payment provider: Stripe ([Stripe Payments Europe, Ltd (Ireland) / Stripe, Inc. (USA)] — to be connected later)Payments, subscriptions, invoicing, fraud preventionContact and billing data, payment data (processed by Stripe), IPEU / USAStripe DPA, SCCs/DPF. Stripe acts as an independent controller for its own regulatory purposes (AML, fraud) [verify]
Monitoring/observability ([PROVIDER, or self-hosted])Metrics, tracing, alertsTechnical data without content[specify]—
Website analytics (consent only; [PROVIDER] or "not used")Marketing-site analyticsCookie identifiers, IP (truncated)[specify]Consent
Customer support/CRM ([PROVIDER] or "not used")Tickets, communicationContact data, requests[specify]DPA

Public data Sources (not sub-processors; we do not act as their processor): Prozorro, Zakupivli, e-Zamówienia/BZP, TED, Baza Konkurencyjności and other platforms; their own policies govern their activity. When a Customer enters credentials for a platform, we act on its behalf.

The current test server is hosted in the EU; the final provider and country are determined before launch [note to owner: internal project notes name the current test hosting — state the legal entity and verify the DPA].


13. Children

The Service is not intended for persons under 18 and we do not knowingly collect their data. If we learn of such collection, we will delete the data. Write to r.latypov@plenergy.co.uk.


14. Links to other sites

The Service contains links to third-party platforms (e.g. Prozorro, Zakupivli). We do not control their privacy policies.


15. DPO and EU/UK representative

15.1. Data-protection contact: r.latypov@plenergy.co.uk / [DPO NAME, if appointed].

15.2. [If applicable: EU representative under Art. 27 GDPR — [NAME/ADDRESS]; UK representative — [NAME/ADDRESS].] [Owner/lawyer decision.]


16. Changes to the Policy

We may update the Policy; material changes are notified by e-mail and/or in the Service at least [30] days in advance. Earlier versions are available on request.


17. Contact and complaints

Contact: r.latypov@plenergy.co.uk, Vesivärava tn 50-201, 10152 Tallinn, Harju maakond, Estonia. You may also contact a supervisory authority: in the EU — the authority of your country of residence/work/infringement; in Poland — the President of UODO (uodo.gov.pl); in Ukraine — the Ukrainian Parliament Commissioner for Human Rights; in the UK — the ICO [if needed]. [Lawyer: confirm the authority for the Provider.]