How we protect your schedule

Access and identity

NIS2 topic: access control, multi-factor authentication

• Sign in preferably with a passkey (WebAuthn, with mandatory user verification); otherwise two-factor authentication is mandatory for everyone who can edit the schedule. Viewers get a strong recommendation.
• Roles per organization (owner, planner) and per project (planner, viewer), enforced on the server. A viewer cannot edit the schedule; what they may see is filtered server-side.
• Passwords are stored hashed; after repeated failed attempts the account is temporarily locked, on top of a per-IP limit.
• Sessions can be revoked immediately; password resets and invitations use single-use, expiring links.

Data and encryption

NIS2 topic: cryptography, data protection

• All traffic runs over TLS. Secrets Plandeck keeps for integrations (API tokens, webhook addresses, keys of external sources) are stored encrypted in the database and only shown masked.
• Incoming webhooks are verified against their signature; public API keys are stored as a hash only.
• Keys and secrets can be rotated without data loss, so they can be replaced immediately in an incident.
• Hourly rates, planner notes and contact details of resources are shielded from viewers and from the public API.

Hosting and continuity

NIS2 topic: business continuity, backup management

• Hosted with a European cloud provider in a data centre in the European Union; the AI, email delivery and visitor statistics also run on European services.
• Daily encrypted off-server backups, plus an extra database dump before every deployment, so a faulty release can be restored within a day.
• A public status page shows the availability of app and site; incidents and maintenance are announced there.
• The application runs in containers without root privileges and with resource limits, so one component cannot take down the rest.

Development and supply chain

NIS2 topic: supply chain security, secure development

• Every change passes automated tests and a blocking vulnerability check of all dependencies; with a known severe vulnerability nothing gets deployed.
• Dependencies are updated and reviewed automatically every week; reported vulnerabilities in the chain are handled within days.
• The code is periodically reviewed internally against the OWASP Top 10; findings are handled as work packages and documented.
• Deploying to production is only possible from a green test run; the deployment takes a backup first and checks the configuration before going live.

Logging and transparency

NIS2 topic: detection, event logging

• Every schedule change, integration, key creation and security event is in the organization's activity log, with who and when.
• The activity log can be exported and is retained according to the subscription's retention period.
• Changes coming from the status request or from an external source are never applied silently: they arrive as proposals for the planner, who decides.

Incidents and reporting

NIS2 topic: incident handling, vulnerability coordination

• Report vulnerabilities through the contact point published on plandeck.nl as security.txt (RFC 9116); reports are taken seriously and answered.
• In case of an incident affecting your data we inform you without undue delay, with what happened and what we did; the arrangements are in the data processing agreement.
• Status and history of outages are public on the status page.

Privacy and data processing agreement

NIS2 topic: data protection

• A data processing agreement comes standard with Plandeck; you receive it on request. The privacy statement describes which data we process and for how long.
• If you delete an organization, all linked data, including logs and measurements, is deleted coherently.
• The website uses no advertising trackers and no analytics cookies; visitor statistics run on our own European installation.

For organizations in scope of NIS2

NIS2 obliges essential and important entities to assess the security of their suppliers. Plandeck itself is not a NIS2 entity and there is no NIS2 certificate; what we can do is make that assessment easy. On request you receive a supplier statement with the measures on this page, the data processing agreement and answers to your own security questionnaire. Request them through the contact form.

What we do not claim

• No ISO 27001 or SOC 2 certificate. The measures above are reviewed internally, not by an external auditor.
• No "NIS2 compliant" badge: that status does not exist for products. We mention NIS2 only as a guide to what you may expect from us.
• No single sign-on with your own identity provider; that is on the roadmap. Until then, passkeys and mandatory two-factor authentication are the standard.