My Calorie Counter Privacy Policy

Information Stored And Used

MCC stores the calorie amounts you enter, daily totals, Today entries, saved daily History, timestamps, your daily goal and selected Accent Color in private application storage on your phone or watch. It also stores randomly generated installation and record identifiers and synchronization/deletion state to keep paired records consistent. These identifiers are not advertising identifiers or hardware serial numbers.

MCC uses this information to provide tracking, History, goal displays, settings and synchronization. Each application can track calories without a connected peer. MCC does not require an account and does not operate a server-side calorie-data store. The applications do not include advertising, advertising tracking, analytics, crash-reporting SDKs, food databases or Health Connect integration. MCC does not sell your calorie data.

Paired Phone And Watch Synchronization

When matching MCC applications are installed on a paired Android phone and Wear OS watch, MCC exchanges calorie records, History, dates/timestamps, record identifiers, deletion state, goal and Accent Color through Google Play services' Wear Data Layer. This can occur in the background when connectivity becomes available, including after entries were made offline. The data is exchanged to make the two MCC installations consistent, not uploaded to a Sonyay-operated backend.

Google Play services manages the connection. Data Layer uses encrypted Bluetooth when available and can route data through Google-managed servers over Wi-Fi or mobile networks when Bluetooth is unavailable. Google documents end-to-end encryption for this cloud-relayed payload. Do not assume that synchronization data never leaves your devices. Google's services and device platforms operate under their own policies and settings; MCC does not control their independent operational handling or retention.

Display Surfaces And Dependencies

If you add them, MCC supplies the current count and relevant goal/display state to the local home-screen widget, Wear Tile or compatible watch-face complication host. Your launcher or watch face controls presentation, including permitted complication colors. The widget can record calories at supported sizes.

MCC uses Google Play services Wearable for paired transport and Android/AndroidX components for storage, rendering and execution. It does not request location, contacts, camera, health/sensor, Health Connect or advertising-ID access for these functions. It does not add an analytics or advertising SDK. Google Play purchases, platform services and the launcher/watch-face host remain subject to their respective policies.

Retention And Deletion

MCC retains local tracking data until you remove it using application or operating-system controls. Deleting an entry or clearing History removes it from visible tracking views and synchronizes that deletion to the paired MCC application. Clearing History keeps today's calorie entries.

Deleted records and related identifiers, timestamps, tombstones and History-clear markers may remain in local storage and synchronized records to prevent an offline peer from restoring deleted values. This is logical deletion, not secure physical erasure; there is no automatic deletion-metadata expiry promised by MCC. Uninstalling or clearing MCC on only one device does not erase the other device's records. A surviving peer may synchronize its records to a reinstalled copy. Removing MCC application data from both devices removes their app-managed local copies under the platforms' behavior; this does not promise erasure of every platform/service copy or historic backup.

Backup, Updates And Reinstallation

Version 1.5 disables Android cloud backup and device-transfer backup for MCC records and preferences on both phone and watch. Normal application updates retain local data and installation identity. Reinstallation, a device reset or a replacement device creates a new installation identity and does not restore MCC data/preferences through Android backup. A surviving paired MCC installation may repopulate its records and settings. Removing or resetting both copies can lose all local records. MCC provides no cloud-backup service; historic backups and device-vendor behavior remain governed by those platforms.

Contact And Policy Changes

For privacy questions, contact Sonyay LLC at support@sonyayllc.com. Information you voluntarily include in a support email is separate from MCC's automatic paired synchronization; avoid sending sensitive calorie/history records unless needed for your request. This policy may be updated when MCC's functionality or data practices change. The effective date identifies the published revision.