California privacy choices

Do Not Sell or Share My Personal Information

Use the current manual intake path to submit a California privacy request. This page provides a request route without claiming that the site's legal applicability, automated fulfilment, Global Privacy Control or DROP workflows are complete.

  • No account required
  • Company details not required in privacy mode
  • Do not send sensitive identity documents initially
Request scope

Available request categories

California privacy rights depend on the business, information, request and applicable exceptions. Listing a request type here does not decide whether a particular record is covered, but it gives support a clear intake category.

Manual intake available

Opt out of sale or sharing

Ask that personal information associated with you not be sold or shared where the California opt-out right applies.

Verification workflow pending

Delete or suppress a record

Ask us to locate and delete or suppress covered information, subject to identity verification and any applicable exception.

Verification workflow pending

Know or access

Ask what personal information is associated with you and how it has been used or disclosed where this right applies.

Manual intake available

Correct information

Report inaccurate information and provide enough context to identify the field and record without sending unnecessary sensitive data.

Current manual process

Submit only the information needed to find your record

The current route reuses the support pipeline. It does not promise an automated acknowledgement, case number or completion deadline until those controls are implemented and verified.

  1. 1

    Open the privacy-mode contact form

    The dedicated link removes the company-name and company-website requirements from the existing support form.

  2. 2

    Choose a clear request subject

    Keep the prefilled California privacy subject or state whether the request concerns opt-out, deletion, access, correction or suppression.

  3. 3

    Provide only matching information

    Include your name, reply email, California residency and the email, phone, license or address needed to locate the relevant record.

  4. 4

    Wait for scoped verification

    Different rights can require different verification. Support should request only information reasonably needed for the specific request.

Do not send identity documents or sensitive account numbers in the first message.

Do not include passwords, Social Security numbers, payment-card details or an unredacted government ID. If verification is needed, support should explain the reason and use an approved secure method proportionate to the request.

Open request form
Browser privacy signal

Global Privacy Control is not yet verified here

California's official guidance says covered businesses that sell or share personal information must honor a valid Global Privacy Control signal as an opt-out request. The current repository does not contain a verified GPC detector, preference store or suppression integration.

California Attorney General: Global Privacy Control
Current limitations

What this frontend change does not solve

A visible request link is only the intake layer. Legal applicability, fulfilment operations and evidence still require owner, backend and counsel work.

  • No dedicated privacy-request backend, case identifier or consumer portal exists in this frontend repository.
  • A dedicated CARealEstateList privacy contact is not yet marked operational; the server-side recipient remains under migration review.
  • Receipt, verification, decision, completion time and downstream propagation are not automatically tracked or exposed to the requester.
  • Global Privacy Control detection and enforcement have not been verified in the current application.
  • California data-broker applicability, CPPA registration and DROP processing status remain pending qualified review and operational evidence.
Deferred backend specification

Controls required for an auditable privacy workflow

These requirements are documented now so the later backend work can reuse one approved contract instead of inferring behavior from the page design.

Pending backend

Request ledger

Create a case ID, request type, receipt date, jurisdiction, deadlines, status, decision reason and completion evidence.

Pending backend

Proportionate verification

Use separate rules for opt-out versus access, deletion or correction; isolate and delete verification-only data when required.

Pending backend

Identity and record matching

Match supplied identifiers across source records, active inventory, monthly releases, customer-support tools and permitted exceptions.

Pending backend

Suppression propagation

Prevent reintroduction and carry approved opt-out/deletion actions to future releases, service providers, contractors and recipients where required.

Pending backend

GPC handling

Detect and honor valid opt-out preference signals where applicable, with auditable scope across browser, account and linked identifiers.

Pending backend

DROP workflow

If the business is a qualifying data broker, implement recurring access, matching, deletion/opt-out results, downstream instructions and retained reports.

Current policy and official guidance

Review the source and ask for clarification

Read the current Privacy Policy and CCPA page, both visibly marked as under review. For general California rights information, use the official Attorney General resource.

Official CCPA guidance