Draft for legal review. This page is not a finished legal document and has not been reviewed by counsel. Simtelligence Technology Inc., incorporated in Alberta, operates this service.
Privacy policy
Draft for legal review. This is a plain-language description of how the Simtelligence pilot works today. It is not a finished privacy policy and it has not been reviewed by counsel. Simtelligence Technology Inc., incorporated in Alberta, operates the service.
Who this is about
Simtelligence Technology Inc., incorporated in Alberta, operates the discrete-event simulation workspace at this site. The pilot is aimed at Canadian public-sector teams, including healthcare flow, public service counters, ports, and defence logistics.
What we store
- Account data: name, email, a password hash if you use a password, and a Microsoft Entra object id if you use Microsoft sign-in.
- Organization data: the organization name, member roles, and invite links. Invites are not emailed.
- Your models, experiment settings, results, traces, and exports.
- An audit log of sign-ins, membership changes, tokens, model edits, runs, and exports.
- Assistant conversations only as far as a turn needs them to call the simulation tools. Tool calls are written to the audit log. We do not sell conversation data.
- Contact-form messages: name, email, organization, the topic you picked, and the message.
Where it lives
The deployed pilot keeps that data in Canada. The data residency page lists each store and the cases that leave Canada Central. Object storage holds results and exports. PostgreSQL holds accounts, models, and the audit log.
How long
The pilot does not yet have an automated deletion schedule. Organization owners can delete models. A platform admin can read contact messages. Ask us if you want an account or a contact message removed.
Sharing
We do not sell personal information. People in your organization can see the models and runs that organization owns, according to their role. A platform admin can see organization names, usage, limits, and contact messages in order to run the pilot. A subprocessor is involved only when you turn on a chat model; that path is described on the data residency page.
Contact
Use the contact form on the home page. Say that the message is about privacy.