CompMaps — Privacy

Interim Pilot · Effective November 8, 2026

What we cannot see

What we can see

Geoapify, the map and address service CompMaps uses, also sees each address you send without coordinates, because its service looks the address up. When CompMaps checks a pin against a municipality's own address points, that municipality's service also sees the street number and street.

1. The link is the key

When you submit a table, CompMaps makes a key for that job: a random code, 32 characters long. The key travels in the link to your maps, after #k=: in the page you land on, and in the email if you give an email address. Browsers never send that part of a link to a server, so the key never reaches us. Your maps, their one-line summary and their notes are locked with it (AES-256 encryption), and your browser unlocks them. The job number printed on each map opens nothing on its own.

Your browser also remembers the key, so you can return from the same browser without the email. Clearing this site's data in your browser forgets it.

2. What happens to what you send

WhatWhere it goesHow longWho can see it
Your spreadsheetRead in your browser. Only its rows (number, address, pin colour, coordinates) are sent.—You
The rowsCompMaps' service in Amazon Web Services, Canada (Central). They wait in a queue until the map maker takes them, usually seconds. If your firm subscribes, its account name travels with them.Deleted once the maps are made; at most one day if the service is downThe service
Addresses without coordinatesLooked up with Geoapify's address search, under its privacy policy. Geoapify hosts its service in European Union data centres and says it generally keeps a successful request no longer than 24 hours. The request comes from CompMaps' server, not your browser.Their policyGeoapify
Street number and streetMunicipal address services (for example the City of London's): the street number and street of each property, when CompMaps checks a pin against the municipality's own address points. CompMaps keeps nothing from this exchange. The request comes from CompMaps' server, not your browser.Not kept by CompMapsThe municipality
Looked-up pointsKept so the same address need not be looked up twice, filed under a one-way code made from the address. The address itself is not stored. Someone who already knows an address could check whether it was looked up.7 daysThe service
Map tilesThe street-map and aerial pieces your maps were drawn from, kept so they aren't downloaded again. They show the general area mapped; close-up tiles are never kept. Street-map pieces come from Geoapify; aerial pieces from the Province of Ontario.7 days (street map), 30 days (aerial)The service
Your maps, summary and notesStored locked. The summary names Subject 1. Once your browser unlocks it, Subject 1's address heads the page and names the browser tab.30 daysWhoever holds the link
Diagnostics fileHow your job ran, for you to send us if something goes wrong. Locked.30 daysWhoever holds the link
Your email addressStored with the job so the link can be sent; the email goes out through Amazon's email service.About 31 daysThe operator
Your firm's account (subscribers)A short account name, whether the account is active, and the date it is paid to. Your firm's access code is not stored: only a one-way code made from it, so the service can check a code but no one can read it back.While your firm subscribes, and 90 days afterThe operator
Your firm's style pack (subscribers)Your logo, colours, fonts and pin artwork, stored privately in Amazon Web Services, Canada (Central), and used only to draw your firm's maps.While your firm subscribes, and 90 days afterThe operator and the service
The email itselfYour inbox. It holds the link and the one-line summary, which names Subject 1.As long as you keep itYou
The job recordStatus, number of rows, times, and the locked items above.About 31 daysThe operator (locked items stay locked)
Service logsJob number, map and note counts, the kind of any error, and your firm's account name if it subscribes. No addresses.7 daysThe operator
Your acceptance of the termsTerms version, time, browser description and IP address.7 years, as the record of your acceptanceThe operator
Audit logEach time we or the service open stored maps or records.7 yearsThe operator

Map pieces (street map and aerial imagery) are fetched by CompMaps' server. Those requests show which area was mapped, never an address or your identity.

3. What the operator can and cannot see

The operator runs the service and can read anything stored in plain form: your email address, the job's status and times, the service logs, and, for a subscribing firm, its account and style pack. The operator cannot read a firm's access code, and cannot open your stored maps, summary or notes without your link.

While your job is being made, the service handles your rows in plain form. It has to, to draw the map. Locking protects what is stored, not a job in progress.

An audit log records each time we or the service open stored maps or records, and keeps it 7 years. It holds no IP address or browser of yours.

4. Checked by outside tools

Mozilla HTTP Observatory: A+ (security headers). Qualys SSL Labs: A+ (encryption in transit). Both last checked 28 September 2026. The links run each test again now, so you see the current grade, not our claim: Run the Observatory test · Run the SSL Labs test.

5. Check it yourself

You don't have to take sections 1 and 2 on trust. The code that locks your maps is published, copied from the running service: lock.py. The status page's own code, which unlocks them in your browser, is p.js. The check that stops any change to the site if a setting this page depends on has changed is privacy_check.py.

To see that your key never leaves your browser: open your maps page, press F12, choose the Network tab, and reload. Your key is the part of the page's web address after #k=. It appears in none of the requests.

We test this ourselves too. On 28 September 2026 we sent a made-up address through CompMaps, then searched everything the service stores: files, records, logs, queues and the audit log. It was found nowhere.

6. Sending no addresses at all

If every row in your table has a latitude and longitude, leave the addresses out. CompMaps then sends no address anywhere, and your summary names Subject 1 by its coordinates.

7. Reporting a problem

If you find a security or privacy problem (or any bug, really), please write to security@comp-maps.ca. We'll reply within 5 business days.

8. Changes

This page describes the interim pilot and will change before CompMaps is offered more widely. The date at the top shows when it last changed.

About CompMaps

CompMaps is a small, independent project built and run by one person in London, Ontario, on personal time and personal resources. It's offered free to invited pilot users while it's being tested. Nothing you send is sold, shared or used for anything but making your maps.

This page explains how CompMaps handles your data in plain language. The binding document is the Terms of Use & Disclaimer. Questions: ask the person who invited you to the pilot.

← Back to CompMaps