Interval TimerOpen timer

Privacy policy

Last updated: October 28, 2026

This page explains what information Interval Timer (the “Service”) handles and how it is used.

Current status: We have not started showing ads yet. The ad space is only for checking the layout and sends nothing externally. We will update this page before ads start.

1. Information stored on your device

The Service has no accounts or sign-in. Your settings (time, repeats, sounds, volume), presets, display layout and ad-free status are stored in your browser (localStorage) and are not sent to our servers. Clearing your browser’s site data deletes them.

For supporters, screen and audio files are also stored on the device (Service Worker) so the timer can launch offline.

2. Information we receive

3. Ads

After ads start, ad providers such as Google AdSense may use cookies and similar technologies to show ads based on your browsing on other sites. For how this works, see Google’s advertising policies; to manage personalized ads, visit My Ad Center.

4. Analytics

We use the following tools to understand traffic and usage. Neither uses cookies or collects personally identifying information.

Hiding ads does not stop analytics. If we add tools in the future, we will update this page.

5. Retention

Information saved in your browser remains until you delete it. Information we receive is kept only as long as needed for its purpose and deleted when no longer needed.

6. Sharing and security

Except where required by law, we do not give personal information to third parties without your consent. Ad, analytics and hosting providers may process information on servers outside Japan. Information we receive is managed so that only those who need it can access it.

7. Requests for disclosure or deletion

We respond to requests to disclose, correct or delete personal information we hold, in accordance with law and after verifying your identity. Settings and presets stored only in your browser are not visible to us; delete them from your browser’s site data settings.

8. Support payments

Support payments are made through Buy Me a Coffee; you do not enter card numbers in the Service. Buy Me a Coffee’s terms and policies apply to payments.

Support and ad-free verification data

When linking a payment, a secret restoration pass and ad-free state are saved in browser localStorage. The pass is sent to our verification API in an HTTPS authorization header. The server stores its hash and the linking code. There is no email-based restoration process.

Buy Me a Coffee notifications may contain names, email addresses and support messages. Our integration database stores only linking codes, payment/transaction IDs, amount, currency, confirmation/refund states and timestamps; it does not store names, email addresses, full messages or card numbers. These records provide the benefit, handle refunds and prevent misuse.

Rate limiting temporarily uses time-bucketed hashes derived from IP information. Expired entries are removed on later verification requests; raw IP addresses are not stored in this rate-limit table. Support records are retained as needed to provide the Service and handle refunds. The operator will finalize retention periods and the contact channel before payments open.

9. Changes and contact

When we change this page, we will announce it together with the updated date.

Our contact channel is being prepared. We will announce it on this page when it opens.

Contact page shows the current availability of the contact channel.