Skip to content
NARAYUPlan clearly. Travel easily.
NARAYU TRAVEL PLATFORM

Privacy Policy

How Narayu handles browser-saved trips, forms, analytics, and affiliate links.

Overview

This policy explains how Narayu handles information submitted through forms, saved in the browser, recorded for basic site operations, or passed to a third-party booking provider.

Information Narayu may collect

  • Contact-form name, email, subject, and message
  • Newsletter email address and signup source
  • Anonymous outbound-click records such as provider, placement, route, and date
  • Trip information saved in the browser or, for signed-in users, in a private WordPress post
  • Technical logs maintained by WordPress, the hosting provider, security tools, or error monitoring

Browser-saved trip data

My Trip can store itinerary details, budget entries, reminders, and notes in local browser storage. This data normally stays on that device unless the user exports it or uses an account-saving feature.

Affiliate and booking providers

When a traveler opens a provider link, the provider receives the information contained in the URL and may use cookies or similar technologies under its own privacy policy. Payment and identity information entered on a provider website is handled by that provider, not Narayu.

Retention

Contact messages and subscriber records are retained only as long as reasonably needed for communication, compliance, security, and business records. Anonymous click data may be retained for performance analysis.

Your choices

You may request access, correction, or deletion of information that Narayu controls by emailing hello@narayu.com. Narayu cannot delete information held independently by a booking provider.

Security

Narayu uses reasonable administrative and technical measures, but no internet system can guarantee absolute security. Do not send payment-card data, passwords, or passport images through the contact form.

Changes

This policy may be updated as tools, providers, analytics, or legal requirements change. The current version published on this page applies to future use of the site.