Cat Passport

Privacy

Last updated 22 November 2026.

Cat Passport is run by Franky, an independent developer in Victoria, Australia. Questions about privacy go to support@cat-passport.com.

On your iPhone

You can keep household and cat records without signing in. The app stores the records, local reminders, settings, generated cat art and caches on the device. The widget reads and records care in shared local storage. If you sync your household, the app can later upload care recorded in the widget. The scanner reads a food barcode. It does not save a camera recording. A backup you export is a separate file containing your records and selected app settings. You choose where to save or send it.

Sign-in and household sync

Google sign-in asks for an OpenID identity with no email or profile scope. Apple sign-in requests no name or email scopes. The app sends the provider’s ID token, a sign-in nonce and a random sync device ID to our service. The service verifies the token, stores its stable provider identity with an internal account ID, and returns an account session. It ignores an email claim. The app keeps session credentials in the iPhone Keychain. Google and Apple handle their own sign-in screens.

After you sign in and link or join a household, the service receives household and member names, account and record IDs, household time zone, cat profiles with birth dates and drawn looks, foods and pack details, stations, routines, care history, servings, amounts, observations, food choices and notes included in synced records. This includes foods marked bought and buy-again answers. Other household members can see the synced records. Local-only preferences and unsupported records stay on the device. A household invitation uses a token in the link.

Use Household to delete your account. The service ends your access and keeps a household available to other members when applicable. When no other eligible member remains, it deletes the online household. The app keeps the current phone’s copy of its records.

Household notifications

If you turn on “When someone else feeds”, the service keeps this phone’s Apple notification device token with your account to deliver alerts. Switching it off or signing out online removes this phone’s token. Deleting your account removes its tokens.

Your phone puts the words of the alert together using names already on the phone. Apple’s notification service receives the device token, a generic care alert, and codes for the household, the member or sitter, the cats and the routine, along with the kind and time of care. Member, cat and meal names stay in the alert on your phone.

Sitter links

Anyone with an active sitter link can open the care sheet in a browser without installing the app or signing in. It shows the household name, when access ends, and today’s cats and care tasks in the household’s time zone. Depending on the task it shows a station name, what food and amount to serve, foods the cat tends to refuse, and who completed a task and when. The browser also receives cat, task and event IDs and the latest intake result where present. The sheet gives access to today’s care only. Shopping lists, account details, photos, private notes and past care history are outside its scope.

The browser sends the secret token with each request. When a sitter marks a task done, notes whether the cat ate all, some or none, changes that answer or undoes their own task, the browser sends the relevant task or event ID, the cat ID where applicable, and the selected answer or a request ID for a new completion. The service records the care action and time, any associated serving and the intake answer in the household’s care history under the link’s sitter identity. A household member can see these records. The page uses no analytics or sign-in cookies. The service stores a hash of the link token and uses separate, short-lived hashes of the token and part of the network address for request limits. The raw token is never stored or logged by the service.

An owner or member in a shared household can use Invite a sitter in the app to choose a sitter display name and an end date, share the link and end access early. The service keeps the sitter label, internal ID and link record after access ends so earlier care can still show who did it. These records are removed when the online household is deleted. The app passes the link to the system share sheet and does not retain the token. Owners and members can end an active link from the People list.

Shared shopping list

For the shared shopping list, the household service stores an item ID and either a catalogue product ID or a household food ID, an optional cat ID, and whether the item is to try or to buy again. It records which signed-in member added the item and when, who marked it bought and when, and when it was updated or removed. Other household owners and members can receive these records, with display names for the people who added or marked items. Sitters cannot access the list. Clearing a bought mark clears the buyer and date on the item. Removed items carry a removal date so other devices can remove them from their lists.

This app build does not submit changes to or display the shared list. If the household already has a list, the service can include its records in sync responses. This version does not use those records. Its separate “Want to try” feature stays on the device.

Catalogue and community

Product details come from Open Pet Food Facts, under the Open Database License, and from product pages on the web. Pictures are shown from their source.

Catalogue requests use a random quota ID and the device’s UTC offset. Searching sends the words you type and can send your country. Barcode search sends the barcode. Suggestions and comparisons with similar cats can send selected food preferences such as protein groups and textures. The app loads product pictures from their source addresses and can request a preview of a product page when needed. The hosts receive the usual details of a web request.

If you turn on trial sharing, selected trial tallies, age stage, food preferences, buy-again answers, product IDs and random sharing keys can be sent. A product proposal sends the printed food and pack details, barcode and country if known. Posting a community page shares a generated nickname and look, cat kind, age in years and country if known, plus selected food counts and tastes. Reactions use the random quota ID. Reporting a page sends its ID and a reason from a fixed list.

For a page, proposal or report, the service keeps a keyed hash of part of the network address alongside an identifier derived from the posting or reporting device’s quota ID or sharing install ID. A keyed hash is a code made using a server secret. The network part is an IPv4 /24 or IPv6 /64. The service uses these codes to count separate networks. The address itself is not stored in these records.

“Delete everything shared from this phone” removes contributions and proposals, closes the phone’s pages, and removes indexed reactions and reports with their stored keys and hashes. Reactions created before the service began indexing them may stay counted until their page closes. Deleted sharing data can remain in database backups for up to 35 days.

Online lookups

The app asks for permission before its first online lookup, summary or label read and remembers your approval. An online lookup sends the product words you entered or a barcode, and the country if available. The service can briefly associate the lookup with a hash of the device’s quota ID while the job is pending, and caches results by normalized search words or barcode and country. Summaries and label reads send catalogue product IDs, with language or country where used. For a job that needs Anthropic’s AI service, our service sends the lookup words or barcode, or sends catalogue product details for a summary or label read. These requests include country or language where applicable. A label read can also send the address and text of a public product page. The service does not send your household records, account or quota ID to Anthropic.

Diagnostics and usage

If an operation fails, the app can send fixed health codes and counts with the app version, iOS major version and database schema version. A low-space result from checking free space stays in the on-device history. These batches have no app identifier and are sent regardless of the usage switch. Our service writes health events to its logs and uses a keyed network hash for rate limits.

Usage counts are on by default. In Household → Usage counts you can see the event list and turn them off. Once a day the app can send counts from that list, the app version, the age of this install in days and a random ID made for usage only. Our service logs the batch. Purchase-related counts cover AI allowance used up, subscription screen opened, Plus opened from Household, allowance or auto mode, purchase started, purchase completed, Restore purchases tapped, free trial started, and free trial became paid. Neither batch contains a name, a record or typed text. Turning usage off clears queued counts and removes the usage ID from the phone.

Report a problem previews your app, iOS and schema versions, recent health codes and times, free space and whether sharing is on. You can add a note. The app opens your mail composer or copies the text for you. The app sends no problem report automatically.

Where data is processed and for how long

Our service runs on Amazon Web Services in Sydney, Australia. Service logs are kept for 90 days and then deleted. Daily database backups are kept for 35 days. Online lookups, summaries and label reads are processed by Anthropic’s Claude models, which receive the request text but no account or household identifiers. Google and Apple handle their own sign-in. The website is served by Cloudflare.

We do not sell your data and do not use it for advertising.

Contact

Write to support@cat-passport.com with any question about your data, or to ask for a copy or deletion that the app’s own controls do not cover.