Public Data Only
Searches target publicly accessible profiles and account details.
Privacy and Security
This page explains, in plain language, what ProfileTrace does, what it does not do, and how search data is handled.
Dating-app safety checks follow the same boundary: public-profile signals only.
Reviewing public identity risk for a team? Compare credit packs before running repeated checks.
At A Glance
No Private Access
ProfileTrace does not bypass private-account controls.
Purpose-Limited Use
Use results for verification, safety review, and public-footprint cleanup.
Transparent Controls
Policy, terms, and contact channels are publicly available.
Data Handling Summary
| Topic | How ProfileTrace Handles It |
|---|---|
| Data source scope | Publicly accessible web sources and profile details only. |
| Private content access | Not supported. Private, deleted, or restricted content is excluded. |
| Search result usage | Used to generate user-visible results, reports, and follow-up actions. |
| Retention and deletion | Retention windows and deletion details follow the Privacy Policy and Terms. |
| Security controls | Transport protection, access controls, monitoring, and incident response processes. |
| Sensitive use cases | Users are responsible for lawful and policy-compliant usage in their jurisdiction. |
For teams
Use credits when public checks become operational
The privacy boundary does not change with volume: ProfileTrace still checks public profile URLs and visible metadata only. Credits are useful when a creator team, support team, or small business needs repeated username checks, wider platform sweeps, or report-ready follow-through.
- Start free when you only need one exact-handle search.
- Use paid credits when the same incident needs more platforms or repeated monitoring.
- Keep exported findings inside your own access-control and retention process.
Best Practices For Safe Use
- Use precise usernames and known aliases to reduce false positives.
- For dating-app checks, search only public handles or clues the match volunteered.
- Treat profile matches as clues and verify context before decisions or reports.
- Store exported findings according to your own security policy.
- For hiring, legal-sensitive, or regulated use, follow your own compliance framework.
Need Clarification?
If you need policy-level details, contact us and reference your use case.