Data residency
UnionStack provides Canadian data residency for the hosted service.
Canadian union management software
A Canadian-hosted platform built around connected union work.
UnionStack combines configurable membership, structure, case, communication, reporting and member-experience workflows with Canadian data residency in Azure Canada Central.
Focused Canadian fit
Residency is one buying criterion—not the whole decision.
For unions that require Canadian data residency, UnionStack is hosted in Microsoft Azure’s Canada Central region. Object storage content is encrypted by the application with tenant-specific keys using authenticated AES-GCM before it is written to Azure Blob Storage.
Those facts belong in a security and procurement review, but geography alone does not establish operational fit. A buying team should also test permissions, workflows, migration controls, integration boundaries, member access, backup and incident-response expectations, and the responsibilities that remain with the customer.
This page keeps Canadian hosting information concentrated in one clear destination. Product pages elsewhere focus on the workflow being evaluated instead of repeating Canada messaging on every screen.
Verified platform facts
Evidence for a Canadian procurement review.
Hosted region
The production hosting region identified for the service is Microsoft Azure Canada Central.
Object storage encryption
Application-managed, tenant-keyed authenticated AES-GCM encryption protects object content before storage in Azure Blob Storage.
Tenant-aware access
Application and API access are evaluated within organization and permission context rather than treating every customer as one shared record set.
OAuth 2.0 integrations
The developer platform uses documented OAuth 2.0 authorization patterns, including PKCE for supported client flows.
Public policies
Published privacy and terms pages give procurement teams a starting point for legal and information-handling review.
Residency architecture
Follow information from authorized access to Canadian object storage.
This is a public procurement-level explanation, not a complete security design or contractual data-flow schedule.
- 01
Authorized user or integration
A user signs in to the hosted application, or an approved integration uses the documented OAuth 2.0 flow. Access remains subject to tenant and permission context.
- 02
Canada Central service
The hosted UnionStack service operates in Microsoft Azure Canada Central for the Canadian data-residency commitment described on this page.
- 03
Tenant-aware application access
Application and API operations are evaluated for the authorized organization and user rather than exposing a global customer record set.
- 04
Object encryption before storage
Object content is encrypted by the application with tenant-specific keys using authenticated AES-GCM before it is written to Azure Blob Storage.
- 05
Connected-service review
Email, identity, campaign, payment or custom API services can introduce separate data flows. Buyers should document those providers and their residency commitments independently.
- 06
Contractual confirmation
Confirm production data, backups, logs, support access, subprocessors, retention and exit requirements in the applicable service and procurement documents.
Procurement workflow
Turn “hosted in Canada” into a complete assessment.
- 01
Classify the information
List membership, grievance, employment, payment, communication and document categories. Identify sensitivity, authority and retention requirements.
- 02
Confirm residency scope
Ask which production data, backups, logs, support processes and subprocessors are covered by the residency commitment. Record the answer contractually where required.
- 03
Review access
Map administrator and operational roles, test representative users and decide how access changes are approved and reviewed.
- 04
Inspect integrations
Document connected email, campaign, identity, payment and API services. Residency and privacy decisions can extend beyond the core application.
- 05
Plan migration and exit
Define source cleanup, validation, cutover, export and retention responsibilities before production onboarding.
- 06
Assign shared responsibilities
Name the people who review users, secure credentials, approve publishing, handle member requests and escalate suspected incidents.
Operational fit
Evaluate the union workflows behind the hosting requirement.
UnionStack connects people and positions to organizational structure, grievances and other cases, email conversations, meetings, reports, public sites and authenticated member experiences.
Use the trial to configure one representative local or bargaining unit, several fake member records, a complete grievance type and a controlled email connection. Then test a report, a public or member experience and any API path that affects procurement.
The best evidence is a reproducible workflow completed by the people who will operate the system—not a location claim viewed in isolation.
Related implementation guides
Prepare a secure Canadian implementation
Use these maintained UnionStack 2.0 guides to evaluate the workflow in detail.
Access
Plan roles, users and access
Give each person the access required for their responsibilities without widening it unnecessarily.
Support Team · UnionStack 2.09 min read → DataPrepare data for UnionStack onboarding
Clean, map and stage source information before creating production records.
Support Team · UnionStack 2.012 min read → GovernanceRun a recurring configuration review
Keep types, fields, statuses and access aligned as union procedures evolve.
Support Team · UnionStack 2.09 min read → DevelopersPlan and authorize an API integration
Use OAuth 2.0 with PKCE and tenant-aware APIs to extend a defined UnionStack workflow.
Support Team · UnionStack 2.012 min read →Built for connected work
Evaluate Canadian residency and operational fit together.
Use the 30-day trial to test the workflows and controls your procurement team requires.