Privacy policy

Counter and session data

We store your counter label, type, mode, chosen date, reset count, visibility, and supported milestone/reminder preferences in a server database. A random user identifier in browser storage and a session cookie associate your requests with your counters. Browser storage can also contain saved preferences and marketing attribution parameters.

Recovery IDs act as access credentials. Do not share them. Counter labels and types can reveal personal circumstances, so use neutral wording if you prefer. We do not sell your counter records to advertisers.

Device and network eligibility checks

To enforce the free-counter allowance and prevent abuse, the app sends a browser/device fingerprint and the server hashes the request's IP address into a network identifier. Stored fingerprint records include free-counter usage. Hashing does not make these identifiers free of privacy implications.

These checks may sometimes classify shared devices or networks together. Contact support if you think a check is mistaken. Clearing browser storage does not necessarily restore free eligibility.

Optional email and recovery

If you link a recovery email, it is stored against your user record until you unlink it using the app's recovery settings or request assistance. It is not discarded at the end of the recovery session. Recovery tokens are stored with expiry and usage state; email delivery is handled by the configured mail service.

If you send a support message, the message and any contact information you include are transmitted to the service's support email provider. Do not include sensitive recovery credentials or card numbers.

Payments and subscriptions

Stripe processes payments and may collect billing information under its own privacy policy. Counter stores payment-related references such as a Stripe customer ID, subscription status, and purchased-counter credits linked to your session. Counter does not store full payment card numbers. Stripe may use cookies or other technical storage for checkout and security.

Hosting analytics and attribution

When enabled for the published site, the hosting provider measures visits and categorical actions such as counter creation, resetting, visibility changes, checkout starts, and sharing actions. Custom event properties do not include counter names, types, IDs, selected dates, recovery email, or free-form text. The hosting provider may process technical request information.

Separately from analytics, operational server logs can contain API response details, including counter information and session-related identifiers. Do not put unnecessary sensitive information in counter labels. We do not promise a fixed log-retention period that has not been verified with the hosting provider.

Marketing source and content parameters may be kept in browser storage and attached to created counters for aggregate attribution. They are not a guarantee that a marketing click caused a purchase.

Advertising

Google AdSense ad execution is disabled in this version. Publisher verification metadata and ads.txt remain available, but the app does not load the AdSense advertising script. Before enabling ads, we must review disclosures, regional consent and certified consent-platform requirements where applicable, and which pages are suitable. Private counter screens and sensitive personal contexts must not become advertising targets.

Public links and indexing

Counters are private by default. If you make a counter public, its label, type, and day count become visible through the public page. Public counters can be included in the sitemap and indexed by search engines. Links can be forwarded; they are not confidential invitations.

Making a counter private blocks future public retrieval, but cannot erase copies, screenshots, or search caches. Never use a public label for information you cannot safely publish.

Retention and deletion

Clearing browser storage removes local access information; it does not delete the records in our database. Counter records remain until deleted through the app or otherwise removed by the service. We do not promise automatic deletion after a session expires or a fixed retention period that has not been implemented.

Deleting an individual counter removes that counter from active application storage; it does not necessarily remove associated billing, abuse-prevention records, email-provider records, or provider backups. Unlinking your recovery email clears the email from the application user record. Contact support for other privacy or deletion requests; additional verification may be needed.

Contact and changes

Use Contact support in the footer for privacy questions, deletion assistance, or a correction to this policy. Include a reply email if you want a response, but not your recovery credentials. We update the revision date when this policy changes.