Purpose
Can you explain why contact or context would be respectful and appropriate?
Frequently asked questions
How requests, privacy and consent are intended to work on MissToSee.
Practical guidance for making careful decisions before you publish or contact anyone.
You can look for a person from your past, ask for help identifying a place or memory, or create a space to preserve a human story. The service is not intended for surveillance, debt collection, legal service, background checks or finding someone who has asked not to be contacted.
No. Start with what you genuinely remember and mark uncertain details as approximate. Do not invent facts to make a request appear more complete.
MissToSee is for reconnecting with people you once knew, learning about someone you remember, rediscovering meaningful places and preserving unfinished stories. It is not an investigation, emergency-response or official reporting service.
No. Contact details are kept out of public requests. Messages are intended to be relayed through protected channels until both people consent to direct contact.
You choose a visibility level: private draft, trusted invitation, or reviewed community request. Sensitive requests may require extra review or may not qualify for public visibility.
Yes. The product is designed to let you archive or remove requests and request account deletion, subject to limited retention needed for security, fraud prevention and legal obligations.
No. A lead is only a possibility. Names, places and memories can overlap. Users should review context carefully and avoid making public claims about identity.
A protected message can be offered to the person. Direct contact details are shared only after both sides choose to proceed.
The request must stop. A person can decline, block future messages and ask to disappear from discovery. Consent can also be withdrawn later.
Use the report control attached to a request, lead or message. Categories should include impersonation, harassment, unsafe personal data, fraud, threats and concerns involving a minor or vulnerable person.
They require stricter safeguards and may be limited to verified parents, guardians or appropriate official organizations. Public identifying information about a minor should never be posted casually.
Yes. Requests may be limited or removed when they create privacy or safety risks, violate the Terms, appear deceptive, or cannot be handled responsibly.
Before you publish
Use this short review to make a request safer, clearer and more likely to receive useful help.
Can you explain why contact or context would be respectful and appropriate?
Do you have the right to share each photograph, recording and personal detail?
Have you removed addresses, phone numbers, documents and live-location clues?
Have you clearly marked remembered details that may be incomplete or approximate?
Still exploring?