EventWatch Web App Privacy Policy

EventWatch (hereinafter referred to as "the Service") considers the protection of user privacy to be of utmost importance and establishes the following privacy policy regarding the handling of personal information.

Article 1 (Definition of Personal Information)

In this privacy policy, personal information refers to information related to living individuals, including names, email addresses, phone numbers, etc., which can identify specific individuals.

Article 2 (Collection Method of Personal Information)

The Service may collect personal information such as names and email addresses when users register accounts or post events.

The Service also accepts an optional contact address, without account registration, through the crawl request form (the screen where you tell us the URL of an event page). This contact address is used only to reach you when we need to check something about publishing the event, and for no other purpose. If the contact is an email address, our staff may email you from contact@eventwatch.app. For any other kind of contact, our staff reach you through that channel. You can send a request while leaving it blank, in which case we cannot reply.

The Service does not store any information that identifies the person who sent a crawl request (such as an IP address or a value derived from it). Because of this, we cannot locate a particular request from a report by the sender, and we cannot honour individual deletion requests for the contact address we hold.

Instead, we erase the contact address automatically 90 days after the crawl request has been resolved or dismissed. The request itself (the URL you sent us, the comment you added, and the outcome) is retained as the record of how the publishing decision was made.

The event report form likewise accepts an optional contact address without account registration. This contact address is used only to reach you about that report when our staff decide a reply is needed. We do not notify you of the outcome individually. If the contact is an email address, our staff may email you from contact@eventwatch.app. For any other kind of contact, our staff reach you through that channel. You can send a report while leaving it blank, in which case we cannot reply.

For reports as well, the Service does not store any information that identifies the person who submitted them (such as an IP address or a value derived from it). Because of this, we cannot locate a particular report when the person who submitted it asks us to, and we cannot honour individual deletion requests for the contact address we hold.

Instead, we erase the contact address automatically 90 days after the report has been resolved or dismissed. The report itself (the event concerned, the reason category, the text submitted, and the outcome) is retained as the basis for responding to rights holders.

When we reply by email to the contact address of a crawl request or a report, we erase the subject and body of that reply at the same time as the contact address (90 days after the request or report has been resolved or dismissed). We keep the record of when the reply was sent and which staff member sent it. The recipient's email address is not kept in the reply record. When the images in our reply are displayed, the email app loads them from the Service's website, and, as with any other visit to the website, the IP address and similar data may remain in the website's delivery logs. The image URLs carry no value that identifies the recipient, and we do not record whether the email was opened. Emails you send back in response to our reply arrive in our staff inbox and are not covered by this automatic erasure. If you ask us from the email address you sent them from, using the contact in Article 9, we will delete them.

Article 3 (Purpose of Using Personal Information)

Collected personal information will be used for the following purposes:

  • Providing and operating the Service
  • Responding to inquiries from users
  • Improving the Service and enhancing user experience
  • Providing important notices and updates
  • Necessary communications and notifications for operation

Article 4 (Use of Cookies and Access Analysis Tools)

The Service uses cookies to improve user convenience and service quality. To analyze how the Service is used, we use Google Analytics 4 (GA4) on the website and Google Analytics for Firebase in the mobile apps. These tools collect browsing activity using cookies or device identifiers. The information collected does not include your name or email address and does not identify you on its own. For visitors from the European Economic Area (EEA) and the United Kingdom, we do not use analytics cookies unless consent has been confirmed.

We also count the total number of views for each event so that organizers can see how often their own submissions are viewed. This count uses neither cookies nor device identifiers: we store only which event was viewed and when. No information that identifies the viewer is recorded.

On the website's home page, we store the area (prefecture) to show in a cookie in your browser and use it to display the home page the next time you open it. We store the prefecture you chose on the home page. If you are logged in and have not chosen one yet, we store the prefecture registered to your account. This cookie is sent to the Service's servers and is used only to choose which events to show on the home page. In addition, when you switch the area on the home page, we store up to 3 areas you were showing before (including all of Japan) in a cookie in your browser. This cookie is also sent to the Service's servers and is used only to list those areas next to the home area so you can choose them again. Neither cookie is removed when you log out. If you delete cookies in your browser settings, the home page goes back to showing all of Japan and the listed areas are removed.

So that the home page does not show the same events every time you open it, we also store part of the identifiers (the last 8 characters) of the events shown on your last two visits to the home page in a cookie in your browser (up to 200 events). This cookie is sent to the Service's servers and is used only to make recently shown events less likely to appear the next time you open the home page. It is kept for 7 days from the last time the record was updated and contains no information that identifies you. Deleting cookies in your browser settings also removes this record.

So that you do not lose what you are typing when you reload or close the page, the text you enter in the event submission form and the event edit page is saved in your browser's storage (local storage) as you type, and is restored when you open the page again. When you edit an event, the tags you chose are saved as well. Images you choose are not saved. So that a submission that fails partway can be retried as the same post, we also save the identifier of the post already created and of the account that created it (these are also deleted when you log out or your login session ends). This data is not sent to the Service's servers. It is deleted when you successfully send or save, or when you log out yourself. Anything last saved more than 7 days ago is deleted without being restored the next time you open the submission form or the edit page. Deleting your browser's site data also removes it.

Article 5 (Third-Party Access)

Only aggregated anonymous data is periodically sent to external services to help service providers improve the application and its services. Service providers may share information with third parties as described in their privacy statements. However, when we reply by email to the contact address of a crawl request or a report, we pass the recipient address, subject, and body to our email delivery provider.

The Service uses third-party services that have their own privacy policies regarding data handling. Below are links to the privacy policies of third-party service providers used by the Service:

Article 6 (Provision of Personal Information to Third Parties)

The Service will not provide personal information to third parties without user consent, except as required by law.

Article 7 (Management of Personal Information)

The Service will appropriately and safely manage collected personal information and take appropriate measures to prevent loss, leakage, falsification, etc.

Article 8 (Changes to the Privacy Policy)

The Service may change this privacy policy as necessary. The revised privacy policy will take effect from the time it is published on the Service.

Article 9 (Contact Information)

For inquiries regarding this privacy policy, as well as questions about the information published on the Service and removal requests from rights holders, please contact us at the address below. Our contact page lists what to include for each kind of request.

  • Email address: contact@eventwatch.app

Established: June 5, 2025

Last updated: October 26, 2026

Festivals, sports, local events and more from all over Japan, gathered in one place. Search by date and area to find events you're interested in.

Save events and get reminders in the app

Copyrights of the images shown belong to the respective organizers. Images of collected events are link previews. Dates and details may change.

© 2026 EventWatch