Privacy policy

Our approach: data minimization

PersonFu surfaces information that is already public or lawfully licensed, and applies a field-level privacy policy engine before anything is displayed. We mask, hide, or route to human review based on risk, suppression status, and source-license permissions.

What we collect about searchers

• Account info (email, name) when you create an account.
• Search activity for history, support, and abuse prevention.
• Hashed IP and user-agent values — we do not store raw IPs for matching.
• Payment data is handled by Stripe; we do not store card numbers.

What we display about people in records

• City/state (not exact street addresses in previews).
• Age ranges (never full dates of birth).
• Masked contact clues in previews; full details only when lawfully sourced and permitted.
• Public usernames, web mentions, and professional/business signals.

We never include SSNs, full DOBs, credit scores, banking or medical data, precise real-time location, private credentials, breached passwords, minor profiles, or protected-class inferences.

Source provenance

Every displayed field carries a source category and a last-checked date. We do not expose raw source dumps or internal identifiers.

Your controls

• Opt out / request removal — easy to find, indexable, no account needed.
• Request corrections to inaccurate information.
• Protective suppression for safety cases.
• Appeal decisions to a human reviewer.
• Delete your account and associated data.

Retention

Generated reports are deleted after a defined retention window. We do not retain raw third-party payloads longer than needed unless a license and policy permit it.

Security

Encryption in transit and at rest for sensitive fields, hashed identifiers for matching, role-based admin access with required 2FA, audit logging of sensitive actions, and strict security headers.

Contact

Privacy questions: contact our team.