Buildertrend Opt Out: Privacy Form, Phone and Deletion

To request deletion or exercise privacy rights with Buildertrend, use the Individual Rights Form in Section X of its privacy notice or call the published toll-free number, 1-888-415-7139. For cookie-based sale or sharing preferences, use its separate “Do Not Sell or Share My Personal Information” page. If your information belongs to a contractor’s project records, identify that contractor too: Buildertrend may process those records on the contractor’s behalf rather than control the decision to delete them.

This Buildertrend opt out guide uses the official privacy notice and state disclosures checked September 23, 2026. Those sources were readable through a source reader, but direct browser visits returned access errors. The guide therefore documents the published routes without inventing form fields, a successful submission, or a removal result.

Buildertrend opt out quick facts

Buildertrend is construction-management software. Its notice covers people such as contractors, subcontractors, clients, prospects, and visitors. A privacy request may therefore concern a business relationship or project account, not a public name-search listing.

For other companies that hold your information, the opt-out guide hub provides separate workflows. A Buildertrend request does not automatically alter records in another construction, property, or marketing database.

First decide who controls the record

Buildertrend’s notice distinguishes two roles. When it has a direct relationship with you and acts for itself, it controls the relevant personal information. When it processes information for a customer, that customer controls the information and Buildertrend acts on the customer’s behalf.

This distinction matters for homeowners and subcontractors. A builder may have uploaded project correspondence, contact details, or documents to manage a renovation. Deleting a platform login does not necessarily settle the builder’s recordkeeping obligations or remove its own copies of those documents.

Identify the project, company, or account involved without sending an entire project archive. Ask Buildertrend whether it controls the data in question or needs the customer’s instruction. If the contractor controls it, direct the request to that contractor and retain both responses.

The notice also covers Buildertrend-related entities, including CB/USA and Buildertrend Insurance Services. Name the relevant relationship when you know it. Do not infer that every product or entity has the same data purpose merely because the notice groups them together.

If the concern is a separate property record, the CoreLogic guide explains another workflow. Removing data from construction software does not amend a public deed, county record, or unrelated property-information service.

How to make the manual privacy request

1. Prepare the request scope before contacting support

Write down which personal information concerns you and what you want done with it. Useful distinctions include access to data, correction of a wrong contact detail, deletion, or an opt-out from particular processing. Include the relevant account or project context you already know.

Use the email address associated with the relationship if you still control it. If you no longer have access, explain that when seeking verification. Do not use another person’s login or create a new paid account simply to make a privacy request.

2. Use Section X or the published phone number

Open the Buildertrend privacy notice and find Section X, Contact Us. The notice gives 1-888-415-7139 and an embedded form for exercising legal rights. The additional state disclosures repeat the phone/form routes for access, portability, correction, and deletion.

If the page does not render, the published toll-free route provides an alternative for those requests. Ask the representative how to record your request and obtain a reference. This guide has not called the number or verified the experience after a call begins.

For a non-cookie opt-out, the state disclosures specifically direct readers to the Individual Rights Form. If that form is unavailable to you, ask the privacy contact for a working submission method and describe the request type. Do not assume a website cookie preference performs the same action.

3. Complete the appropriate verification

Buildertrend says it may verify identity and residence before processing certain rights requests. Its disclosures describe account authentication or matching information against existing records. Additional information may be requested depending on the sensitivity of the action.

Provide the requested matching information through the official channel. Do not attach passwords, full tax records, or unrelated construction documents to the first email. If a document is requested, ask what fields are necessary and how to send it securely.

Authorized agents may need a power of attorney or signed authorization with specified details. Buildertrend may also contact the individual directly. A contractor, relative, or service acting for you should follow this authorization process rather than presenting itself as you.

4. Retain the response and clarify exceptions

Keep a private record of the date, requested action, case number, verification steps, and final answer. Check whether Buildertrend acted on its own records, routed the matter to a customer, or retained information for a stated purpose.

A request may be declined if identity cannot be verified or the information cannot be located. Clarify the matching details before repeating the same request. If the provider offers an appeal applicable to your situation, use it with the original reference and a specific explanation of what remains unresolved.

Cookie controls and marketing need separate attention

The Do Not Sell or Share page is the notice’s designated route for cookie-based sale and targeted-advertising controls. The state disclosures also say Buildertrend recognizes Global Privacy Control on its public-facing sites. These controls address browsing-related information associated with the visit.

They should not be described as a deletion request for every account or project record. Different browsers, devices, and app contexts may need their own settings. Read the cookie notice alongside the rights request if tracking is part of your concern.

Promotional email can be stopped using its unsubscribe link. Service-related messages, such as security notices or account updates, can remain necessary for an active relationship. If you are still receiving project notifications, ask whether they come from the contractor’s workflow rather than assuming the marketing unsubscribe failed.

For unwanted exposure on other sites, the address-removal guide helps separate source records, public listings, and search results. Those are different tasks from changing website advertising preferences.

Timing, appeals, and future records

The checked instructions do not establish one universal deletion-completion period. Ask for an expected response date and preserve any explanation of additional verification or retained records. A website access error does not establish that the underlying rights process is unavailable by every channel.

The state disclosures provide privacy@buildertrend.com for appeals. They display two subject-line variations in different sections: “Consumer Rights Request Appeal” and “Privacy Request Appeal.” Use a clear appeal subject and include your original reference; ask the privacy team to confirm receipt rather than treating the wording as a guarantee of processing.

The privacy notice describes retention based on business and legal purposes. New project activity, another contractor upload, or a new account relationship may also create later records. An old confirmation should be read according to its date and scope, not as a promise about all future information.

Use the data broker opt-out list for separate requests elsewhere, and the broader removal checklist to track confirmations and exceptions. If you want to inspect public exposure on supported sources, run a free data broker scan. It does not inspect private Buildertrend projects or determine what a contractor must retain.

• Identify whether Buildertrend or the contractor controls the particular record.
• Use the rights form or documented phone route for the appropriate request.
• Treat cookie preferences and account or project deletion as separate actions.
• Keep the reference and ask which retained records or verification issues remain.

Frequently asked questions

Can I delete a builder’s records by closing my login?

Not necessarily. The contractor may control project data and keep its own records outside Buildertrend. Ask which organization controls the specific data, and request a written explanation of what account closure changes.

Is the public opt-out page the same as the rights form?

No. The state disclosures distinguish cookie-based controls from the Individual Rights Form used for non-cookie requests. Choose the route matching the data and action you are concerned about.

What should I do if the form is blocked?

The official notice supplies a toll-free number for privacy rights and a privacy email for relevant contact and appeals. Explain the access problem and ask for the correct alternative. Do not guess fields or send sensitive data to an unofficial form.

Will opting out stop project and security emails?

Promotional email preferences are different from service-related communications. Clarify whether the messages are marketing, account administration, or contractor-generated project notifications before assuming one unsubscribe handles all three.

Do I need to prove my identity?

Verification may be required for certain requests, using authentication or information matching. The method depends on the request and circumstances. Wait for the official instructions instead of preemptively attaching sensitive documents.

Sources and verification

Source basis checked September 23, 2026: Buildertrend’s privacy notice, additional US state disclosures, and their linked cookie and opt-out routes. Direct notice and state-page browser visits returned 403, so no form screenshot or field-level walkthrough is claimed. Published phone and contact instructions are documented alternatives; no call, request, or deletion was performed.