Last updated: 14 September 2026
Count is an iPhone and iPad app developed and operated by James Storer, the controller responsible for personal information handled by the Count service. For privacy questions or requests, contact james@jamesstorer.com.
This policy covers the Count app and its account service. Apple, Google and the website hosting this page may also process information under their own privacy notices.
Information Count handles
Moments and photos. Count stores the moments you create or import, including titles, dates, notes, categories, recurrence, reminder settings, collections, appearance choices and photos you select. It also stores record identifiers and update/deletion information needed for syncing. This information is saved on your device and shared with Count's widget extension so the app and widgets can work offline.
Optional account information. If you sign in with Apple or Google, Count receives identity information supplied by that provider, such as your email address, provider account identifier and available profile information. Apple may supply a private relay email address if you choose Hide My Email. Authentication records include session information and may include IP address and user-agent information for account security. Count does not receive your Apple or Google password. The app stores its Count session credential in Apple's Keychain.
Cloud sync. When you sign in, your saved moments and selected photos are uploaded to your Count account. This includes existing local moments adopted on first sign-in and saved moments imported from calendars. Cloud data is linked to your account and used to restore and sync your library.
Calendar information. If you connect a calendar, Count reads calendar information on your device or through Google's Calendar API to show available events and refresh saved imports. This can involve reading calendar lists and events beyond the ones you ultimately select. Only selected events are saved as moments and included in Count account sync. Saved imports contain their title, date, all-day status, calendar source and external identifiers; a Google calendar identifier may contain an email address. Count does not write changes to your source calendars.
Purchase information. Apple processes purchases. Count uses verified transaction information, including product and transaction identifiers, purchase status, expiry and revocation information, to provide and restore Count Plus. When associated with a Count account, entitlement records are stored by the Count service. Count does not receive your payment card details.
Photo search. Searching free photos sends your search words and page requests through Count's API to Unsplash. Count temporarily caches search results. Selecting an Unsplash photo sends its selection to Unsplash's download-reporting endpoint; thumbnails and selected images load from Unsplash's image service. These providers can receive technical request information such as IP address. The selected photo, its photographer credit and source links are saved with your moment and included in account sync. This feature also works without a Count account.
Google sign-in SDK. Google's bundled sign-in software declares collection of profile information (including name, email and phone number), approximate location, user and device identifiers, usage information and other technical data for sign-in functionality and, for certain identifiers and usage data, analytics. Count itself does not ask you to enter a phone number or request device-location permission. The SDK declares that these data are not used for tracking. Google's processing is also covered by its privacy notices.
Support and service information. If you contact support, we receive your email address and the information you include. Authentication and hosting services may process technical information such as IP addresses, request times and error information to deliver and protect the service.
How information is used
Information is used to display your moments and widgets, schedule reminders, import and refresh chosen calendar events, authenticate your account, sync your library, verify purchases, answer support requests and maintain service security.
Count does not use advertising SDKs or cross-app advertising tracking. We do not sell your personal information or use your moments, photos or calendar information for targeted advertising. Count does not use Google user data to train general-purpose AI or machine-learning models.
Where UK or European data protection law applies, the legal bases are performance of our contract with you for the features you request; legitimate interests in providing support and keeping the service secure; consent where required for optional access or processing; and compliance with applicable legal obligations. You can withdraw optional permissions at any time. This stops future access but does not automatically erase information already saved.
Permissions and your choices
You can use Count without creating a Count account. In that case, your moments are not uploaded to Count's account service. Optional Google Calendar connections and Apple purchases still communicate with those providers when used.
Photo selection uses Apple's system photo picker. Count receives the photos you choose, rather than general access to browse your photo library. Selected photos are resized for use in the app and are synced if you sign in.
Calendar access is optional and used read-only, even where Apple's permission wording grants broader access. You can revoke access in your device's Settings or through your Google Account connections. Count's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Notifications are scheduled locally. You can change notification permissions in device Settings. Event titles and photos can be visible in widgets, notification previews or content you choose to share, depending on your settings and sharing choices.
Service providers and sharing
Count uses Vercel to host its API and Neon to store account, authentication, event/photo and purchase-entitlement data in Postgres. Better Auth is the authentication software running within that service. Apple and Google provide the sign-in, calendar or purchase services you choose to use. Unsplash provides optional photo search, image delivery and photo-selection reporting.
These providers process information needed to deliver their services. We may also disclose information where required by law or necessary to protect users and the service. If you share a moment through your device's share sheet, the recipient or service you select receives the content you choose to share.
Service providers may process information outside your country, including outside the UK or European Economic Area. Where legally required, international transfers must be covered by an applicable adequacy decision or appropriate contractual safeguards. Contact us for information about the safeguards relevant to your data.
Storage, retention and deletion
Active account data is retained while your account remains open so Count can provide syncing and account features. Deleting an individual moment hides it from your library but retains its record, including its content and photo, to synchronise the deletion across devices. These records currently remain until account deletion; removing a moment is not immediate permanent erasure of its stored content.
Use You → Delete account while signed in to remove your account, synced moments and photos, sessions, provider account records and purchase associations from the live Count service. If you cannot sign in, contact james@jamesstorer.com for assistance. We may verify your identity before acting on a request.
Signing out hides the current library and retains an archived local copy. Account deletion also signs you out; it does not purge every archived copy on your devices. Removing the app's local data removes those local files. Device backups may contain earlier copies and are managed through your device or backup provider. Uninstalling Count alone does not delete its server-side account data.
Deleted server data may remain in provider backups until those backups expire under the configured retention settings. Operational and security logs, and support correspondence, may be retained separately for the time needed for security, troubleshooting, resolving requests or applicable legal obligations. Contact us for the retention information applicable to a specific request.
Apple retains its own purchase records under its policies. Deleting your Count account does not cancel an Apple subscription; manage or cancel it through Apple.
Security
Count uses HTTPS for app-to-service communication, device storage protections, Keychain storage for its Count session credential, and authenticated access to account data. Cloud sync is not end-to-end encrypted: the service processes readable event and photo data to provide syncing. No storage or transmission method can guarantee absolute security.
Your rights
Depending on where you live, you may have rights to access, correct, erase or receive a portable copy of your personal information, restrict or object to certain processing, and withdraw consent where processing relies on consent. Contact james@jamesstorer.com to exercise these rights. We will respond within the timeframe required by applicable law.
You may also complain to your local data protection authority. In the UK, this is the Information Commissioner's Office.
Changes to this policy
This page will be updated when Count's data practices change. The date above identifies the latest revision. Where required, we will give additional notice of significant changes.