Privacy, in plain language.
Website and mobile privacy notice · Updated October 5, 2026
The website calculator
Your birthday, selected age, personal labels, chosen dates, frequencies and calculator results stay in the current browser tab. The life calculator and personal-count demo do not send these inputs to a server, save them in browser storage or put them in the page URL. Closing or reloading the tab clears the inputs held by our code. Your browser may independently remember form entries.
No advertising trackers
This site does not use advertising SDKs, analytics scripts, tracking cookies, third-party fonts or embedded social media.
Hosting
Cloudflare hosts this website and processes connection information, such as IP addresses and request metadata, to deliver and protect it. This is separate from your calculator inputs. We do not promise that visiting a website creates no server records.
The mobile apps
The iOS and Android apps are in testing. The current local-first build stores birthdays, counter names, chosen dates and frequencies on your device. Screen-time minutes and reading habits are entered manually; the app does not read your device usage or reading history. Selected celebration choices are stored locally and included in optional cloud backup. Chosen traditions may reveal personal beliefs, especially if you include them on a shared card. We do not ask your religion or infer it to select celebrations. Calculations happen on-device. Cloud-enabled builds offer optional account sign-in and backup as described below. The apps do not include advertising SDKs. Billing analytics are described below.
Account sign-in and cloud backup
When you choose Sign in with Apple, Apple supplies an app-specific identifier. We do not request your name or email address. Our dedicated Cloudflare service stores that identifier, an internal account identifier, encrypted Apple authorization credentials, and protected app-session records to authenticate you and manage deletion. App credentials are kept in your device's secure credential storage.
Android also offers Google sign-in through Google and Firebase Authentication. Those providers process the selected Google account and authentication information. Our service verifies the Firebase token and uses its project-specific user identifier for the account; it does not use an email address or display name as the account's identity. Signing in with another provider does not automatically merge accounts.
After sign-in, your birthday, chosen horizon, appearance preference and personal count details are synchronized to our Cloudflare service. D1 databases hold synchronized records; Durable Objects manage account, session and sharing state, and R2 stores supported media and recovery records. Count details include names or nicknames you enter, dates, frequencies, manually entered habits and optional celebration choices. Child profiles also include the child’s birthdate and links to custom events you create for them. Birthday milestone cards are calculated from that birthdate. Share previews do not include the stored birthdate; you choose whether to include names before sharing. Partner profiles may include a birthdate, anniversary date and an optional Valentine’s Day choice. These produce annually recurring cards. Original birth years and anniversary years are not printed in those shared cards. Parent connection plans include your chosen activity, planning window, and rhythm. Earlier versions could store a manually recorded shared-moment total; existing totals are retained for compatibility but are no longer displayed or collected through recording controls. We do not monitor your calls, visits or location. Career goals include a chosen template and target date, plus any optional reason, next step or personal intention you enter. Those optional reflections are backed up after sign-in but omitted from shared card images. These records are linked to your account to support backup and recovery. If you add an optional California A–G checklist, its self-reported semester statuses are also backed up and synchronized privately with your account. We do not collect grades, transcripts or school credentials through this checklist. Checklist data is not included in shared cards, invitations or notifications, but is included in your own JSON exports. You can remove a checklist by removing it in the card editor and saving the card; normal backup retention and account-deletion rules still apply. Optional celebration choices and free-form names may reveal sensitive information; enter only what you are comfortable backing up. We do not use these details for advertising or send them to RevenueCat.
Connections use HTTPS. Apple authorization credentials are encrypted separately before storage; synchronized count records are not end-to-end encrypted. Cloudflare processes network/request information to deliver and protect the service. Our application error logs omit birthdays, names, count payloads and authentication tokens.
You can request deletion under Account and backup after recent authentication with your sign-in provider. An accepted request disables account access immediately and removes this phone’s local counts. Server cleanup and Apple authorization revocation run asynchronously and retry if a service is unavailable. Database recovery history may retain earlier data for up to 30 days. Deletion does not remove files you exported or shared, other devices’ offline copies, or store transaction records. For deletion help, use the contact below. Keep another copy of important counts during testing.
After account deletion, we keep limited records that prevent deleted accounts or shared content from returning during recovery. These include internal account and content identifiers, deletion dates, and technical routing information. They do not contain private count details or photo files and are separate from recovery copies of your content.
When we remove a shared card following a report, we keep an enforcement record with a case identifier, the affected account and card identifiers, the version reviewed, a reason category, and the action date. It contains neither a copy of the card nor the full report message. Account deletion does not automatically remove this record or support email correspondence.
Optional Count+ purchases
The billing integration is inactive in builds without store configuration. When enabled, the app uses RevenueCat and Apple’s App Store or Google Play to verify purchases and restore access. RevenueCat processes purchase history, transaction identifiers, an anonymous app-user identifier or an account-linked billing identifier, and technical connection/device information needed to operate billing. Purchase history and billing identifiers are also used for billing analytics. This can include an approximate country derived from your connection’s IP address. We do not send birthdays, counter names, celebration choices, frequencies or card images to the billing service. Payment details are handled by your store.
Billing can connect in the background to refresh access when configured; your local calculations do not wait for it. We disable optional billing diagnostics and automatic advertising-identifier collection. See RevenueCat’s privacy policy for its processing practices. To request help with purchase-related data, contact the publisher below. Deleting local counts does not cancel, refund or erase store transactions; financial records may have separate retention requirements.
Backups, sharing and reminders
Android app data is excluded from operating-system cloud backup and device transfer. iOS backups may include local app data according to platform settings; device-only credentials and widget cache files are excluded. You can export and restore your own JSON backup; these exported files are not encrypted by the app, so store them carefully. Share cards are rendered on-device and previewed before you choose a destination. The share composer includes your personal labels by default; turn off Show my personal labels to omit them. Cards show chosen target dates, which may still reveal personal information. Calculation details remain available in the app. Files you share are handled by the destination you choose.
Optional card backgrounds can use a photo you select from the system photo picker. The app stores a resized, re-encoded copy without the original photo metadata in its private local storage. Personal photos are not uploaded for account backup unless you explicitly enable “Back up card photos.” This account-level option saves private, optimized copies of selected card and default-appearance photos, not your photo library or originals. Copies restore on your signed-in devices and are not shared with connections. Turning it off stops uploads but retains existing cloud copies. “Remove cloud photo copies” immediately removes access and queues deletion after a 24-hour safety window; local copies remain. Account deletion also queues cloud-photo cleanup. Copies remain until you remove cloud copies or delete the account, even if you change a card's background. Together sharing is separate and uploads only explicitly shared copies accessible to the selected recipients. Photo files are not included in this app’s exported JSON backups. Sharing includes available card backgrounds by default. You can turn off Include card backgrounds before previewing. When enabled, the selected photos, event images or colors are rendered into the image you preview and share. Photos may identify people even when names are hidden. In Settings → Widgets, you can explicitly allow selected cards in local widget storage. Titles and small background previews are optional and off by default; each widget has separate display controls. Widgets may be visible on your Home or Lock Screen. Source birthdates, private goal notes and account credentials are not copied to widgets. Deleting a count removes its saved background and refreshes widget choices; deleting local data or the account removes saved backgrounds on this device. Operating-system backups may still include app data, and system photo-picker temporary caches are managed separately by the operating system.
Weekly reminders are optional, scheduled locally and use generic copy. You can remove your local profile and counters in Settings. This does not erase prior exports, shared images or operating-system backups. Signed-in accounts provide a separate account-deletion action.
Private event invitations and optional email updates
You can respond to a web invitation without an app account. The web response form asks for your name, email address and RSVP, with an optional phone number and note. These details are visible to the host and co-hosts. If the host enables the guest list, eligible guests can see attendee names and party sizes; email addresses, phone numbers and private notes are not shown in that list. Anyone holding your private invitation link can access that invitation and edit its response; do not forward it.
Hosts may also share a reusable event link. Anyone holding that link can view the event and submit a separate response. After responding, save your own private editing link; sharing the event link does not share your response. Hosts can close or replace the shared event link.
After a web RSVP, the invitation service may email a private return link and event details to the address you provided. This service email is separate from optional ongoing event updates and marketing.
Where email updates are available, you may choose to provide an email address after responding. We verify it before enabling important event changes and a day-before reminder. This is consent for that event only, not marketing or an account. Hosts and other guests cannot view your email address. We encrypt addresses in our database; Cloudflare Email Service processes the recipient address and message to deliver email. Your email links also let you reopen your response on another device.
Each email includes a link to stop updates without changing your RSVP. Stopping removes the stored address and recovery secrets. Unverified addresses expire after 24 hours; other event email records expire no later than the invitation expiry or seven days after the event date recorded when you subscribed. Cleanup runs periodically. Limited keyed identifiers are retained for up to 33 days for abuse prevention. Provider delivery logs and suppression records follow Cloudflare's retention. Email may be delayed by delivery problems or safety limits; check your invitation link for the latest information.
Shared content and notifications
When you share a card, publish an event or contribute to a celebration board, the service stores the content and access permissions needed to show it to the selected recipients or people holding the relevant invitation or board link. Hosts can moderate board contributions. People who receive content may keep copies; revoking access does not recall an image or file they already saved.
Optional push notifications use Apple Push Notification service on iOS and Firebase Cloud Messaging on Android. The service stores a device registration token linked to the current account session and notification preferences. Apple or Google processes delivery metadata and the notification payload. You can manage permission in system settings and notification preferences in the app. Local reminders are scheduled on your device.
Support and abuse reports
When you submit the support or report form, we receive your reply email address, your message, and the topic or report reference shown in the form. We use these details to investigate and respond to your request. The form does not automatically attach your private counts, photos, invitation links or account credentials. Please include only information needed to explain the problem.
Cloudflare processes delivery of form messages. Mail sent to support@countwhatmatters.com is forwarded to the publisher's Gmail inbox, where Google processes the email. Support correspondence is separate from app account data; deleting your app account does not automatically delete an email conversation. Contact the support address to request deletion of support correspondence.
Publisher
Count What Matters is being developed by Hakan Taymaz. For support or privacy questions, email support@countwhatmatters.com. Please avoid sending birthdays or other sensitive details unless needed to resolve your request.