Your places. Your privacy.

01

Who this policy covers

This policy explains how Routeyst handles information when you browse guides, use travel essentials, sign in, save ideas, share collections, submit enquiries or have a manually recorded booking. Contact contact@routeyst.com for privacy questions, access, correction or deletion requests.

Public destination guides remain available without an account. Routeyst is an independent travel project; this policy describes current website features rather than a future mobile app or payment service.

02

Information we receive

Google sign-in supplies basic identity information, including your account ID, name and email; Firebase may also receive a profile picture. We store account saves, visited-place markers, collection names, cover choices, private collection and individual-save notes, and optional trip dates, traveller counts and planning/completion status. You may save an optional phone number for enquiry contact autofill; it is not OTP-verified and is not a marketing subscription. Signed-in enquiries are associated with your account and optionally a trip so you can view their references and customer-facing updates. We use your account email for transactional enquiry update notifications and store delivery attempt records for retries; these notifications do not subscribe you to marketing. We also record your current vote on a shared collection or your choice within each eligible trip section; other visitors receive aggregate counts, not voter identities. We do not ask for access to your Gmail messages or Google contacts.

An enquiry includes your name, contact details, dates, guest count, requested listing and questions. A manually recorded booking can include provider references, dates, guest count, agreed room or package, totals, recorded received/refunded amounts and cancellation terms. We do not collect card numbers, banking passwords or OTPs through these forms.

Hosting and service providers can process technical information such as request logs, IP addresses and browser details to operate and secure the website. Enquiry abuse prevention stores a hashed daily network identifier and request fingerprint.

03

Why we use it

We use account information to authenticate you, maintain your profile, sync saves and show your private booking history. We use enquiry and correspondence details to answer requests and communicate with the relevant provider. Booking records help keep a clear record of an arrangement.

Security information helps prevent duplicate or abusive submissions and protect the service. We do not sell personal information or automatically subscribe you to marketing just because you sign in or enquire. Any future marketing or advertising feature will need an appropriate notice and choices.

04

Who can receive information

Firebase/Google handles authentication and database services; hosting providers operate the website. Authorised Routeyst administrators can access records needed for support and administration. We may share relevant enquiry or booking details with the property or tour provider involved in your request.

We may disclose information where required by law or necessary to address fraud, security or a legal claim. Service providers may process information outside your home region under their own arrangements. We do not claim that every record or technical log stays exclusively in India.

05

Private notes and public collection links

Collections are private until you enable sharing. Anyone who obtains a shared link can see the collection name, cover and selected published places, stays, tours or travel stories. Signed-in link holders can vote and compare options. Each account has one current vote per collection, which can be changed or removed. Results are not restricted to invited friends; anyone with the link and an account can participate. Later edits update that shared view. Private reminders, account email, profile and booking history are excluded.

Turn sharing off to revoke future access, or delete the collection. This does not remove screenshots or copies already made by others. A shared link is unlisted, not password-protected; avoid personal details in collection names. WhatsApp sharing opens a prefilled message which you choose whether to send.

06

Cookies and browser storage

Firebase maintains browser sign-in state. Routeyst uses an HTTP-only server session cookie for private account features and administration; the current cookie lasts up to five days. Signing out removes the website session and Firebase sign-in state.

Older browser-only bookmarks may remain in local storage and are not automatically imported into an account. Clearing this site’s browser data removes local data but does not delete account records in Firestore. Essential authentication/storage is separate from advertising cookies. Routeyst records cookie-free daily totals for city selections, guide and hub clicks, save attempts, completed saves, shared shortlists, votes and comparisons. These counters contain no account IDs, names, contact details, search terms or page URLs. We honour the browser Do Not Track preference. To limit abuse, a hashed network address may be held briefly in server memory; it is not written to these counters.

07

Weather, maps and external services

Weather requests pass through Routeyst’s server to WeatherAPI.com using the selected destination’s configured forecast area. Weekend ideas load from Routeyst’s own curated listings. These tools do not require your private home address.

When you open Google Maps, WhatsApp, an external image host or a provider’s website, that service processes requests under its own policies. A Weekend Ideas Maps link includes the place name and location context in its search query. Routeyst does not automatically send a WhatsApp message or control external conversations. External image requests can disclose technical browser information to the image host.

08

Retention and security

We keep account saves and collections until you remove them or request account deletion. Enquiries, correspondence, booking records and administrative audit history are retained as needed for support, disputes, security and applicable record-keeping obligations. We review deletion requests against those needs rather than promise that all records disappear instantly.

Access controls, server-side account checks and restricted database access help protect information. No system can guarantee absolute security. Keep your Google account secure and tell us promptly if you suspect unauthorised access or an incorrect booking record.

09

Your choices and requests

You can update your display name and enquiry contact details, clear your optional phone number, remove saves and visited markers, change or remove votes, edit or delete collections, disable sharing and sign out. To request access to, correction of or deletion of other personal information, email contact@routeyst.com, preferably from the account email involved. We may need to verify identity without requesting your password.

Account deletion is currently handled through support, not an automatic dashboard button. Deleting an account may require separate removal of database records and shared links. Where a record must be retained, we will explain the applicable reason. You can also raise concerns through available lawful grievance channels.

10

Children and policy changes

Accounts are intended for adults aged 18 or over. We do not knowingly seek account information from children. An adult should manage family-travel enquiries. If you believe a child has submitted personal information, contact us so we can review and act appropriately.

We update this page when our information handling changes. A future mobile app, affiliate tracking, advertising, analytics or payment flow may require an updated notice before it starts. The date above identifies the latest version of this website policy.