Privacy Policy for PetList

Reviewed informally — not a substitute for legal advice. This document was grounded in an engineering audit of what the PetList app actually does, and its identifying details (entity, contact, governing law) have since been filled in with real values. It has still never been drafted or reviewed by a qualified privacy lawyer. If you have concerns about its legal sufficiency for a particular distribution market, have it reviewed before relying on it as final.

Last updated: 2026-08-11

Overview

PetList ("the app") is a mobile app for organizing multi-pet household records — vaccination and deworming history, health event timelines, and expense tracking. This policy explains what information the app handles and, just as importantly, what it does not.

The short version: PetList stores everything you enter — your pets' profiles, health records, expenses, and photos — in a database on your own device. As of this writing, the app has no user accounts, does not send your data to any server the developer operates, includes no analytics or advertising SDKs, and includes no crash-reporting service. The only network activity the app performs on its own is checking for app updates (see "App updates" below).

Information the app stores

All of the following is entered directly by you and stored only in a local SQLite database on your device (via expo-sqlite), plus a local photos folder in the app's own document storage (via expo-file-system) for pet profile photos:

None of this is transmitted to the developer, to the developer's infrastructure, or to any analytics or advertising company, because no code path in the app sends it anywhere. It is not backed up to any cloud service by the app itself. If your device is lost, or the app is uninstalled, this data is not recoverable by the developer — the developer never had a copy of it.

Multiple pets/households: the app can organize records for more than one pet or (in principle) more than one household, but this is a purely local organizational grouping within the on-device database — it is not a shared or synced feature between different people's devices. Nothing about adding another pet or household sends anything off your device either.

Permissions the app requests

Camera and Photo Library

The app asks for camera and/or photo library access only when you choose to set or change a pet's profile photo. The photo you pick or take is copied into the app's own local storage on your device and displayed within the app. It is not uploaded anywhere. You can deny these permissions and still use every other feature of the app — a pet simply has no photo.

Notifications

The app asks for notification permission so it can remind you about upcoming health events and daily tasks. These are local notifications scheduled directly on your device by the app itself — the app does not use push notifications, does not register your device with any push notification service, and does not collect a device token or any other identifier for this purpose. You can decline or later revoke notification permission in your device's Settings; the app continues to show upcoming items in-app either way, it just won't alert you.

Exporting a vet summary

PetList can generate a PDF summary of a single pet's health records — identity details, logged health events, vaccinations, spay/neuter status, current medications and recent weight readings — and hand it to your device's own share sheet. It is reached from the "..." menu on that pet's profile screen and only ever runs when you tap it.

What happens, precisely:

What the app does not do

As of this writing, PetList does not:

App updates

PetList uses Expo's over-the-air update service (expo-updates) to check for and deliver app updates without requiring a full app store reinstall. As part of this, your device communicates with Expo's update servers, which — like any network request — necessarily involves standard technical information such as your device's platform and the app's current version/build. This is operational infrastructure for delivering app updates, not data collection by the developer, and no data from your pet/health/expense records is involved. This is a data flow to a third-party infrastructure provider (Expo), even though no app content is included in it — Expo's own privacy policy, covering their update/EAS service, is published at https://expo.dev/privacy.

Children's privacy

PetList is not directed at children and, based on the "What the app does not do" section above (no accounts, no analytics, no advertising), the app does not knowingly collect personal information from anyone, including children under 13 or the relevant age in your jurisdiction. This assessment is an engineering-level judgment, not a lawyer's review against COPPA (US) or any other applicable children's-privacy law for the app's actual distribution markets — treat it accordingly.

Data deletion

Because all data lives only on your device, you control its deletion directly:

There is currently no server-side copy for the developer to delete on your behalf, because none is ever created.

Changes to this policy

The current version of this policy is always published at https://h-canasa.github.io/petlist-legal/privacy-policy/. When it changes, the "Last updated" date at the top of this document will be updated to match. This app does not currently link to this policy or notify you in-app of changes to it; if that changes, this section will be updated to describe how.

Contact

Questions about this policy: petlist.app.support@gmail.com

This policy is issued by Harley Canasa, operating as a sole proprietorship (there is no separate registered company). No physical mailing address is listed, as none is currently required for this app's distribution markets; one will be added here if a specific market's requirements make it necessary.

Governing law

These practices, and this policy, are governed by the laws of the Republic of the Philippines, without regard to its conflict-of-law principles.