Skip to content

Privacy

Last updated: 12 November 2026. Publisher and processor: Van de Wynckel, Maxim, trading as MVdW-Software (a trade name), Draaiersstraat 33, 9300 Aalst, Belgium (VAT BE 0729.544.225).

You are the controller of your data. MVdW-Software processes it as your processor to run the subscription: the synchronization of OpenProject and Exact Online happens on our servers, on your behalf, and only within your organization.

This privacy statement supplements the general privacy policy of MVdW-Software, which also applies. Where this page is more specific about this service, this page prevails.

For the technical detail of how the data is handled and protected, see Data & Security.

Which Exact Online data we use

OpenProject Sync only calls the Exact Online endpoints needed to synchronise time and work packages. The Exact refresh tokens stay in the portal; the app receives a short-lived access token per call.

Exact Online resource Data Use
project/Projects existing projects (code, description, customer) link an existing Exact project, or create one from OpenProject
project/WBSActivities WBS activities, including start/end dates and budgeted hours OpenProject work packages become WBS activities; the app reads them and creates or updates them, including the plan fields
project/WBSDeliverables WBS deliverables OpenProject versions become deliverables; the app reads them and creates or updates them
project/TimeTransactions hour lines and their status create and update one draft hour line per person, work package and day; read the status (submitted, approved, rejected); approved hours are never overwritten
payroll/Employees employees (name, business email address) match OpenProject users to Exact employees; read only
crm/Accounts customers the customer picker when a project is created from OpenProject; read only
logistics/Items items marked as a time unit choose the hour type; read only

We do not use any other Exact Online data (sales, purchase, manufacturing, financial, ...). The app stores no copy of this data: only the identifiers and hashes a later sync needs, as described below.

What we store, and why

Data Where Why
The OpenProject API token of each connection encrypted in the app's database (AES-256-GCM, bound to its own record; only its last four characters are ever shown) to call the OpenProject API. It is never shown again after it is saved, never logged, and can be replaced at any time from OpenProject connections
The linked projects and their sync state (cursors, the last run, the hashes of the written lines) the app's database, per organization to keep the sync idempotent and resumable; the hashes are what make a run never write the same line twice
The logins and e-mail addresses of the OpenProject users who logged time, and their match to an Exact employee the app's database, per organization so a time entry lands on the right employee
Account, organization and billing records in the portal to run the subscription

What we do not store

  • Project content is passed through, not kept. The sync reads a time entry or a work package, writes the hour line or WBS line, and discards the rest: we hold no copy of your work package subjects, descriptions or comments, nor of your Exact projects, employees, invoices or any other Exact data, only the identifiers and hashes a correct next run needs.
  • No attachments or documents of your OpenProject projects.
  • No Exact refresh tokens in this app. The portal's Exact token broker hands the sync a short-lived access token (10 minutes, memory only) per call; the refresh token stays in the portal, encrypted.
  • No telemetry or tracking. The service has no analytics, no license check and no advertising.

What leaves our servers

To What Why
your OpenProject instance the token's calls (time entries, work packages, versions) and the comments the sync posts on work packages the purpose of the service
Exact Online (start.exactonline.*) the same, for the enabled administrations: draft hour lines and WBS lines are written, projects, employees and hour statuses are read the purpose of the service
Mollie the payment for the subscription, in the portal billing

The writes to OpenProject and Exact are exactly what is described in How the sync works: draft hour lines, WBS lines and the status comments, nothing else.

Your responsibilities

  • Give the OpenProject token's user only the access it needs (a dedicated user that is a member of the synced projects is the recommendation; Replace token rotates the token without touching the linked projects).
  • Keep the portal's admin accounts protected: changes in OpenProject Sync require an organization admin and two-factor authentication, and the audit log in the portal records who changed what.
  • Remember that a user who may comment can have the sync post status comments on the work packages it can see.

Your rights and deletion

Questions about your data, or a request for export or deletion, go to info@mvdw-software.com. Deleting an organization in the portal deletes everything the app stores for it (connections, links, people, sync state), immediately.

The portal's audit log is kept for as long as your organization exists and is deleted together with it. Encrypted backups are kept for at most 1 year, so deleted data is gone from them within 1 year at the latest. You can withdraw your consent at any time by disconnecting Exact Online and the other connections in the portal, or by e-mail; the app then stops processing your data.