PRIVACY & INQUIRIES

Your details,
considered with care.

This page explains how the inquiry tools in this website work.

Public travel and airport inquiries

The public travel and airport inquiry forms run in your browser. They prepare an email addressed to Michael.johnson@fora.travel; they do not automatically send it or save it to a website database. You decide whether to send the email in your own mail app.

Information you choose to share

The forms ask for contact details, broad travel preferences and itinerary information needed for initial planning. Do not include passport numbers, payment-card information, dates of birth or detailed medical information. Any sensitive documents needed later should be exchanged through an agreed secure channel.

Copies and browser storage

Saving a text copy creates a file on your device. The Copy request button copies the request to your clipboard. This website does not intentionally store inquiry fields in local storage, use advertising cookies or include third-party analytics scripts.

Email and hosting

Once you send an email, the information is handled through the relevant email services and the agency's travel-planning process. Hosting services may maintain standard technical access logs. This front-end website does not control those services.

Questions or corrections

Contact Michael.johnson@fora.travel about an inquiry, a correction or a privacy question.

Private client-trip access

The password-protected client area uses a necessary session cookie to keep you signed in. Access is checked on the server and expires after 30 minutes of inactivity or eight hours from sign-in. Signing out removes access. A shared trip password grants access to that trip; it is not a secure document or payment vault.

When you review your private-trip choices, the selections and comments are held in server-side session storage until logout or hosting session cleanup. This lets you return to the choices during the same authenticated session. They are not saved to a customer database or your browser local storage. The response is prepared for your email application; you must send it there.

Server-side login throttling uses keyed hashes of connection addresses, attempt counters and timestamps. Hosting access logs and session cleanup remain under the hosting service's control. Do not enter passport numbers, card details or other sensitive documents in this area.