Practical answers for meaningful memories

MissToSee is a place to organize memories about people, places and family stories. Begin with the context you remember and decide what you want to understand. It is not an identity-verification, investigation or emergency service.

Choose a person when your memory concerns someone you knew, a place when a photograph or location needs context, and a story when you want to record an experience. You can describe uncertainty without forcing your memory into a definite answer.

Gather an approximate year, a general place, the shared setting and one or two distinctive details. Separate first-hand memories from things you heard later. Leave out phone numbers, private addresses, identity documents and unrelated personal information.

Yes. A school, workplace, event, nickname or approximate period can give a memory useful context. Say “around 1998” or “possibly a school trip” when that is all you remember; do not turn a guess into a fact.

Use a short title describing the context, such as “A classmate from a school trip in the late 1990s.” A clear setting helps a reader understand your request. Avoid personal contact details and sensational claims in the title.

No. A useful outcome may be a better timeline, an identified location or a preserved story. Some clues remain inconclusive, and another person may choose not to reconnect. Treat every possible connection as unconfirmed until supported.

Write down where and roughly when you knew each other, what you shared and why you want to reconnect. Begin with information you already know. Avoid publishing current addresses, employer details or private contact information about someone else.

A shared school, course, team, neighborhood or event can distinguish one memory from many people with similar names. Include only relevant details, and keep sensitive family, health or financial information out of the request.

Record the name or nickname you knew at the time and the period when you knew it. Names can change and spellings can differ across languages. A name similarity is a clue, not proof that two records concern the same person.

Do not use a memory request to evade a refusal, block or boundary. Respect a person’s decision to remain unreachable. You can preserve your own account privately without seeking contact or exposing information about them.

No. If someone may be in immediate danger, contact the appropriate local emergency services or official reporting authority. A memory platform is not a substitute for urgent assistance or an official missing-person process.

Automatic matching and end-to-end delivery of messages between two people are not yet completed. Creating or saving a request does not mean an identity search has run or a message has reached another person.

It may be. Clothing, signs, objects, buildings and the setting can remain helpful even when a face is unclear. Keep an untouched original and make a separate copy for cropping or annotation. A damaged image may also leave important details uncertain.

Look for readable signs, uniforms, event decorations, buildings, transport and objects that suggest a period. Record where the image came from and what is written on the back. Distinguish visible evidence from your interpretation of it.

No. Similarity can be misleading, especially in low-resolution or old photographs. Seek independent context such as a shared event or a known date. Do not label an unknown person publicly on the basis of resemblance alone.

Keep the original privately and use a copy containing only the details relevant to your question. Crop private documents, addresses or unrelated people when appropriate. Review the image and any embedded location metadata before sharing it.

The current private upload route accepts JPG, PNG, WebP and PDF files, with a 10 MB limit per file. Public support attachments have a separate limit of three JPG, PNG or WebP images, up to 6 MB each. A file being accepted does not verify the information inside it.

Enhancement may make some existing details easier to see, but it can also introduce invented details. Preserve the original and label edited copies. Do not treat an enhanced face, sign or number as independent evidence.

Sometimes. Architecture, road layout, signage, landscape and the position of landmarks can help narrow a location. Start with a broad region and compare several visible features. If the evidence remains weak, keep the location tentative.

Note signs and their language, building materials, street furniture, mountains, coastlines, transport and landmarks. Approximate time of day or season may add context. Do not infer a precise address from one small detail.

Compare the image with material from the likely period, rather than only current views. A shop may have closed or a road may have been rebuilt. Keep a record of which features agree and which ones do not.

Look for agreement across independent features: a landmark, the street arrangement, a sign and the likely date. Keep the source of each comparison. One similar building or a confident suggestion is not enough to establish a location.

Check metadata before sharing a photograph because it may reveal a private location or device details. Record useful context privately, then share only what is needed. Avoid exposing a home address or another person’s movements.

No. These guides concern remembered places and historical context. Do not use them to locate a person’s current home, routine or live movements. A remembered place does not establish where a person is today.

Start with one photograph, event or remembered phrase. Record who is telling the story, when the account was recorded and the approximate time and place of the event. A small, well-described account is more useful than a long narrative with no context.

Ask open questions: “What do you remember about this day?”, “Who was there?” and “What happened next?” Let the narrator choose what to discuss. Avoid suggesting an answer or pressuring someone to revisit a difficult experience.

Mark what the narrator recalls, what a document supports and what remains uncertain. Record the source and date of each addition. A first-hand account matters, but it may still contain incomplete dates or conflicting details.

Keep the separate accounts and identify who contributed each one, with their permission. Note the disagreement rather than merging it into a single certainty. Differences in viewpoint can be part of the historical context.

Contributor records can be organized in the workspace, but automatic contributor email invitations are not yet completed. Do not assume that adding an email address sends an invitation or grants someone access to your story.

Keep original photographs and documents, use descriptive filenames and maintain another copy in a location you control. Record permission and source information alongside each item. Do not assume that saving a story on a website replaces your own backup.

No. The guides and frequently asked questions are public. An account is needed to use the private workspace and save requests or upload files. Use the Account link in the header to reach the sign-in and registration page.

The draft is associated with your account on the server. Its title, memory and supporting files help you organize your starting point. Saving a draft does not publish it as a public search result or prove that a matching process has run.

Private is the recommended starting point. Other visibility labels describe an intended audience, but invitation and community distribution workflows are not fully completed. Selecting a label is not evidence that another person has received access or an invitation.

Use the password-recovery option on the account page. When a valid reset link is used, existing sessions and outstanding reset links are invalidated. Check your spam folder if an email is expected; external mail delivery still requires end-to-end verification.

Use Contact us or Report an issue in the footer. Describe the page, what happened and the relevant request reference. Provide only necessary details. Do not send passwords, full identity documents or another person’s private information in a support message.

Automatic matching, delivery of messages between two people and contributor email invitations remain in development. Full Google sign-in and delivery to an external email inbox still need end-to-end verification. The guides explain a careful approach; they do not guarantee an outcome or replace these checks.