Public Data Only
Searches target publicly accessible profiles and signals.
Privacy and Security
This page explains, in plain language, what ProfileTrace does, what it does not do, and how search data is handled.
At A Glance
No Private Access
ProfileTrace does not bypass private-account controls.
Purpose-Limited Use
Use results for safety, verification, and footprint management.
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 signals only. |
| Private content access | Not supported. Private, deleted, or restricted content is excluded. |
| Search result usage | Used to provide user-visible reports and follow-up workflows. |
| 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. |
Best Practices For Safe Use
- Use precise usernames and known aliases to reduce false positives.
- Treat profile matches as signals and verify context before decisions.
- Store exported findings according to your own security policy.
- For hiring and legal-sensitive use, follow your compliance framework.
Need Clarification?
If you need policy-level details, contact us and reference your use case.