Privacy Policy

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 policy explains how A-Line Services (we) processes personal data when you visit or use A-Line.cloud. It follows the EU General Data Protection Regulation (GDPR) and Belgian law.

Who is responsible

For the data described here, A-Line Services, Terweeenstraat 13, 9630 Munkzwalm, Oost-Vlaanderen, Belgium, is the controller. Data protection officer: Arthur De Witte. Contact for all privacy matters: privacy@a-line.cloud.

For personal data inside the applications and data you run on the Service (Your Content), you are the controller and we are your processor; see the Data Processing Agreement.

What we process, why and on what legal basis

We do not use your personal data for advertising and do not sell it. We use no third-party analytics or advertising trackers on the website. We set only cookies that are strictly necessary for sign-in and security, which need no consent.

If we ask for your consent for something optional, you can withdraw it at any time.

Purpose and dataLegal basis (art. 6 GDPR)
Account and sign-in: email, name, avatar, organisation membership, authentication data (passkeys, two-factor secrets, recovery evidence), sign-in via GitHub or Google (their account ID and email)Contract (6.1.b)
Providing the Service: clusters, apps, domains, DNS records, backups, API keys and the configuration you enter, deployment and build historyContract (6.1.b)
Billing: invoices, credit ledger, billing name and address, VAT number, payment status. Card or bank details are handled by the payment provider, not by usContract (6.1.b), legal obligation for bookkeeping and tax (6.1.c)
Security and abuse prevention: session records, audit log of account actions, rate limiting, moderation cases and evidenceLegitimate interest in securing the Service (6.1.f); legal obligation where a duty applies (6.1.c)
Operating the Service: logs and metrics of the platform, error diagnosticsLegitimate interest (6.1.f)
Service emails: verification, security alerts, billing notices, changes to termsContract (6.1.b), legitimate interest (6.1.f)
Support: your messages and the data you share with usContract (6.1.b), legitimate interest (6.1.f)
Legal claims, requests from authorities and reports of suspected crimeLegal obligation (6.1.c), legitimate interest (6.1.f)

Data from Google and GitHub sign-in

You can sign in with your Google account. We ask Google only for the openid, email and profile scopes: your Google account ID, your email address and whether Google has verified it, and your basic profile. We do not ask for access to any other Google service or data.

From Google we store your Google account ID, your email address, the time you linked the account and the time you last signed in with it. We sign you in only if Google has verified the email address. When you create an account by signing in with Google, we use your Google name as your account name; you can change it in Settings. We do not store your Google profile picture. The access token Google gives us is used once to read your profile and is not stored; we do not request or store a refresh token.

You can also sign in with GitHub. We ask GitHub only for the user:email scope and store your GitHub user ID, your GitHub username, your primary verified email address and the same link and sign-in times. Connecting GitHub repositories for builds is a separate GitHub App that you install and authorise yourself.

We use this data only to sign you in and to link the sign-in account to your A-Line.cloud account. Linking and unlinking are recorded in your organisation's activity log, which is kept as described below.

We keep the data while the sign-in account is linked. It is deleted when you unlink it in Settings, Security, Connected accounts, or when you close your account.

We do not sell Google user data, do not use it for advertising, and do not use it to train AI or machine learning models. We do not share it with anyone, except with processors needed to run the Service or when required by law.

To revoke access, unlink Google in Settings, Security, Connected accounts, and remove A-Line.cloud from your Google account at https://myaccount.google.com/permissions.

A-Line.cloud's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The policy is at https://developers.google.com/terms/api-services-user-data-policy.

Sign-in sessions

When you sign in we keep a record of the session: the browser and operating system, the country, and the network the request came from. We use it to show you your active sessions and to ask for a second confirmation when a session suddenly looks different.

We store the network as a prefix only (the first three parts of an IPv4 address, a /24, or the first 48 bits of an IPv6 address, a /48), never the full address.

Security events of a session (sign-in, sign-out, step-up, token reuse) are kept for 90 days and then deleted. Sessions you sign out of, or that expire, are removed from the session list.

You can sign out of any session, or of all other sessions, from Settings, Security.

Activity log and network prefix

The activity log of an organisation records who did what and when (for example creating a cluster or rotating a key), with the network prefix of the request (a /24 for IPv4, a /48 for IPv6), never the full address. Only owners and admins of the organisation see the prefix.

The legal basis is our legitimate interest, and the organisation's, in auditing the security of the organisation (6.1.f). The prefix is removed after 90 days; the entry itself is kept for 1 year.

When an organisation accepts the terms of an infrastructure provider we record who accepted which version, when, and the network prefix of the request. We keep this record as evidence of the agreement while the organisation exists. When the organisation or the person who accepted is deleted, the record is kept detached from them (no longer linked to any account) and deleted 5 years after the organisation is deleted.

Location from IP address

To show the country of a session we look up the network prefix in a local GeoLite2 database from MaxMind that runs on our own servers. The address is not sent to MaxMind or anyone else.

Who receives data

We share data only with service providers (processors) that help us run the Service, listed on the Subprocessors page, with authorities when legally required or when we report suspected criminal activity, with the infrastructure provider involved when it reports abuse or a breach of its rules, and with professional advisers under confidentiality. Billing data goes to our payment provider. If you connect GitHub or sign in with GitHub or Google, data flows to and from that provider as you authorise.

International transfers

We prefer providers and regions in the European Economic Area. Where a provider or its group companies are outside the EEA (for example GitHub and Google in the United States), the transfer relies on an adequacy decision (such as the EU-US Data Privacy Framework where the provider is certified) or on the EU Standard Contractual Clauses with additional safeguards. You can ask us for a copy of the safeguards at privacy@a-line.cloud.

How long we keep data

  • Security events of a session: 90 days.
  • Account data: while your account exists, then deleted when you close the account, except what is listed below or what a moderation hold preserves.
  • Invoices and accounting records: 7 years, as required by Belgian accounting and tax law.
  • Activity log of an organisation: 1 year; the network prefix of each entry is removed after 90 days.
  • Provider terms acceptances (who, which version, when, network prefix): while the organisation exists, then detached from the organisation and the person who accepted, and deleted 5 years after the organisation is deleted.
  • Audit log of actions taken by our platform administrators: 2 years.
  • Usage metering of object storage requests (with the network prefix only): 90 days.
  • Logs kept as evidence for a moderation case: never deleted while the case is open, and deleted one year after the moderation case is closed.
  • Moderation cases: never deleted while the case is open or under appeal, and deleted 2 years after the moderation case is closed, longer if needed for a legal claim or an authority's request.
  • Backups made by us for platform recovery: up to 12 months (daily copies for 14 days, weekly copies for 8 weeks, monthly copies for 12 months); data deleted from the Service disappears from the backups as they expire.
  • Your Content: until you delete it or close your account; see the Data Processing Agreement.

Your rights

You have the right of access, rectification, erasure, restriction, data portability and objection to processing based on legitimate interest (arts. 15 to 21 GDPR), and the right not to be subject to solely automated decisions with legal effect. We do not take such decisions; moderation decisions are made or reviewed by a person. Write to privacy@a-line.cloud; we answer within one month. We may need to verify your identity.

You can complain to the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit / Autorité de protection des données, www.gegevensbeschermingsautoriteit.be), or to the authority of your country of residence.

Security

We protect data with measures such as encryption in transit, access control with two-factor authentication, audit logging, network restriction of management interfaces and regular backups. See the Data Processing Agreement for the list. If a personal data breach puts you at risk we notify you and the authority as the law requires.

Children

The Service is not for people under 18 and we do not knowingly collect their data.

Changes

We announce material changes to this policy by email or in the product before they apply.