Past the Hedge
Menu
Trust & Security

Your travel data deserves to be protected.

Privacy first. You choose which emails to forward, and we never connect to your inbox. We don’t run ads or sell your information, and your bookings aren’t used to train AI. You can download everything or delete your account from Account settings whenever you like.

This page explains, in plain language, how we protect your travel information and how to reach us if you have a security question or a concern to report.

Report a security concern Read the Privacy Policy

No. 01 · Who runs it

Who runs Past the Hedge

Past the Hedge is a small, independent service, and the party you deal with. Each kind of question has its own address, so it reaches the right place. We don't promise a response time.

No. 02 · Protection

How we protect your information

The safeguards around your account and your travel records.

Data in transit

Your browser and our servers communicate over HTTPS, so information you send — including anything you type into a form — is encrypted along the way.

Data at rest

Sensitive fields in your booking records, and account-security secrets like your two-factor key, are encrypted in the database rather than relying on application logic alone. Passwords are never stored in a form that could be read back — only a salted, one-way hash: a scrambled fingerprint that can check a password you type but can’t be turned back into it. Backups of stored information are encrypted before they ever leave our server.

Access controls

Your travel records are scoped to your account. If you choose to share a trip with another person, they must accept, that access is explicit and opt-in, and can be limited — hiding prices, confirmation numbers, or traveler names from what's shared.

Data minimization

We aim to collect and retain only what's needed to build and maintain your itinerary. There's no advertising or analytics tracking, and a forwarded confirmation email exists to build (and, if needed, later correct) your itinerary — not for any other purpose. Your travel data is never sold. IP addresses are not used to track where you travel; they appear in security logs of failed sign-ins and suspected abuse, as the Privacy Policy describes.

Account security

From Account Settings, you can change your password, turn on two-factor authentication with backup codes, add a passkey to sign in with Face ID, a fingerprint or your device’s PIN, review your sign-in methods, and sign out of sessions on other devices. Where Google sign-in is offered, it works only for an account that has linked it; Past the Hedge receives your Google account ID and email address only, with no access to your inbox.

Secure development

Security is a consideration throughout ongoing development, not an afterthought. The account-security actions worth protecting most carry additional request-forgery protections, which check that a request really came from your own signed-in page and not from another website. The forms most exposed to automated abuse — sign-in, password reset, sign-up — are rate-limited. We track application errors and background job failures, and if something looks wrong, we investigate it.

No. 03 · Privacy

Privacy & data handling

Past the Hedge exists to turn your travel confirmations into an organized record, which means it necessarily handles information about where you've been and where you're going. We collect only what's needed to do that: your account credentials, the profile details you choose to enter (home country, passport countries, driver's licenses and travel companions), the bookings you forward or add, and any Travel Memory reflections you write.

That information is used to build and display your itinerary back to you — not to profile you, sell to advertisers, or share beyond what a feature you actually use requires.

You're in control of most of it directly: edit or delete a booking or remove a passport country any time from Account Settings, which also lets you export your travel records or delete your account outright.

This section summarizes our approach. The Privacy Policy is the authoritative, detailed source for exactly what's collected, why, and how it's handled — read it for the full picture.

No. 04 · Forwarded email

Your travel information

Past the Hedge is built around a simple idea: forward a booking confirmation to a private address unique to your account, and it becomes an organized entry in your itinerary. Because that means real confirmation emails pass through the service, it's worth being direct about how they're treated.

The content of a forwarded email is used to extract your itinerary's details and is otherwise handled as your data — not analyzed for advertising and not sold. When an AI provider helps read it, the provider is configured or contracted not to use it to train their models, and Past the Hedge does not train models on it.

Keep your original confirmation in your inbox: it stays your reference. Once the booking details have been extracted, we erase our processing copy of the message and its attachments. The extracted booking stays in your archive, where you can correct it yourself. If a message cannot be read, or its result needs review, its content is kept, encrypted, for up to 7 days to retry or resolve it, and is then erased automatically. Backups and recovery copies follow the retention section of the Privacy Policy.

Access to that content follows the same account-scoped rules as the rest of your data. For the complete detail, see the Privacy Policy.

No. 05 · Third parties

Third-party services

Running Past the Hedge means relying on a small number of outside service providers for specific tasks — for example, Stripe for Premium subscription billing. Each one is given information for a specific purpose, such as delivering email or taking a payment.

The Privacy Policy names each service provider, what it does and what it receives. If you need more for a business or procurement review, contact us.

No. 06 · Practices

Security practices

Broader detail on specific areas of our security program, at a level appropriate for a public page — what we protect and why, not a blueprint of how it's built.

Application security
Security is considered throughout the development and maintenance of Past the Hedge, not bolted on afterward. We use automated tools to help identify known vulnerabilities in the open-source components the application depends on.
Data protection
Sensitive fields in your travel records are encrypted at the database level, in addition to the access controls already built into the application.
Access management
Access to your data is scoped to your account by default. Sharing anything with someone else — an invitation to a specific person, a link to an upcoming trip — is an explicit, opt-in action you take, with control over exactly what's visible.
Privacy
We collect what's needed to run the service and nothing more. There's no advertising or analytics tracking anywhere on the site.
Infrastructure security
The application runs on established, professionally managed hosting and network infrastructure, with network-level protections in front of it. Provider and data-flow details are in the Privacy Policy; sensitive operational configuration is not public.
Vulnerability management
We use automated scanning to help identify known vulnerabilities in the software this application depends on, and address what we find as part of ongoing maintenance.
Business continuity
Stored information is backed up regularly, encrypted before it leaves our server, and off-site backups are deleted after 30 days. We periodically test that a backup can actually be restored — not just that one exists.
Third-party risk
Before relying on an external service provider, we consider what information it would need access to and limit that to what the specific task actually requires.
Incident response
If we identify or are made aware of a security issue, we prioritize investigating and addressing it. If an incident affects your account or information, we’ll tell you by email at the address you sign in with: what happened, what it affects and what you can do. See “Found a security issue?” below for how to reach us.
No. 07 · Report a concern

Found a security issue?

If you believe you've found a security vulnerability affecting Past the Hedge, we want to hear about it. Email security@pastthehedge.com and include:

  • what you found, and the page or address it affects;
  • the steps to reproduce it;
  • what someone could do with it.

We'll review it and follow up. Please avoid accessing, modifying, or downloading data that isn't yours while investigating — reach out first and we can help you verify it safely. We don't currently run a formal bug bounty program, but we appreciate responsible, good-faith reports and will treat them accordingly. The same contact is published in our security.txt.

Email security@pastthehedge.com
No. 08 · Compliance

Our approach to compliance

Past the Hedge doesn't currently hold formal certifications like SOC 2 or ISO 27001 — those are significant undertakings we haven't pursued at this stage, and we'd rather say so plainly than imply otherwise. We're committed to protecting user information and to evaluating our practices against applicable privacy and security expectations as the service grows. If a specific certification or compliance question matters to how you'd use Past the Hedge, contact us.

No. 09 · Reliability

Reliability

Past the Hedge doesn't yet publish a dedicated public status page or uptime statistics. If you're having trouble reaching the service, or something looks wrong with your account, contact us and we'll look into it.

No. 10 · Resources

Documentation & resources

This page was last reviewed October 30, 2026.