Legal

Cookie & Analytics Storage Policy

BuildPair uses browser storage and similar technologies where needed to keep sessions working, remember choices and understand how the service is used.
Last updated 26 September 2026
01
Essential storage
Some cookies or local-storage items are necessary for authentication, account security, navigation and core app behaviour. Disabling these may stop parts of BuildPair from working correctly.
02
Basic statistical analytics
BuildPair uses first-party aggregate statistics by default to understand and improve the service. This can include visit starts, page views, meaningful button or link clicks, scroll-depth milestones, time spent on pages, named form fields reached, referral source, campaign parameters, broad device type, browser and operating-system category, language, timezone, screen or viewport size bands, connection category and coarse country, region or town/city location. Basic analytics does not retain an individual visitor journey or create a persistent visitor identifier.
03
Coarse location
BuildPair may use location information supplied by the hosting or network layer. Where that does not provide a useful town or region, the server may temporarily use the request IP address with an IP geolocation service, currently ipwho.is, to estimate country, region and town/city. BuildPair stores the coarse result in analytics rather than the raw IP address. IP geolocation is an estimate and is not treated as a street address, exact postcode or precise device location.
04
Optional detailed journey analytics
Detailed journey analytics is separate from basic statistics and is enabled only when a visitor actively chooses “Allow detailed analytics”. It uses a random first-party browser identifier, normally retained for up to 90 days, and a shorter-lived visit identifier to understand a sequence of pages and actions. It does not record the contents typed into fields. Switching back to basic analytics or turning analytics off removes the browser identifiers and requests deletion of detailed journey records associated with the anonymous identifier.
05
What visitor analytics excludes
BuildPair visitor analytics does not store passwords, authentication secrets, payment-card or bank-account details, the contents typed into form fields, precise GPS coordinates, street addresses, exact household location, mouse-movement recordings, hidden keystroke recordings, advertising profiles or cross-site tracking identifiers.
06
Privacy signals
BuildPair respects the browser privacy signals used by its analytics code, including Global Privacy Control and Do Not Track where available. Those signals disable BuildPair visitor analytics for that browser.
07
Analytics choices
Your current BuildPair analytics setting: Basic aggregate.
Basic aggregate analytics is the default. It does not create a persistent visitor ID or retain an individual browsing journey. If you start registration from a campaign link, BuildPair may keep its campaign source in this browser tab until sign-up finishes and count the completed sign-up without your name or email. Detailed analytics creates a random anonymous browser identifier only after you choose it.
08
Third-party services
Authentication, payment, hosting and other service providers may set or read their own cookies or storage when their features are used. Their handling of those technologies is governed by their own notices and our agreements with them. BuildPair visitor analytics is designed for product measurement and improvement rather than advertising.
09
Contact
Questions about cookies, browser storage, location estimation or analytics can be sent to info@buildpair.co.uk.
One project. Both sides connected.
A fairer UK marketplace and project platform for homeowners and tradespeople, from first search to finished job.
info@buildpair.co.uk
FOLLOW BUILDPAIR
© 2026 BuildPair. All rights reserved.
BuildPair is a marketplace and project platform, not a building contractor or building-control body. See Payments, Terms and Disclaimer for full details.