Este documento está disponible en inglés y rumano. A continuación se muestra la versión en inglés.
Version 1.1 · Effective date: 11 November 2026
This Data Processing Agreement (“DPA”) under Article 28 of Regulation (EU) 2016/679 (“GDPR”) is concluded between:
- the Customer that has accepted the PlusPanel Terms of Service (the “Terms”), as controller, or as processor acting for its own customers (the “Customer”); and
- 2Lines Sistem SRL, CUI 16807695, Trade Register no. J2004001481239, registered office Str. Fizicienilor, bl. M2, ap. 1, 077125 Măgurele, Ilfov County, Romania, as processor or, where the Customer is itself a processor, as sub-processor (“2Lines”, “we”).
It forms part of the Terms and is accepted together with them.
1. Definitions
Terms defined in the GDPR (such as personal data, processing, controller, processor, data subject, personal data breach, supervisory authority) have the same meaning here. “Customer Personal Data” means personal data contained in Customer Data (as defined in the Terms) that we process on the Customer’s behalf when providing the Service. “Sub-processor” means another processor engaged by us to process Customer Personal Data.
2. Subject matter and roles
2.1. We process Customer Personal Data only to provide the PlusPanel Service: managing the Customer’s servers through the control plane and the agent, and the hosted platform services (backups, DNS, mail relay, monitoring, security, migrations). The details are in Annex I.
2.2. Customer servers. The servers enrolled in PlusPanel are chosen and controlled by the Customer. The providers of those servers (hosting, cloud or data-centre companies chosen by the Customer) are not our sub-processors; the Customer engages them directly. Data stored on those servers is processed by us only through the agent, by the typed and signed operations described in Annex II.
2.3. Customer as processor. Where the Customer processes data on behalf of its own customers (for example as a hosting company or reseller), the Customer warrants that its controllers have authorised the engagement of 2Lines as sub-processor on terms equivalent to this DPA, and the Customer remains our sole point of contact.
2.4. Our own processing. Data we process as controller (accounts of the Customer’s users, billing, security of our platform, the audit log of the panel) is described in our Privacy Policy and is outside this DPA, except where the audit log contains Customer Personal Data, for which this DPA also applies.
3. Instructions
3.1. We process Customer Personal Data only on the Customer’s documented instructions, including with regard to transfers to third countries, unless EU or Member State law requires otherwise; in that case we inform the Customer before processing unless the law prohibits it.
3.2. The Terms, this DPA, and the Customer’s configuration and use of the Service (panel, API, settings such as retention, opt-in to central observability storage, mail relay, SFTP, migrations) are the Customer’s complete instructions. Additional instructions must be in writing and agreed if they go beyond the Service.
3.3. We inform the Customer immediately if, in our opinion, an instruction infringes the GDPR or other data protection law.
4. Confidentiality
We ensure that persons authorised to process Customer Personal Data are bound by confidentiality obligations and have access only as needed for their tasks. Staff access to the platform requires two-factor authentication and every action, including acting as a user (impersonation), is recorded in the audit log and attributed to the person who performed it.
5. Security
5.1. We implement the technical and organisational measures in Annex II, taking into account the state of the art, the costs, and the nature, scope, context and purposes of processing and the risks for data subjects (Art. 32 GDPR).
5.2. We may update the measures, provided the overall level of protection does not decrease.
5.3. The Customer is responsible for the security of what it controls: its servers outside the agent’s scope, its users’ credentials and second factors, its websites and their software, and its configuration choices.
6. Sub-processors
6.1. General authorisation. The Customer gives a general authorisation for us to engage sub-processors. The sub-processors at the date of this DPA are listed in Annex III.
6.2. Notice of changes. We inform the Customer of any intended addition or replacement of a sub-processor at least 30 days in advance, by e-mail to the organization’s administrators and on a public page Annex III of this DPA, stating the sub-processor, its service and location.
6.3. Right to object. The Customer may object on reasonable data-protection grounds within the notice period. We will try to resolve the objection (for example by not using the sub-processor for the Customer’s data). If we cannot, the Customer may terminate the affected paid service before the change takes effect and receive a pro rata refund of prepaid fees.
6.4. Obligations. We impose on each sub-processor, by contract, data protection obligations equivalent to this DPA, in particular sufficient guarantees of appropriate security measures. We remain liable to the Customer for their performance.
6.5. EU only. Our sub-processors process Customer Personal Data only in the European Union. We will not engage a sub-processor outside the EEA, or one that transfers Customer Personal Data outside the EEA, without the notice of section 6.2 and an appropriate transfer mechanism under Chapter V GDPR.
7. Assistance with data subject rights
Taking into account the nature of the processing, we assist the Customer with appropriate technical and organisational measures to answer data subject requests (access, rectification, erasure, restriction, portability, objection), primarily through the self-service functions of the panel and API (export, deletion, audit log export). If a data subject contacts us directly about Customer Personal Data, we refer them to the Customer without answering on the merits, unless the law requires otherwise.
8. Personal data breaches
8.1. We notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data, and in any case within 48 hours, so that the Customer can meet its 72-hour deadline under Art. 33 GDPR.
8.2. The notification describes, as far as known: the nature of the breach, the categories and approximate number of data subjects and records, the likely consequences, the measures taken or proposed, and a contact point. Information not yet available is provided in phases without undue delay.
8.3. We take reasonable steps to contain and remedy the breach and assist the Customer with its notifications to the supervisory authority and to data subjects. Notifying a breach is not an admission of fault.
9. Impact assessments and consultation
We provide the Customer with reasonable information and assistance for data protection impact assessments and prior consultations with supervisory authorities (Arts. 35–36 GDPR) relating to the Service, primarily through our documentation and this DPA.
10. Audits
10.1. We make available to the Customer the information necessary to demonstrate compliance with Art. 28 GDPR, including this DPA, our documentation of the measures in Annex II and answers to reasonable security questionnaires.
10.2. If that information is not sufficient, or a supervisory authority requires it, the Customer may carry out an audit or inspection, itself or through an independent auditor bound by confidentiality, at most once every 12 months (more often after a breach or at an authority’s request), with 30 days’ written notice, during business hours and without disrupting the Service or compromising other customers’ data. The Customer bears its own costs; we may charge reasonable costs for audits that go beyond one working day.
10.3. Audits by a supervisory authority are always allowed.
11. International transfers
We do not transfer Customer Personal Data outside the EEA. Annex III, Part B lists suppliers outside the EEA that do not receive Customer Personal Data, and services the Customer may choose to use that involve such suppliers. If a transfer becomes necessary, we will do it only under section 6 and Chapter V GDPR (adequacy decision, including the EU-US Data Privacy Framework, or the Standard Contractual Clauses).
12. Return and deletion
12.1. During the contract the Customer can export Customer Data at any time through the panel and API.
12.2. After the end of the contract, the Customer has a transition period of 30 days to export its data. Afterwards we delete Customer Personal Data held by the control plane within 30 days, including backup repositories held for the Customer on our storage, unless EU or Member State law requires storage.
12.3. Encrypted copies in our disaster-recovery backups expire with their rotation and are not restored except for disaster recovery. Retained audit-log entries (7 years, IP addresses truncated after 90 days) are kept as described in Annex I. On request we confirm the deletion in writing.
12.4. Data on the Customer’s own servers stays under the Customer’s control and is not deleted by us.
13. Liability
Each party’s liability under this DPA is subject to the limitations of the Terms, without prejudice to the rights of data subjects under Art. 82 GDPR and to any liability that cannot be limited by law.
14. Term and precedence
14.1. This DPA applies for as long as we process Customer Personal Data, including after the end of the Terms until deletion under section 12.
14.2. In case of conflict, this DPA prevails over the Terms in matters of data protection. A separately signed Enterprise data processing agreement prevails over this DPA.
14.3. Self-hosted Enterprise. Where the Customer runs the control plane on its own infrastructure under a licence, we do not process the Customer Personal Data stored there; we receive only the licence check-in data (licence identifier, installation identifier, number of servers, software version). This DPA applies only to support access the Customer grants us.
14.4. This DPA is governed by the law that governs the Terms.
Annex I — Description of the processing
Controller / exporter: the Customer (contact: the administrators of the Customer’s organization). Processor / importer: 2Lines Sistem SRL, ops@pluspanel.net, phone +40 21 570 87 98.
Categories of data subjects
- the Customer’s users of the panel and API (administrators, resellers, clients and their invited users);
- the Customer’s own customers (End Customers) and their contact persons;
- visitors of websites hosted on the Customer’s servers;
- senders and recipients of e-mail handled by the Customer’s mail servers and our mail relay;
- any other person whose data the Customer or End Customers store in websites, databases, files and mailboxes.
Categories of personal data
- identification and contact data of panel users (name, e-mail, role), authentication data (hashed passwords, second-factor data), sessions and audit-log entries (actions, IP addresses);
- hosting metadata: account and site names, domain names and DNS records, database and database-user names, SFTP user names and public keys, scheduled tasks, WordPress inventory (plugins, themes, administrator user names, used to detect new administrators);
- content data chosen by the Customer, processed in the following ways:
- backups: snapshots of websites, databases and mailboxes, encrypted on the Customer’s server before upload and stored on our object storage;
- file transfers and file reads: streamed between the browser and the server through the control plane without being stored; a file read for display is kept in memory for at most 15 minutes, for one read;
- web terminal: input and output pass through and are not stored; only metadata (who, when, byte counts) is recorded;
- migrations: credentials of the source system, encrypted in our vault and sealed for the destination agent, destroyed with the source; data is copied from the source to the Customer’s server;
- mail relay: outgoing messages (headers and content) transiting our relay, spooled until delivered or bounced; delivery events (sender, recipient, status) kept 90 days;
- security data: web application firewall events (visitor IP address, request, rule) kept 30 days; firewall bans; SFTP authentication events (in the audit log);
- observability data: metrics and logs of the Customer’s servers and sites (including web access logs with visitor IP addresses and user agents), stored centrally only if the Customer opts in, otherwise read on demand from the server; agent crash reports (system journal extracts) kept 90 days.
Special categories of data: not required by the Service. The Customer decides whether its content includes them and is responsible for the corresponding safeguards.
Nature and purposes of processing: hosting, storage, transmission, encryption, backup and restore, structuring, retrieval, monitoring, security filtering and deletion, solely to provide the Service under the Terms.
Frequency: continuous for the duration of the contract.
Retention:
| Data | Retention |
|---|---|
| account and hosting metadata | contract term, then section 12 |
| backups | according to the Customer’s retention settings within its Edition (defaults: Free 7 daily; Pro and Enterprise 14 daily, 8 weekly, 6 monthly); snapshots of a deleted account held for 30 days by default, then deleted |
| central observability data (opt-in) | metrics / logs: Free 7 / 3 days, Pro 30 / 14 days, Enterprise 90 / 30 days; purged on opt-out |
| WAF events | 30 days |
| mail relay delivery events | 90 days; messages until delivered or bounced |
| agent crash reports | 90 days |
| audit log | 7 years; IP addresses truncated after 90 days |
Annex II — Technical and organisational measures
Hosting and location
- The control plane, its PostgreSQL database, backup storage and mail relay run only in EU data centres (Annex III). No cloud-provider-proprietary services are used for Customer Personal Data.
Architecture: no inbound management ports
- The agent on each Customer server initiates every connection outbound; servers expose no inbound management port. The connection uses gRPC over mutual TLS inside a WireGuard tunnel; WireGuard is a network layer on top of mTLS, never a replacement.
- Each agent is identified only by its client certificate issued by our private certificate authority at enrolment (single-use enrolment tokens).
- Signed commands only. The agent never executes arbitrary shell commands. Each job is an Ed25519-signed envelope with job id, server id, command, issue time and expiry; the agent verifies signature, addressee, validity window and replay before executing, and refuses unknown commands or fields. Commands come from a closed allowlist; destructive test operations are restricted to lab servers and a separately granted permission.
Isolation on Customer servers
- Each hosting account runs in rootless Podman containers managed by systemd, with dedicated networks and volumes, user namespaces, SELinux multi-category separation, XFS project quotas and defensive mount options. PlusPanel OS is an immutable, image-based operating system with signed updates, gradual rollout, health gates and automatic rollback.
Encryption
- In transit: TLS 1.2+ for the panel and API, mTLS + WireGuard to servers and platform hosts, TLS to object storage; certificates for Customer sites via ACME.
- At rest: backups are encrypted on the Customer’s server before upload, with repository keys derived from per-organization keys; those keys are wrapped by a key-encryption key held outside the database. Secrets (TOTP keys, notification channel secrets, migration credentials, connector keys) are encrypted in a vault with per-organization data keys (AES-256-GCM). Off-site database backups are encrypted with age.
- The agent never holds storage credentials: it receives short-lived pre-signed URLs for each backup session.
Access control and authentication
- Role-based access control with explicit permission × role × scope rules; account-scoped users can reach only their own accounts (automatically tested for every API operation).
- Passwords hashed with argon2id, a password policy that rejects common passwords, two-factor authentication (TOTP, passkeys/WebAuthn, recovery codes), mandatory for our operator staff; organization policies can require it for all users. Step-up authentication for sensitive changes; lockout after repeated second-factor failures; network bans after repeated failed sign-ins.
- The application connects to the database with a least-privilege role that cannot alter or delete audit records or change the schema.
Logging and accountability
- A tamper-evident audit log: every entry is hash-chained (SHA-256); a daily Ed25519-signed anchor is written to object storage with compliance-mode object lock (write-once) and verified regularly; alerts on any discrepancy. Personal identifiers in audit entries are separated and keyed-hashed, and IP addresses are truncated after 90 days.
- Impersonation is visible to the user and double-attributed in the audit log.
Secrets never stored
- Passwords generated for Customer sites, databases or SFTP are shown once and are not stored by the control plane; private keys of imported certificates and written file contents are scrubbed from job records after execution.
Resilience
- Daily encrypted off-site backups of the control-plane database to a different site (Finland), with immutable snapshot history; documented restore procedures and restore tests; automatic, monitored backups for Customer data with periodic restore tests; Premium backups keep a second copy at a different provider and country.
- Monitoring, alerting and a public status page (status.pluspanel.net).
Development and operations
- Code review, static analysis and vulnerability scanning in continuous integration; signed release images verified by the hosts; pinned dependencies; mandatory test coverage for security-critical components.
- Administrative SSH access to platform hosts only from fixed addresses with pinned host keys; secrets kept out of source code.
- Staff confidentiality, least-privilege access, and an incident response procedure aligned with section 8.
Annex III — Sub-processors
Part A — Sub-processors of Customer Personal Data
| Sub-processor | Service | Processing location | Transfer basis |
|---|---|---|---|
| Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany | hosting of the control plane and its database, central observability stores and image registry (Germany); object storage for Standard backups and audit anchors (Germany); encrypted off-site backups (Finland); authoritative nameservers for Customer DNS zones (Germany, Finland) | Germany, Finland | EU — no transfer |
| OVH SAS, 2 rue Kellermann, 59100 Roubaix, France | virtual servers of the mail relay that delivers Customers’ outgoing e-mail (Poland, France); planned: second copy of Premium backups (France) | Poland, France | EU — no transfer |
| Scaleway SAS, 8 rue de la Ville l’Evêque, 75008 Paris, France | transactional e-mail to the Customer’s users (account, security and alert messages, which may name Customer resources) | France | EU — no transfer |
At the date of this DPA, Premium backups in the pre-production environment use a storage gateway on our own Hetzner server (Germany) until the OVH destination is available.
Part B — Suppliers that do not receive Customer Personal Data, and Customer-chosen services
| Supplier | Role | Location / note |
|---|---|---|
| Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Dublin 2, Ireland (parent: Stripe, Inc., USA) | payment processing for our fees; acts largely as an independent controller for payment data; not a sub-processor of Customer Data | EU entity; transfers within the Stripe group to the USA under the EU-US Data Privacy Framework and/or Standard Contractual Clauses |
| Amazon Web Services (Route 53) | DNS hosting of our own domain pluspanel.net only, until migration to our nameservers; Customer zones are served by our own nameservers | USA parent; no Customer Personal Data |
| GitHub, Inc. | source code and build pipeline | USA; no Customer Personal Data |
| Let’s Encrypt (Internet Security Research Group, USA) | certificate authority: the agent on the Customer’s server requests TLS certificates for the Customer’s domain names, which are published in public Certificate Transparency logs | USA; requested on the Customer’s configuration |
| Browser push services (e.g. Google, Mozilla, Apple) | deliver end-to-end encrypted push notifications to devices the Customer’s users choose to register | chosen by the user’s browser; may be outside the EEA |
| Customer’s own S3 storage (Enterprise “bring your own S3”) | backup destination chosen and contracted by the Customer | Customer’s processor, not ours |
| Providers of the Customer’s servers | hosting of the Customer’s servers | Customer’s processors, not ours (section 2.2) |