How We Handle Your Tripsy Data

At Tripsy, we take your privacy and security seriously and our goal is to be good stewards of the data you entrust us with about your travel plans.

Whilst this isn't an exhaustive deep-dive into the technical details of our architecture, we hope it gives you the confidence in our processes and security practices.

Your Tripsy Account

  • A Tripsy account is always optional. If you don't want to use any of our syncing or sharing features, including email forwarding, the calendar feed, and don't need to sync your data between multiple devices then you don't need to sign up for an account and can use the majority of Tripsy's features without an account.
  • If you do sign up, Your Tripsy account is protected with either:
    • Your Apple ID details if you used our 'Sign in with Apple' feature.
    • Your email address and chosen password if you're using a regular login. We strongly encourage the use of a randomly generated password with a suitable password manager such as Apple's Passwords app, 1Password, or BitWarden (there are many other wonderful options, these are just the three that instantly come to mind).
  • You can delete your Tripsy account at any time, all of your data will be removed from our servers and the only copy of your Tripsy data would be on any devices you had previously synced with.

Data Storage

  • All of your Tripsy data is stored on our own servers, which are hosted by AWS (Amazon Web Services) in their US East region.
  • Access to our servers are only possible by means of authorized encryption keys, which are securely stored and access controlled so that only the appropriate team members have access.
  • All data is backed up on a regular basis.

Third Party Data Processing

We try to keep third-party access to your Tripsy data as limited as possible, but in order to provide you with many of our features we may need to use third-party data and services such as APIs.

General Features

  • We use both Apple Maps and the Google Places APIs to find locations when adding new activities within Tripsy. None of your Tripsy account data is shared with either provider.
  • We use the native MapKit access to Apple Maps to find routes between locations when using our travel routes features.
  • If you choose to connect Tripsy to an AI tool via our MCP server, then:
    • The provider of that tool will authorise your Tripsy account via OAuth and once authorised will have a token for API access which is tied to your Tripsy user account.
    • Should you wish to revoke any of your tokens for specific tools, just contact us via Settings > Talk to Us and let us know which service you wish to revoke access to and we can remove the token for you.
    • The AI tool in question will be able to request your permission to read or write selected data to and from your Tripsy account.

PRO Features

  • Any emails you forward as part of Tripsy's automation features are processed first by our email parsing partner and these raw emails are then deleted after 14-days. We set this timeframe to allow us to flag any parsing errors with the provider.
    • Our email parsing partner has no access to your Tripsy data, or any information about your account, they simply have access to the email itself in order to process this to provide us with the relevant data to create activities for your trips.
  • To enable flight alerts we will send the flight number and departure date and time to our flight data providers in order to provide you with updates and alerts on your flights within Tripsy - no other flight or reservation information is sent.
  • If you subscribe to the Calendar Feed then depending on the calendar application or service, this provider may have access to your calendar data as presented. They would not have any direct access to your Tripsy account, and you can prevent certain information from being shown on the calendar feed.
  • If you're using our TripIt import feature, this is a one-way (from TripIt to Tripsy) import only, and so no Tripsy data is sent to TripIt - we authenticate with your TripIt account and the appropriate authentication token is stored in your Tripsy account to allow future imports to take place.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.