Privacy Policy

Publication draft: operator details, hosting information and applicable legal terms need to be completed and reviewed before public launch.

Search and comparison browsing do not require an account. No third-party analytics or advertising scripts are installed. Optional first-party analytics run only after you choose Allow analytics; you can decline or withdraw permission using Analytics preferences in the footer.

With permission, analytics records public page paths, catalogue tools searched or viewed, search result counts, filters, match completion counts, referring domains and broad viewport sizes. Random browser and session identifiers are stored as hashes. The application does not store IP addresses, raw search text, full referrer URLs, match criteria or account identities in analytics. These pseudonymous events are retained for 180 days and reported to signed-in editors as aggregate counts.

A visitor count estimates browsers that accepted analytics, not individual people. Analytics respects Do Not Track and Global Privacy Control signals, and excludes signed-in editors and recognised bots. Withdrawing permission stops future collection and removes the analytics identifier cookies; previously recorded events expire under the retention period.

Editorial accounts store a username and a salted password hash. Sign-in creates a necessary HttpOnly session cookie with an eight-hour lifetime. The database retains session hashes, short-lived request counters and an editorial audit trail.

The hosting provider may process IP addresses and access logs. The operator must document the actual hosting provider, logging settings, retention periods, legal bases, rights and contact details before public launch.

Outbound links take you to independent vendors, whose privacy practices apply on their sites. Any future third-party analytics or advertising integration requires a review of these notices and consent controls.