Privacy
A clear view of what the connected product may handle.
This integration draft describes the data flow currently implemented. It still requires formal legal review before production.
Current supplier connections
Activity searches and details are requested from GoSure's server, which then calls the Viator Partner API. The Viator API key is not sent to the browser.
Accommodation properties and prices remain labelled sample content. TuGo questionnaire metadata is live Development data, while TuGo products and quotes remain unavailable in this environment.
Future supplier interactions
The current Viator search sends destination, optional dates, sort order, result count, language, and currency. GoSure does not send names, emails, medical answers, or payment information to Viator.
A future TuGo quote may send necessary trip and traveller information only after the required product configuration is validated. GoSure's Booking.com link opens the provider's main website without transferring the sample destination, dates, or guest fields.
The production version will identify each provider before information leaves GoSure and will document the applicable provider policies.
Analytics and sensitive information
The future analytics plan excludes names, birth dates, email addresses, medical answers, payment information, access tokens, and secrets.
Consent, retention, access, correction, and deletion language must be reviewed before the connected product is launched.