Searchbug: data broker profile and opt-out route
This record explains how to contact Searchbug, what the catalog currently records about its request workflow, what information may be needed to match a record, and what evidence to keep. It is a source-backed routing reference—not proof that Searchbug accepted, processed, or completed a request.
Quick answer
To request removal from Searchbug, use the recorded provider route at searchbug.com ↗. The catalog currently records Both as the request method, an estimated processing time of Not stated; verify any response timeline with Searchbug, and latest evidence dated 2026-08-13.
Searchbug at a glance
- Domain
- searchbug.com
- Request method
- Both
- Catalog difficulty
- 4/5
- Processing estimate
- Not stated; verify any response timeline with Searchbug
- Standard ID flag
- Not flagged in standard workflow
- Country scope
- US
- Evidence grade
- First-party route checked
- Evidence status
- Current route evidence recorded
- Independent route observation
- URL route observed
- Read-only semantic disposition
- Not recorded
- Legal operator
- Not recorded
- Parent entity
- Not recorded
- Catalog lifecycle
- Active Catalog Record
- Lifecycle status
- Active Catalog Record
- Registry matches
- None recorded
- Evidence conflicts
- None recorded
- Recorded data domains
- marketing audience, data aggregation, demographics, household data
- Source checked
- 2026-08-13
- Entity reviewed
- 2026-08-12
- Next route review
- 2026-09-27
How to use this Searchbug opt-out record
- 1
Open the provider route and confirm that it matches Searchbug and the type of record you want to address.
- 2
Prepare only the matching information the provider asks for. The catalog records required fields as Information Requested By Searchbug'S CCPA Form, Information Sufficient To Identify The Subject Of The Request.
- 3
Review the request, submit it yourself, save any confirmation, and re-check the source listing after the provider window. A prepared draft is not a completed deletion.
Recorded workflow details
Request types
- Opt Out Sale Or Sharing
- Delete Personal Information
- Access Or Copy Personal Information
- Protected Individual Deletion Request
Submission channels
- Opt Out Web Form
- Privacy Email
- Telephone
- Postal Mail
Required fields
- Information Requested By Searchbug'S CCPA Form
- Information Sufficient To Identify The Subject Of The Request
Optional or contextual fields
- First And Last Name
- Email Address
- Phone Number
- Street Address, City, State, And ZIP Code
- Protected-Person Documentation When Claiming A Protected Status
Extra steps
- The California Attorney General Registry Lists Searchbug As A Data Broker And Identifies The CCPA Form As Its Consumer Request Route.
- The Registry Says Searchbug Does Not Maintain Consumer Data For Sale But Will Block Requests For Information When Applicable; Keep The Customer Copy Scoped To Blocking Or Deletion Requests, Not A Guaranteed Database Purge.
- The Live Searchbug Page Was Not Retrievable In This Browser Pass, So The Route Should Be Rechecked Before Sending A Later Request.
Completion evidence to keep
- Opt Out Form Confirmation
- Email Or Broker Response
- Future Searchbug Route Or Record Recheck
What this record is associated with
The catalog and matched registry evidence associate this provider with the following data domains:
- marketing audience
- data aggregation
- demographics
- household data
These labels describe documented business or registry context. They do not prove that a particular person has a profile or that every listed domain uses the same request route.
Registry-declared data and regulatory signals
Data signals
Not recorded in matched registry rows.
Published sharing context
No positive sharing flag recorded.
Regulated contexts
No positive regulated-context flag recorded.
These are provider or registry declarations where available. They describe collection or business context; they do not prove that a particular person appears in the database or that removal will affect every downstream recipient.
Identity and verification boundary
Provider-specific expectation: The California registry directs consumers to Searchbug's CCPA form; the exact current verification and data-minimization instructions must be followed on that form.
Government-ID expectation: The registry describes supporting documentation for protected-individual requests, but does not establish a universal government-ID requirement for ordinary opt-out requests.
Do not attach a government ID or other sensitive document unless the provider's current instructions require it for the request you are making. Redact unnecessary fields where the provider allows it.
Legal entity and registry context
No matched government-registry profile is recorded for this catalog entry yet. Treat the provider name and route as source-backed catalog data, not as a confirmed legal-entity relationship.
Evidence, freshness, and limitations
Evidence grade: First-party route checked. Useful evidence: this record tracks 71/258 tracked fields across 90 evidence facts. Current route checked 2026-08-13. Next route recheck due 2026-09-27.
The source links below support the recorded route and workflow fields. A source page, HTTP response, registry row, or email address does not prove that a provider accepted a request, deleted data, or will not republish it.
Source ledger
| Evidence type | Source | Observed/checked |
|---|---|---|
| catalog route | https://www.searchbug.com/ccpa.aspx ↗ | 2026-08-13 |
| provider-published workflow source | https://oag.ca.gov/node/186690 ↗ | 2026-08-12 |
| provider-published workflow source | https://www.searchbug.com/ccpa.aspx#DoNoSell ↗ | 2026-08-12 |
Evidence label: Official Registry Confirmed First Party Route Recheck Needed. Source checked: 2026-08-13.
Latest web route observation: 2026-08-13 · reachable · HTTP/status 403 · final URL https://www.searchbug.com/ccpa.aspx.
Latest independent provider URL observation: 2026-08-13 · reachable · HTTP/status 403 · final URL https://www.searchbug.com/ccpa.aspx · observed URL https://www.searchbug.com/ccpa.aspx. This is a read-only observation of a provider-published URL; it does not by itself establish canonical route semantics, form submission, request acceptance, or deletion.
Latest email-domain observation: 2026-08-13 · DNS reachable · searchbug.zohodesk.com. Mailbox acceptance was not tested.
What is still unknown in this snapshot
This profile is intentionally explicit about its limits. “Not recorded” means no source-backed value is present in this snapshot; it does not mean the provider lacks the information.
Missing or unknown tracked fields (3 total):
- Aliases
- Parent Entity
- Suppression Group
Next evidence actions:
- Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.
- Classify the broker's products, data types, use cases, and operating scope from first-party or regulator evidence.
- Match regulator records to the legal entity and preserve jurisdiction-specific scope, collection, sharing, and request-metric evidence.
Incomplete evidence dimensions: Entity, Business, Regulatory, Workflow, Route, Privacy, Verification, Catalog, Provenance.
Evidence completeness by dimension
| Dimension | Documented | Coverage | Status |
|---|---|---|---|
| catalog metadata | 6/14 fields | 42.9% | partial |
| contact routes | 16/22 fields | 72.7% | partial |
| data categories | 2/32 fields | 6.3% | partial |
| entity identity | 4/20 fields | 20.0% | partial |
| privacy risk | 5/28 fields | 17.9% | partial |
| registry profile | 0/39 fields | 0.0% | missing |
| request workflow | 11/41 fields | 26.8% | partial |
| route checks | 12/38 fields | 31.6% | partial |
| source provenance | 15/24 fields | 62.5% | partial |
Coverage is the share of tracked fields with a recorded value in this evidence snapshot. It is not a quality score, removal rate, or proof that unrecorded information does not exist.
Related Marketing & Audience Data profiles
These records are grouped with Searchbug under the same catalog category. The grouping is for discovery; it does not establish common ownership, shared suppression, or a shared request outcome.
- 01Advertising Inc
01advertising.com
Current route evidence recorded
- 180 by Two, LLC
180bytwo.com
First-party request-route candidate; manual review required
- 33 Mile Radius LLC
33mileradius.com
First-party request-route candidate; manual review required
- 360 Media Direct
360mediadirect.com
Current route evidence recorded
- 365DataSolutions, LLC
365datasolutions.com
Current route evidence recorded
- 4EYES AI Inc
4-eyes.ai
Ambiguous page observed; submission route not confirmed
Searchbug opt-out FAQ
How do I opt out of Searchbug?
Use the provider route at https://www.searchbug.com/ccpa.aspx. Review the fields and verification steps before submitting. A reachable page does not prove that the provider accepted or completed a request.
Does Searchbug require government ID?
The registry describes supporting documentation for protected-individual requests, but does not establish a universal government-ID requirement for ordinary opt-out requests.
How long does Searchbug take to process an opt-out?
The catalog estimate is Not stated; verify any response timeline with Searchbug. This is an estimate, not an SLA or proof of deletion. Check the provider response and re-check the source listing yourself.
What is still unverified about Searchbug?
This snapshot does not record source-backed values for Aliases, Parent Entity, Suppression Group. Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.