Skip to content
TripPass
Request demo

Security & privacy

Your customers' information stays yours.

TripPass holds trip and event information about real people, so the boring parts matter. Here is plainly how it is kept separate, kept private, and kept out of reach.

Isolation

One account cannot reach another

Separation is enforced at the database layer on every table, not by remembering to filter in the application. A request for another account's rows comes back empty.

Access

Private links, no passwords

Passengers and attendees never create an account. Each link carries a long random token scoped to a single trip or session, and expires on a schedule you set.

Assistant

Margo is scoped, not open

Each version of Margo can only reach what its experience needs. She refuses attempts to change her behaviour and hands account questions to verified support.

The practical detail

How data is protected

  • Row-level isolation on every account-owned table
  • Public endpoints are token-scoped and read only what that token owns
  • Incoming webhooks are signature-verified before anything is written
  • API access uses per-account keys you can revoke at any time
  • Every import, change and access is recorded for audit
  • Traffic is encrypted in transit; data is encrypted at rest

What TripPass will not do

  • Sell or share your customer data with anyone
  • Use one account's information to answer another account's questions
  • Show a partial page for an expired or invalid link
  • Expose a driver's personal number unless you have chosen to
  • Contact your customers under our own name

Questions

The ones procurement always asks.

Can another company see my data?

No. Every record belongs to one account, and that rule is enforced in the database itself rather than only in the application. A request carrying another account's identity returns nothing, not a filtered list.

Are the passenger and attendee links private?

Each link contains a long random token that is not guessable and is tied to a single trip or attendee session. Links can be expired on a schedule, and an expired or invalid link shows nothing at all — not a partial page.

Do passengers or attendees have to create an account?

No. There is no signup and no password, which means there is no account for anyone to break into and no credential for your customer to lose.

What data does TripPass hold?

Only what you send: the details of the trip or the event, and the contact information needed to deliver the link. TripPass does not sell data, does not share it between accounts, and does not use one customer's information to answer another's questions.

Can Margo be tricked into revealing something?

Margo can only reach the information in scope for the experience she is answering inside. Instructions typed by a visitor trying to change her behaviour are refused rather than followed, and account-specific requests on the public site are routed to verified support instead of answered.

Need this in writing for a review?

Ask and we'll walk your team through the architecture and answer a security questionnaire.

Request a demoCall Margo · 774-436-2746

Ask for 774-436-MARGO if it is easier to remember.