Privacy, in plain language.

Handy Timer for Android

Handy Timer stores your timers, saved presets and sets, up to six recent one-off templates, widget choices, and app preferences on your device. Clear recent timers from the timer screen without removing running timers. Timer functions work offline, with no account or advertising.

Android app analytics: the Google Play release includes Statsig usage analytics that starts when the app starts, without a consent prompt or an in-app opt-out. Configured private test builds have included this analytics since October 31, 2026; some earlier test builds have no analytics. Website Analytics preferences do not control Android app analytics.

What the app sends: the app records opening the app, starting or finishing a timer, and selected timer actions. These custom events use fixed categories; they exclude timer names and IDs, exact durations, presets or backup contents, and raw application errors. We do not supply your name, email, advertising ID, Android ID, or an account user ID to Statsig. The SDK uses a random identifier kept for this app installation, a session identifier, and SDK version information. This is not anonymous measurement.

The Statsig SDK also exchanges initialization and configuration data and sends technical diagnostics; SDK-internal errors may include a stack trace. Activity logging and extra non-SDK and network-metadata collection are disabled. Its network connections still expose ordinary connection information, including your IP address, to Statsig. Handy Timer does not request precise location, camera or microphone access. Timer names, preset contents and backup files are not uploaded by this analytics integration.

Names while locked: a separate app choice, off by default, can show timer names on the finish screen while your phone is locked. People near your phone may see those names. Explicitly private timer categories stay hidden, and Android notification-text settings may differ. You can turn the app choice off in Settings → Notifications → Lock-screen names.

Backups you choose: saving a backup creates a readable file containing preset and set names, durations, and their selected options. It excludes running timers, Android permissions, notification settings, and widget assignments. You choose the file and destination using Android’s document picker. Your selected document provider can handle that file and may upload it to cloud storage under its own privacy policy. Handy Timer does not save the document address or request continuing access.

Optional spoken names: if you enable this feature, your timer name is passed to your device’s installed text-to-speech engine. Handy Timer selects an installed voice marked for offline use and does not request a voice download or network-voice fallback. The installed engine is a separate app or system component with its own settings and privacy practices.

Keeping and deleting data: saved app data remains on the device until you remove it in the app, clear Handy Timer’s app storage, or uninstall. The SDK may also cache configuration and event batches locally and retry failed batches for up to three days. Clearing app storage or uninstalling removes local app data; it does not delete analytics already received by Statsig. Statsig server records follow the provider and project’s retention settings; we have not established a single retention period for those records.

Exported backup files remain wherever you saved them; clearing app storage or uninstalling does not delete those files or a provider’s records. Delete exported files through the destination you selected.

Links and questions: links open your browser only when you tap them, without attaching timer data. Visits to quietlyhandy.com follow the website notice below; third-party destinations have their own privacy practices. For Handy Timer support or privacy questions, email matt@quietlyhandy.com.

Browser tools: your inputs stay on your device

Lists, spreadsheet values, photos, mouse timing, audio, screen inspection marks, and chapter lists are processed in your browser. We do not upload those inputs to our servers or include them in analytics. Inputs stay in the current workspace, not in an account or saved history. Refreshing clears the workspace; files you download or text you copy remain on your device or clipboard. Original image and audio files are not changed.

Audio Repeat decodes your chosen recording locally and creates a WAV with your selected repeats and pauses. It does not request microphone access, transcribe speech, or store recordings in browser history. The downloaded practice track remains on your device.

Screen Check displays solid colors that you choose and keeps your inspection marks, observations and report only in this tab. It does not request camera or screen-capture access, read physical pixels, diagnose hardware, or retain your checklist after a refresh. Copying or downloading a report is a deliberate local action, not an upload.

Chapter Check inspects your chapter text and optional supplied video duration locally, preserving your text and order. It does not fetch a video or link, verify the supplied duration, or determine whether YouTube will show chapters. Chapter titles, timestamps, supplied duration and the report stay in this tab unless you deliberately copy or download a report. They are not saved in browser storage.

Website requests still happen

Vercel hosts the website. Loading pages and assets sends normal connection information, such as your IP address, requested page, and browser information, to the hosting provider. Hosting and security records are separate from optional usage analytics.

When no saved choice or browser privacy signal already decides the result, we make one short request to our own measurement-policy endpoint. It uses Vercel’s IP-based country indication—not GPS—to decide between a U.S. default and opt-in elsewhere. The app does not log or store that country, return it to the browser, or use another location-lookup service. Missing or uncertain country information leaves analytics off. IP-based location can be imperfect.

When website analytics runs

For visits identified as U.S. visits, Google Analytics 4 and Statsig are enabled by default unless you have opted out or your browser sends Global Privacy Control or Do Not Track. You can turn them off using Analytics preferences at the bottom of every page. There is no automatic pop-up.

For other or unknown locations, these services stay off until you explicitly allow analytics through the same control. A saved decline is respected across the tools and does not automatically expire. A saved affirmative choice expires after 180 days. Choices are stored locally in this browser; clearing browser storage or using another browser changes what we can remember. If storage is unavailable, a choice applies to the current visit but may not survive a reload. We do not store an automatic U.S. default as if you had clicked Allow.

What website analytics receives—and what it does not

We measure known pages, deliberate tool starts, successful results, coarse size and duration ranges, fixed error categories, exports, and selected features. Example actions and automated tool calls are labeled separately. Measurement helps us find useful tools and fix confusing or broken interactions.

Google Analytics and Statsig use random browser identifiers in cookies or local storage. Their connections also expose normal information such as your IP address, browser, and device information. This is not anonymous tracking. We do not send pasted values, list entries, photos, audio, filenames, exact audio settings, screen inspection observations, exact checklist counts, report text, pixel coordinates, clipboard text, raw errors, or arbitrary URL parameters. Screen Check may report only whether a finished checklist is complete or partial, never what you observed. Chapter Check may report a fixed inspection outcome and whether available text-check coverage is blocked, partial or complete; complete coverage does not mean the checks passed or that YouTube accepts the chapters. Chapter text, titles, exact timestamps, supplied video duration and report contents never enter analytics. We do not install session replay or autocapture, and we disable Google advertising personalization, Google Signals, and Enhanced Measurement. We do not use this measurement to sell visitor data or personalize advertising.

Statsig may help us test small wording or feature changes; the normal tool remains available without measurement. An experiment entry point does not mean an experiment is currently running.

Turning website analytics off

Turning it off stops new collection in the current page and clears durable measurement cookies and local storage that our implementation controls. The choice also tells other open Quietly Handy tabs to stop. It does not erase information already received by a provider or promise that an already loaded SDK loses every in-memory identifier. Actions performed while measurement was off are not replayed later. The tools keep working. This browser choice does not turn off Android app analytics.

Website providers and retention

Analytics providers retain information according to their service settings and policies; opting out is not a request to delete their history. Our GA4 event-level retention setting is two months. Browser cookies and local storage can have different lifetimes. We do not promise a matching retention period for all provider records.

• How Google uses information from sites that use its services
• Statsig privacy and compliance documentation
• Vercel privacy policy

Questions and requests

For privacy questions or requests, email matt@quietlyhandy.com. Please do not send private lists, images, timing reports, or other tool inputs with your request.