Know who can see what
Every request should show its current audience and warn before a visibility change.
Trust center
Last updated: 11 September 2026
Understand what information the service may use, what stays private, and the controls available to you.
Privacy controls
Production controls should make visibility, retention and contact choices visible before a user commits.
Every request should show its current audience and warn before a visibility change.
Automated tools may organize clues or surface possibilities, but should not confirm identity or override consent.
Drafts, verification materials, reports and messages need separate documented retention periods.
The current demonstration does not transmit or store form entries. This policy describes the intended production service and must be reviewed for the operating company and applicable law before launch.
MissToSee is designed to help people reconnect without making private contact information public. We aim to collect only information needed to operate, protect and improve the service. Visibility and contact are controlled by the user, and a possible lead never automatically reveals an identity or address.
Name, email address, authentication details, language, region and account preferences.
Text, approximate dates, photographs, audio, places and other context you choose to provide. You should share only information you are permitted to use.
Reports, moderation decisions and, when a sensitive feature requires it, verification status. Verification documents should be processed with restricted access and deleted when no longer needed.
Device, browser, approximate region, timestamps, security events and limited usage data used to prevent abuse and maintain reliability.
We do not intend to sell personal information. Information may be shared with service providers acting under contract, with people you intentionally invite, when you approve a connection, or when required to protect people, comply with law or respond to valid legal process. Public-facing content is limited by the visibility choice and safety review.
You can change request visibility, withdraw a contact invitation, block users, report content, and ask to access, correct or delete account information. Rights vary by jurisdiction and may include objection, restriction, portability or appeal of certain decisions.
Production safeguards should include encryption in transit, controlled administrative access, monitoring, rate limits and separation of public content from contact details. Information should be retained only as long as needed for the stated purpose, security, dispute resolution and legal compliance.
General accounts are intended for adults. Requests involving minors or vulnerable people require additional rules, limited visibility and, where appropriate, verified authority from a parent, guardian or recognized organization.
Information may be processed in countries with different data-protection laws. Before production launch, the operator should document hosting locations, safeguards and regional rights.
Material changes should be explained before they take effect. The final production policy will identify the legal operator, physical address, privacy contact and regional representative where required.