Privacy Policy

Last updated: July 14, 2026

The short version: the local timer keeps everything on your machine. If you use TimerMCP Cloud, we store your Google account basics and the timer history you choose to sync. The service is free, we take no payments, and we do not run ads, sell data, or use third-party trackers.

Who we are

TimerMCP (timermcp.com) provides a local, open source timer for Claude via the Model Context Protocol, and an optional free cloud service for syncing your timer history. Questions about this policy: julan.krofile@gmail.com.

The local timer: your data stays with you

The open source TimerMCP server runs entirely on your computer. Your timers, history, personal bests, and result cards are stored in the .timermcp folder in your home directory. Nothing is sent to us or to anyone else unless you explicitly enable cloud sync with a token you create. Deleting that folder deletes the data.

What TimerMCP Cloud collects

When you sign in and use the cloud service, we store:

  • Account basics from Google sign-in: your name, email address, profile photo, and a user ID. We never see your Google password.
  • The timer history you sync: timer names, durations, timestamps, splits, and derived statistics such as streaks and personal bests. Timer names are chosen by you; avoid putting sensitive information in them if that concerns you.
  • Sync tokens you generate to connect your local timer.

We do not collect your precise location, contacts, browsing history, or anything from your machine beyond the timer data you sync.

Payments

TimerMCP is free while in beta. We do not collect payment information of any kind.

Service providers

We rely on two processors to run the cloud service:

  • Google Firebase for sign-in and data storage (United States).
  • Vercel for hosting the website and API (United States).

Each receives only what it needs to perform its function. We do not sell or rent your personal information to anyone, and we do not use third-party advertising or analytics trackers.

Cookies and local storage

We use browser storage only to keep you signed in (Firebase authentication state) and to remember interface preferences such as fun mode. We set no advertising cookies.

Retention and deletion

Cloud data is kept while your account is active. You can delete your synced history at any time by emailing us, and we will remove your account data from our systems within 30 days. Local data is always under your direct control.

Your rights

Depending on where you live (for example under GDPR or CCPA), you may have the right to access, correct, export, or delete your personal data, and to object to processing. Email julan.krofile@gmail.com and we will honor these requests. We do not sell personal information, so there is nothing to opt out of selling.

Children

TimerMCP is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has created an account, contact us and we will delete it.

Changes

If this policy changes materially, we will update this page and the date above. Continued use of the cloud service after a change means you accept the updated policy.