Loading…
Last updated: July 2026
Two surfaces, two rules
Comms graphics and brand settings stay on your device. The Officer Hub runs on the host that operates it, and that operator is responsible for the data it holds.
When you sign in, that Hub stores your session and case records. Demo setups may lose data on restart; a real deployment keeps each union's records secure and separate.
Designed around PIPEDA and, where applicable, FIPPA. Comms stay on-device. Hub hosts must apply access control, retention, and breach practices for labour records.
Your responsibilities
You remain responsible for photo consent and for posts and case handling that match your local policies and CA. Not legal advice. photo consent checklist.
Desktop / install as an app
Supported browsers can install UnionOps as an app window. Offline shell stays on-device; Hub case data still needs a network when live. install guide.
Site feedback
If you send a note from the feedback page, this host stores the text and any optional name or email you include, so the operator can improve UnionOps. Optional email is for a reply only, never a mailing list. You can ask the operator to delete your note. site feedback page.
Contact
UnionOps is stewarded by Ryan Morris. For questions about this policy, contact your local communications chair or see Support. Support.
Security practices
HTTPS, access control, and honest limits on encryption for hosted Hub and Portal are on the Security page.