Privacy

A search is a destination, dates and party size. They live in the URL rather than in an account, which is why a search is shareable and why we do not need to know who you are to run one. Results are cached for a short time — minutes for prices, a day for place names — so that two people asking the same question do not cost the supplier two calls. The cache holds no personal data.

Hotels. Your name, email, phone number, the ages of any children, any special requests you choose from our list, and the state on your billing address. Name, email, phone and party go to the hotel through its distributor (LiteAPI), because a reservation cannot exist without them. We keep the requests you chose with the booking, so that changing it or adding nights can fill them in again; those details are shown only after you enter a code we email to the address on the booking.

Flights. Flights are not on public sale. What follows governs any flight booking made through us. For every passenger: title, name as on their travel document, date of birth and the gender marker on that document; plus one email and phone number for the booking and the state on your billing address. The passenger details and contact go to the airline through its distributor (Duffel), because airlines refuse to ticket without them and match them at the gate. If you tell us a passenger needs help at the airport — a wheelchair, a service animal, oxygen, or any other option you tick — we keep what you ticked with the booking, so your booking page can repeat it with the reminder to tell the airline, and so our support team can see it. We do not send it to the airline: the distributor does not pass it on, so you tell the airline yourself.

Payment. Card details are entered into a form served by Stripe and go to Stripe directly; they never reach our servers. For a payment we take ourselves, we keep the card brand, its last four digits and the statement descriptor, for your receipt. A hotel room is paid for through Nuitée Travel Limited (LiteAPI), and we keep none of that card's details. The billing state is kept as the basis on which we agreed to sell.

We keep booking records for seven years after the trip: tax and accounting law requires it, and a refund or a dispute can arrive long after travel. The personal details in a booking (names, email, phone numbers, dates of birth, requests and any airport assistance) are removed once 540 days, about eighteen months, have passed since travel, by a check that runs monthly; what remains is the record of what was sold and paid.

Signing in uses a link sent to your email; there is no password. We store your email and a hashed session identifier. Your browser holds the session in a cookie that lasts thirty days, and our Android app holds it on your phone for the same thirty days. You can also find a booking by its booking number: enter it with the email address it was booked with, and if both match a booking we email a six-digit code to the address on that booking — never to an address you type. We store that code only as a hash, for ten minutes, with the times codes were sent for that booking so we can limit them; entering it signs that address in, just as the emailed link does. We do not store the booking number or email address you type. Travelers you choose to save — each one's title, name, date of birth and gender marker as a travel document shows them, with an email address and phone number — are stored against your account until you remove them or delete your account. Checkout does not fill them in for you. When you are signed in, a hotel checkout instead starts from the name, email, phone number and billing state on your most recent hotel booking with us, and you can change any of them before you pay.

A price watch stores what you asked us to watch — a flight route, or a hotel with its name — with the dates and party size, the price you saw (or, if you ask us to watch a booking you made on another site, the price you told us you paid there), and your email so we can tell you when it falls. We check its price about once a day. The email we send about it is a commercial message and every one carries a one-click way to stop them. Deleting the watch deletes all of this.

Price Guard is a watch of a booking you made on another site. It also keeps the bed you booked and the last day you told us it can be cancelled for free; it sends one reminder two days before that day and one note after it, and is deleted once that day has passed. If you start it without being signed in, we keep the stay for up to an hour, with no email address until you ask for the link, and the watch starts only when you open the link we send.

A hotel's page on our site can also start a price watch for dates you choose. We work out that stay's total when you ask, and keep it as the price the watch is measured from. If you are not signed in, we keep the stay and that total for up to an hour, with no email address until you ask for the link, and the watch starts only when you open the link we send. If you close the box that offers it, your browser remembers that for 30 days so it is not offered again; that stays on your device.

A group trip keeps the stay it was made for, the hotels added to it with the total we worked out for each and when, and the first name and choice of each person who votes. It keeps no email address and no account. The organizer and each voter’s browser are recognized by random keys we store only in a form that cannot be turned back into them. Anyone with the trip’s link can see it and vote. It is deleted seven days after check-out, or sooner if the organizer deletes it.

Once during a hotel stay booked with us, on the second-to-last night, we may email the address on the booking to offer another night at the same hotel, and only when a room is available. It is sent once per stay and never repeated. It is a commercial message and carries a one-click way to stop these offers; we record the stop on the booking, and no later stay under that address is offered one.

While a hotel booking with us can still be cancelled for free, we may check the price of the same room about once a day and email the address on the booking if it falls, so you can change your stay to the lower price. It is a commercial message with a one-click way to stop it; one stop ends these emails and offers of another night for every booking under that address.

If you ask for our monthly resort fee report, we store your email address and when you asked, and email you a link to confirm. Nothing else is sent until you confirm, and an address that is never confirmed is deleted after a week. Once you confirm, we store when, and which of the welcome emails and monthly issues have gone to you. Each one is a commercial message from news@njstravel.com and carries a one-press way to stop; stopping deletes your address. We use it for the emails you asked for and nothing else, and it is never connected to your visits.

If you sign up from our home page, the box says it is for the report and for occasional news and offers from us, and you may also choose, from our list of cities, where you are headed. We store that you agreed to those emails, and the city if you chose one, with your address; we may then email you news and offers, about that city when you named one, each with the same one-press way to stop. An address that signed up anywhere else gets the report alone.

If you add a hotel booking to Google Wallet, we send Google what the pass shows: the hotel, its address and phone number, the dates and check-in times, the room, its meal plan and the number of guests (with any children's ages), the name the reservation is under, the hotel's confirmation number and ours, whether the room is paid and what the hotel collects, our phone number and email address, and a link to your booking, which opens it without signing in when you pressed the button from your booking link. Nothing is sent until you press the button on your booking. Until the stay is over we update the pass when the booking changes, so a cancellation or the hotel's number reaches it; Google files it away after check-out. The pass is kept in the Google account you save it to, under Google's privacy policy. We keep a record that the pass exists, never the link it carries.

Confirmations, cancellation notices, reminders before free cancellation ends, the hotel's own confirmation number when it reaches us, a check of your booking before you arrive, the choice when an airline changes your flight, the notice that nothing was cancelled when you keep a flight you had asked us to cancel, sign-in links and the codes we send to confirm it is you, price alerts, price drops on a booking, offers of another night and the resort fee report are sent through our mail provider, who sees the message and the address it goes to in order to deliver it. Replies to them, and anything you write to help@njstravel.com, go to the address they were sent from or to, which our mail provider holds for us.

Price alerts, price drops, offers of another night and the resort fee report are our commercial emails. The page each one's stop link opens also offers a way to stop all of them at once, which ends every price watch for the address, takes it off the resort fee report and stops our offers about stays booked with it; or reply to any of them and we will. Confirmations, receipts and reminders about your bookings still come.

When you email help@njstravel.com, our system reads your message and its attachments from that one folder of our mailbox and files it as a support case. It cannot send, change or delete mail. Our staff can also open a case when you call us, and note what was said. If you ask us to find a hotel through our trip-help page, your answers travel as an ordinary email from you, and we use them only to answer it.

We keep a support conversation, including its emails, our staff's notes on it and any files you send, for two years after it is closed, then delete it. A conversation waiting on your reply closes after 30 days without one. For mail our system does not file (automatic replies, mailing lists), we keep only the sender and subject, for 90 days. So that no message is ever filed twice, we also keep a note of which messages our system has read: our mail provider's identifier for each one and the date, nothing of the message itself. Notes our staff make about a booking are kept with the booking record.

Staff can see your booking, its cancellation, our checks with the hotel and your conversations with us. They cannot see our payment references. Staff can resend your confirmation and, with the code we email you, cancel at your request. Every action is recorded with the staff member who took it, and a cancellation also with the reason they gave.

We never ask for your card number. If one appears in the text of a message or a text file you send, it is masked before we store it, all but its last four digits; if a photo or other file shows one, tell us and we delete that file. When you claim under our Fee Promise we keep the bill with the conversation, and our decision, and the PayPal email or Venmo handle you give us for the payment, with the booking record.

Deleting a conversation removes it from our live records; copies in our backups remain until those backups are replaced.

We keep an anonymous record of how the site is used, on our own server. Nothing is sent to a third party for it, no cookie is set, and there is nothing to accept or decline. For each visit it records:

• the website you came from, by name only — for example google.com — never the page you were on or what you searched for there;
• the campaign tags on the link you followed (utm_source, utm_medium and utm_campaign), and whether it came from an ad platform, without that platform's click identifier;
• the pages you view, in order and with the time, with anything after the “?” removed and booking references and other identifiers in the address replaced by a placeholder;
• the city a search was for — never a ZIP code;
• the buttons, links, tabs and filters you click, by what they say, and where a link leads;
• on the booking pages, which step you reach (your details, requests, review, payment), that you pressed to pay, and on review whether the total had changed since your search — never what you typed, a name or a price;
• how long search results took to appear, and how long until your first tap, click or key press after they did, to a tenth of a second — never what you pressed;
• whether your device is a phone, a tablet or a computer;
• when a payment is refused, the reason your bank or Stripe gave and whether you paid by card, Link, Apple Pay, Google Pay or another wallet — never any part of the card;
• roughly where you are: the country, state and city that our network provider, Cloudflare, associates with your connection. We receive these as place names from Cloudflare, which works them out from your IP address; we never receive or keep the address itself for this, nor the coordinates or postal code Cloudflare can also supply. It is approximate, and on a mobile network it can be a different city or state from the one you are in.

When a payment fails we may also be emailed about it, so we can help: what was being booked, the dates and the amount. To find those, a refusal inside the card field is sent with the checkout's identifier, which we use to look the checkout up and, where Stripe answers, to check the failure with Stripe, and do not keep. If the failure comes after your card was accepted, that email also includes the name and email address you entered. We are not emailed about a card number you had not finished typing, nor more than a few times about one checkout. If your card is accepted and no booking follows, our twice-daily check of unused rate holds tells us that too, without your name.

Separately, and without any visit identifier, we count which hotels have their rooms opened (the hotel and the city searched, and whether it was the website or the app), and, for each search, how many days ahead it was, how many nights and how many people it was for — never the dates themselves.

It never records what you type into a field, what a drop-down menu is set to, or whether a box ends up ticked. On checkout, booking, sign-in and account pages, which can show your own name, it notes that a control was used, and where a link leads, but not what the control said. Your IP address, your browser's full description of itself and the network your connection belongs to are read to tell automated crawlers and data-centre machines from people, and to stop one source flooding the record; none of them is stored. A visit from a town that is mostly data centers is counted as a machine. The approximate place above comes to us from Cloudflare as a country, state and city, and is the only part of where you are that the record keeps. The state is also read, and not kept, to choose whether a page tells you we cannot yet accept bookings from residents of your state.

Your browser makes up a random identifier when you arrive and keeps it in its own session storage, with the site and campaign tags you arrived with and a count of clicks recorded; all of it is emptied when the tab closes. It is not a cookie, it does not follow you between visits, and we never connect it to a booking, a name or an email address. Whether a visit reached our checkout or confirmation page is worked out from the pages it viewed, not from any booking.

If you would rather not be counted at all, tick the box below. This browser then sends us no page views, clicks or booking steps. If a payment fails, it still tells us, without any visit identifier, so that we can check no money was held by mistake. The choice is kept in this browser's local storage and applies to this browser only.

Raw records are kept for 90 days and then deleted. Hourly and daily totals — how many searches, how many bookings, how many visits came from each kind of source and from each state and city, how far visits got, how often each control was clicked — are kept longer, and carry no visit identifier.

No third-party analytics service is running on this site. Server errors are recorded on our own server, grouped by the route that failed with any booking reference removed from it, and are not sent to any third party. Card details never reach our server, so they cannot be in one.

We set no advertising or tracking cookies, and browsing the site — the home page, searches, hotel and city pages — sets no cookie at all, which is why there is no cookie banner to accept. A cookie is set only when you do something that needs one:

• Signing in keeps you signed in for thirty days, and a second cookie, set when you ask for a sign-in link, ties that link to the browser that asked for it for fifteen minutes. A one-time cookie guards the “Is this you?” page for the same fifteen minutes.
• Changing a booking sets a cookie that lasts an hour, so the checkout knows which booking you are replacing.
• Paying: the card form is Stripe’s, and Stripe sets its own cookies on the payment step to prevent fraud, under Stripe’s privacy policy.

Signing out, or the time running out, removes ours. Your browser’s settings can clear or block any of them; signing in and paying do not work without them.

Your filters, declared needs, the result you last selected on a search page, your color scheme and whether your visits are counted are kept in your browser's local storage. They never reach our servers. A half-completed checkout is kept in your browser's session storage so a crash does not cost you the form, and is cleared when the booking completes or the tab closes.

Our Android app searches and books through the same servers as this website, so everything above applies to it as well. What is different:

• It keeps the same anonymous record of use, with a random identifier the app makes up each time it is opened and holds only in its memory, so the identifier is gone when the app closes. It records the screens you open and the booking steps you reach, and never the buttons you tap. The approximate country, state and city described above are recorded for the app's visits in the same way. From version 1.8 the app has its own “Don't count my visits” switch, on its copy of this page, which works the same way for the app.
• It uses no advertising identifier. Each request it makes names the app and its version (for example NJSTravel-Android/1.0) where a browser would describe itself, and carries your phone's time zone so that a deadline is shown in your own time. We read the name to tell the app from a browser, and keep only the fact that it was the app and whether it ran on a phone or a tablet — never the version or the time zone.
• Payments in the app are taken by Stripe's own Android software, and your card details go from it to Stripe directly, never to our servers. To prevent fraud, that software collects information about your device, which Stripe handles under Stripe's privacy policy.
• Once you sign in or book, the app keeps your sign-in session on your phone, and for each booking made in the app, or opened in it from a booking email, its access key, reference, name and dates, so that booking opens from Trips without signing in. When you ask for a sign-in link in the app, it also keeps a code that lets it recognize that link as its own; the code is good only until the link expires.
• While you are signed in, it keeps the last list of your trips it loaded — each booking's reference, name, dates, status and total, and the travelers and price watches you saved, with the travelers' names and dates of birth — so Trips opens with no signal, marked with when the list was loaded. It is forgotten when you sign out, when you delete your account, and when our server says your sign-in has ended.
• It also keeps a copy of the few booking pages you opened most recently, so a booking can still be shown at a front desk with no connection. Signing out of the app, or deleting your account in it, deletes the saved booking pages; the access keys stay, because the bookings outlive the account and those keys still open them.
• All of this is encrypted with a key held in Android's secure key storage and left out of your phone's backups, so none of it travels to another device inside one.
• It remembers the last search you ran — the place, the dates, and how many adults, children and rooms, with each child's age — so the search form is filled in the next time you open it. That copy stays on your phone: it is never sent to us, it is left out of your phone's backups, dates that have passed are dropped rather than offered again, and clearing the app's storage or uninstalling it removes it.

Our browser extension, Resort Fees by NJSTravel, reads the hotel page or hotel search results you are looking at on the sites it supports (Booking.com, Expedia, Hotels.com, Google, Tripadvisor and Kayak), inside your browser: the hotels' names, and the dates, guests and rooms of the stay in the page's address. It compares the names with a list of fees built into the extension. It sends nothing to us or to anyone else, makes no request of its own, stores nothing and asks for no permission beyond running on those sites. If you follow one of its links to our site, you arrive like any visitor, with campaign tags saying you came from the extension. A link to a hotel's rooms also carries that stay's dates, guests and rooms in its address, so our page opens on the same stay.

You can add our connector to Claude, Anthropic's AI assistant, at njstravel.com/mcp. When Claude uses it, Claude sends us only what the question needs: a hotel's name, a city or state, or a place, dates and the number of guests for room prices. We use those to answer and keep none of them. For each use we record which of the two tools was used, how the answer ended, whether a fresh price check was made, the language of the answer and how long it took; never what was asked, and nothing that identifies you. The connector needs no sign-in, and it cannot book or charge anything: booking happens on our site. Its links bring you to our site with campaign tags saying you came from Claude, and you arrive like any other visitor. Its requests come from Anthropic's servers rather than from your device, and pass through Cloudflare like every request to our site. What Claude itself keeps is covered by Anthropic's own privacy policy.

If you use NJSTravel in ChatGPT, ChatGPT sends us the hotel, place, dates and party your question needs, and with every request an anonymised user identifier, an approximate location (city, region, country and time zone) and the language. We use the question to answer and keep none of it, and we do not store the identifier or the location. For each use we record which tool ran, how the answer ended, whether a fresh price check was made, the language and how long it took.

Our booking database is backed up nightly. The database copy is encrypted with AES-256-GCM before it is written, so a copy that has been tampered with fails to restore rather than restoring quietly altered records. Copies of it, and of the whole server, are kept on our server, on a backup server at the same site and on encrypted drives kept off-site.

This site is for adults booking travel, and we do not knowingly collect personal information from children under 13. When you book for a family, you give us what the hotel or airline needs about the children traveling with you — their ages for a hotel room, and for a flight each child passenger’s name, date of birth and gender marker — and we use it only for that booking, kept with it as described above. If you believe a child has given us personal information, write to help@njstravel.com and we will delete it.

Every company that handles your data for us, in one place. We sell nothing to anyone, and none of the companies above PayPal and Venmo may use it for their own advertising.

• LiteAPI (hotel bookings) and Duffel (flight bookings): what the hotel or airline needs to make your reservation.
• Stripe: your payment.
• Our mail provider: the emails we send you and the ones you send us.
• Cloudflare: carries every request to our server.
• Google: a Google Wallet pass, only when you add one.
• PayPal or Venmo: an approved Fee Promise payment, sent to the account you name there, under their own privacy policies.

You can delete your account yourself, at any time, on the Delete your account page, or from Trips in our Android app. It deletes the travelers you saved, your price watches and any newsletter subscription, ends every sign-in for your address on every device and cancels any sign-in link not yet used, straight away. It does not delete booking records, which we keep for the seven years described above; they are held against the email address a booking was made with, so signing in again with that address shows them again. It does not delete your conversations with our support team, which are kept as described under “Support and our staff”. Deleting your account does not cancel a booking.

For anything else, ask us: for a copy of what we hold about you, or for it to be corrected or deleted, and we will do it, with two limits. Deletion cannot extend to booking records we are legally required to retain, or to a booking that has not yet been traveled. And a support conversation is kept for two years after it is closed: when you ask, we remove the words of your messages and the files you sent, each replaced by a dated note that it was removed, but the record that the conversation took place, with its subject and the contact details it was opened with, stays until then. We respond within thirty days.

TravelSyncro LLC, a New Hampshire limited liability company, of 221 Main St Ste N, Nashua, NH 03060.

Email help@njstravel.com, quoting your booking reference. Replies to any confirmation email reach the same place. Phone: (603) 207-1674.