Updated 13 October 2026.
BuilderVet collects available official register records about businesses and occupational licences. Records can include sole traders’ public occupational information. Public profiles include source information and dates; they are not private customer notes.
We store your account email, authentication records, purchased rights, monitored builders, delivery preferences, and notification history. Professional workspaces also store client folder names. Notes and checklist responses are private to the owning account.
Do not put bank details, identity documents, or unnecessary personal information in notes or client names. A checklist records your actions; it does not certify compliance.
If you ask for updates about a report or practice plan, we store the email address, offer, consent date and version, and the builder you chose if you started from a builder profile. This is not an order or a reservation. We do not charge you or start monitoring from this request. We do not verify ownership of the email address when you submit it. Contact us to remove your interest.
Stripe processes payments. BuilderVet keeps payment references, purchase or subscription state, and access dates so it can provide the service. Card entry occurs with Stripe. Cloudflare provides application hosting and data storage. Email services receive the address and message needed to deliver sign-in links and enabled alerts.
We compare source records for the builders you monitor and retain dated evidence and change history. Your account controls change-alert emails and monitoring settings. Transactional sign-in and billing messages are separate from optional change alerts.
Existing free address watches remain separate from paid builder monitoring.
Ad and campaign source. When you arrive from an ad or a tagged link, this browser keeps the ad click ID, the campaign tags (UTM values), the page you landed on and the referring site (without its query) in local storage for up to 90 days. Nothing is sent while you browse. If you create an account or start a checkout, we save them with that account or order, and with the payment record at Stripe, so we can tell which campaign led to it. We may upload the click ID, time and amount of a purchase to Google Ads to measure that ad. No email or name is uploaded.
We record optional funnel events only after you accept analytics in Analytics settings. You can reopen those settings and reject analytics at any time. Rejection removes analytics identifiers. Account sessions and the email-update choice are separate. Public marketing pages record coarse page categories, selected CTA placements, audience, and approved campaign codes. A random session ID lasts for the browser tab. We record first and latest campaign sources within that session. We do not store raw referrer URLs, search queries, arbitrary UTM text, advertising click IDs, emails, or passwords in these events. Do Not Track and Global Privacy Control override your choice and stop optional analytics. Consented email requests are counted when the server saves them; duplicate requests do not count twice. Essential account, security and error services operate separately from optional analytics. BugTape reports errors on eligible logged-out public pages. It is excluded from private app pages, form pages, URLs with queries or fragments, and pages with a saved account session. Optional Cloudflare Web Analytics can measure eligible public-page performance after consent when configured. Google tags are off unless configured and you accept analytics. Google events use page groups and a virtual URL and title. Private account pages, query strings, builder identity and form contents are not sent to Google. Advertising features stay off. Page exits and incomplete flows are estimates; they do not prove why a visitor left. Infrastructure providers can process technical request information for service delivery and abuse prevention. Private notes and checklist content must not be sent in product analytics.
A homeowner purchase retains its saved snapshot after monitoring ends. Professional evidence remains read-only after the subscription expires. Payment and service records can need longer retention for accounting, disputes, and legal obligations.
To request account-data access, correction, or deletion, contact us. We may need to verify ownership. We will explain any record we must retain rather than promise immediate deletion of every record.
Contact the source register to correct the authoritative record. You can also ask BuilderVet to review its presentation with the profile URL and specific fact. An archived record and a current record can differ; source dates and context must stay visible.