CloverTrip – Privacy policy (English)
11 novembre 2026 · La version anglaise à jour est présentée ci-dessous.
Traduction à titre informatif. Seule la version anglaise fait foi.
Who operates CloverTrip
CloverTrip is provided by HIH-DIGITAL LIMITED (trading as HIH Digital), Ireland. Published correspondence address: Unit 12, CTEK Building 1, Carrickmacross, A81 K316, Ireland. Privacy enquiries: michael.meissner@hih-digital.com. Contact your tour operator about the booking records it controls. HIH processes operator-provided travel information on the operator's documented instructions and processes necessary platform-security and business-contact information for its own service responsibilities. Your operator must supply its own privacy information. This notice is not proof that an individual operator agreement has been signed.
Travel access, devices and service events
Your booking code is sent to the regular CloverTrip API to resolve and retrieve the authorised operator and journey. The service processes access/session information, device identifiers and selected service events, such as opening a trip, map or document. These records are not described as anonymous. Expedition registration additionally processes a device public key, its fingerprint, proof of possession and approval/revocation status. Authorised administrators can manage devices only within their permitted workspace. Registration alone does not authorise a device.
Content and local storage
Itineraries, approved documents and other journey information are provided by your operator. Messages, feedback, photographs or notes you submit to your operator are transmitted to the service. Submitted photos can retain metadata, including location coordinates contained in the selected image. Private travel-diary content in the local diary feature is separate from those uploads. Local export, sharing and operating-system backups can send selected content to the destination you choose. Signing out or uninstalling is not a promise that all server records, backups or private memories have been erased.
Location, maps, weather and notifications
Location permission is used for relevant foreground map/emergency functions. The inspected app path does not request background location. A user-selected emergency message can include coordinates; sending remains your action. This is separate from location metadata in uploaded photographs.
The Nepal online map uses OpenStreetMap tiles. Tile requests disclose connection information and the requested map area to the configured provider; see https://osmfoundation.org/wiki/Privacy_Policy . Other authorised country profiles can use their separately configured map service. Weather for itinerary locations may be requested by the backend from Open-Meteo; this is not automatically your current device position. Online maps require connectivity and are not an offline-navigation or rescue service. Push libraries are included but legacy push initialisation is blocked in the current regular journey path; this is not a promise that push is enabled.
Purposes, recipients and choices
Journey access, document delivery, operator messaging, authorised offline packages and synchronisation support the travel service. Your operator determines the lawful basis for its records, including contract performance where applicable. HIH's necessary and proportionate security/abuse prevention and service analysis are distinguished from optional consent-dependent processing. An operating-system permission is not a substitute for an applicable legal basis.
Authorised operator personnel and necessary HIH support/technical providers can process information within their roles. Hosting is provided through netcup; backups use Wasabi storage; enabled transactional email can use Resend; operational monitoring can involve Netdata Cloud. Apple platform services and configured map/weather providers are additional technical recipients where the corresponding functions are used. Processing is not represented as exclusively within the EEA: provider services can involve other countries, including the United States. Contact HIH for applicable provider and transfer-safeguard information. This notice does not assert that every provider contract or transfer assessment has been independently verified.
CloverTrip does not sell personal data or use cross-company advertising tracking under HIH's adopted policy. There is no advertising in the inspected app path. Internal service statistics and technical providers are not a claim of zero data collection or no third-party disclosure.
Retention and deletion - current limitation
HIH's adopted standard is 90 days after actual journey end for operator-held journey records, messages, feedback and photos; API/security logs have a 30-day target; device identifiers are subject to logout/revocation and the documented latest removal date. Complete automatic enforcement across all components is not established and is not promised here. Erasure requests require coordination with the operator and the actual storage concerned. Private memories retained locally can require a separate local deletion action.
HIH's adopted backup retention period is 30 days. Since 11 November 2026, new backups in the dedicated production database bucket have a verified 30-day COMPLIANCE lock. A new encrypted backup was read back successfully and is locked until 11 December 2026 at 09:45:33 UTC. The bucket now has an automatic expiry rule after 30 days and permanent noncurrent-version removal one day later; provider processing can add further delay. This is not a guarantee of complete erasure exactly on day 30.
Older backups created under the previous 90-day COMPLIANCE setting remain locked; a verified older copy cannot be deleted before 9 February 2027 at 07:00:05 UTC. Such existing locks cannot be shortened. Uploaded-file and configuration backups in the separate legacy path now have an hourly 30-day expiry process; 204 expired objects were removed and their absence verified on 11 November 2026. Local encrypted migration backups also have an hourly 30-day expiry process. Hourly scheduling and provider processing do not provide second-exact deletion. The production server’s customer-managed snapshot and custom-image lists were checked on 11 November 2026 and were empty. This does not establish whether the hosting provider retains additional internal copies. Signing out or deleting a live record therefore does not immediately erase every backup copy. This notice does not change the adopted 30-day policy or certify that all retention and deletion obligations have been completed.
Rights and contact
Subject to applicable conditions you can request access, correction, erasure, restriction, portability, object to processing and withdraw consent for future consent-based processing. Contact your operator or HIH using the business addresses above; do not send booking secrets or identity documents unnecessarily. You may complain to the Irish Data Protection Commission, https://www.dataprotection.ie/ , or another competent supervisory authority. The service uses HTTPS, scoped access checks and encrypted storage in the inspected private-data paths; absolute security is not guaranteed. The website has a separate notice covering website cookies and analytics.