Canadian data residency
UnionStack production services and customer data are hosted in Canada using the Microsoft Azure Canada Central region.
Buyer evidence: the production region is configured as Canada Central.
Trust & security
Connected information deserves deliberate boundaries.
UnionStack is designed around organization-scoped data, authenticated permissions, private object storage and secure integration patterns. Here is what buyers can examine today.
A layered model
Security is enforced across the request, record, file and integration.
Union work can combine member information, case evidence, documents, email and public content. UnionStack uses several technical boundaries rather than relying on a single sign-in screen.
The controls below describe implemented product behaviour. They are intentionally separate from certifications, service-level commitments or operational assurances that require their own current documentation.
Security model
Evidence at each layer of the platform.
Tenant-scoped persistence
Data access is filtered to the current tenant, and persistence rejects attempted writes when a record’s tenant does not match the active tenant.
Buyer evidence: both reads and writes participate in tenant isolation.
Permission-respecting access
Application and API access follow the authenticated user and approved roles or rules, so an integration does not become a shortcut around application permissions.
Buyer evidence: API authorization is evaluated with tenant and user context.
Private object containers
Object storage uses tenant-specific container names with public access disabled. Object paths are validated before the application performs storage operations.
Buyer evidence: stored objects are not placed in anonymous public containers.
Application-layer encryption
Before object content is written to blob storage, UnionStack encrypts it with a tenant encryption key using authenticated AES-GCM envelopes, including a random nonce and authentication tag.
Buyer evidence: content encryption occurs before the storage write.
Modern API authorization
Developer integrations use OAuth 2.0 authorization code flow with PKCE. Administrators create credentials within UnionStack, and access is tenant-aware.
Buyer evidence: the public developer documentation describes the authorization flow.
Procurement review
What your buying team can verify.
Use this as a starting checklist and request current supporting material for any contractual requirement.
Data location
Confirm that Canada Central meets your organization’s data-residency policy and document any additional location requirements.
Tenant boundary
Ask how read filters, write validation and private tenant containers work together to separate organizations.
Authorization
Map staff roles to sensitive workflows and verify that API calls remain subject to tenant and user permissions.
Encryption
Review the application-layer AES-GCM design for object content and distinguish it from transport or infrastructure encryption.
Public versus member
Test that public site content is intentionally published and that member experiences begin behind registration and sign-in.
Contractual assurances
Request current documentation for certifications, availability, retention, recovery or incident terms when they are procurement requirements.
Shared responsibility workflow
Turn platform controls into dependable day-to-day administration.
- 01
Design roles
Give staff the access needed for their work and separate administrative capabilities from routine operations.
- 02
Review access
Periodically review users, groups and responsibilities; remove or change access when duties change.
- 03
Protect secrets
Keep issued client secrets in an appropriate secret manager and do not place them in browser code or public repositories.
- 04
Control publishing
Define which documents and records can appear publicly and test member-only navigation with representative accounts.
- 05
Reassess
Review integrations, site ownership and permissions when structure, vendors or staffing changes.
Security questions
Useful answers, stated precisely.
Where is UnionStack customer data hosted?
UnionStack production services and customer data use the Microsoft Azure Canada Central region, providing Canadian data residency.
How are stored objects protected?
Object content is encrypted by UnionStack before it is written to tenant-specific, non-public blob containers. The application uses tenant-specific keys and authenticated AES-GCM envelopes.
Does UnionStack scope API access to an organization?
Yes. The documented API model is tenant-aware, and requests operate within the organization that granted access.
Do API integrations follow user permissions?
Yes. API access follows the authenticated user’s approved roles and access rules; authorization is not replaced merely because an integration uses an API.
How should integration credentials be stored?
Client secrets should be held in an appropriate secret manager, kept out of client-side code and public repositories, and rotated or removed when the integration is retired.
Can member information be separated from public site content?
Yes. Public UnionStack Sites and separate authenticated member experiences serve different audiences. Administrators should still apply a deliberate publishing and access-review process.
Does UnionStack claim a specific compliance certification?
This page does not claim a certification that has not been independently documented. Ask UnionStack for current security and procurement information relevant to your organization’s requirements.
Built for connected work
Build connected workflows on clear access boundaries.
Explore the product or review the public developer security model.