Privacy, in plain English.
TheftScore is designed to work without an account and without building a profile of individual riders.
Saved models and areas
The watchlist is stored in your browser using local storage. To show whether new reports have been indexed, the saved model or area identifiers are sent to a read-only status endpoint when the list is displayed; TheftScore does not persist that list or associate it with a user. Removing the items or clearing site data deletes the browser copy.
Local area lookups
A postcode query is used to find an outward-code centre through Postcodes.io and request aggregated street-level vehicle-crime context from Police.uk. Completed monthly aggregates are cached against the outward code so the public services do not have to be queried repeatedly. TheftScore does not create a rider profile from the lookup. Use only an outward code, such as “SW1A,” if you do not want a full postcode to appear temporarily in ordinary hosting or access logs.
Contact
If you email [email protected], the message and address are processed so the enquiry can be answered. They are not added to a marketing list.
Cookies and measurement
TheftScore uses privacy-conscious aggregate measurement to understand which pages and features are useful. It does not use advertising cookies or cross-site tracking, and this measurement is not used to build individual visitor profiles.
External links and source records
Links to source registries, government services, social platforms and AskCarl have their own privacy practices. TheftScore displays information already contained in its cited source material. Requests about a source record itself should also be directed to the original publisher.
Your questions
For privacy questions or deletion requests concerning correspondence, email [email protected].