Tours, activities and private transfers for WordPress, with a booking request form. It is a request and confirmation system: the agency answers each request, and there is no payment processing.

Website and documentation: tripvance.net

Tours

A gallery, highlights, an itinerary (days, or a timeline for a day trip), inclusions, a meeting point and FAQs. Eight layouts (Salma, Sara, Atlas, Sahara, Medina, Qamar, Noir, Classic) draw the same content and booking form, site wide or per tour. Empty sections are never shown. Tours are filed by destination, type, departure, length and category.

Bookings

A date, a party size and a way to reach the traveller; optional seat capacity is held atomically. Each request has statuses, notes, quotes and a Guest Pass, with an operations dashboard.

Transfers

Private transfers with their route and stops, Vehicle Types priced per vehicle and an optional Fleet, booked through the same request system.

Tailor-made trips

A trip builder wizard, a request inbox, and a private proposal page per traveller, who confirms it or asks for changes; a confirmed proposal becomes a booking with its Guest Pass.

Two presentations

Standard (a catalogue with prices and a booking form) or Luxury Editorial (a travel magazine with a private enquiry), switched without touching your content.

Multilingual

Ready for translate.wordpress.org, with French, Spanish and Arabic fallbacks and right-to-left layouts. Polylang is fully supported: translations are linked, addresses can follow the language, and a switcher fits the theme’s menus.

Search engines

No canonical, meta description, Open Graph or site-wide schema: those belong to your SEO plugin. Eligible tour and activity pages get limited Product data (the bookable price and genuine on-site reviews), merged into Rank Math’s graph when it is active.

Also included

An optional cookie consent banner, listings with filters, a Tours block and shortcodes, a homepage template, a car hire template and a WooCommerce import with a dry run.

Privacy

Booking requests and operational records are stored in the site’s database. These can include names, email and WhatsApp/telephone numbers, country, travel dates, party sizes, pickup details, messages, quotes and records of payments received outside the site. Transfer requests can also include a drop-off address, pickup and return times, luggage and flight details. Notifications use wp_mail() and the mail provider configured by the site owner. Tripvance sends no telemetry to its developer and loads no remote fonts.

WordPress personal-data export and erasure tools are supported for bookings matched by email, including bookings in the trash; transfer bookings are exported with their route, pickup, drop-off, return and flight details. Erasure removes identifying booking fields, campaign attribution, email queue/history and free-text history notes, clears linked reservation emails and pickup details, and revokes private links. Non-identifying booking, quote and payment records are retained. For requests without an email address, the operator must identify the relevant records manually. Backups and mail already delivered by the site’s mail provider are outside this eraser.

Optional first-party campaign attribution uses the wptm_attr cookie for up to 30 days. It stores UTM values, referral code, referring host (not the full referring URL), first tour visited and timestamp. It is read or written only when the visitor has consented to analytics; without consent it is disabled and an existing cookie is expired on the next uncached page request. Booking totals and manually entered attribution remain available. Consent is taken from the WordPress Consent API when a consent manager configures opt-in mode, otherwise from the Analytics choice in Tripvance Privacy & Cookies when that module is switched on. Other integrations can supply the visitor’s consent through the wptm_attribution_consent filter. Do not return true globally as a substitute for visitor consent.

The optional Privacy & Cookies module (off by default) stores the visitor’s choice in one first-party cookie, wptm_consent, holding the accepted categories, the consent version and a timestamp.

Tailor-made trip requests store the name, email address and, when given, telephone, country and message a traveller enters, with their travel preferences. Nothing is sent or stored while they move between the wizard’s steps; the request is saved once, when they press Send. Requests are private, excluded from search, feeds, REST and sitemaps, and are covered by the WordPress export and erasure tools (erasure keeps the reference, dates, length and party size). A proposal page opens only with its private key (a random 43-character key, stored as a salted hash), is never indexed or cached, and the changes a traveller asks for on it are kept on the request and removed by the erasure tool.

Issued quotes, invoices and trip programmes are stored in the site’s database as frozen copies of what they printed (the customer’s name, the billing details an operator entered, the trip and the prices), together with the PDF file as issued. They are never written to the uploads folder, and a customer can download one only when the agency shared it, through their own Guest Pass or quote link. Erasure keeps issued invoices, which are accounting records, and removes the booking’s quote and programme documents.

Anti-abuse counters use salted hashes of the requesting IP address with expiring transients. The raw IP is not stored in those counters. Private Guest Pass, quote and voucher links act as access keys and should be shared only with the intended traveller.

Third-party libraries

TCPDF 6.11.4 by Nicola Asuni — https://tcpdf.org — LGPL-3.0-or-later (vendor/tcpdf/LICENSE.TXT). Bundled to produce PDF documents on the site’s own server; trimmed to the engine and two fonts.
DejaVu Sans fonts — Bitstream Vera and Arev fonts licence, public-domain changes (vendor/tcpdf/fonts/DEJAVU-LICENSE.txt).

External services

No external service is required for the core booking workflow. Site owners choose the optional links, media and mail service they use and should reflect them in their privacy notice.

WhatsApp: contact buttons open wa.me after a click and may include a prepared message. No WhatsApp API or automatic WhatsApp messaging is included. Terms: https://www.whatsapp.com/legal/terms-of-service ; Privacy: https://www.whatsapp.com/legal/privacy-policy .
YouTube and Vimeo: an operator-supplied video URL can be embedded through WordPress oEmbed; WordPress may request embed metadata and the visitor’s browser connects to the video host when displayed. In the Luxury Editorial experience, a YouTube address pasted into the Video field of the hero or the full-bleed story is embedded directly from www.youtube-nocookie.com and plays on its own, silently, as the background of that one section; nothing is requested from any video host on a site that has not supplied such an address, no script is loaded from a third party at any point, and the embed is never created for a visitor whose browser asks for reduced motion or reports a slow or metered connection. YouTube terms: https://www.youtube.com/t/terms ; Google privacy: https://policies.google.com/privacy ; Vimeo terms: https://vimeo.com/terms ; Vimeo privacy: https://vimeo.com/privacy .
Google Maps and Search: optional meeting-point and weather links open after a click and include the selected place, coordinates or weather query. Terms: https://policies.google.com/terms ; Privacy: https://policies.google.com/privacy .
External media: if an operator enters a remote image or direct video URL, the browser requests that host when the media is displayed. Use the WordPress media library to serve these assets from the site itself.
External payment links: an operator may provide a PayPal or another payment link. The link opens its provider after a click; Tripvance does not process the payment or receive card details. PayPal terms: https://www.paypal.com/legalhub/useragreement-full ; Privacy: https://www.paypal.com/legalhub/privacy-full .