TripStub keeps trip names, dates, expense amounts, categories, notes, and any receipt photos you add. All of it is saved locally in a private container on your device using Apple's on-device storage frameworks. None of it is uploaded to a server, because TripStub does not operate one.
TripStub asks for camera access so you can photograph a receipt, and photo library access so you can import an existing photo. Both are used only to attach an image to an expense you're creating — the photo is copied into the app's own storage and processed for text recognition entirely on your device, using Apple's built-in Vision framework. No image or receipt data is transmitted anywhere.
The Settings screen lets you optionally enter your name, email, phone number, or a payment note. This is used for one purpose only: printing it in the corner of a PDF expense report that you generate and choose to share. TripStub never reads your contacts, never sends this information anywhere on its own, and never shows it to anyone unless you personally export and share a report.
When you export or email a trip summary, the PDF is created on your device and handed to iOS's standard share sheet or Mail composer — the same system tool used by every app on your phone. Where that PDF goes after that is entirely up to you and whoever you send it to; TripStub has no visibility into or control over what happens next.
If TripStub ever adds a feature that changes this — such as optional iCloud sync — this policy will be updated first, and any such feature will be opt-in.
Since everything lives only on your device, deleting a trip or expense inside TripStub removes it immediately and completely. Deleting the app deletes everything else. There is no remote copy to separately request the removal of.
TripStub is a business expense tool and is not directed at children. It does not knowingly collect information from anyone, of any age, since it does not collect information at all.
Reach out any time at bsrossen@gmail.com — I read every message myself; there's no support team behind this, just the person who built the app.