Orbyte markSupport

Task Clock

Privacy policy

Effective date: 3 November 2026

Developer / operator: Orbyte mark
Privacy contact: support@orbytemark.uk
App: Task Clock (Android package: com.taskalarm)

This policy explains how Task Clock handles information when you use its alarms, clock tools, and challenges. Task Clock does not require an account. Its core alarm and personal-content storage is on your device, but third-party Google components can process technical information as described below.

Information used on your device

Alarms and preferences. The app stores alarm times, repeating days, labels, sounds, vibration and snooze settings, challenge settings, display preferences, and selected world-clock cities. World-clock cities are selected by you; the app does not request GPS location permission.

History and challenge progress. The app stores scheduled and dismissal times, alarm outcomes, completion duration, and saved progress for supported challenges. This can include selected or typed answers, attempts, memory selections, and custom typing sentences. This information is used to run challenges, restore progress, verify completion, and display history.

Camera and object information. With camera permission, the app analyzes images for push-up counting and object challenges. Push-up analysis uses live camera frames and does not record a video of that challenge. When you register an object, reference photos, an object name, and visual feature descriptions are saved in the app's private storage for later matching. These features check challenges; they are not intended to authenticate a person's identity.

Activity and motion. The app uses supported step and motion sensors for step counts, daily step goals, shaking tasks, and relevant movement challenges. Step totals and related counter state can be stored locally. These are utility features, not medical measurements.

Audio and video you choose. The app accesses selected media for custom sounds or video challenges. It can copy chosen files into app storage to retain access. Microphone access is used when you choose to record alarm audio. Video recording, when selected, is handled through the device's recording application. The app stores the resulting media or its reference for playback. Selecting a file is not an upload to a developer-operated server.

Why permissions and background access are used

You can manage permissions in Android Settings. Declining a permission can limit the feature that needs it.

Google services and technical data

Task Clock includes Google ML Kit for camera-based features. Google states that ML Kit processes its image/video inputs on the device and does not send those inputs or recognition results to Google servers through ML Kit.

ML Kit does send technical diagnostics and usage metrics to Google. These can include device manufacturer/model and operating-system details, app package/version, installation-related identifiers, API configuration, input/output sizes, feature events, performance measurements, and error information. Google components may also download models, updates, or configuration. Some ML Kit components use Firebase Installations and Firebase Remote Config.

Google uses this technical information for SDK operation, diagnostics, maintenance, improvement, and abuse prevention. Its SDK documentation describes HTTPS protection for the listed transmitted data. Google's handling of information is covered by its own policies:

The current app does not include an advertising SDK or a developer-operated account/cloud-sync service. It does not upload your alarm database, step totals, custom sentences, registered-object photos, or chosen recordings to a developer-operated server. Google SDK technical processing and Android backups are separate from that local storage.

Android backup and device transfer

The current app enables Android backup and device-transfer support for its alarm database and saved alarm audio/voice recordings. Whether a backup occurs depends on your Android version, device, backup provider, and settings. The database may contain alarm history, custom sentences, and saved challenge progress. Not all app content is included in the configured backup.

A backup provider may store eligible data outside your device under its own terms. Manage backups and device transfers through your device/account settings. This is a platform backup feature, not a Task Clock developer-operated cloud service.

Retention, deletion, and your choices

Saved alarms, custom content, and history generally remain in app storage until removed through available app controls, cleared in Android Settings, or removed by uninstalling. Working counters, temporary files, and cache can also be reset or replaced during normal operation. The app does not currently apply a fixed automatic deletion period to saved alarm history and personal content.

You can delete alarms, remove history records, and use available object/sentence deletion controls. Deleting an alarm does not necessarily remove older history or every copied media file. To remove all current local app data, use Android Settings > Apps > Task Clock > Storage > Clear storage/data, or uninstall the app. This removes your saved alarms and other app data. It does not delete original files in your music/gallery library or files retained by another app.

Clearing or uninstalling the app does not by itself delete existing platform backups or technical information already processed by Google. Manage backups separately; Google's policies explain choices for Google-held information. A later restore may bring backed-up app content back to a device.

Security and support

The app uses Android's private app storage and permission controls for locally saved information. Device security and backup settings also affect protection of that data. Google documents HTTPS protection for ML Kit's listed technical transmissions.

If you contact the privacy/support email above, the recipient receives the message, your email address, and anything you choose to include. We use support correspondence to respond to requests and address issues, retaining it only as needed for that purpose and applicable obligations. Avoid sending recordings or other sensitive content unless it is needed for your request.

Task Clock does not require an age profile. For questions about a child's information or a privacy concern, contact the developer using the address above. For access, correction, or deletion requests concerning information you have sent to support, use that same contact address; available rights depend on applicable law.

Changes and contact

We may update this policy when the app or its data practices change. The revised policy will show an updated effective date.

Developer / operator: Orbyte mark
Privacy contact: support@orbytemark.uk