Contact

The fastest route is email: support@whereisthisplace.world. We are a small team, so we cannot offer live chat or phone support, but every message is read and most get a reply within two business days.

For time-sensitive bug reports, put 'BUG' in the subject line and include: the page URL, the browser you used, what you expected and what happened. For privacy questions, put 'PRIVACY' in the subject — those are prioritised.

Bug reports: the tool name (location finder, metadata viewer, date finder or remover), the file format and size if a photo was involved, and the exact wording of any error message. Please do not attach photos of identifiable private individuals — describe the scene instead.

Translation feedback: name the language and quote the phrase that reads oddly. Our six locales — English, French, German, Spanish, Japanese and Korean — are maintained by humans, and corrections are genuinely welcome.

Privacy requests: state what you are asking for (for example, deletion of an analytics event class) and how the request relates to your use of the site. Note that the local tools never send us your files in the first place.

We do not locate people, investigate individuals or analyse photos of private persons on request — the tools exist for your own photos and lawful, legitimate questions. Requests to identify a person, a home address or private property from a photo will be declined.

We also cannot restore metadata that a platform already stripped, guarantee the accuracy of AI estimates for legal proceedings, or provide data-processing agreements for the local browser tools, which process nothing server-side.

Bug reports and privacy matters: within two business days. Translation corrections and feature suggestions: within a week, batched. Partnership and API questions: best effort — we read everything, but we answer selectively to keep the tools free.

Before writing, it is worth checking the FAQ sections on each tool page and the guide — roughly half of all questions we receive are answered there, usually with more detail than a mail reply can offer.

Tool bugs and error states: if a tool shows an error code or behaves unexpectedly, we want the exact message and the steps that triggered it. Include the browser and operating system; never include photos of private individuals. If a reply has not arrived after three business days, check the spam folder and write again with the same subject line so the thread stays together.

Privacy questions and requests: questions about what the AI path transmits, requests related to server logs, or objections under GDPR/CCPA-style frameworks. These are prioritised and answered within two business days.

Translation corrections: quote the language and the phrase that reads oddly. Localization is maintained by humans and improves exactly this way.

Security reports: if you believe you found a vulnerability, write with details and a reproduction sketch. We credit honest reporters in release notes unless they prefer anonymity.

Partnership and API questions: best effort — we read everything and answer selectively, because keeping the tools free is the priority.

If the location finder returned no result, the photo most likely lacks both metadata and distinctive features — try a wider shot with signs or buildings. If the metadata viewer found nothing, the file almost certainly passed through a platform that strips EXIF. If the remover flagged an unverifiable clean, re-export the photo as plain JPEG and run it again.

Each tool page carries an FAQ that answers roughly half of all incoming mail in more detail than a reply could.

Messages are triaged once a day: privacy and security first, bugs second, everything else in arrival order. Replies come from support@whereisthisplace.world — check your spam folder if you expected an answer. We never ask for photos of private persons, passwords or payment details over email.

Privacy and security matters: within two business days, usually faster. Bug reports: within two business days with an acknowledgement and a ticket for anything reproducible. Translation corrections: batched weekly. Feature suggestions: read and prioritised monthly; you will not always get a reply, but you are shaping the roadmap. Bulk or automated requests may be ignored as abuse.

Write in any of our six site languages — English, French, German, Spanish, Japanese or Korean — and you will be answered in that language where possible. If you rely on accessibility features and hit a barrier (keyboard traps, contrast issues, unlabeled controls), describe the page and the assistive technology; accessibility reports are treated as bugs, not suggestions.

Wrong-looking AI results are usually regional ambiguity — a scene type that exists in many countries — and that context helps us more than the photo itself. Tell us the scene type (city street, coastline, interior), the region you believe is right, and which clue you think the estimate missed. We aggregate these reports to tune prompts and clue guidance; individual photos of private individuals are never requested and never stored.

We answer technical mail in plain language, without marketing padding, and we say 'we do not know' when we do not know. Feature requests are read as signals, not as tickets with delivery dates: the roadmap prioritises keeping the four existing tools fast, private and honest over adding new surfaces.

One request we consistently decline: asking us to run the AI analysis on a photo of a private individual and report where it was taken. Whatever the stated reason, that is person-tracking, and it is outside what this site will do — the same boundary is written into the Terms of Service.