Privacy Policy

1. No account, no sign-in

TripBoard has no user accounts. You don't create a profile, hand over an email, or log in. We don't assign you an identifier, and we don't have a server-side record of who you are. Because there's no account, there's nothing for us to leak, sell, or hand over.

2. What we store and where

Everything you create in TripBoard — your trips, your saved places, their names, categories, notes, and map coordinates — is stored locally on your device.

If you have iCloud enabled, that data syncs across your own devices using Apple's CloudKit private database. It travels inside your personal iCloud account, governed by Apple's privacy terms. We never see it, can't read it, and have no copy of it on our infrastructure.

The app also keeps a small amount of local app data — such as your settings, your monthly AI usage count, and a temporary inbox of items you've just shared — in standard on-device storage (UserDefaults and an app-group container). This never leaves your device.

3. Precise location

With your permission, TripBoard uses your precise location for two things, both of which happen on your device:

• Showing what's nearby — so the app can surface places near you and tell you how far away a saved spot is.
• Biasing search — so when the app looks up a venue, it prefers results in the area you're actually in.

Your location is used in the moment to power these features. It is never sold, never shared with advertisers, and never used to build a profile or to track you across apps or over time. You can revoke location access at any point in iOS Settings; the app keeps working without it, just without the nearby and distance features.

4. Sharing a link or screenshot

The core of TripBoard is sharing a place to it — a link from Instagram, TikTok, or Maps, or a screenshot — and having the app figure out the real venue and pin it for you. To do that, the app sometimes needs help identifying the place.

TripBoard first tries to resolve the place entirely on-device (for example, by reading coordinates straight out of a Maps link, or using Apple's on-device intelligence). When that isn't enough, the derived text and image content from what you shared — the page's title and description, and any text read from the screenshot — may be sent to our backend proxy, which forwards it to Anthropic's Claude API purely to extract the venue name and location.

Anthropic processes this request under its own privacy policy and API terms, which prohibit using API inputs to train models.

5. What we never do

• We never sell your data.
• We never use your data, location, or shared content for advertising or cross-app tracking.
• We don't include third-party analytics SDKs, ad networks, or tracking pixels.
• We don't build a profile of you, and there are no tracking domains contacted by the app.

6. Third-party services

TripBoard relies on a small set of services to function:

• Apple iCloud / CloudKit — syncs your trips and places within your own iCloud account.
• Apple Maps (MapKit) — powers maps, place lookup, and reverse-geocoding.
• Anthropic Claude API (via our proxy) — identifies the venue from shared links and screenshots, as described above.
• Apple App Store — handles any subscription purchases and billing. We never receive your payment details.

Each of these processes data under its own terms; we only send what's needed for the feature to work.

7. Children

TripBoard is intended for a general audience and is not directed at children under 13. We do not knowingly collect personal information from children. Since the app has no accounts and stores data only in your own iCloud, no personal data is gathered by us in any case.

8. Data retention & your control

Because your data lives on your device and in your iCloud, you control it. Delete a place or a trip and it's gone from your devices on the next sync. Delete the app and remove its iCloud data from iOS Settings to wipe everything. We hold no separate copy to delete on your behalf.

9. Changes to this policy

If we change how TripBoard handles data, we'll update this page and revise the "Last updated" date above. Material changes will be reflected here before they take effect.