1. Who is responsible
TripNexa is the name of the travel-planning service described in this notice.
OWNER REVIEW: insert the legal entity or responsible individual, registered address, country, privacy contact and any required representative or data protection officer details. Confirm the effective date.
2. The public website
This marketing website provides product information and links to the separate TripNexa application. It does not provide an account sign-up form, collect payment details or accept uploaded documents. The production marketing pages use Google Analytics to understand website visits and page usage. Google Analytics may use cookies and process technical information about your browser and device. This website integration does not send private trip documents or booking details to Google Analytics.
Trip Examples and payment options request public information from the TripNexa application. The application counts catalog views, filtering and public-itinerary actions without attaching account identifiers or private trip content to those events. Copying an example uses a temporary application cookie to resume your selection after sign-in.
The homepage product video is delivered by an external media CDN. Your browser may contact it for video metadata and playback; automatic playback is limited to when the video is visible and respects reduced motion. Hosting and network services may process request information such as IP addresses, requested pages, timestamps and browser details when delivering the website.
OWNER REVIEW: identify the actual hosting and network providers, their logging practices, retention and any additional tools introduced before launch.
3. Information in the application
When you use the separate application, its features involve information you provide, including:
- Account details such as your email address, account profile and authentication information.
- Trip names, destinations, dates, travelers, preferences, planned activities, booking details and notes.
- Files you choose to upload, such as tickets, confirmations and personal travel documents, together with any labels or traveler details you add.
- Subscription, purchase and trip-credit records needed to provide paid features.
- Usage, security and diagnostic events used to operate and protect the service.
The information associated with a trip depends on which optional features you use. Avoid adding personal information you do not need for your trip.
4. How features use information
The app uses saved information to organize trips, build and edit itineraries, retrieve files, maintain account access and manage premium entitlements. Security and diagnostic records support protection and troubleshooting.
OWNER REVIEW: confirm each processing purpose and applicable legal basis, any legitimate-interest assessment, required notices for other travelers’ data, age requirements and the exact operational event inventory.
5. AI, maps and optional providers
AI planning may send relevant trip information and prompts to the configured AI service. If you request document extraction, the selected file is sent for processing and the resulting details are presented for review. Uploading a document is separate from requesting extraction.
Place search, photos, restaurants and interactive maps can involve Google services. Generated Full Travel Book maps may use Geoapify. Before You Go uses relevant destination, date and passport-country context for practical guidance; critical claims require official evidence. Calendar files are exports rather than automatic calendar synchronization. Optional social login involves the provider you select, when that login method is available. Payments may be handled by Stripe and payment methods made available through it. Files may be handled by a configured storage provider.
OWNER REVIEW: confirm the providers actually enabled at launch, data categories sent, contractual roles, data-processing terms, processing locations, international-transfer arrangements and applicable provider privacy links. No data-residency or AI-training guarantee is made by this draft.
6. Shared itineraries and private files
A public trip link makes the shared itinerary available to people who have the link. The app excludes private notes, private ticket file links and Wallet documents from that public view. Sharing controls let you hide accommodation details and associated routes, disable sharing or replace the link.
Public itinerary examples
The separate “Share an anonymized version of this trip” setting is off by default. If you turn it on, eligible completed trips may produce a public example discoverable in search engines and Trip Examples.
These public copies contain only reviewed destination and place names, day numbers, general schedule times, meal types and transport choices. They exclude your identity and account identifiers, traveler details, exact travel dates, flights, accommodation, private addresses, booking references, personal notes and uploaded documents. Unreviewed free text is not published.
You can turn this setting off in the trip planner at any time. The public example is then unpublished and removed from future sitemaps. This setting is separate from an itinerary link you explicitly choose to share.
People who can view a shared itinerary may copy it. Revoking a link cannot remove copies someone has already made.
7. Cookies and account sessions
The application uses cookies to maintain sign-in sessions. External authentication and payment services may also use their own cookies during their flows. The marketing website and the application have different functions; visiting this website does not sign you into the app.
OWNER REVIEW: complete the cookie inventory, providers, purposes and lifetimes for the deployed service. Review consent requirements for non-essential analytics and advertising.
8. Affiliate links and external sites
Booking links may take you to a third-party website with its own privacy practices. Affiliate links may identify a referral. The application can record outbound affiliate interactions to operate its referral features. Read the provider’s notice before making a booking.
9. Retention and security
Uploaded travel documents have no automatic expiry and are not automatically deleted when a trip ends. Documents attached to your trips may remain stored indefinitely while you keep them and your account, until you remove them or request deletion, subject to legitimate legal or security requirements. Unattached uploads and files marked for removal are handled by the application's cleanup process.
Deleting a file, trip or account initiates the applicable removal process; storage cleanup and any required retention may affect when deletion is complete. Keep your own copies of essential documents.
TripNexa includes access controls for accounts, trips and private files. This notice does not promise absolute security or end-to-end encryption.
OWNER REVIEW: specify retention for accounts, trips, uploads, backups, support records, security logs and financial records; explain deletion timing, legal retention obligations and the verified security description.
10. Your choices and requests
You can edit information in available account and trip controls and manage whether a trip is shared. The rights and formal request procedures that apply depend on the service’s legal context and your location.
OWNER REVIEW: provide a verified privacy request channel, explain applicable access, correction, erasure, portability, objection and consent-withdrawal rights, response periods and the relevant supervisory authority. Complete this section before publication.
11. Updates and contact
When approved, changes to this notice should be dated and communicated where required. See Contact for the current availability of a public support channel.
OWNER REVIEW: approve the final notice, add the effective date and confirm how material changes will be communicated.