Privacy Policy
Last updated
Past the Hedge is operated by Past the Hedge LLC (“Past the Hedge”, “we”, “us”). We decide how personal information is used for the service and are its controller where that term applies. This policy covers our website, accounts, travel tools and related communications.
On this page22 sections
Account and contact information
We collect your email address, account identifiers, account creation and sign-in records, and settings. Passwords are stored as hashes. If you enable two-factor authentication, or sign up with or link Google sign-in, we keep the information needed to support that choice, including your linked Google account identifier and email. Google sign-in asks Google for nothing else and does not give us access to your inbox. If you add a passkey, we keep its public key, the name you give it, and when it was added and last used. Its private key stays on your device, and your fingerprint or face never reaches us.
You may also provide your home country (where you live, which tailors travel guidance), passport countries and expiry dates, driver's-license issuing countries and expiry dates, and travel-companion names. These profile settings do not ask for passport or license numbers or scans. We receive the email address you sign up with or are invited at, a record of when you agreed to our Terms and this Privacy Policy and which versions, and the contact details and messages you send for support, billing questions or privacy requests. That includes support requests you open in your account and, only if you choose to attach one, the original email a request is about.
Travel and booking information
We receive the confirmations you forward, including email text, relevant headers and sender/recipient information, and attachments supplied with them, which may include PDFs or ICS calendar files. We also collect bookings you add manually and corrections you make. A confirmation may contain information about you and accompanying travelers.
Depending on what you provide, records may include flights, accommodation, rail, rental cars, cruises, ferries, rideshares and other travel services; confirmation and ticket numbers; traveler names; dates and times; destinations, routes and booking addresses; seat, room and guest details; and prices, currency or points. We organize these records into future trips and travel history. Travel Memories, where available, also keep your reflections, answers and associated trip information.
If you submit or forward personal information about another person, including a travel companion, you represent that you have the legal right or authority to provide that information to Past the Hedge for the relevant travel-management purpose. We use that information to organize the trips of the account holder who provided it. A traveler who is not an account holder can contact us about it as described below.
Avoid unnecessary sensitive information, identity document copies, passwords and payment credentials. We process the messages you send to your forwarding address; we do not scan your personal mailbox.
Automated parsing and AI
We use automated processing to extract and organize booking information. Where needed, AI and automated data-processing service providers may receive portions of booking content, such as email text and text extracted from a PDF. That content can include traveler names, confirmation numbers, addresses and itinerary details. We may also use these providers to generate trip descriptions from travel dates, types of bookings and destinations or booking addresses.
The AI providers we use to process customer content are configured or contracted so that this content is not used to train their models and is not used for other purposes inconsistent with providing the service to us. Past the Hedge does not use booking content to train its own AI models. Providers may still process and keep content as permitted by their applicable service terms, for example to deliver the request or for security. The providers are named under Service providers and other disclosures.
After a booking has been extracted successfully, we delete the original forwarded message and its attachments from our active processing systems and keep the booking details extracted from it, together with limited processing records. If a message cannot be processed or its result needs review, we keep the source, encrypted, for up to 7 days to retry or resolve it, then erase it, unless you choose to share it with us as described in Held emails you share with us. Backup copies are handled as described in Retention and recovery copies.
Automated extraction can make mistakes. You can review and correct your bookings. We use processing and usage records to investigate problems and manage the service.
Held emails you share with us
When a forwarded email can’t be added, it’s listed under Bookings to review. While we still have our copy of it, you can choose to share that email with us to help fix the problem. Sharing is optional, applies only to the email you choose, and is off unless you select it.
If you share an email, people on our team, and the AI developer tools named under Service providers and other disclosures, may read it, including its attachments, to find out why it couldn’t be read. We may also run it through our reading again, including through the AI providers described in Automated parsing and AI. We use it only to investigate and fix how emails are read, and, once the problem is fixed, to read it one more time so its booking can be added to your account, as if you had forwarded it again. We may keep a short, edited excerpt with personal details replaced, as a test case for the fix, but not the email itself.
We keep a shared email encrypted until we’ve finished with it, and never more than 30 days from when it arrived, then erase it. You can withdraw at any time from the email’s page in Bookings to review; dismissing the email withdraws it too. Withdrawing doesn’t affect anything we did with the email before then. After you withdraw, or once we’ve finished, we erase our copy. Backup copies are handled as described in Retention and recovery copies.
We rely on your consent for this use.
Travel locations
We use destinations, booking addresses, place identifiers and geocoded coordinates to organize trips and provide maps, destination imagery, nearby-place information and weather. Location providers may receive a place or address query or coordinates. An address or itinerary can reveal a sensitive location even when your name is not included.
Airbnb and Vrbo stays are usually someone’s home. To pin one on your own maps, we send only its address, without your name or booking details, to OpenStreetMap’s Nominatim, and, if it can’t find the house, to Google’s geocoding service. We keep the result encrypted with your booking; a location from Google is deleted after 30 days, as Google’s terms require, and looked up again when it’s next needed. The pin is never added to the place records other accounts can use, and a trip you share shows it only when that share shows stay addresses. If the address can’t be found, the stay is shown on your travel history at the town its booking names, and has no pin on its trip’s map.
We do not request your current precise device geolocation or use your IP address to build a travel-location history. Travel locations come from your bookings and information you provide. Following an external map link sends its destination query to that provider.
Technical and security information
Our service and its infrastructure providers receive connection information such as IP addresses and request timestamps. Security logs can include IP addresses and failed sign-in or suspected-abuse events. We also keep service, error and processing records to diagnose problems and protect accounts.
Infrastructure and security providers may process browser, device and network information when delivering the site or checking for automated abuse. This operational information is distinct from advertising or browser analytics.
When you sign up from a link on one of our pages, such as a guide, we note which of our pages it was with your account, so we can tell which pages are useful. It comes from the link itself, not from cookies, your browser history or any third-party analytics.
Why we use information
We use information to create and authenticate accounts; receive and parse confirmations; maintain, correct and export your travel archive; provide itinerary-related guidance, trip descriptions, maps and destination information; and carry out sharing you choose.
We also use it to provide Premium access, administer trials and subscriptions, send service and billing messages, answer requests, detect abuse, troubleshoot errors, recover from failures, complete account deletion and resolve billing or legal matters. Optional profile information helps tailor travel guidance; you do not need to fill in every optional field to have an account.
When you attach an email to a support request, we use it to improve how the service reads booking emails like it. We may review it ourselves and analyze it with AI developer tools from Anthropic and OpenAI. We don’t use it to change your bookings; you can correct those yourself.
Payments and billing
Paid Premium is not open yet. When it is, you will pay on our checkout page, where Stripe’s payment form collects your payment details, and manage your subscription in Stripe’s hosted Customer Portal. We send Stripe your account email and references needed to manage billing. Our billing records include customer and subscription identifiers, invoice and payment references, trial and billing dates, payment status, Premium access, and billing audit, deletion and refund-review records.
Our billing system does not store full payment-card numbers, card security codes or bank-login credentials. Payment details you enter in Stripe’s payment form or Customer Portal go to Stripe. Stripe also processes information for its own payment, security and legal purposes under its privacy notice. You can manage your subscription and payment method through billing settings. Our Refund & Cancellation Policy explains cancellation and refunds.
Service providers and other disclosures
These providers help run the service. Each receives only what its task needs:
- Amazon Web Services (Lightsail): hosts the service and its database.
- Cloudflare: network security for every visit to the site (including your IP address); receives the emails you forward, with their attachments, checks their DKIM signatures (looking up the sending domain’s public key through Cloudflare’s DNS service) and passes them to us; stores our backups, which are encrypted before they leave our server, so Cloudflare holds only the encrypted copy.
- OpenRouter, and the AI model providers it routes to (Google, Anthropic and OpenAI): read the text of a forwarded email and its PDFs when a booking needs AI to extract, and write trip descriptions. Our OpenRouter account is set so that providers may not train on this content.
- Stripe: subscription billing, once paid Premium opens. Receives your account email; payment details you enter in Stripe’s payment form or Customer Portal go only to Stripe.
- Google: sign-in, only if you link a Google account (your Google account ID and email); and place, map and destination-photo lookups, which send hotel or place names from your bookings, never your name or email; and the address of an Airbnb or Vrbo stay that OpenStreetMap can’t find.
- Resend: sends service emails, such as invitations, password resets, sending-address verification codes, support replies and our notices of new support requests: your email address and the message, which for support includes the text you wrote.
- Anthropic and OpenAI, as AI developer tools: an email you choose to attach to a support request, or to share with us from Bookings to review, analyzed to improve how emails like it are read.
- OpenStreetMap Nominatim and Open-Meteo: turn place names into map coordinates, and coordinates into weather.
- Wikimedia Commons: destination photos, looked up by destination name.
- AeroDataBox (through RapidAPI) and Aviationstack: flight lookups by flight number and date only. Their schedule checks cover only flights on our own test account, and there are no live flight alerts. AeroDataBox may also be asked for the aircraft type of an upcoming flight when your confirmation leaves it out.
Providers can also receive connection or operational information, and process it under their own terms. User-directed sharing is explained below. We may disclose information when required by law or where legally permitted and necessary to address abuse, protect rights or respond to a legal claim.
We do not sell personal information. We do not use or disclose personal information for targeted advertising or cross-context behavioral advertising, and we do not share it with advertisers for targeting. We do not provide travel histories to advertisers or data brokers. The provider disclosures described here support the service and its operation.
Sharing trips and calendars
You can choose to share trips. Anyone with a valid public share link may view the content available through it without an account. You can also invite a specific person by email; we store the address you enter, encrypted, to send and match the invitation, and remove it 30 days after the invitation closes or expires. No account is created for them unless they create one themselves. Until they accept, only the trip’s name, dates, countries and number of bookings are shown, and only to an account signed in with the invited address. Shared content can include dates, destinations, traveler names and booking details, depending on the view and privacy controls you select.
Controls can limit selected details such as confirmations, prices, names and addresses. They do not make an itinerary anonymous: place names, routes or text you supplied can still reveal where you are traveling. Review what a recipient can see before sharing. Existing links and grants may remain available with fewer features after Premium ends; you can revoke them. Ending Premium does not itself make a shared trip private.
On a trip shared with people, a collaborator can add their own bookings, which everyone on the trip can then see under that person's privacy choices. Bookings and memories stay in the account of the person who added them, and ending a share removes the access, not their data. After the trip, memories a collaborator writes after joining are shared with the trip's owner and other collaborators unless they turn that off; memories written earlier are shared only if they choose.
If you mark someone as a traveler on a trip and they accept, the trip counts in their own map, stats, history and Schengen days. If you then delete that trip or close your account, the traveler keeps a small record of its dates, places and countries, without confirmation numbers, prices, addresses or names, until they remove it or close their own account.
A calendar subscription is separate. Anyone with its valid link, including your calendar provider, may receive booking information and locations; trip-share privacy controls do not apply to that feed. You can regenerate the calendar link in settings. Revoking a share link or regenerating a calendar link stops future access through that link, but cannot remove copies already saved or redistributed by recipients.
Cookies and browser storage
We use cookies for sessions, sign-in and security, including remembering a trusted device and helping prevent forged requests. We also use cookies or browser storage to remember limited preferences, such as a dismissed prompt or display choices.
The site has no advertising trackers, advertising pixels, browser analytics or session-replay scripts. Cloudflare's security checks and external sign-in or payment pages may use their own technologies. You can manage cookies and browser storage in your browser; blocking security or session cookies can prevent sign-in or other features from working.
International processing
Past the Hedge is operated from the United States. If you use the service from outside the United States, your information will be transferred to and processed in the United States, and may also be processed in other countries where our service providers operate. These countries may have different privacy laws from those where you live, and their authorities may have lawful access to information.
Where transfer rules apply, the appropriate legal safeguards depend on the provider, destination and processing involved. Contact our privacy contact below for information about processing locations and safeguards relevant to your information, or to request details of any applicable transfer arrangements.
Retention and recovery copies
We retain personal information only as long as reasonably necessary for the purposes described in this Policy, including providing the service, maintaining security, resolving disputes, meeting legal and accounting obligations, and maintaining backups.
How long things are kept:
- Your account, trips, bookings, Travel Memories and other travel history: while your account is open, or until you delete them. Editing a Travel Memory answer replaces it; when a reflection is regenerated, the earlier version is kept with it until your account is deleted.
- An email address you invite to a shared trip: kept encrypted until 30 days after the invitation closes or expires.
- A traveler's record of a trip someone shared: dates, places and countries, kept if the trip's owner deletes it or closes their account, until the traveler removes it or closes their own account.
- A forwarded email that was read: our copy of the message and its attachments is erased as soon as the booking is extracted. The booking details stay in your account.
- A forwarded email that couldn’t be read, or needs review: kept encrypted for up to 7 days from when it arrived, so it can be retried or resolved, then erased automatically.
- A held email you choose to share with us: kept encrypted until we’ve finished with it, and never more than 30 days from when it arrived; erased sooner if you withdraw it or dismiss it. See Held emails you share with us.
- A TripIt PDF you upload: read on our servers without AI, and erased as soon as its reading is recorded. If reading is interrupted and has to be retried, the PDF is kept encrypted only until a retry finishes, and never more than 7 days. The bookings we found in it are kept, encrypted, with its record so you can add them, until your account is deleted.
- Sending addresses you add: kept until you remove them or delete your account.
- A forwarded email from an address that isn’t your sign-in email or a verified sending address: not read and not kept. Only its subject, sender, dates and size are recorded, so you can see that it was rejected.
- Records of forwarded emails: a record of each email you forward (when it arrived and what happened to it, and for one that couldn’t be added, its subject and sender, never its text or attachments) stays with your account, so you can see what was received, until your account is deleted.
- Support requests: the conversation stays with your account until your account is deleted.
- An email attached to a support request: kept encrypted until 30 days after the request is closed, then erased automatically; erased at once if you delete your account. Copies we make while improving the email reader are deleted once that work is done.
- Sign-in sessions: expire after 30 days. Password-reset links expire after an hour.
- Trips you save for offline (Premium): a copy kept in your browser on that device, which anyone using the device can open without signing in. It’s removed when you remove it, sign out or delete your account, and when the site is next opened after the trip has been over for two days, or opened online by another account or by one without Premium.
- Error and scheduled-job records kept by the service: up to 30 days.
- Backups: encrypted before they leave our server and stored off-site. Backups are deleted automatically after 30 days.
- Copies of the database taken before an administrative change: deleted after 90 days.
- Safety copies taken before a software update that changes the database: copies set aside during a release or maintenance backup are removed from our server during later software updates once they are more than 30 days old. Copies the server still needs to undo the current or previous update, and the few most recent copies it works from, are kept until later updates replace them.
- Waitlist sign-ups: deleted after 12 months if no invitation has been sent. An invitation creates your account, and the address then stays with it.
- Your agreement to the Terms and this Privacy Policy: the date and the versions you agreed to, kept with your account and deleted with it.
- Billing records: once billing cleanup for a deleted account has finished, a minimal billing reference is kept for 90 days. Some billing and refund records are removed only after manual review, and records we are legally required to keep, such as payment records, stay with Stripe under its terms.
So anything you delete is gone from the live service at once and from administrative copies within about 90 days. Copies of it can remain in backups until they are deleted after 30 days, and in the safety copies above, which are not erased when you delete data. Shared place records used across accounts (a hotel’s location, for example) may remain. Records needed to resolve an unresolved charge, dispute or legal duty can be kept longer, for that purpose only. Stripe and other providers keep their own records under their applicable terms and legal obligations.
Deleting your account
You can request permanent account deletion from the account-deletion page, or contact us for help. Deletion removes your active account and its associated travel records and access. Separate source cleanup, billing cleanup and backup or recovery copies are handled separately and can remain after deletion, as explained above.
Limited billing references, audit and refund-review records may remain so we can complete cancellation, investigate charges and resolve outstanding matters. External billing cleanup may need retries or manual review. Account deletion ends your Premium access and does not automatically provide a prorated refund. Cancel Premium first if you want to keep access through the paid period, then delete the account afterward. See the Refund & Cancellation Policy.
Security
We use safeguards including password hashing, authentication and access controls, protections against common request abuse, and encryption for selected sensitive stored information and off-site backups. These safeguards do not mean that every field or copy is encrypted in the same way. No service can promise absolute security.
We open an account’s bookings only to answer that account’s request, fix a problem with its bookings, or resolve a billing or legal matter. Each time, we record who opened them, when and why, and the access ends after an hour.
Keep your credentials private, use the available security settings, and tell us about suspected account compromise. If a security incident affects your account or information, we’ll tell you by email at the address you sign in with. Report a security concern, including a suspected incident, to security@pastthehedge.com; privacy concerns go to privacy@pastthehedge.com.
Your choices and privacy requests
You can correct or delete bookings, change optional profile details, unlink Google sign-in, revoke sharing and manage security settings. If you were marked as a traveler on someone's trip, you can remove that trip from your record at any time. Account export provides archive downloads. Subscription cancellation and payment-method changes are available through billing settings; cancellation is different from account deletion.
For access, correction, deletion, a portable copy or another applicable privacy right, contact us at privacy@pastthehedge.com. We handle privacy requests individually by email. This also applies if someone else supplied information about you, or you need help beyond the self-service controls. Tell us what you are requesting and how we can identify the relevant account or information. We may need to verify your identity or an authorized agent's authority without collecting more than is needed.
Rights and exceptions depend on applicable law. We will handle requests within the applicable legal time limits, explain any refusal and any available appeal route, and protect other people's information when responding. Where processing is based on consent, you may withdraw it; this does not affect earlier lawful processing, and may prevent us from providing a feature that needs the information.
EEA and UK privacy rights
Past the Hedge may be used from the EEA and the UK. It is operated from the United States and has no establishment in the EEA or the UK. Where EEA or UK data-protection law applies, we rely on contract necessity to use an account holder's own account, booking and billing information as needed to provide their account, requested travel tools and subscription. Our legitimate interests in operating a reliable service, preventing abuse and resolving problems support security, troubleshooting and dispute records, subject to the protections required by applicable law. We rely on a legal obligation where an applicable law requires processing, such as retaining required financial records or responding to a valid rights request. Consent is relevant where required for the particular processing.
Depending on the circumstances, you may have rights to access, correction, deletion, restriction, portability and objection, including objection to processing based on legitimate interests. Where we rely on consent, you can withdraw it. Contact us as described above. You can also complain to a supervisory authority, including one where you live or work or where you believe an infringement occurred, or to the UK's Information Commissioner's Office.
California and other U.S. states
Depending on where you live and subject to applicable thresholds and exceptions, U.S. privacy laws, including California's CCPA as amended by the CPRA, may give you rights to know or access your information, correct it, delete it, and obtain a portable copy. Where applicable, you may also opt out of sale, sharing for cross-context behavioral advertising, targeted advertising or certain significant profiling, and exercise rights concerning sensitive information.
Our advertising practices are described in Service providers and other disclosures. We do not discriminate against you for exercising rights protected by applicable law. Contact us to make a request or, where state law provides one, appeal a refusal by replying to our response and asking for an appeal. Applicable law may also allow a complaint to your state regulator.
Canadian privacy rights
Depending on the circumstances, PIPEDA or provincial private-sector privacy laws, including those of Quebec, Alberta and British Columbia, may apply. You may request access to your personal information and correction of inaccuracies, ask how it is used or disclosed, and withdraw consent where applicable, subject to legal or contractual restrictions. Other rights, including portability or deletion, may apply in particular circumstances.
Information can be processed outside Canada, including outside Quebec, as described above. Contact our privacy contact for questions about foreign service providers, safeguards or retention, or to make a privacy complaint. You may also contact the Office of the Privacy Commissioner of Canada or the applicable provincial privacy commissioner, including Quebec's Commission d'accès à l'information.
Children
The service is not directed to children. Account holders must have reached the age of legal majority where they live, as described in the Terms, and we do not knowingly offer accounts directly to children or other minors who cannot legally enter into the Terms. Travel confirmations may include children accompanying an account holder. Provide that information only with appropriate authority and only as needed for travel management. Contact us if you believe a child's information has been provided inappropriately.
Changes to this policy
We may update this policy as the service and its data practices change. The current version is posted here with its date. Where applicable law requires notice or consent for a change, that requirement still applies. Last updated November 21, 2026.
Contact and other information
For privacy questions, privacy-rights requests and privacy or security concerns, email privacy@pastthehedge.com. For ordinary support, use support@pastthehedge.com; for billing questions, contact@pastthehedge.com.
The Terms of Use and Refund & Cancellation Policy cover using and paying for the service. The separate question of public map and rail datasets and their licenses is explained in the colophon.
