Data the platform holds
| Data | Why it's needed | Required? | Shared with |
|---|---|---|---|
| Name, email, phone of account holders | Signing in, notifications, a record of each change | Name and email: yes. Phone: optional | The customer's own staff |
| Unit and building links | Approvals, limits per unit, permits | Yes, for residents | The customer's staff and patrol |
| Licence plates and vehicle details | Passes, plate checks, permits and rentals | Plate: yes. Description: optional | The customer's staff and patrol |
| Visitor contact details | Sending the pass and reminders | One way to reach the visitor | Email and text delivery providers, for delivery only |
| Visit times and reason for visit | Rules, front desk, reports | Times: yes. Reason: optional | The customer's staff |
| Vehicle photos (visitor) | Helping the desk and patrol identify the car | Optional | The customer's staff and patrol |
| Patrol location and time | Proving checkpoints were visited, site-visit reports | Only while a patrol is working | The customer's managers |
| Parking notices, evidence photos, disputes | Enforcement and fair review of disputes | When a notice is issued | The customer's staff; the driver sees their own notice |
| Payment records | Receipts, statements, refunds | When paying online | The payment processor (card details stay with them) |
| Sign-in and audit history | Security and accountability | Yes | The customer's administrators |
ParkCommand does not collect government ID numbers, dates of birth, health information or card numbers. Plate photos read on the phone are processed on the device; only the plate text is sent.
Who has access
- The customer decides. Each person gets a role per building (manager, front desk, patrol, resident and others), and sees only what that role allows at the buildings they are assigned to.
- Residents see their own unit, vehicles, guests and notices, never their neighbours'. A resident sharing a spot is never identified to the person booking it.
- Visitors and drivers reach only their own pass or notice, through a private link.
- Customers never see each other's data. Separation is enforced by the application and again by the database itself.
- ParkCommand staff are not members of any customer. When support needs to look at an account to solve a problem, that access is limited and recorded in the audit log.
Security practices
- Encrypted connections everywhere, behind a network security service that filters attacks before they reach our servers.
- Passwords stored only as Argon2id one-way hashes; we can never read them.
- Two-factor sign-in with an authenticator app, and single sign-on with Microsoft, Google or other work accounts for enterprise customers.
- Sign-in sessions held in secure cookies that page scripts cannot read.
- Sensitive settings, such as a building's own payment or email credentials, encrypted at rest and never shown back in the browser.
- Every create, change and delete recorded in an audit log with who, when and from where.
- Rate limits that slow down password guessing and other abuse.
- Software updates reviewed and tested before release, with automated tests covering access rules.
Retention and deletion
Each customer chooses how long it keeps each kind of record. To keep disputes and security reviews possible, the platform sets minimums:
| Record | Minimum kept |
|---|---|
| Visitor passes and reservations | 30 days |
| Photos | 30 days |
| Parking notices and violations | 90 days |
| Audit history | 90 days |
When a record passes the customer's retention period, it is deleted automatically. A customer can also delete people and records sooner, for example when a resident moves out. When a customer leaves ParkCommand, it has 30 days to export its data, after which the data is deleted.
Backups and recovery
A full backup runs every night. It is encrypted before it leaves our servers, with a key that only ParkCommand's administrators hold, and stored with a separate storage provider. Backups expire on a fixed schedule, so deleted data does not live on in them indefinitely.
If something goes wrong
The platform is monitored around the clock and its status is published at parkcommand.ca/status. If we learn of a breach affecting personal information, we contain it, investigate, and notify the affected customers without delay. Where there is a real risk of significant harm, we also notify the people involved, as Canadian privacy law requires, and report it to the Privacy Commissioner of Canada.
Requests and questions
Residents, visitors and drivers: the building or company that manages your parking can show, correct or delete your records, and we help them do it. You can also write to us at [email protected], and we will pass your request to the right customer or answer it ourselves.