Security & privacy

Your project belongs to you.

Identity and signed licensing use minimal online metadata. They remain technically and operationally separate from the local Workbench where project work belongs.

Read the privacy notice

Local Workbench data

Under your control

Workbench flows keep the operational project picture in local workspace packages, portable folders, backups, and exports selected by the user.

  • Project information and work items
  • Actions, decisions, risks, and milestones
  • Notes, documents, and attachments where used
  • Workbench state, backups, reports, and exports
  • Local history and package metadata
Current local-first posture

Online commercial-account data

Minimal and separate

The online account is for identity and licensing. It does not receive Workbench project files.

  • Verified email, name, optional organisation, and sessions
  • Licence model, owner, status, seats, and update eligibility
  • Device activations bound to a licence
  • Billing records only if purchasing is later opened
  • No card numbers or project data in the online account
Minimal account and licence authority

What this means in practice

Local work. Separate identity. Bounded claims.

01

What stays local

Project records, attachments, backups, and exports remain in the workspace you keep on your computer.

02

What goes online

A customer account holds identity and licence metadata. It does not receive Workbench project files.

03

Backup is your responsibility

Use the product’s verified backup and restore paths. This website does not hold a copy of your project.

Claims we do not make

Specific about the architecture. Honest about the claims.

01

No invented certification

No SOC 2, ISO 27001, military-grade, or independent-certification claim is made.

02

No hidden project sync

Authentication and licensing do not upload, inspect, or synchronise Workbench project content.

03

No return-URL shortcut

A verified account or checkout return grants nothing on its own. Licence and download rights remain separate from visiting a page.

Technical detail

How identity and licensing stay separate.

Authentication and licensing boundary

Sign-in and licence activation use a separate online service. They exchange the minimum identity and entitlement metadata needed to bind a licence to a device.

What is not uploaded

Workspace databases, attachments, and exports are not synchronised to the customer account. Copying a portable folder does not copy activation.

Device and entitlement records

A signed licence record can include owner, status, seats, update eligibility, and device activations. Those records are not a project archive.

Audit and support events

Bounded account and licensing events may be retained to operate the service. They do not include Workbench project content.

Trust contacts

Security and privacy mailboxes.

Mail to these addresses is received. Use the matching role address for your subject. There is no on-site contact form.

Securitysecurity@pmcontrolworkbench.comMonitored mailbox
Privacyprivacy@pmcontrolworkbench.comMonitored mailbox
Read the legal notices

The privacy notice and legal pages describe what this website and the local Workbench actually do. No security certification is claimed.

See legal documents