Privacy Policy

vClock ("we", "us", "our") is committed to protecting your privacy. This Privacy Policy explains how we handle information when you use our website and time tools.

In short: We don't collect personal data. We don't use tracking cookies. We don't require accounts. Your usage stays in your browser.

We do not collect any personally identifiable information. You can use all vClock tools without creating an account, providing an email address, or sharing any personal details.

Local Storage Only

Some tools may store preferences locally in your browser using localStorage. This includes:

• Theme preference (dark/light mode)
• Timer sound preferences
• Custom timer durations you create
• World clock city selections
• Pomodoro/interval timer configurations

This data never leaves your device. We cannot access it. You can clear it anytime via your browser settings.

vClock does not use cookies, tracking pixels, fingerprinting, or any form of user identification technology.

• No Google Analytics or similar analytics
• No Facebook/Meta pixels
• No advertising tracking
• No session recording
• No heatmaps or behavior tracking

If we ever add privacy-respecting analytics (like Plausible or Umami) in the future, this policy will be updated and you will be notified.

All vClock tools run entirely in your browser using JavaScript. No timer data, stopwatch laps, or clock settings are ever sent to our servers.

Timer Engine

Our timers use Date.now() timestamp calculations for drift-free accuracy. This happens locally — no server communication required.

World Clock

Time zone calculations use the browser's built-in Intl.DateTimeFormat API. No external time services are queried.

Audio Alerts

Timer completion sounds are generated using the Web Audio API locally in your browser. No audio files are loaded from our servers.

vClock does not integrate with any third-party services that collect user data. The only external requests made are:

• Font loading (Google Fonts - Geist) — loaded via Next.js font optimization with display: swap
• Static assets (images, icons) — served from our own domain/CDN

We do not use CDNs that track users. All resources are served with appropriate caching headers and no tracking parameters.

If you use our contact form, the information you provide (name, email, subject, message) is sent to our email service provider for the sole purpose of responding to your inquiry.

We do not store contact form submissions in a database. They are processed by our email provider and deleted after response.

When you embed vClock tools on your website via iframe, the embedded version:

• Loads from our domain (vclock.app)
• Does not set cookies
• Does not track the parent page
• Does not access your site's data
• Runs the same privacy-first code

Since we don't collect personal data, there's nothing to retain. Local storage data persists until you clear it or your browser clears it automatically.

Since we don't process personal data, traditional data subject rights (access, rectification, erasure, portability) don't apply in the usual sense. However:

• You can clear all local storage data anytime via browser settings
• You can disable JavaScript to prevent any local storage usage
• You can use browser extensions to block local storage

vClock does not knowingly collect information from children under 13. Since we don't collect any personal information from anyone, this is inherently satisfied.

We implement reasonable security measures:

• HTTPS enforced everywhere
• Content Security Policy headers
• No inline scripts (CSP compliant)
• Regular dependency updates
• Static site — no database to breach

We may update this Privacy Policy to reflect changes in our practices or legal requirements. The "Last Updated" date at the top will be revised. We encourage you to review this page periodically.

If we make material changes (e.g., adding analytics), we will provide a prominent notice on the site.

Questions about this Privacy Policy? Contact us at privacy@vclock.app or use our contact form.