Privacy resources · product boundary
A report can open the file. It cannot close every tab.
Rookveil’s free report is a bounded lead-finding snapshot. It can help you decide what to verify and which source-specific next step to consider—but it is not an internet-wide inventory, legal opinion, identity proof, or guarantee of discovery or removal.
The short version
01 / Automated scan scope
Visibility with edges.
The clues you choose—such as a name, broad region, username, or public profile URL— shape what a report can look for. Supported public sources may surface profiles, directory or people-search listings, repeated handles, and breach-adjacent context.
Not an inventory. The free report does not inspect every page, database, private account, or future publication on the internet.
Not identity proof. A name, handle, photo, or location can belong to someone else or be inferred from incomplete data.
Not legal advice. A lead does not decide whether a privacy right, deadline, or exception applies to you.
02 / Coverage and jurisdiction
One source is one source.
Rookveil works within supported sources and their own request processes. Coverage is intentionally narrower than the public internet, and legal coverage is not a promise that a particular country, state, or source will accept your request.
Use the exact URL and source name when you follow up. The data sources directory provides official opt-out links and source-specific guidance where available.
Read the US state privacy guide and the GDPR, LGPD, and PIPEDA guide for documented context. Regions outside the currently documented US and international scope are not yet promised. A qualified local adviser or authority can help with a situation-specific question.
03 / Removal semantics
Status is not disappearance.
“Verified removal” is deliberately narrow: a later check of the specific target source or URL shows that the relevant listing is no longer available, with the check date and source context recorded.
Even a verified source disappearance does not prove the information is gone from other brokers, records, caches, search indexes, screenshots, or future copies.
04 / If a removal is not honored
Keep the record. Escalate carefully.
A source may deny, delay, ignore, or reverse a request. That is a source outcome—not a reason to erase your own evidence or repeatedly expose the original page.
- 1
Preserve both versions
Keep the original evidence and the current response or page state. Record the timestamp, exact URL, source name, request details, and any case or reference number.
- 2
Re-check the exact source
Open the precise listing or URL again, preferably from a safe account and device. A different result on a cached, search, or copied page is not the same source outcome.
- 3
Use the official next channel
Follow the source’s appeal, escalation, or privacy-request process. Observe any applicable deadlines and keep a copy of what you submit.
- 4
Get the right help
Contact Rookveil for workflow help, and seek a qualified local adviser or authority when the question turns on legal rights, jurisdiction, or urgent risk.
If someone is threatening you, publishing sensitive live-location information, or you face imminent danger, get to a safer place and contact local emergency services or a trusted safety professional. Rookveil is not an emergency response service.
05 / Practical safety playbooks
Make the next move safer.
These are general safety steps, not a substitute for local emergency, legal, or specialist support. Start with the risk in front of you and share the minimum necessary details.
- 1. Get safe. Move away from a known risk and tell someone you trust.
- 2. Don’t engage. Avoid replying to, threatening, or negotiating with the poster.
- 3. Preserve evidence. Capture URLs, timestamps, screenshots, and platform identifiers.
- 4. Report and escalate. Use the platform’s safety channel and contact local authorities when appropriate.
- 1. Change unique passwords. Use a password manager; prefer passkeys or strong MFA.
- 2. End unknown sessions. Review signed-in devices, recovery email, phone, and active app access.
- 3. Tighten privacy. Review public profiles, location sharing, and discoverability settings.
- 4. Protect the carrier layer. Add an account PIN or port-out protection where your carrier offers it.
- 1. Add timestamps. Note when you saw it and when each capture was made.
- 2. Save exact URLs. Include usernames, post IDs, and source context when visible.
- 3. Export carefully. Keep original files and screenshots in a secure, access-controlled location.
- 4. Minimize redistribution. Share only with the platform, an adviser, or an authority that needs it.
Use this page as a checkpoint
Good privacy work stays specific.
Return to the resource library, review the FAQ, browse source-specific guidance, or contact Rookveil with a workflow question.
This page is general information for safety and planning. It is not legal advice, security advice, identity verification, emergency response, or a promise of discovery, removal, monitoring, or coverage in every jurisdiction.