Canadian fleet data residency and sovereignty: a buyer checklist
Data residency is where copies of your fleet records are kept. Sovereignty is who can reach and control them. A vendor's head-office address answers neither. Get six answers in writing before you sign: storage, backups, processing, access, subprocessors, and control at exit.
Where ReWheel stands
ReWheel can offer a deployment in a Canadian region, and in other countries' regions on request; storage, processing and access locations and subprocessors are confirmed in a reviewed deployment proposal.
Check its storage, processing, access and subprocessor answers against questions 1, 3, 4 and 5 below; raise backups and exit (2 and 6) separately.
The six questions
Ask each vendor, and accept only a named, written answer
- Where are the primary records stored? The contracting company and the storage can sit in different countries.
- Where are backups and recovery copies kept? Backups are often held apart from primary storage.
- Where is the data processed, including reports and logs? Processing can run somewhere other than storage.
- Who can access the data, and from where? Support and administration staff may work from other countries.
- Which subprocessors handle the data? Each one is another party with its own location. Ask for the list and how you are told about changes.
- Who controls keys, export and deletion when you leave? Location says nothing about getting your records back.
A blank or general answer is an open item, not a yes. Record who answered, from which document, and on what date.
The mistake to avoid
Choosing by address. A Canadian company can keep backups or support access outside Canada, and a foreign company can store data in Canada. Compare the written answers to the six questions, not where the vendor is based.
Outside Canada
The same six questions work anywhere. Name the country and get the answers for that deployment; an answer for one country does not carry over to another. Whether an arrangement meets your legal or contractual obligations is for your own qualified review; this checklist gives that review its facts.
Fleets that cross the border have one more question: which networks and roaming terms carry vehicle data on each side. Ask it separately from storage, because driving into another country does not change where the records are kept.
Data-location checklist
Fill each row only from a documented answer. Nothing is prefilled.
On a small screen, scroll this table horizontally. Keyboard users can focus the table region and use arrow keys.
| Area | Written answer | Review question |
|---|---|---|
| Company | Contracting entity and applicable agreement | Who is accountable for the service? |
| Storage and recovery | Primary, backup and recovery locations | Which copies are covered by the answer? |
| Processing | Locations and purposes of operational processing | Are logs, analytics and support processing included? |
| Access | Authorized roles, access locations and controls | Who may read or recover the records? |
| Subprocessors | Named services, roles and change process | Who else handles the data? |
| Keys and control | Key custody and authorization procedures | Who can authorize decryption or recovery? |
| Jurisdiction and exit | Applicable terms, export and deletion proof | Which questions need qualified contractual review? |
Sources and review context
What ReWheel provides
ReWheel FMS connects supported vehicle information with equipment and operational records for field and institutional operations. Vehicle compatibility, data-access requirements, connectivity and installation are assessed per deployment, never assumed.
Continue with ReWheel: Operational fleet records for Canadian buyers
Discuss your workflow