CoreLogic Opt-Out Guide: Cotality Privacy Steps 2026

A CoreLogic opt-out in 2026 uses the current Cotality privacy pages. CoreLogic now does business under the Cotality brand, so old CoreLogic links may redirect or no longer describe the active request. Use the general visitor form for covered website data, the separate B2B form when eligible, or the sale-and-sharing choice for targeted advertising. This does not automatically erase property, credit, or other public records.

Start with a free exposure scan if you need a broader inventory. Keep this page with the opt-out guide hub and the data broker opt-out list so you can track this request alongside other removals.

Source basis: Cotality’s U.S. state supplemental privacy notice, general visitor form, B2B form, privacy policy, and current legal pages were checked July 31, 2026. The notice lists access, deletion, correction, sale or sharing opt-out, profiling, verification, and appeal choices. No form was submitted.

CoreLogic and Cotality opt-out facts at a glance

Use the current Cotality request, not an outdated CoreLogic form

Cotality’s current supplemental notice covers personal information connected to its website and defined U.S. state privacy rights. It lists access, deletion, correction, sale or sharing opt-out, targeted-advertising limits, certain profiling choices, and appeals. The available action depends on residence, relationship, and legal exceptions.

The general visitor form is for website visitors. The B2B form is narrower and identifies California business contacts, such as representatives who supplied contact data in a business relationship. Employee and applicant data use another form. Pick the route based on how Cotality obtained the information rather than selecting the first form in search results.

CoreLogic and Cotality also work with property, risk, and other regulated or public-record information. A website privacy request does not promise removal of source records, data processed for a client, or information retained for legal, security, transaction, or fraud-prevention purposes.

What to prepare before you start

Identify where you saw the data: a Cotality website interaction, B2B marketing contact, account, property product, consumer report, or another service. Save the page URL and a non-sensitive description of the record.

Choose the matching request type. Use sale or sharing opt-out when the goal is targeted-advertising control, deletion when you want eligible stored data removed, and correction when the record is inaccurate. A product-specific dispute may be required for regulated reporting data.

Prepare your name, email, phone number, and mailing address because Cotality says it may use those fields to match and verify a request. Do not upload more evidence than the active official form requests.

Record the CoreLogic name as the legacy query and Cotality as the current destination. This helps support understand why an old link or product label led you to a newer privacy page.

How to opt out of CoreLogic and Cotality step by step

1. Open cotality.com/legal/notice-at-collection-and-u-s-state-supplemental-privacy-notice and confirm the page lists the privacy right you want to exercise.
2. Follow the General Website Visitor Form for ordinary website data, the B2B form for an eligible California business contact, or the employee form only for the defined employment relationship.
3. For sale or sharing and targeted-advertising control, use the active Do Not Sell or Share link, the published privacy phone number, the privacy email route, or cookie preferences described in the notice.
4. Select access, deletion, correction, or another available choice. Explain the specific Cotality or legacy CoreLogic interaction without adding unrelated sensitive information.
5. Complete identity verification. Cotality says it may ask for name, email, phone number, or mailing address and may request more information when the first match is insufficient.
6. Save the submission confirmation, request type, date, and page URL. If the form embeds dynamically, keep a screenshot only when it contains no private entries.
7. Follow up through the published phone or privacy email if the route fails. Use the appeal channel when Cotality denies an eligible request and the state notice provides an appeal right.

Verification, timing, and follow-up

Cotality says requests are processed under applicable state privacy laws. That means the response window, verification standard, and available appeal can vary. Use the deadline in the response rather than assuming one universal period.

Check whether the result addresses website data, B2B contact data, or the specific product you named. A confirmation for cookie preferences is not proof that a property record or client-controlled database was deleted.

If an old CoreLogic URL redirects, verify the final cotality.com domain and page title before entering data. Retain the redirect destination and date because brand migrations can leave stale instructions in search results.

Public records, client data, and regulated products

Cotality may obtain property and other information from public or regulated sources. Deleting a website profile does not change a county record, title record, or other source. Correct the source when the underlying record is wrong.

Cotality can process information for clients. When it acts as a service provider, the client may control the request and need to receive it directly. Use the response to identify the controller instead of repeatedly submitting the same website form.

Legal obligations, fraud prevention, security, and transaction records can create retention exceptions. The provider can also ask for verification to avoid deleting another person’s data. Do not interpret a partial response as a full internet removal.

Why data can reappear and what to monitor

Property and business data can be refreshed from public records, customer submissions, and new website activity. A sale or sharing opt-out can limit a defined use while the source record remains available for another purpose.

Recheck after a property transaction, move, new business role, or account change. Track each Cotality product separately and use the source agency for corrections where the provider cannot alter the original public record.

Create a small request log for CoreLogic and Cotality. Record the official URL, request category, submission date, confirmation channel, expected response window, and the identifier you used. Do not copy a full government ID, Social Security number, password, or security answer into the log. A reference number and a short description are enough for follow-up. This record helps you distinguish an unfinished request from a new exposure months later.

Check the sender and date when marketing or a listing returns. A message prepared before the opt-out can arrive after submission, while a newly dated campaign may show that another identifier or source is still active. Save only the minimum evidence needed, such as a redacted header, page URL, or company name. Use that evidence to contact the correct controller instead of repeating every request.

Treat verification messages as sensitive. Open the provider site directly instead of following an unexpected shortened link, confirm the domain, and avoid paying anyone to process a free privacy form. If a portal asks for identification, review why it is needed and whether a less sensitive matching route is available. Stop when the domain, request purpose, or recipient is unclear.

Recheck the result on a schedule that matches the data source. Marketing and identity databases can refresh after a new purchase, account, job, move, or partner upload. Start with a 30 to 45 day check when the provider does not publish a faster window, then check again after a major change in your identifiers. Keep separate notes for source correction, suppression, deletion, and device controls because each action has a different result.

Continue with the manual broker removal workflow, compare the PropertyRadar opt-out guide, and review the BlockShopper opt-out guide. For an ongoing option, see the service comparison hub.

CoreLogic and Cotality opt-out FAQ

Is CoreLogic now called Cotality?

Yes. Current legal pages use Cotality while still identifying CoreLogic in company and legacy-form language. Use the active Cotality domain for privacy requests.

Which Cotality privacy form should I use?

Use the general visitor form for website data, the B2B form for the defined California business-contact relationship, and the employee form only for employment or applicant data.

Will a CoreLogic opt-out remove public property records?

Not automatically. Public or regulated source records can remain, and a correction may need to go to the source agency or product-specific dispute process.

What can Cotality ask for to verify me?

Its notice says it may request a name, email, phone number, mailing address, or additional information needed to match the request.

Can I appeal a denied Cotality privacy request?

Some state laws provide an appeal. The current notice publishes an appeal phone and email route; follow the response and the rules for your state.