CourtRecords.us: data broker profile and opt-out route
This record explains how to contact CourtRecords.us, 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 CourtRecords.us accepted, processed, or completed a request.
Quick answer
To request removal from CourtRecords.us, first verify the current request route because the latest read-only page observation is first-party request-route candidate; manual review required using privacy@courtrecords.us. The catalog currently records Email as the request method, an estimated processing time of 2-15 business days, and latest evidence dated 2026-08-13.
CourtRecords.us at a glance
- Domain
- courtrecords.us
- Request method
- Catalog difficulty
- 3/5
- Processing estimate
- 2-15 business days
- Standard ID flag
- Not flagged in standard workflow
- Country scope
- US
- Evidence grade
- First-party request-route candidate; manual review required
- Evidence status
- First-party request-route candidate; manual review required
- Independent route observation
- URL observed; semantics pending
- Read-only semantic disposition
- First-party request-route candidate; manual review required
- 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
- people search, public records, background screening, identity resolution
- Source checked
- 2026-08-13
- Entity reviewed
- 2026-08-10
- Next route review
- 2026-09-27
How to use this CourtRecords.us opt-out record
- 1
Open the provider route and confirm that it matches CourtRecords.us 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 First Name, Last Name, State, City When Needed To Locate The Record, For Covered-Person Email Requests: Complete Name, Residence, Email, And Covered-Person Status.
- 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 Account Or Personal Data
- Access Or Download Data
- Correct Personal Data
- Object Or Restrict Processing
Submission channels
- Opt Out Form
- Privacy Email
Required fields
- First Name
- Last Name
- State
- City When Needed To Locate The Record
- For Covered-Person Email Requests: Complete Name, Residence, Email, And Covered-Person Status
Optional or contextual fields
Not recorded in this workflow snapshot.
Extra steps
- Use The Public Opt-Out Form To Find The Record And Request Removal.
- Covered Persons Under The Daniel Anderl Judicial Security And Privacy Act Should Email Privacy@Courtrecords.Us With The Subject ‘Attention Covered Person Removal Request’.
- The Site Is Not The Original Public-Record Source, So Removal From CourtRecords.Us Does Not Remove The Government Record Itself.
Completion evidence to keep
- Form Confirmation
- Email Confirmation
- Listing Recheck
- Source Recheck
What this record is associated with
The catalog and matched registry evidence associate this provider with the following data domains:
- people search
- public records
- background screening
- identity resolution
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: CourtRecords.us says it may ask additional questions to confirm information associated with the requester; the cited form does not require government ID for the ordinary opt-out path.
Government-ID expectation: not_requested_on_current_form
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 request-route candidate; manual review required. Useful evidence: this record tracks 59/258 tracked fields across 63 evidence facts. First-party request-route candidate; manual review required (date not recorded). 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 |
|---|---|---|
| provider-published workflow source | https://courtrecords.us/optout/ ↗ | 2026-08-10 |
| provider-published workflow source | https://courtrecords.us/privacy/ ↗ | 2026-08-10 |
| read-only observation · First-party request-route candidate; manual review required | https://courtrecords.us/privacy/ ↗ | 2026-08-13 |
Evidence label: Official Source Confirmed. Source checked: 2026-08-13.
Latest independent provider URL observation: 2026-08-11 · reachable · HTTP/status 200 · final URL https://courtrecords.us/privacy/ · observed URL https://courtrecords.us/privacy/. 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.
Read-only semantic disposition: First-party request-route candidate; manual review required. Observed 2026-08-13 · final URL https://courtrecords.us/privacy/.
Next evidence action: Confirm that the page accepts the relevant request type and belongs to the recorded provider before relying on it.
This is a bounded page observation. It does not prove entity identity, route ownership, request delivery, acceptance, or deletion.
Latest email-domain observation: 2026-08-11 · DNS reachable · courtrecords.us. 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 (4 total):
- Optional Or Contextual Fields
- 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 | 7/14 fields | 50.0% | partial |
| contact routes | 8/22 fields | 36.4% | 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 | 9/41 fields | 21.9% | partial |
| route checks | 9/38 fields | 23.7% | 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 People Search & Public Records profiles
These records are grouped with CourtRecords.us under the same catalog category. The grouping is for discovery; it does not establish common ownership, shared suppression, or a shared request outcome.
- ACH, Address Clearing House
achcoop.com
First-party request-route candidate; manual review required
- AddressSearch
addresssearch.com
Current route evidence recorded
- AdvancedBackgroundChecks
advancedbackgroundchecks.com
Current route evidence recorded
- Aristotle International, Inc.
aristotle.com
Current route evidence recorded
- Asset International, Inc
issmarketintelligence.com
Current route evidence recorded
- Backgroundchecks.com LLC
backgroundchecks.com
Privacy or consumer-rights context page; submission route not confirmed
CourtRecords.us opt-out FAQ
How do I opt out of CourtRecords.us?
Use the recorded privacy contact at privacy@courtrecords.us and keep a copy of what you sent. The catalog record was checked on 2026-08-13.
Does CourtRecords.us require government ID?
not_requested_on_current_form
How long does CourtRecords.us take to process an opt-out?
The catalog estimate is 2-15 business days. 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 CourtRecords.us?
This snapshot does not record source-backed values for Optional Or Contextual Fields, Aliases, Parent Entity, Suppression Group. Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.