Data & Security¶
How OpenProject Sync handles and protects your data. It explains the purpose of the app, the data it uses, and how that data is used and protected.
Purpose¶
OpenProject Sync books the time logged in OpenProject as hours in Exact Online, one draft line per person, work package and day, turns OpenProject work packages (and versions) into Exact WBS activities (and deliverables), and reports the hour status back to OpenProject as a comment on the work package.
Data we access¶
| From | Data | Use |
|---|---|---|
| OpenProject (cloud or your self-hosted instance) | time entries, work packages, versions, project metadata and the users' name and e-mail | to create the draft hour lines and WBS lines, to match people, and to post status comments |
| Exact Online | projects, WBS deliverables/activities, hour lines (project/TimeTransactions) and employees |
the synchronization target, one draft hour line per person/work package/day |
OpenProject Sync never reads attachments, documents or wiki pages, only the time entries, work packages, versions and project metadata listed above.
Exact Online¶
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.
How data flows¶
- An administrator links an OpenProject project to an Exact project (the link requires an organization admin with two-factor authentication).
- On schedule or on "Sync now", OpenProject Sync reads time entries and work packages from OpenProject, and the current project/WBS/hour state from Exact.
- It writes to Exact only draft hour lines and WBS lines (hour lines are only changed while they are still draft or rejected), and posts a status comment on the work package in OpenProject.
- Every write is recorded with a hash so a run is idempotent: it never writes the same line twice.
What we store, and why¶
| Data | Where | Protection |
|---|---|---|
| The OpenProject API token of each connection | the app's database | AES-256-GCM encrypted, bound to its own record (AAD). Only the last four characters are ever shown; the token itself is never returned or logged |
| Linked projects and sync state (cursors, last run, the hashes of the written lines) | the app's database, per organization | to keep the sync idempotent and resumable |
| Logins and e-mail addresses of people 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 | see the portal's data & security document |
What we do not store¶
- Project content is passed through, not kept. The sync reads a time entry, writes the hour line, and discards the rest. We hold no copy of your work package subjects, descriptions or comments, your Exact projects, employees, invoices or any other Exact data, only the identifiers and hashes a correct next run needs.
- No attachments, documents or wiki pages.
- No Exact refresh tokens. The portal's token broker hands OpenProject Sync a short-lived access token (10 minutes, memory only) per call; the refresh token never leaves the portal.
- No cache. OpenProject Sync does not cache Exact or OpenProject data in any form.
- No telemetry or tracking. No analytics, no license check, no advertising.
How the data is protected¶
In transit¶
- TLS everywhere: browser ↔ OpenProject Sync, OpenProject Sync ↔ OpenProject, OpenProject Sync ↔ Exact Online, OpenProject Sync ↔ portal.
- Between the portal and the app the edge exchanges the session for a short-lived, EdDSA-signed assertion (60 s, bound to this app); the app and portal authenticate each other on an internal network with a per-app service token.
At rest¶
- OpenProject API tokens are AES-256-GCM encrypted with a versioned keyring and an AAD bound to the connection, so a token copied from one row does not decrypt in another.
Outbound safety (SSRF)¶
- Customer OpenProject URLs are reached only through a safe fetch pinned to the host the tenant configured for that instance, so the token can reach nothing else.
- The connect-time DNS answer is checked (rebinding-safe), private/loopback/link-local ranges are refused,
redirects are refused, and only the OpenProject
/api/v3paths are used. - Exact access is limited to the organization's enabled administrations (via the broker), and the writes are limited to the project/WBS/time resources by the resource schemas.
Access control¶
- Changes (tokens, links, mappings) require an organization admin with two-factor authentication; "Sync now" is available to members.
- Exact events are triggers only: the payload is ignored and the sync re-reads Exact and OpenProject, so a spoofed event cannot inject data.
- The audit log in the portal records who changed what.
Hosting and operations¶
- Hosted in the EU. Containers run as a non-root user on a read-only root filesystem with all capabilities dropped.
- Dependencies and container images are scanned for vulnerabilities daily (Trivy, HIGH/CRITICAL fail).
- Error reports (GlitchTip) are opt-in and scrubbed: no headers, cookies, bodies, query strings or user information are collected.
Retention and deletion¶
- Deleting the organization in the portal immediately deletes everything OpenProject Sync stores for it: connections (and their encrypted tokens), links, mappings and sync state.
- Replacing a token from OpenProject connections rotates it without touching the linked projects.
- The audit log lives in the portal and is kept for as long as the organization exists; it is deleted together with the organization.
- Encrypted database backups are kept for at most 1 year. Deleted data (including a deleted organization) therefore disappears from backups within 1 year at the latest; backups are only used to restore the service.
Who receives the data¶
| To | What | Why |
|---|---|---|
| your OpenProject instance | the token's calls (time entries, work packages) and the status comments written back | the purpose of the service |
Exact Online (start.exactonline.*) |
draft hour lines, WBS lines, and the project/WBS/hour reads, for the enabled administrations | the purpose of the service |
| Mollie | the payment for the subscription, in the portal | billing |