What stays local
Project records and managed attachments stay in the active local workspace. You or your organisation choose where approved backup copies and explicit exports are stored.
Security & privacy
Local project workspace. No PMCW project-data cloud.
PMCW does not host your project workspace. Identity and signed licensing exchange separate online metadata. Local storage does not replace your organisation’s security controls.
Read the privacy noticeLocal Workbench data
Under your control
The active project workspace is a local SQLite database, including managed attachments. Backups and explicit exports are separate recovery and sharing files under organisational controls.
- 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
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
Storage and responsibility
Local storage has a precise boundary.
Active workspace and files
The Windows pilot stores its SQLite authority at %LOCALAPPDATA%\PM Control Workbench\user_db\live\workspace-authoritative.sqlite, including managed attachments. Verified snapshots sit under user_db\backups\authoritative. A supplied universal package uses user_db inside its extracted folder. Reports, exports, and local settings are separate files. Follow your exact package’s instructions.
Active storage stays local
Use a fixed local drive outside OneDrive, iCloud Drive, Dropbox, network shares, removable media, and linked paths. Known unsafe locations are rejected; IT must also check folder redirection and sync policies that the app cannot detect. No PMCW project server or collaborative backend is required.
Backup copies can leave the device
Verified snapshots and an optional mirror provide recovery copies. Use an organisation-approved protected destination and verify recovery. A writable mirror folder is not a certification of your company’s OneDrive or network policy. Never sync the active database. Exports and backups inherit the destination’s access and retention controls.
Online identity and device metadata
Activation includes device name, platform, device public key/hash, pseudonymous OS/hardware/user-scope fingerprints, release identity, request identifiers, timestamps, and proof. New permanent licences have no recurring refresh. Initial and replacement-device issuance require the service; legacy refresh sends device/release identifiers and proof. Project records and attachments are absent from those requests. Website logs and account events are described in the privacy notice.
Diagnostics and support
The supported pilot runtime has no supported telemetry or automatic crash-report upload. There is no automatic workspace-access or support-bundle upload feature. Review copied diagnostics; share project files only through an explicitly approved support process. OS, browser, and endpoint services have their own boundaries.
Protection and ownership
PMCW does not claim application-level encryption at rest. Disk encryption, account and folder permissions, endpoint controls, and approved transfers remain organisational responsibilities. Employer and client project information remains governed by the organisation that owns or controls it; a software licence does not grant data-transfer rights.
Data and security questions · Workspace and backup instructions
What this means in practice
Local work. Separate identity. Bounded claims.
What goes online
A customer account holds identity and licence metadata. It does not receive Workbench project files.
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.
No invented certification
No SOC 2, ISO 27001, military-grade, or independent-certification claim is made.
No hidden project sync
Authentication and licensing do not upload, inspect, or synchronise Workbench project content.
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.