Privacy Policy
Last updated: November 13, 2026
Petpet is designed around a quiet promise: the journal you keep about your pet belongs to you, and should feel that way.
This page explains, in plain English, exactly what information Petpet handles, where it goes, and how you can control it. If anything here is unclear, please write to the support address at the bottom.
The short version
- No Petpet-owned backend. Nothing you write in Petpet is sent to a server we operate.
- Your journal lives on your device. If you turn on iCloud sync, it writes to your own Apple ID container only — not to us.
- HealthKit is read-only. Petpet reads step count and walking distance to frame “Walks together.” We never write to HealthKit, and this data never leaves your device.
- AI Poetize is BYOK. When you use the optional AI Poetize feature, your note goes directly from your device to the AI provider whose API key you supplied. Petpet does not route, log, or copy that content.
- No ads, no tracking SDKs, no sign-up.
- Opt-in diagnostics only. Analytics and crash reports are off by default and share a single switch. If you turn them on, Petpet sends anonymized, bucketed event counts to TelemetryDeck and crash reports to Sentry — never pet names, never photos, never any text you wrote.
- Purchases via RevenueCat. In-app purchases are validated by RevenueCat. Only Apple’s signed receipt, the product identifier, and an anonymous RC-assigned user ID leave the device. No journal data, no device identifiers.
- Children under 13. Petpet is intended for ages 4+ but is not directed at children under 13. Please keep Petpet off a child’s device if you are concerned about data minimization.
If you want the full details, keep reading.
What Petpet stores on your device
Petpet uses Apple’s Core Data framework to store every piece of your journal locally:
- Pets: name, species, breed, birthday, adoption day, microchip, allergies, veterinarian, cover photo reference.
- Entries: title, body, kind, timestamp, tags.
- Photos: image data (originals + thumbnails), optional captions.
- Weight logs: value in kilograms, date, note.
- Vaccine records: vaccine name, date, next due date, notes.
- Medication records: name, dose, schedule, active flag, notes.
All of this lives inside Petpet’s own on-device database. It is never automatically sent anywhere.
iCloud sync
Petpet uses NSPersistentCloudKitContainer so your
journal can synchronize across your iPhone and iPad. This is
Apple’s standard end-to-end-encrypted sync; the data
moves between your devices through your
iCloud account.
- We cannot see it. Petpet does not run any CloudKit server; the “backend” is Apple’s CloudKit on your behalf.
- You control it. You can turn Petpet’s iCloud container off in Settings → [your Apple ID] → iCloud → Petpet on any of your Apple devices.
- Simulator / dev builds: iCloud is disabled by default in developer builds; only released builds sync.
HealthKit
Petpet reads two HealthKit data types to power the “Walks together” feature and the Insights activity card:
- Step count
- Walking + running distance
That is all. Petpet does not request write access, cannot write to your Health store, and the data is never transmitted off your device. Turn it off in Settings → Activity → Walks together, or revoke it in the system Health app.
AI Poetize (BYOK)
AI Poetize is optional and requires you to provide your own OpenRouter API key.
When you use it:
- The entry body you are rewriting, plus your pet’s name for context, is sent in a single HTTPS request directly from your device to openrouter.ai using the key you provided.
- OpenRouter forwards the request to the model you chose (Claude 3.5 Haiku by default).
- The rewritten text comes back to your device and never leaves it unless you choose to share it.
Petpet does not see, log, or route any of this content. Your API key is stored in the iOS Keychain on the device that added it — not in iCloud, not synced across devices.
OpenRouter and the underlying model provider have their own privacy policies and data-use terms. You can review them here:
- OpenRouter: https://openrouter.ai/privacy
- Anthropic (Claude): https://www.anthropic.com/legal/privacy
Purchases
Petpet’s in-app purchases (Pro Monthly, Pro Annual, Lifetime) are processed by Apple and validated via RevenueCat, a purchases infrastructure provider that handles receipt verification and entitlement bookkeeping on Petpet’s behalf.
What Apple sees
The payment itself is handled entirely by Apple and the credit card you have on file with your Apple ID. Petpet does not see or store your payment information.
What is sent to RevenueCat
When you complete a purchase or tap Restore:
- Apple issues a signed receipt that is tied to your anonymous App Store transaction.
- The Petpet app forwards that receipt, along with the product identifier (
com.xun.petpet.monthly/.yearly/.lifetime) and an anonymous RC-assigned user ID, to RevenueCat’s servers. - RevenueCat validates the receipt and returns the active entitlement (
pro) back to the app.
That is the complete set of fields that leaves the device for a purchase. No pet data, no journal content, no Apple account identifiers, and no device identifiers like IDFA / IDFV.
Identifier
The RC-assigned user ID is created locally by the RevenueCat SDK on first launch and stored on your device. It is not linked to your real identity, not shared with ad networks, and is reset on app uninstall.
Provider
RevenueCat’s privacy policy is at https://www.revenuecat.com/privacy. RevenueCat does not use purchase data for advertising and does not sell purchase data to third parties.
Diagnostics (opt-in)
Diagnostics are off by default. If you turn on Settings → Diagnostics → Help improve Petpet, Petpet begins doing two things: emitting bucketed event counts so we can understand which features matter, and sending crash reports so we can fix bugs that shipped. Both are governed by the same switch.
Analytics · what is sent
A small, fixed set of event types, each with no raw content:
app_launch— nothing.pet_added— species (dog / cat / other).entry_added— kind (note / photo / weight / vaccine / medication / mood / walk).walk_started— nothing.walk_ended— duration bucket:<5m,5-15m,15-30m,30-60m,>60m.paywall_shown— which surface opened it (settings, multi-pet, lifetime-book, walks-live-activity).purchase_success— product ID (monthly / yearly / lifetime).recap_viewed— nothing.ai_poetize_used— nothing.book_exported— nothing.
Analytics · what is never sent
- Pet names.
- Entry titles.
- Entry bodies.
- Photos or image data.
- Raw walk durations (only buckets).
- Which month a recap was for.
- Any exact timestamps beyond when the event was received by TelemetryDeck.
- Your IP address beyond what any HTTPS request contains in transit.
- Any Apple identifier that could be linked to your Apple ID.
Analytics · identifier
Petpet attaches an opaque clientUser string to
each event: the SHA-256 hash of your device’s vendor
identifier (Apple’s identifierForVendor).
This is:
- Pseudonymous. It cannot be reversed to your Apple ID or any personal identifier.
- Vendor-scoped. The vendor ID is unique to Petpet; no other developer sees the same value.
- Resettable. Uninstalling and reinstalling Petpet changes the vendor ID, and therefore the hash, to a brand-new value.
Analytics · provider
Events are sent to TelemetryDeck, an EU-based, privacy-first analytics provider. TelemetryDeck’s own privacy policy is at https://telemetrydeck.com/privacy. TelemetryDeck does not use cookies and does not sell data to third parties.
Crash reports · what is sent
When the Diagnostics switch is on and the app crashes or hits a non-fatal error Petpet wants a heads-up about, a single crash envelope is sent to Sentry, Petpet’s error-monitoring provider. The envelope contains:
- The crash signal and stack trace (file names and line numbers in Petpet’s own binary, plus the system libraries involved).
- Device type (e.g. “iPhone 17 Pro”), iOS version, and free disk space at the moment of the crash.
- App version and build number.
- A categorical tag naming the operation that failed, for non-fatal reports only (e.g.
non_fatal: core_data_save).
Crash reports · what is never sent
- Pet names, entry titles, entry bodies, photos, or any journal content.
- Breadcrumbs that originated from any user-interface event (
ui.*breadcrumbs are dropped before the envelope is built, because SwiftUI accessibility labels can include a pet name). - IP address beyond what any HTTPS request contains in transit; Sentry’s default
user.ip_addressfield is explicitly cleared. - Email, username, or any other user-object fields.
- Any Apple identifier that could be linked to your Apple ID.
- HTTP request bodies, cookies, or
Authorization/Cookie/X-Api-Keyheader values; these are redacted to[redacted]before the envelope is built. - URL query-string parameters named
api_key,apikey,token,access_token,authorization,dsn,secret, orkey; their values are replaced with[redacted].
Crash reports · provider
Reports are sent to Sentry, an error-monitoring provider. Sentry’s privacy policy is at https://sentry.io/privacy. Sentry processes crash reports as a data processor on Petpet’s behalf, does not sell crash data to third parties, and does not use Petpet’s crash data for its own product analytics beyond aggregate SDK telemetry.
Crash reports · retention and lifecycle
- Opt-out is absolute. Petpet starts the Sentry SDK on every launch so crash handlers are armed, but every outgoing event is dropped by an in-app
beforeSendfilter until the Diagnostics switch is on. There is no “queued while opted out” path. - Sessions are disabled. Sentry’s optional per-launch session pings are turned off, because those envelopes bypass the opt-in filter.
- Performance / tracing is disabled. Petpet does not emit spans, tracing, or performance envelopes.
Turning it off
Settings → Diagnostics → Help improve Petpet. The toggle takes effect immediately. No further events or crash reports are sent until you turn it back on.
Permissions Petpet may ask for
- Photo Library: to attach photos to entries. Required only if you use the photo attach action.
- Notifications: for vaccine reminders, if you opt in.
- HealthKit: for Walks together, if you opt in.
Petpet does not ask for Camera, Location, or
“Add to Photo Library” permissions. The binary
ships without the matching NSCameraUsageDescription /
NSLocationWhenInUseUsageDescription /
NSPhotoLibraryAddUsageDescription strings; grep
the source and you’ll find no AVCaptureDevice,
no CLLocationManager, and no
UIImageWriteToSavedPhotosAlbum anywhere in v1.
You can revoke any permission at any time in iOS Settings → Petpet.
Data export and deletion
- Export (Petpet Pro). Pet Profile → Create Lifetime Book generates a keepsake PDF of a pet’s journal entries. The PDF is rendered entirely on-device and handed to the system share sheet.
- Export (JSON archive). A full-journal JSON archive is planned for a future release and will land as “Settings → Data → Export.” Today, the Settings → Data → Export row shows “Coming soon.”
- Delete your Petpet journal. To remove every Petpet record from your device, uninstall the app from iOS (long-press the icon → Remove App → Delete App). The local Core Data store is deleted as part of app removal.
- Delete from iCloud. If you had iCloud sync on, the records also live in your iCloud account. iCloud Settings → Manage Storage → Petpet → Delete Data wipes them from your iCloud container. Alternatively, signing Petpet out of iCloud under Settings → [your Apple ID] → iCloud → Petpet before uninstalling leaves the device copy intact but detaches it from sync.
- An in-app “Erase all data” action is planned alongside the JSON export in a future release.
Children
Petpet is rated 4+ and contains nothing objectionable, but it is not directed at children under 13 and does not knowingly collect any information from children under 13.
Changes to this policy
If the privacy posture changes (adding a new provider, adding a new analytics event, changing retention), this page is updated and the new “Last updated” date at the top reflects the change.
Material changes — anything that broadens what we collect or where it goes — will also be surfaced in-app on next launch via a small sheet so you can review before continuing.
Contact
If anything on this page is unclear, or you want to exercise a privacy right under GDPR, CCPA, or similar regulation:
Email: privacy@petpet.app
Please allow up to 30 days for a response.