Privacy Policy

The public website does not load analytics or tracking scripts. The page shell — navigation, theme, sign-in, and on-screen notices — includes no Google Analytics, tag manager, advertising pixel, or session recorder. The web app has no analytics dependency. Your sign-in tokens and theme choice stay in this browser. They are not sent to a tracking vendor. We share your details with a property only with your consent. Sharing is off until you turn it on, and a copy is taken only when you submit a booking inquiry while signed in.

Account: your email address, your password (stored only as a scrypt hash, never in readable form), and your display name. If you add a short bio in account settings, we keep that too. Inquiries: your name, email, optional phone number, dates, party size, message, and the property or journey you enquired about. Dedicated advisor (optional): if you opt in, any regions and specialties of interest you enter, used to match you with an advisor. Private Client Profile (optional): pillow, bed, and room preferences; dietary requirements and allergies; celebrations; accessibility needs; travel companions; and special requests. Only what you choose to save. Server logs: when you sign in, we record the IP address and browser user agent for the session, for sign-in and security purposes.

To run your account and keep you signed in; to answer your inquiries, so that an advisor can confirm availability, pricing, and terms with you; to match you with a dedicated advisor if you opt in; to protect the service, for example by limiting repeated failed sign-in attempts; and to send the transactional email described below.

To arrange a stay, your advisor works with the property or supplier concerned on your behalf. Your Private Client Profile is shared with properties only when you turn on “Share my preferences with properties I book”. It is off until you turn it on. While it is on, a copy of your profile is attached to the inquiries you send while signed in, for your advisor to forward to the property. Turning it off stops future inquiries from including a copy; it does not recall a copy already sent. Your assigned advisor can read your profile so they can prepare your stay. Other Atlas concierge and admin staff can read it only while sharing is on.

No payment is taken on the website. There is no cart and no checkout, and we do not collect or store card numbers.

Signing in stores two tokens in your browser’s localStorage: an access token, valid for 15 minutes, and a refresh token, valid for 7 days, which keeps you signed in. Signing out removes both from the browser and ends the session on our side. Your light or dark theme choice is also kept in localStorage. The website does not use cookies for sign-in, and it does not set tracking or advertising cookies.

The website does not load analytics, tag-manager, advertising-pixel, or session-recording scripts, and the web app has no analytics dependency. Some content is fetched directly from other providers: our typefaces are loaded from Google Fonts, and some photographs are loaded from the image hosts where they are published. As with any web request, those providers receive standard request information such as your IP address and browser type.

We send transactional email only: at present, the password-reset message you request, with a single-use link valid for one hour. There is no newsletter and no marketing email. Your advisor may write to you about an inquiry you have sent.

We keep your account details and Private Client Profile while your account is active, and inquiry details for as long as they are needed to handle the inquiry. You may ask us to delete your data at any time.

You can view and edit your display name and Private Client Profile, and turn sharing on or off, from your account at any time. To request access to, correction of, or deletion of your personal data, contact us through the contact page. Requests are handled by hand for now; self-serve export and deletion tools are not yet available.

Traffic to the production website is encrypted in transit with TLS. Passwords are hashed with scrypt, a memory-hard function, using a unique salt for each password. Repeated failed sign-in attempts temporarily lock the account, and resetting your password signs out every session. No method of storage or transmission is perfectly secure, and we will keep improving these controls.

We will update this policy when our practices change. The date at the top of this page shows when it last changed.