Privacy
How we check that we do not keep your searches
1. What we promise
None of our records can tell what a person searched for. The exceptions, published: what you send us yourself (an order, an alert you switch on), and Cloudflare's records from before the change, which expire on their own.
2. How we check it
Every day at 06:10 UTC, a program on our server:
- compares the code that is running with the code of the last full test;
- reviews the records of the last 24 hours (23 stores), looking for anything that could link someone to what they searched for;
- publishes the result in a public, chained GitHub log: each entry includes the fingerprint of the previous one, so none can be deleted or changed without it showing;
- asks two independent timestamping authorities (FreeTSA and DigiCert, RFC 3161) to timestamp the entry's fingerprint, and Software Heritage and the Internet Archive to keep a copy we do not control. A timestamp proves that the entry existed at that moment; it does not vouch for its content. The authorities receive only the fingerprint.
On top of that, every hour (at :25 UTC) a shorter check compares the fingerprint of our five components (site, API worker, backend, server configuration and the checker itself) with the last full test, and reviews our own records since the hour before. Each hour adds a chained line to the log, and the next daily entry anchors the whole day's lines. Our providers' records are reviewed once a day.
3. What each colour means
- Green: nothing found on our systems (our server and the records our own code writes), all of them reviewed.
- Amber: something found on our systems; we publish it as it is until we have looked into it.
- Grey: the check has not been published for 36 hours, or one of our records could not be read. We then show no number.
- The number adds up the daily review and the hourly checks since. If the hourly check has not been published for more than two hours, the details say so.
- Records kept by our providers (Cloudflare and Google Analytics) are counted apart, in the indicator's details, and do not change its colour. If we change what we record, the details say so until the next full test.
4. Check it yourself
The log is at github.com/anbrme/mapasocietario-privacy-log. Download the repository and run node verify-evidence.mjs (needs Node 18 or later, and openssl): it checks that every entry matches its hash and that the chain is intact, the hourly ones too, and verifies the timestamps against the two authorities’ certificates. An alteration shows up when compared with a copy kept earlier, or with the Software Heritage and Internet Archive copies. Each entry shows the date, the records reviewed, what was found and the code fingerprint.
These checks are operated by Mapa Societario. Anyone can verify the integrity of the published reports; that verification does not by itself establish that every possible logging location was inspected. That is why we publish what each check covers and what it does not.
This link takes you to GitHub, which will see your visit.
5. Full test
When what we record changes, we run a full reconstruction test: we search rare companies with test data and check that they appear in no record. Latest result: 24 October 2026, 26 of 26 stores with no trace of the test searches (Google Analytics pending; its reports take 24–48 hours).