Security & Trust
Security & Trust
We are committed to developing secure and reliable technology solutions for public-sector and commercial organizations.
Our approach prioritizes data protection, secure system architecture, access management, and responsible development practices.
We continuously improve our security practices as our products and operations mature. Formal certifications and independent audits will be pursued based on business needs and client requirements.
We provide transparent and accurate information about our security and compliance status upon request.
Hosting
This is our deployment architecture. Production runs in AWS Canada Central, in Montréal (ca-central-1). The recovery copy is in AWS Canada West, in Calgary (ca-west-1). Staging and backups stay in Canada.
A live model is in scope only in Canada, and only after the residency acknowledgement in settings is confirmed. The phone-platform region defaults to Canada Central.
Access security
Access is by role. Each division has a role profile, and a user permission can limit work orders and service requests to that division. Residents work in the portal, on their own requests and bills.
The social insurance number on the employee record is visible to HR managers. OneCity AI uses the same permissions as the screen.
Data protection
The public site and the hosted service are served over TLS. This site sends a content security policy that upgrades insecure requests. Browsers should be offered TLS 1.2 or newer only. Disks and object storage in the Canadian hosting design are encrypted at rest by the cloud platform.
Record changes keep a version history. OneCity AI writes an interaction log, with a retention setting. Reads of social-services records, including reads through the assistant, are written to the client access log. Payment screens store a card brand and the last four digits.
Disaster recovery
Before a production upgrade, a full backup is taken, including files. The release is restored and rehearsed on a staging copy, with outbound email muted. If the municipality rejects the release, the previous build is restored from that backup.
Recovery of the service is designed across the two Canadian regions: Montréal for the primary, Calgary for disaster recovery.
Privacy
The product is shaped for the federal Personal Information Protection and Electronic Documents Act (PIPEDA). Provincial statutes are configured for the municipality. In Ontario, that includes the Municipal Freedom of Information and Protection of Privacy Act, and the privacy impact assessment Ontario requires under MFIPPA from 1 January 2027. Other provinces use their own municipal privacy statute.
Social-services settings hold a notice of collection and a place to attach a privacy impact assessment. A privacy impact assessment for a live AI model — what is sent, how long the log is kept, who can read it — is a step the municipality takes before that model is enabled.
Accessibility
The marketing site and the application are described on the accessibility page: what each one is designed to do, for people using a keyboard, a screen reader, or French and English.
Read the accessibility statement
Security contact
For a security or privacy question about OneCity Canada, write to support@dailycheck.work.