Data Processing Agreement

Draft, pending legal review. This text is not final and is not yet legally binding. Items in [[double brackets]] are still to be filled in.

Last updated 2026-11-13

This Data Processing Agreement (DPA) applies between the customer (controller) and A-Line Services (processor) when we process personal data contained in Your Content on behalf of the customer in the course of the Service. It is part of the Terms of Service and meets art. 28 GDPR. It applies automatically when you accept the Terms; no separate signature is needed unless you ask for a countersigned copy at legal@a-line.cloud.

Subject matter, duration, nature and purpose

We host, store, back up, transmit and otherwise process Your Content to provide the Service. The DPA lasts as long as we process Your Content. Categories of data subjects and personal data are those that the customer places in Your Content (for example the customer's own users, employees and contacts); the customer decides what that is.

Instructions

We process personal data only on the customer's documented instructions, which are the Terms, this DPA and the customer's use of the Service and its settings, unless EU or Member State law requires otherwise; then we tell the customer first if the law allows. We tell the customer if we think an instruction breaches data protection law.

Confidentiality

Persons we authorise to process personal data are bound by confidentiality and get access only as needed.

Security measures (art. 32 GDPR)

  • Access control: two-factor authentication for staff and platform administration, least-privilege access, management interfaces restricted to a private network or allow-listed addresses.
  • Customer separation: per-organisation isolation of data (including database row-level security) and of workloads; customer clusters are separate from the platform.
  • Encryption: TLS for data in transit; secrets stored encrypted; volume encryption where the storage class supports it.
  • Logging: audit log of account and administrative actions.
  • Resilience: backups of the platform data with restore tests; customer backups as configured by the customer.
  • Change control: tested releases, staged rollout and rollback.
  • Incident handling: detection, escalation and the breach process below.

Subprocessors

The customer gives general authorisation for the subprocessors on the Subprocessors page. We bind each of them to data protection obligations no less protective than this DPA and remain responsible for them. We give at least 30 days' notice of a new or replaced subprocessor; the customer can object on reasonable data protection grounds within that period. If the parties cannot resolve it, the customer may end the affected part of the Service and get a refund of unused prepaid fees for it.

International transfers

We process Your Content in the EEA for clusters placed on EU locations. Where a transfer to a country without an adequacy decision takes place, it relies on the EU Standard Contractual Clauses (Commission Decision 2021/914): module two (controller to processor) between customer and us, and module three (processor to processor) with the subprocessor, with the options and annexes completed from this DPA. Where the customer places clusters outside the EEA, the customer decides that transfer.

Assistance

We help the customer, with appropriate technical and organisational measures and as far as possible, to answer data subject requests (arts. 12 to 22), and with security, breach notification, data protection impact assessments and prior consultation (arts. 32 to 36). If a data subject contacts us directly about Your Content we refer them to the customer. We may charge reasonable costs for assistance that goes beyond the normal operation of the Service.

Personal data breach

We notify the customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Your Content, with the information we have (nature, categories and numbers, likely consequences, measures taken). Notices go to the account owner's email; write to privacy@a-line.cloud to name an additional security contact.

Logs we keep for the customer

  • App logs (what the customer's workloads write, including access logs of static sites with the visitor's full IP address): kept for the cluster's log retention setting, 30 days by default and at most 365 days, then deleted. Deleting an app's project, a cluster or the organisation deletes its logs. Organisation owners and admins can also delete the logs of an app or a cluster over a time range, for example to answer an erasure request.
  • Access logs as request metadata (time, route, method, status, duration and size, without IP addresses): 7 days; per-minute totals 90 days.
  • Request metadata of object storage (with the client's network prefix only, never the full address): 90 days, used for metering.
  • Logs a moderation hold preserves are kept while the case is open and until one year after the moderation case is closed.

Return and deletion

On closure of the account or when the customer deletes a resource, we delete the related Your Content, including live copies, within [[DELETION PERIOD, E.G. 30 DAYS]]; backups expire within [[BACKUP EXPIRY PERIOD]]. Before that the customer can export its data using the Service. We keep copies only where the law requires it or a hold or legal request applies.

Audits

We provide the information needed to show compliance with art. 28 GDPR, including up-to-date summaries of our security measures and, on request, relevant third-party reports we hold. The customer may audit us once a year, or after a breach, with 30 days' notice, during business hours, under confidentiality and without harming other customers, at the customer's cost.

Our own role

For account, billing and security data about the customer and its users, we are an independent controller; see the Privacy Policy.

Liability, order of precedence and law

Liability under this DPA follows the limits of the Terms of Service, except where the law or the Standard Contractual Clauses provide otherwise. If this DPA and the Terms conflict on data protection, this DPA prevails; the Standard Contractual Clauses prevail over both. Belgian law applies, and the Standard Contractual Clauses are governed by Belgian law with the Belgian courts competent.