Privacy Policy

What we store

• Account data: your email address and display name, managed by our authentication provider (Supabase Auth).
• Household: the travelers you add, with their names, optional birthdates (full, or month and year) and notes. Birthdates exist only so the app can warn about minimum ages; they are visible to you and to members of a trip that traveler is on.
• Travel data you or a connected assistant enter: your bucket list of destinations (with seasonality, cost, notes and an optional cover image URL), places inside them, trips and their context line, bookings (including confirmation codes, costs and points), saved fare options, and your travel dates.
• Preferences: your home base (geocoded), home countries, default trip context, appearance, and whether to show the Jewish calendar.
• Connections: if you connect an AI assistant over MCP, we store the app’s registration, your consent (scopes), and hashed refresh tokens, never plaintext secrets.
• Forwarded email (if the operator enabled it for your account): messages you forward to your Vektrip address, or that reach your private address, are stored as redacted text (headers we keep, the message text, the text of its HTML) plus any PDF attachments, the bookings and credits extracted from them, and a record of what each message changed. Card numbers, passport and ID numbers, Social Security numbers, Known Traveler and Redress numbers are removed before anything is written; PDFs cannot be redacted and are kept for a shorter time. Also kept: your inbound addresses, the sender addresses you verified, the sender and subject (never the body) of mail that was refused, and daily usage counts.
• Cached public data: zmanim and Jewish-calendar data per coordinate and date, from Hebcal; not personal data.

What leaves our servers

Very little, and never for advertising. If you use email ingestion, two processors handle forwarded mail on our behalf: inbound mail to your Vektrip address passes through Cloudflare (Email Routing on our mail subdomain), which hands it to us without keeping a copy, and the redacted text and PDFs of each message are sent to Anthropic’s API to extract the booking facts, under its commercial terms, which do not permit training on that content. Nothing else about you is sent with it. To look up places, cover photographs and zmanim we send place-name queries and coordinates and dates to public data APIs (Open-Meteo geocoding, Wikipedia, Hebcal), server-side, without your identity attached. Cover images and map tiles are loaded by your browser from their hosts (Wikipedia, OpenStreetMap, or whatever image URL you or your assistant saved). If you connect Claude (or another MCP client), your travel data is shared with that assistant, at your instruction, under the scopes you approved; revoking the connection in Settings stops it immediately.

What we don’t do

• No selling or renting of personal data. No ad networks.
• No inference about your religious practice beyond what you chose to write down; trip context is stored verbatim and used only as context you hand to your assistant.
• No third-party analytics on trip content; aggregate page analytics and operational logs are for reliability and security.

Forwarded email

• Your choice, per message. Nothing reaches Vektrip unless you forward it, set up a forwarding rule yourself, or give a vendor your private address. We never read your mailbox.
• Only mail that is provably yours is filed. Mail to your address is accepted when it authenticates as coming from one of your verified addresses; mail from anyone else is refused at delivery time and only its sender and subject are noted so you can see it. Your private address is accepted on the address alone; cancellations and changes arriving there wait for your approval.
• Retention. Message text is kept 90 days and PDFs 30 days after arrival (the operator may shorten these); the extracted bookings, the record of what each message changed and daily counts stay with your account. You can delete any message’s copy at once from the inbox.
• Deadline alerts. If you turn them on, we email you — at your account address or a verified address you chose — before a free-cancellation or hold deadline on your own bookings. These are service messages about your data, switchable in Settings; we send no other mail except the one-time code that verifies a sender address.

Sensitive data, handled deliberately

Trip context such as “keeps Shabbat” or “kosher only” can reveal religious affiliation, and a household’s birthdates are personal. We treat all of it as private: it is protected by row-level security so only you (and, for a trip, its members) can read it, connected assistants act under your own permissions, and nothing is ever public.

Your rights

Self-serve, in Settings: export your data as JSON at any time, and delete your account, which revokes all connected apps, removes you from shared trips (ownership transfers to a co-traveler), and permanently deletes your household, bucket list and trips only you own. Depending on your jurisdiction you may have additional rights (access, rectification, erasure, portability, objection); exercising them starts with the same export and delete tools, or by contacting us as described below.

Storage, security, retention

Data is stored with managed providers (Supabase/PostgreSQL for data and auth; our hosting provider for the application), in transit over TLS and encrypted at rest by those providers. Access-control checks are enforced in the database itself and covered by automated tests. We keep trip data for as long as your account exists; deleting a trip or your account removes it, and backups expire on the provider’s schedule.

Cookies

We use only the session cookies required to keep you signed in. No tracking cookies.

Children

Accounts are for adults. A child appears only as a traveler their guardian added to the household (a name, optionally a birthdate, notes) or in free-text trip context; nothing about a child is collected from the child.

Changes and contact

Material changes to this policy will be posted here with a new date. Questions: contact the operator of this site through the address it was shared with you from. See also our Terms of Service.