Privacy Policy

TripDB is a personal travel organizer built for individual use. This policy explains what information the app collects, how it is used, and the choices you have.

Information we collect

Account & contact information. When you sign in with Apple, we receive a Firebase user identifier and, if you choose to share it, your Apple-provided email address. You may also enter a name, phone number, and nationality in your profile.

Trip and itinerary data. This includes trip names, destinations, dates, segment notes, day summaries, activity details, and booking information (airline, hotel, restaurant, car rental, confirmation codes, cost amounts, and currencies) that you enter into the app.

Location data. Airports, hotel addresses, restaurant addresses, and other places you manually enter when creating bookings or activities. TripDB does not access your device's GPS or collect background location data.

Photos. When you use the "Scan" feature to extract booking details from a confirmation photo, the image is compressed on your device and sent to our server solely to perform the extraction. The image is not stored after processing.

Information we do not collect

• Passport number — stored only on your device, never transmitted to any server.
• Background or passive location — we only store place names you type yourself.
• Payment card or bank information — we store trip cost amounts you enter, not payment credentials.
• Advertising identifiers or tracking data — TripDB contains no ads and no third-party tracking SDKs.

How we use your information

• Sync your trip data across your devices via Firebase Firestore.
• Allow you to share read or edit access to a trip with collaborators you invite by email.
• Extract structured booking details from confirmation photos you choose to scan (processed by Anthropic Claude, not stored).

Data storage and security

Your data is stored in Google Firebase Firestore under your authenticated user account. Firestore Security Rules restrict access so that only you (and collaborators you explicitly invite) can read or write your data. Data is encrypted in transit and at rest by Firebase.

Booking confirmation codes are stored as user-entered text. While they are scoped to your account, you should treat them as you would any sensitive reservation detail.

Third-party services

• Google Firebase — authentication (Sign in with Apple relay), Firestore database, and Cloud Functions. Firebase Privacy Policy
• Anthropic — processes booking confirmation photos on our behalf when you use the Scan feature. Images are sent for extraction only and are not retained. Anthropic Privacy Policy
• Apple Sign in with Apple — authentication. Apple may provide a private relay email address rather than your actual email. Apple Privacy Policy

Data retention and deletion

Your data is retained for as long as your account exists. You can delete all server-side data at any time by tapping Profile → Delete Account in the app. This permanently removes your Firestore data and Firebase account. Local SwiftData on the device is also wiped.

To request deletion without opening the app, email us at the address below.

Children's privacy

TripDB is not directed at children under 13. We do not knowingly collect personal information from children under 13.

Changes to this policy

If we make material changes to this policy, we will update the date at the top of this page. Continued use of the app after changes constitutes acceptance of the updated policy.

Contact

Questions or deletion requests: hello@tripdb.app