Let’s Build Travel Plans

Privacy Policy

How the current local-first Travel Plans product uses your device and optional Apple services.

Last updated: 28 July 2026

Who operates the app

Let’s Build Travel Plans is developed by Brian Leary, referred to here as “we”, “us” or “our”. Privacy questions can be sent to support@letsbuildhq.com.

We do not sell personal information, use it for advertising, or track you across other companies’ apps and websites. The current Travel Plans V2 app does not require an account, Sign in with Apple login or Supabase account.

Local-first trip data

Trips, itineraries, packing items, costs, document references, traveller details, emergency contacts, family notes, settings and archive information are stored first in a versioned file in the app’s private Application Support area. The free experience is designed to work without a cloud connection.

You control the information you add. Avoid storing sensitive information unless it is needed for your trip and you are comfortable keeping it on the device or sharing it with invited participants.

Travel Plans Plus and iCloud

TestFlight build 37 can use Apple CloudKit for synchronisation, trip sharing, family chat and document-vault files. CloudKit uses the iCloud account configured on the device; we do not receive an Apple password or operate a separate Travel Plans account database.

  • Private data: your own synced trips are stored in your private CloudKit database.
  • Shared trips: Apple CKShare invitations allow participants to access the trip, messages and attached records shared with them.
  • Messages: chat messages are stored as CloudKit records associated with the shared trip.
  • Vault files: documents can be stored locally and, for Plus, synchronised as CloudKit assets.

People with access to a shared trip can see the information shared into it. Stop sharing or remove participants using Apple’s sharing controls when access is no longer appropriate.

Documents, camera and on-device recognition

If you choose to use the document vault, the app can import files or photos and can open Apple’s document-camera interface. Camera or photo access is requested only when you choose those actions. Apple Vision and PDFKit process document text on the device to support search and editable title/category suggestions.

On-device Apple Intelligence features

On supported devices running iOS 26 or later, Travel Plans can use Apple Foundation Models to structure pasted travel notes and provide calm, trip-specific checks. The implementation uses Apple’s on-device language model: the text and trip context supplied to these features are not sent to our servers or to Supabase.

Generated suggestions are checks, not verified travel facts. Review bookings, payment status, document validity and official travel information yourself.

Maps, notifications and sharing

  • MapKit: Apple MapKit may retrieve map imagery used for destination previews. The V2 implementation does not request your current location.
  • Notifications: Plus can schedule local reminders on the device. CloudKit may use silent push notifications to tell the app that shared data changed; we do not keep a Supabase/APNs device-token record for V2.
  • Exports: trip summaries, files and exports leave the app only when you use Apple’s Share Sheet or file controls and choose a destination.

Subscriptions and purchases

The current Plus plan offers monthly and annual auto-renewing subscriptions through Apple StoreKit. Each person who wants Plus subscribes individually; Plus is not inherited automatically from another family member. Apple handles billing, renewal, cancellation and payment details. The app reads verified entitlement status directly from StoreKit and does not mirror it to Supabase or another developer backend.

Deletion and retention

You can archive trips and use the app’s “Delete forever” control for archived trips. Local deletion removes the app’s stored trip and associated local vault files. For a Plus trip owned by you, the app also requests deletion of its CloudKit records and sharing record. Data already exported or copied by another participant is outside that deletion.

Deleting the app removes its local container but may not remove records previously stored in iCloud. Use the in-app deletion controls before removing the app, and manage iCloud data and sharing through Apple’s settings where applicable.

TestFlight and release status

Build 37 is the current verified TestFlight upload and includes the V2 data flows described above. We will update this policy if the release implementation changes.

Contact

Privacy questions: support@letsbuildhq.com. Product support: support@letsbuildhq.com.