Privacy Policy (Draft)
Last updated: Stage 7 Draft · Canadian Data Residency · Zero Request Logging
1. Canadian Hosting
All application servers, databases, and geocoding/routing engines for Geo Service are hosted exclusively in Canada (OVHcloud Beauharnois, Québec). API requests are processed entirely on our Canadian servers and are never forwarded to third-party geocoding providers.
2. No Request Logging & No Request Caching
We do not log or cache the contents of your API requests:
- Live lookups, suggestions, routes, and tables: No request paths, search queries, addresses, coordinates, or keys are written to proxy access logs, web-server logs, application logs, exception reports, databases, Redis, or engine logs/caches. Addresses and coordinates exist only in volatile memory while answering your request.
- Usage counters only: We record only aggregate numeric counters per key, per UTC day, and per call kind (lookups, suggestions, routes, route points, table cells, bulk rows) to enforce plan limits and display your usage in the dashboard.
3. Bulk Lookups (72-Hour Encrypted Retention)
The sole exception to in-memory-only processing is when you explicitly submit a bulk lookup batch (/batch or via the dashboard):
- Your uploaded address list and its geocoded result are encrypted at rest on the Canadian application server using AES-256-GCM authenticated encryption.
- They are never written to logs and are accessible only to your account.
- They are permanently deleted as soon as you delete the batch, or automatically at most 72 hours after submission.
4. Account & Billing Data
For account administration and billing, we store your account name, verified user email address, password hash, two-factor authentication secret (encrypted), registered browser origins, key prefixes and HMAC-SHA256 hashes, daily usage counters, and Stripe customer/subscription identifiers. Payment card numbers are handled directly by Stripe and are never stored on our servers.