TOMOSHIBI LLC handles records and usage information in Countain as described below.
Records on your device
Counter names, values, history, categories, selected images, and settings are stored on your device. There is no separate account registration or iCloud sync. Biometric authentication uses the operating system; the app does not receive face or fingerprint data. Verification information for the four-digit app code is stored in the device Keychain.
Private counters display their contents after authentication and stay out of regular lists, notifications, and sharing. This is display access control, not a separate encrypted vault for all record data.
Apple Watch
Counter names, values, categories, and settings needed for recording are sent to your paired Watch. Records added on Watch sync to iPhone. Private counter data is included in Watch sync, but its contents are not displayed before authentication. Selected counter images are not included in Watch sync.
Shake counting uses device motion to detect counts. Optional sensitivity test results are not added to your counter records.
Optional analytics and crash diagnostics
You can choose Firebase Analytics usage analysis and Sentry crash diagnostics separately. Both are off by default. You can record without enabling them and change your choices in settings.
When analytics is enabled, usage information such as paywall views and completed purchases is sent to Google's Firebase. The SDK may process app usage, app-instance identifiers, and technical information about the device and OS. App-specific events do not include counter names, values, history, private contents, or passwords. Advertising consent is disabled.
When diagnostics is enabled, crash information and technical details about the device and app are sent to Sentry. The app removes user information, free-text messages, and request details before sending, and disables screenshot and view-hierarchy attachments. These settings do not guarantee that every piece of information is completely anonymous.
Turning a choice off invokes controls to stop future collection and sending. It does not itself delete information already sent. See Firebase privacy information and Sentry privacy information for provider data handling.
Purchases, notifications, sharing, and backups
Apple processes purchases, and the app checks entitlement and validity. Countain does not collect payment-card details through its own form.
Notifications are scheduled on the device after OS permission. They may display regular counter information. Sharing passes regular counter text to the destination you select.
Backups are encrypted with a password and exported to a location you choose. If that location is a cloud service, that service's terms also apply. Backups do not transfer purchase entitlement, diagnostic consent, or unlocked authentication state. Device and OS backups are separate mechanisms.
Deletion and contact
You can delete records in the app. Exported backups, OS backups, and content sent to sharing destinations may remain after removing the app. Manage those copies at their respective locations.
For support, information entered in the contact form and contact details supplied when requesting a reply are used to handle your inquiry. See also the website privacy policy . You do not need to send private records or passwords. Contact us through Support about data questions. Changes to this policy will be announced on this page.
In-app feedback
Submitting feedback sends its type and message, optional name and email when requesting a reply, app version/build, language, Free/Pro status and submission time through Cloudflare to the operator’s Discord channel. Counter names, records and secret contents are not automatically attached. Information you include in the message is sent. Simulator delivery was confirmed by the user; device delivery and retention/deletion operations remain separate checks.
Operator and shared contact channel
The operator is TOMOSHIBI LLC. See company information and the TOMOSHIBI APPS contact form . Select “TOMOSHIBI APPS site” and include “Countain” in your message. Enter your name and email only if you request a reply.
> Before publication: check effective date, service-specific retention/deletion settings, processing regions Inquiry retention follows the policy below.
Retention of inquiries
We keep inquiry information for as long as needed to receive, reply to, investigate and manage the inquiry, and delete personal information when it is no longer needed. Unresolved inquiries or legally required retention are handled for as long as that need remains. Improvement notes that do not identify individuals are managed separately from original messages and contact details. No fixed number of years is set; this is not a policy of indefinite retention without reviewing necessity. Use the shared contact channel below for deletion and other data questions.
> Operational check before publication: a process for tracking resolution, reviewing necessity and deleting unneeded information, including Discord messages, contact details and attachments, has not yet been established. Existing history has not been deleted.
Verified external-service settings (pre-publication review)
On September 30, 2026, the connected administration pages showed this product’s Google Analytics property retains event data for two months and user data for fourteen months, with reset on new user activity enabled. This setting does not mean all standard aggregated reports are deleted after those periods. The Sentry organization uses the US data-storage region. The diagnostic-event retention applicable to its current Developer subscription, the scope of international processing by Google and other providers, and deletion handling for previously received data were not established by this check.
An existing Countain diagnostic event still contained SDK device-identification information and provider-added geographical information after the app’s sanitization. It is not treated as completely anonymous.
