How to Opt Out of PublicRecordsNow (2026 Step-by-Step Guide)
Source-aware guide to reviewing a PublicRecordsNow listing, separating broker copies from court or government records, and preserving request evidence.
This guide treats PublicRecordsNow as a public-record-search target. Its home page is live, but the recorded opt-out URL currently redirects in a loop and the recorded privacy URL returns a 404 page. No current PublicRecordsNow removal route or privacy email is verified. A search result is not proof that every category described in an older article is present in your profile.
Do not submit personal information until a working first-party removal route is confirmed. Do not send a government ID, date of birth or other sensitive information to an old or unverified address.
Key takeaways
- Review the exact listing and save its URL before making a request.
- There is currently no verified PublicRecordsNow removal route or privacy email to use.
- Removing a broker listing does not seal, expunge, correct or delete the underlying court or government record.
- A dismissal, acquittal, sealing order or expungement has a different legal effect in different jurisdictions. Do not promise that a private broker must remove a record without checking the order, source and applicable law.
- A provider acknowledgment proves receipt. A provider response is the evidence for the scope actually addressed.
- Address other brokers separately if they publish the same record.
What a listing may contain
The live result—not this article—would control what PublicRecordsNow currently displays. A public-record search result may show a name, location, an event or filing reference, a case or record date, a disposition, or a link to another source. Because direct first-party inspection was unavailable, these are general possibilities rather than a PublicRecordsNow-specific inventory. Treat any match as potentially incomplete or misattributed until you compare it with the authoritative record.
Before submitting anything, check:
Tired of dealing with data exposure?
Choose relevant provider workflows, review the generated drafts in your browser, and send or submit each request yourself. Matching, eligibility, and provider requirements still need checking.
- the exact name and location;
- the date, case number or record identifier;
- whether the result says arrest, charge, filing, judgment, disposition or another status; and
- whether the source link points to a court or government record.
Do not repeat an allegation as a fact merely because it appears in a search result. A data broker may omit a dismissal, merge namesakes or present an old record without context.
Step-by-step removal workflow
1. Find the current first-party route
Open the PublicRecordsNow home page. The recorded opt-out URL currently redirects in a loop and does not expose a verified request form. The recorded privacy URL returns a 404 page. No current PublicRecordsNow removal route or privacy email is verified, so do not submit personal information until a working first-party route is confirmed.
2. Capture the record evidence
Save the exact profile URL, result title, date, location and any case or record identifier. Keep a private screenshot or PDF if it is safe to do so. Do not publish the screenshot or include unnecessary personal information in analytics or support tickets.
3. Submit only the matching details required
There is currently no verified PublicRecordsNow removal form or privacy email to submit. Do not send personal information to the recorded opt-out or privacy URLs or to an old address copied from another source.
If a working first-party route becomes available, read its purpose, retention and secure-upload instructions before providing identity documentation. Do not email a full government ID to an unverified address.
4. Save the acknowledgment
There is currently no verified PublicRecordsNow request workflow or acknowledgment to save. If a working first-party route becomes available, keep the submission date, URL, request type, confirmation number and any email-verification step.
5. Recheck the same listing
Do not submit a request through an unverified route. If a working first-party route becomes available, use its stated response window and recheck the exact URL. For an old Google result whose source page no longer exists or has changed significantly, use Google's Refresh Outdated Content tool separately.
Court and government records are separate layers
Removing a PublicRecordsNow result does not change the source record. If the information is wrong, contact the agency or court that created the record and follow its correction process. If a record is sealed or expunged, obtain the order and ask the source agency what access restriction applies. Then give the relevant broker a precise request with the order only through a verified secure channel.
The legal effect of an expungement, sealing order, dismissal or acquittal varies by jurisdiction and record type. Some orders restrict a source database without compelling every private publisher to erase an old copy; other laws or orders may impose additional duties. A lawyer or the issuing court can explain the effect for your facts.
Privacy-law requests
Some residents have access, deletion, correction or sale/sharing rights under a state, national or regional privacy law. Eligibility depends on location, business, processing purpose, thresholds, exemptions and identity verification. California residents can begin with the California Attorney General's CCPA guidance and current CPPA data-broker guidance. Do not assume a California right applies to every resident or every record.
If you use a statutory request, identify the law and request type that actually fit your facts. Do not copy a 45-day deadline, universal exemption or legal conclusion from an old template without checking the current official source.
If the provider does not respond
Keep the original request and confirmation. Then:
- follow up through the published privacy or support route;
- ask which product, record and processing purpose were addressed;
- correct a matching problem without volunteering unnecessary data;
- use the relevant regulator or court process only if the law and facts fit; and
- submit separate requests to other sites that still publish the record.
Do not threaten a complaint or claim a legal violation unless you have checked the current law, the provider's role and the exact record.
What a removal response does—and does not—prove
| Evidence | It supports | It does not prove |
|---|---|---|
| Submission receipt | A request was sent | Removal is complete |
| Profile no longer loads | The checked result is unavailable at that time | Source-record deletion or downstream deletion |
| Provider confirmation | The provider addressed the stated scope | Every affiliated or independent site changed |
| Court or agency order | The order has the stated legal effect | Every private database received or followed it |
Frequently asked questions
How long does PublicRecordsNow take?
The current provider route should control. No verified provider-published SLA is presented here. Keep the receipt and use the provider's own response language rather than relying on a fixed three-to-seven-business-day promise.
Does removal delete my court record?
No. A provider-page request, if available and accepted, addresses only the provider's copy; it does not itself alter the court or government source. Source availability depends on the custodian's record and applicable law.
Does a dismissal or acquittal guarantee removal?
No. A dismissal or acquittal does not have one universal publication or deletion effect. Whether a record remains available, can be sealed or expunged, or should be corrected depends on the jurisdiction, record type, order and agency procedure. Do not assume expungement is the only route.
Does this remove the result from Google?
Not automatically. There is currently no verified PublicRecordsNow removal route or privacy email. For a Google result whose source page no longer exists or has changed significantly, sign in to a Google account and use the Refresh Outdated Content tool; this is separate from removing a source page or underlying record.
Should I send an expungement order?
Only through a verified provider route that explains why it is needed and how it is protected. Keep the original order private and send only the relevant pages if the provider permits redaction.
OfflistMe workflow boundary
OfflistMe can prepare reviewable request drafts for catalog entries. You review the matching evidence, choose what to submit and send the request from your own channel. A catalog workflow is not proof that PublicRecordsNow has your information, that a statutory right applies, or that a provider will complete a request.
Review data brokers in the OfflistMe directory.
Sources and limits
Source status rechecked October 9, 2026:
- PublicRecordsNow home page, recorded opt-out pointer and recorded privacy pointer — the home page is live; the recorded opt-out URL redirects in a loop and the recorded privacy URL returns a 404 page. No current PublicRecordsNow removal route or privacy email is verified.
- FTC: What to know about people-search sites — supports general people-search source, opt-out, public-record, related-listing and reappearance limits, not a PublicRecordsNow-specific inventory.
- California Attorney General: CCPA guidance — supports jurisdiction-specific CCPA rights, public-record exclusions and request boundaries; it does not establish that PublicRecordsNow is a covered business or that a particular request will be accepted.
- California Privacy Protection Agency: Data Broker Registry and DROP guidance — current California data-broker and DROP context. The registry page was last updated July 29, 2026 and currently displays zero 2026 registered brokers to the verifier; that display does not establish that PublicRecordsNow is an active covered broker or participates in the California mechanism.
- Google Search Help: Refresh Outdated Content — Search-result handling is separate from changing a provider page or source record.
- OfflistMe Privacy Policy — describes OfflistMe's browser-local request-drafting boundary, not provider effectiveness.
No PublicRecordsNow request should be submitted until a working first-party route is confirmed. The provider home, recorded opt-out pointer and recorded privacy pointer were not retrievable in this pass, so the previously recorded redirect-loop and 404 observations remain access-limited historical observations rather than a newly confirmed live state. Opt out of other sites separately if they publish the same record.
Related guides
Understand your privacy rights
Where a privacy right is relevant, these plain-English explainers show what each law covers and what to verify before making a request.
Related Data Broker Removal Guides
Take back your privacy today
Review provider-specific routes, prepare your requests locally, and send or submit each one yourself.
Review Provider RoutesFree to review provider routes · Optional one-time unlock from $9.00 · No subscription