Sumkan Privacy Policy

Applies to: Sumkan for Android phones, tablets, and Wear OS, including the version-scoped releases described below

Effective date: September 2, 2026

Last updated: September 2, 2026

Operator: Sumkan

This policy uses one public URL for both older and newer installed versions while legacy versions remain active. The version-specific sections below identify the behavior that applies to each release.

Overview and scope

Sumkan is an offline-first Pomodoro timer for Android phones, tablets, and Wear OS watches. Sumkan has no account, sign-in, or Sumkan-operated remote app-data sync in this release. Core timer, task, settings, and watch-companion data are local-first.

Sumkan does not sell personal information or use it for targeted advertising. It uses Google/Firebase, Google Play/Google Payments, and RevenueCat for the services described in this policy.

Data stored on the device

Sumkan stores timer settings; session history; timestamps, duration, and result; statistics; Todo title, note, due date, completion, and focus association; theme, sound, notification, and watch settings; an app-generated local device/install identifier; and local purchase-entitlement cache data.

This local data remains until you delete individual records where the app provides that control, clear Sumkan app data, uninstall the app, or replace it through backup restore. A user-managed backup can contain the applicable local settings and records; you choose where to save, share, or import it. Depending on Android OS settings, the existing user-data database (sumkan.db) and a user-created backup file may be included in Google cloud backup or device-to-device transfer.

Analytics behavior by app version

Phone and tablet versions through 1.0.2.1 (versionCode 29):

Firebase Analytics is enabled after app startup without an in-app Privacy Choices decision.
There is no Sumkan-managed 5 MiB SQLite Analytics queue.
Legacy identifier collection, Advertising ID/Android AdServices permission and SSAID metadata, RevenueCat Firebase app-instance linkage, and the related deletion limitations continue to apply as described in the current-release policy.

Phone and tablet version 1.0.2.1 (versionCode 30) and later:

On every cold start, Firebase Analytics remains disabled while Sumkan obtains a current Google Play billing country signal. Sumkan does not store, log, send to Analytics, or send to Crashlytics that country value or the region derived from it.