Corrections Policy

We correct, we don't hide

Factual accuracy is the whole point of a seasonal-events site — a wrong date, price or station exit can ruin a trip. We correct errors as soon as they are confirmed, document the change on the affected article, and surface significant corrections here.

How to report an error

• Use the feedback form on the article page where you spotted the error — it tags the submission with the article slug automatically.
• Include the specific claim that is wrong, what you believe the correct information is, and a source (official operator URL, a station announcement, a dated photo) if you have one.
• Report languages: we accept correction reports in English, Japanese, Traditional Chinese, Simplified Chinese, Korean, Indonesian and Thai.

Our response timeline

• Within 24 hours: we triage the report and, if the error is clear-cut (a wrong date, a dead URL), we correct it immediately.
• Within 7 days: we respond to reports that require verification against primary sources (operator announcements, prefectural tourism boards, JMA data).
• Prices & opening hours:because these change frequently, we treat them as always-correctable; we will not dispute a report that cites the operator's current public page.

How corrections are marked

Minor corrections (typos, small clarifications, dead-link replacements) are made silently. Substantive corrections (factual changes that could affect a reader's plans) are marked:

• The article's structured-data dateModified field is updated to the correction date.
• A "Corrected [date]" note is appended to the relevant paragraph where the change was made, with a brief description of what changed.
• For significant corrections (incorrect event cancellation status, incorrect ticket windows, etc.) a note is also added to this page under "Recent corrections" below.

Recent corrections

None logged yet. Significant corrections will be published here as they are made.

What is not a correction

A disagreement about recommendations ("you should have recommended Sakyomachi, not Pontocho") is editorial feedback, which we read gratefully but do not file as a correction. A dispute about an event's subjective quality ("the Shibuya Halloween atmosphere was better than you said") is also feedback, not a correction. We use corrections strictly for verifiable factual mistakes.

How to escalate

If you reported a correction, it was ignored for more than 14 days, and you believe it is a safety or legal issue (not a minor fact dispute), reply to the feedback thread with the subject line "Escalation request" and we will respond personally.