# Consent management for your booking engine

Flip.to **only** uses first-party cookies that are placed on the site that the user is visiting. We are a **data processor** (or **service provider**) and our customers have full ownership of all data collected or processed on their behalf.

Flip.to supports consent signals out-of-the box for CookieBot, OneTrust, and Google Tag Manager. Most other consent management platforms integrate with Google Tag Manager, allowing them to provide consent signals without requiring any additional configuration.

{% hint style="info" %}
If you are configuring a consent management platform, you can find more information below on the two types of cookies that are used by Flip.to—**Strictly Necessary** and **Analytics**.

Be sure to include the **asterisk (\*)** when configuring these cookies in your consent management platform. The cookie names are prefixes and the asterisk is a wildcard representing a variety of property-specific suffixes.
{% endhint %}

Flip.to scripts are **essential** and should always run. There are three products, [Spacetime](#spacetime), [Discovery](#discovery), and [Advocacy](#advocacy) that require consent management configuration for your booking engine.

***

## **Spacetime**

Spacetime is behavioral analytics for travel and categorized as **Analytics**, and **places one cookie** on a visitor's browser if and when consent is provided for **Analytics**.

<table><thead><tr><th width="207.66666666666666">Cookie</th><th width="213">Description</th><th>Duration</th></tr></thead><tbody><tr><td>sa_ft*</td><td>Analytics identifiers</td><td>400 days</td></tr></tbody></table>

Based on the visitor's consent, Spacetime logs pageviews without any PII, in the following way:

* When **Analytics** consent is **granted**: the pageview would include the analytics user-id.
* When **Analytics** consent is **not granted**: the pageview would include a randomized and anonymized id.

## **Discovery**

Discovery is akin to shopping cart behavior and categorized as **Strictly Necessary** throughout the customer journey as it’s required for the application to function (website + third party booking engines), in compliance with all consent management and privacy regulations.

Discovery **places one local storage entry** on the visitor's browser.

<table><thead><tr><th width="208">Local Storage</th><th width="217">Description</th><th>Duration</th></tr></thead><tbody><tr><td>ftDiscoveryState</td><td>Maintains guest plan state.</td><td>N/A</td></tr></tbody></table>

The Discovery script logs the completion of the transaction. There are no other cookies or local storage entries.

## **Advocacy**

Advocacy turns travelers into storytellers and categorized as **Analytics,** and **places one cookie** on the visitor's browser when on the booking engine.

<table><thead><tr><th width="208.05859375">Cookie</th><th width="216.671875">Description</th><th>Duration</th></tr></thead><tbody><tr><td>ft-it*</td><td>Maintains Flip.to components' interaction state.</td><td>6 months</td></tr></tbody></table>

***

Spacetime, Discovery, and Advocacy are fully compliant with consent management as well as with all privacy regulations, such as GDPR, CCPA and others.

Flip.to implements a number of measures to comply with privacy regulations. Find out more at our [Privacy and Security Overview](https://policies.flip.to/platform/privacy-and-security-overview) and our [Privacy Policy](https://policies.flip.to/platform/privacy-policy).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flip.to/docs/integrations/booking-engines/consent-management-for-your-booking-engine.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.