Skip to content
Tonari Tokei

StackWorks/Tonari Tokei

Tonari Tokei

Tonari Tokei Android Privacy Policy

ContentsOn-device dataOptional calendarOptional location, forecast and place searchGoogle Play BillingDeletionIndependent demo

Updated October 5, 2026 · StackWorksDev

On-device data

Settings, a selected weather place, cached forecasts and Play-confirmed Plus status stay in app-private storage. There is no developer server, account, cloud sync, advertising SDK or developer behavioral/crash analytics SDK. Android automatic backup is disabled.

Optional calendar

READ_CALENDAR is requested only when you choose to allow the calendar. Titles, start times and all-day flags are read into memory for display. They are never stored, modified or sent off-device. You can use the clock without permission.

Optional location, forecast and place search

Before choosing a weather place, the app explains recipients and data use. Current location requests optional approximate-location permission and is obtained only for that action, without continuous/background tracking. Coordinates are rounded to two decimal places (about 1 km) before storage or forecast transmission. Unrounded coordinates are not stored.

Rounded coordinates and your connection IP are sent by HTTPS to MET Norway to obtain forecasts. MET records IP/coordinates in its access logs in Oslo, Norway. The identifying request header contains app/version and a public support URL, without a user ID or email. Provider log retention and deletion follow provider policies. See weather attribution and terms.

Place-search text is sent to the Android device's Geocoder/map service. Provider identity and retention vary by device. This app does not save search history; the selected locality name and rounded coordinates are stored locally.

Google Play Billing

Optional Plus purchases and restoration use Billing 9.1.0. Product, purchase state/tokens and related data are exchanged with Google Play. Confirmed entitlement is cached locally. The app does not obtain/store payment details or Google-account credentials.

The SDK may automatically send technical connection/API success or failure diagnostics and package/app/SDK versions to Google. A random BillingClient session ID and flow-specific ID are associated with this processing. These differ from Advertising ID and persistent tracking identifiers created by this app. This is not developer analytics of clock usage or calendar content. There is no separate in-app opt-out for SDK automatic diagnostics.

Deletion

Delete the place and weather cache in weather settings. Revoke calendar/location permission in Android app settings. Clear app data or uninstall to remove local settings/cache. Purchase records and Google/MET/map-provider logs remain under those providers' controls; app deletion does not guarantee deletion there.

Independent demo

Demo events/forecasts are fictional. Demo does not access the calendar/location or start forecast/geocoding requests. Its settings do not alter normal settings, widgets or purchase entitlement. Billing initialization diagnostics may occur as described above.

Contact contact@stack-works.dev. You need not include calendar contents, locations, purchase tokens or payment details.

SUPPORT & CONTACT

Support

Questions, bug reports and suggestions are welcome.

contact@stack-works.dev ↗