Private by design
The current app requires no account and has no advertising or third-party analytics. Journal records and kit photographs are stored locally on the iPhone.
| Account | No account or sign-in is required. |
|---|---|
| Journal storage | Drink, wee and medication entries are held locally in the app’s SwiftData store on the iPhone. |
| Kit photographs | Stored locally with the kit item. Photo preparation and optional foreground extraction happen on-device. |
| Advertising | The app contains no advertising. |
| App analytics | The current app does not include third-party analytics. |
| Cloud journal | There is no CloudKit journal or Pee & Pour account server. |
The Watch companion and iPhone app communicate through Apple’s WatchConnectivity framework. Pee & Pour uses current-state updates, immediate messages and queued background transfers depending on whether the paired device is reachable.
The iPhone remains the journal’s source of truth. The Watch receives current-day totals and named kit details; it does not receive kit photographs or the complete historical journal.
Apple Health integration is optional. After the user grants permission, eligible new water entries can be written to HealthKit.
Apple Health has no suitable urine-volume record type, so wee entries stay in Pee & Pour. Medication journal notes are not sent to Apple Health. HealthKit samples are not included in a Pee & Pour backup or recreated during restore.
The widgets receive only a small aggregate snapshot through the private App Group: today’s intake, output, output count, daily reference and generation time.
They do not receive individual records, timestamps, notes, medication, vessel names or photographs. Numeric values are marked privacy-sensitive so iOS can redact them according to the device’s widget privacy behaviour.
A PDF is created only when the user invokes the report action. The app then hands the file to the native iOS share sheet, where the user chooses the destination.
After that choice, the selected destination, such as Files, Mail, Messages, AirDrop or an installed third-party extension, controls its own copy. Reports can contain sensitive journal information, so the recipient and save location should be checked carefully.
A `.pap` file is a versioned JSON backup containing the complete local journal, kit records, photographs, background-removal and framing state, plus relevant preferences.
Export is explicit. Import validates the file and asks for confirmation before replacing the current local journal and kit. The file itself is not encrypted by Pee & Pour, so it should be stored and shared carefully.
Individual journal and kit records can be deleted inside the app. Removing the app from the iPhone removes its local app container according to iOS behaviour. A separately exported PDF or `.pap` file must be deleted from its chosen destination separately.
This initial static website does not load advertising pixels, third-party analytics or third-party web fonts. Standard server logs may still be created by whichever hosting provider is selected. This wording must be checked against the final hosting configuration before public launch.
Last reviewed: 25 October 2026. A formal privacy policy and confirmed privacy contact must be added before the public App Store release.
