Data-Processing Agreement (Draft)
Last updated: Stage 7 Draft · PIPEDA Compliant
1. Scope & Roles
This Data-Processing Agreement ("DPA") applies when an account customer ("Controller") submits personal data (such as civic addresses or geographic coordinates associated with individuals) to Geo Service ("Processor") via the API or dashboard.
2. Processing Location & Subprocessors
All API processing takes place on dedicated servers in Beauharnois, Québec, Canada (hosted on OVHcloud Canadian infrastructure). No third-party geocoding or routing subprocessor receives API request payloads.
3. Retention & Deletion of Personal Data
- Synchronous API calls (
/search,/reverse,/api,/trip,/route,/table): Processed strictly in volatile memory with zero request logging or caching. No personal data from these requests is retained after the HTTP response is sent. - Asynchronous bulk batches (
/batch): Stored encrypted at rest on the Canadian application server and automatically purged within 72 hours of submission or immediately upon deletion by the Controller.
4. Security Measures
Processor enforces HTTPS with HSTS, HMAC-SHA256 key hashing with constant-time verification, strict account isolation on all account-owned resources, disabled access and query logging across all proxy, web, database, and geocoding/routing components, and authenticated encryption for database backups and temporary bulk lookup files.