VINSON / POLICY CENTER
Dated policy revision

Countdown Timer Widget
Privacy Policy

Effective 14 November 2026Android 2.0 and native 3.1.5 updatecom.vinsontech.widgetmasterfree

What stays on your device and what Google Mobile Ads processes to show advertising.

https://policy.vinsontech.in/apps/com.vinsontech.widgetmasterfree/

This is a dated revision. Read the current policy.

Scope and contact

This policy covers Countdown Timer Widget for Android, package com.vinsontech.widgetmasterfree, provided by Vinson Developers. It describes the currently distributed app and the native 3.1.5 update. Version-specific differences are explained below. Contact vinsondevelopers@gmail.com with privacy questions. Android, Google Play and services you choose to use have their own privacy practices.

Countdown information stored on your device

Countdown titles, dates, notes, categories, selected designs, widget choices and app preferences are stored in private app storage on your device. The app has no account system or developer-operated cloud database. Countdown details are not sent to Vinson Developers or included in the app's ad requests. The native update can read supported records from the previous local CountdownTimerDB for migration; the previous database may remain on the device for upgrade safety. Version 2.0 enabled Android backup, so eligible data may be copied by your Android backup provider according to your device settings. The native 3.1.5 update disables Android backup for app data.

Advertising and Google Mobile Ads

The free app uses Google Mobile Ads (AdMob). The native 3.1.5 update displays banner and native ads, and may show a capped interstitial after repeated successful timer saves. This update does not load or show app-open ads; earlier app builds used different placements, including app-open advertising. Ad requests wait for the app's consent checks. Google states its Mobile Ads SDK may collect and share IP address information used to estimate general location, product interactions, diagnostic information, and device or account identifiers for advertising, analytics and fraud prevention. The SDK data is encrypted in transit using TLS. Android advertising ID collection may depend on device settings and SDK behavior. Google and its service providers determine their own retention and processing under their policies.

Related information: Google Privacy Policy and Google AdMob data disclosure.

Consent and advertising choices

The native update uses Google User Messaging Platform (UMP) to refresh consent information at app launch and display regional privacy messages configured for the app. Ad requests wait until UMP permits them. When UMP requires a privacy-options entry point, Settings provides Ad privacy choices. Version 2.0 did not include UMP or an in-app privacy-options screen. Android and Google settings also provide advertising and identifier controls. Google determines how information received by its advertising services is retained and processed under its own policies.

Related information: Google Privacy Policy and Google AdMob data disclosure.

Reminders, widgets and sharing

Completion reminders are scheduled locally. Notification permission, Android notification channels, battery restrictions and device settings can affect delivery and lock-screen visibility. Widgets show timer information selected by the user on the home screen, where it may be visible to anyone who can access the device. Optional sharing uses Android system sharing; the app does not control the destination selected by the user.

Retention and deletion

Timer records and preferences remain in app-private storage until changed or deleted in the app, app storage is cleared, or the app is uninstalled. A prior local database may remain after migration for upgrade safety. The app has no developer account or server-side timer records to delete. Deleting local timer data does not delete advertising data already received by Google; use Google and Android privacy controls for that information.

Security and connected services

The app uses Android app-private storage. The native 3.1.5 update excludes app data from Android backup; version 2.0 backup settings are described above. Google states that data collected by the Google Mobile Ads SDK is encrypted in transit using TLS. Ad requests connect to Google; optional sharing or links may connect to a destination selected by the user. These practices reduce risk but cannot guarantee complete security or control how another provider processes its data.

Changes and version scope

This policy is dated 14 November 2026. Older version 2.0 and the native update both use Google Mobile Ads, while backup and in-app consent controls differ as explained above. Dated revisions are available in the policy history. We will update this page when material data practices change.