gone.bot

California DROP

Official sources

Supported goals

Channels and required capabilities

Minimum known fields

The live portal determines the required fields. California’s program information says that a resident verifies identity through California Identity Gateway and chooses what data to provide. Do not pre-collect identity data outside that portal.

Procedure

  1. Confirm that the user is requesting action for themself and says they are a California resident.
  2. Open the official request portal and let the user complete identity verification directly.
  3. Explain the choices shown by the portal without making an eligibility or legal determination.
  4. Stop before final submission and ask the user to review the live request.
  5. After the user submits, record only the date, status, and non-secret reference they choose to retain.

California queue overlap

After a user submits DROP, do not immediately queue separate direct deletion requests to Data Axle, Acxiom, or Epsilon. DROP applies to all current and future active DROP data brokers unless the user narrows their request; wait for the broker-specific DROP status before treating a direct deletion form as necessary. The list and status displayed in the user’s DROP account are authoritative for a particular company.

Keep these as separate, non-duplicate cases when the user wants their distinct result:

Defer Cotality’s direct privacy route until DROP reports a status or the user identifies a separate need. Its property/public or consumer-reporting data can be outside DROP’s deletion scope or legally exempt.

Manual checkpoints

Evidence and status interpretation

A portal confirmation means only that DROP accepted the request. Broker processing and deletion are later states. Do not claim that a broker held the user’s data or completed deletion without evidence from the official process.

Limitations