← Help centre

NeoValley Travel

Your journey and your data

How the current service uses and keeps your information.

Planning a journey

With your consent, your trip description, answers and selected places are sent to configured model services to plan your journey. OpenAI generates the itinerary and proposed changes; other planning steps may use DeepSeek. The site stores your draft, generated itinerary, revisions and records needed to resume or undo changes.

Describe practical needs such as walking distance or dietary restrictions. Do not include payment details, identity documents or unnecessary medical diagnoses. A journey can be created without an account; this does not make its contents anonymous.

Returning to your private itinerary

Access permission is kept in the browser that created the journey. Keep its site data and your Reference ID. The ID alone is not permission to read or edit a private Final. Another device or cleared browser data may not be able to restore access. Some older reference-based route summaries use a different sharing model; avoid sharing their IDs if you want to keep them private.

Storage and deletion

Draft access expires after 90 days. Access expiry is separate from deletion: the service does not currently promise automatic deletion of all draft, Final or inquiry records on that date. Replacement previews expire after 30 minutes; expired preview text is cleared when the proposal service next processes that journey. Limited operation records remain to prevent a repeated save.

Use Contact to request a review or deletion of your information. Include the Reference ID or inquiry receipt, without sending browser access tokens. We need to verify the request before changing private records; submitting a request is not confirmation that deletion has finished.

Contacting us

The contact form stores your email, message, consent and optional journey context in the site’s owner inbox. It does not automatically send email. Hashed source and email identifiers help limit repeated submissions; hashing does not make these identifiers anonymous.

Contact NeoValley