Skip to content

Terms

Last updated: 8 November 2026. These terms apply to GitLab Sync, a hosted service offered by MVdW-Software, a sole proprietorship registered in Belgium (VAT BE 0729.544.225), Draaiersstraat 33, 9300 Aalst, Belgium.

They apply in addition to the general Terms of Service of MVdW-Software and take precedence for this service. A signed agreement with MVdW-Software, such as a quotation or a support agreement, prevails over both. Mandatory law, including the rights of consumers, always applies.

Subscription

  • The service is offered per organization of the portal, by subscription. The price is shown in the portal before you subscribe (Organization → Subscriptions), and the subscription is paid through Mollie.
  • One subscription covers one organization and an unlimited number of linked GitLab projects, GitLab connections and members of that organization.
  • The subscription renews until it is cancelled; you can cancel in the portal with effect from the end of the current period. After cancellation the app stays available for the organization until the end of the paid period, and the data is kept in the portal until the organization is deleted.
  • Prices exclude VAT where applicable.

Service

  • GitLab Sync runs on MVdW-Software's infrastructure, continuously updated: fixes and improvements are deployed without a separate version per customer (see the changelog).
  • The service synchronizes GitLab with Exact Online as described in this documentation. MVdW-Software is liable for the service according to the general Terms of Service; it is not liable for the processing of your GitLab or Exact Online data by those platforms, which is covered by your agreements with them.
  • The service requires an Exact Online connection made in the portal. If the connection lapses (a re-authorization in Exact Online), the sync pauses with a visible state in the app and resumes when the connection is restored.

Supported GitLab versions and GitLab's end-of-life window

  • GitLab Sync supports gitlab.com and self-hosted GitLab major versions 17.x, 18.x and 19.x. These are the versions GitLab itself supports: the current major version and the two previous major versions, as set out in GitLab's Statement of Support and its release and maintenance policy.
  • The tested releases are 17.11.7, 18.11.14 and 19.5.3. The unit, contract and end-to-end tests run for each of them.
  • GitLab's support window moves when it releases a new major version: the oldest supported major then reaches its end of life (EOL) under GitLab's policy. The window is three major versions wide (for example, 17.x leaves the window when 20.x becomes GitLab's current release). GitLab Sync follows that same window. When GitLab ends support for a major version, GitLab Sync may end support for that version at the same time; the current list is kept in the documentation and the changelog.
  • A GitLab version outside the supported window may still work, but it is not supported and is not covered by the compatibility tests or by support. For self-hosted GitLab, you are responsible for upgrading to a supported version. MVdW-Software is not liable for failures caused by an unsupported or end-of-life GitLab version.

Conduct

You are responsible for the accounts and tokens you connect: give a GitLab token only the access your organization may use, and keep the portal's admin accounts protected (two-factor authentication is required for changes). MVdW-Software may suspend the service when it is used to breach the law or the terms of GitLab or Exact.

Data

The processing of your data is described in the privacy notice. When your organization is deleted in the portal, everything the service stores for it is deleted.