Contact Us

Questions, bug reports and feature ideas are all welcome. We usually reply within 1–2 business days.

Email

The fastest way to reach the VClock team:

📧 support@vclock.pro

What We Can Help With

Before You Write: Quick Fixes

No alarm sound? Browsers block audio until you interact with a page. Click anywhere on the VClock page once — setting an alarm or starting a timer counts — and audio is unlocked. Also check your system volume and make sure the tab is not muted (right-click the tab in Chrome to check).

Alarm did not ring? The tab must stay open, and the computer must not be asleep. A sleeping machine pauses the browser entirely. For critical wake-ups, set a phone alarm as a backup.

Timer seems slow in a background tab? It is not — VClock calculates remaining time from the real clock, so the final alert is accurate even if the visible digits update less often while the tab is hidden.

Lost your alarms? They are stored in your browser using local storage. Clearing site data, browsing privately, or switching to a different browser or device will remove them — they are deliberately not synced to any account.

World clock missing a city? Tell us which one and we will add it. The list covers major cities across every populated time zone, but it is not exhaustive.

Want a timer length that is not listed? Any duration up to 99 hours can be typed directly into the timer page. The preset pages simply cover the most-requested lengths — if yours would be useful to others, let us know and we will add it.

Reporting a Bug Usefully

Three details turn a vague report into something we can fix quickly:

What We Cannot Help With

VClock is a browser tool, so a few things are outside our control: alarms cannot ring if your computer sleeps or the tab is closed, we cannot recover alarms lost when browser data is cleared, and we cannot control which advertisements a network chooses to display. For anything safety-critical — flights, medication, examinations — please use a dedicated device alarm as a backup, as our terms of service sets out.

Response Times

We read every message. Bug reports usually get a reply within one to two business days; feature requests may take longer, since we tend to batch them. If you do not hear back within a week, it is worth checking your spam folder before resending.