Where to write
One person reads all of these, so a specific subject line genuinely helps.
- [email protected]
- General questions, press, and anything about the project itself.
- [email protected]
- Wrong opening hours, a closed place still listed, a place in the wrong district, a bad visit duration. Include the page URL.
- [email protected]
- A mistranslation, or an offer to help with one of the eleven content languages.
- [email protected]
- An ad in the wrong place, an ad that covers content, or anything that breaks the advertising rules.
- [email protected]
- Data access, correction and erasure requests under the GDPR or the KVKK.
Reporting a data error well
The fastest fix comes from a report that names the page, says what is shown, and says what is true. If the underlying error is in OpenStreetMap, correcting it there fixes it for everyone rather than only here — and the next ingest picks it up.
- Include the URL of the place or city page.
- Say what the page claims and what you saw on the door.
- A photograph of the opening-hours sign settles almost every dispute.
Editorial values are never overwritten by an automated sync. A correction reviewed by hand is routed to a review queue and survives the next ingest run.
What we cannot do
We cannot book anything, cannot hold a ticket, cannot confirm a timed entry on your behalf, and cannot advise on visas. The plan tells you what the data says; the venue is the authority on its own door.