dvrLogin to Portal phoneRequest a call back
  • phone +(44) 1252 123456
  • email sales@gamaaviation.com
Welcome to Gama Aviation

October 27 2021

Cookie policy

Gama Aviation Plc and its subsidiary companies operate a strict privacy policy around the world. We are committed to being transparent about the technologies we use, and we’ve outlined below how we use cookies when you visit our website.

Cookies

We use cookies to improve and customise your experience of our website; cookies are not harmful to your device. By using our website(s) and accepting cookies you agree that we can place these types of cookies on your device.

If the user has any doubt as to the use of cookies then the user should decline receiving cookies from our websites.

What are cookies

Cookies are small text files that are placed on your device by websites you visit. Cookies help make this website work and provide information to us about how users interact with it. We do not seek to identify individual visitors unless they volunteer their contact details through one of the web forms operating on this site. In such cases the information is used by Gama Aviation Plc and its subsidiaries to improve your website experience and the information that we provide to you. We will never sell this information to third parties or use it in a way that contravenes our privacy policy. We use cookies primarily from Google Analytics and Hubspot to deliver this function. On November 1, 2019, Hubspot made a change to its Google Analytics integration that prevents the Google Analytics tracking script from firing until a visitor opts in to cookie tracking via the HubSpot cookie banner. Therefore, according to this functionality, if you decline to receive cookies from us via this banner then you should not receive cookies from either party (More information can be found here)

If any website user has any doubt about how this information is used, then the user is requested to decline receiving cookies from our websites..


How do I opt out of cookies?

In the first instance, if you have any doubt you should decline the use of cookies. If you have accepted cookies and wish to change your cookie settings then the you can manage the cookies that you allow on your computer through the internet browser that you use. You can block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies by doing so this may affect some minor aspects of your website experience, however all our content outside of any ‘walled gardens’ such as our portal will be accessible to you.

Cookie settings in Internet Explorer https://support.microsoft.com/en-us/help/17442
Cookie settings in Microsoft Edge https://privacy.microsoft.com/en-us/windows-10-microsoft-edge-and-privacy
Cookie settings in Firefox https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences
Cookie settings in Chrome https://support.google.com/chrome/answer/95647?hl=en
Cookie settings in Safari https://support.apple.com/kb/PH21411?locale=en_GB&viewlocale=en_US


The type of cookies that Gama Aviation uses (or may use)

The first section provides details of those pertaining to Hubspot and the second, pertains to those used in conjunction with Google Analytics.

Cookies associated with Hubspot

Necessary cookies

These are essential cookies that do not require consent.

__hs_opt_out

  • This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again.
  • This cookie is set when you give visitors the choice to opt out of cookies.
  • It contains the string “yes” or “no”.
  • It expires in 13 months.

__hs_do_not_track

  • This cookie can be set to prevent the tracking code from sending any information to HubSpot.
  • It contains the string “yes”.
  • It expires in 13 month

__hs_initial_opt_in

  • This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode.
  • It contains the string “yes” or “no”.
  • It expires in seven days.

__hs_cookie_cat_pref

  • This cookie is used to record the categories a visitor consented to.
  • It contains data on the consented categories.
  • It expires in 13 months.

hs_ab_test

  • This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before.
  • It contains the id of the A/B test page and the id of the variation that was chosen for the visitor.
  • It expires at the end of the session.

_key

  • When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again.
  • The cookie name is unique for each password-protected page.
  • It contains an encrypted version of the password so future visits to the page will not require the password again.
  • It expires in 14 days.

hs-messages-is-open

  • This cookie is used to determine and save whether the chat widget is open for future visits.
  • It is set in your visitor’s browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity.
  • If your visitor manually closes the chat widget, it will prevent the widget from re-opening on subsequent page loads in that browser session for 30 minutes.
  • It contains a boolean value of True if present.
  • It expires in 30 minutes.

__hs-messages-hide-welcome-message

  • This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed.
  • It contains a boolean value of True or False.
  • It expires in one day.

__hsmem

  • This cookie is set when visitors log in to a HubSpot-hosted site.
  • It contains encrypted data that identifies the membership user when they are currently logged in.
  • It expires in one year.

__hs-membership-csrf

  • This cookie is used to ensure that content membership logins cannot be forged.
  • It contains a random string of letters and numbers used to verify that a membership login is authentic.
  • It expires at the end of the session

__hs_langswitcher_choice

  • This cookie is used to save the visitor’s selected language choice when viewing pages in multiple languages.
  • It gets set when an end user selects a language from the language switcher and is used as a language preference to redirect them to sites in their chosen language in the future, if they are available.
  • It contains a colon delimited string with the ISO639 language code choice on the left and the top level private domain it applies to on the right. An example will be “EN-US:hubspot.com”.
  • It expires in two years.

__cfruid

  • This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. It expires at the end of the session.

Performance cookies

These are non-essential cookies controlled by the cookie banner. If you’re a visitor to a site supported by HubSpot, you can opt out of these cookies by not giving consent.

__hstc

  • The main cookie for tracking visitors.
  • It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
  • It expires in 13 months.

hubspotutk

  • This cookie keeps track of a visitor’s identity. It is passed to HubSpot on form submission and used when deduplicating contacts.
  • It contains an opaque GUID to represent the current visitor.
  • It expires in 13 months.

__hssc

  • This cookie keeps track of sessions.
  • This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.
  • It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.
  • It expires in 30 minutes.

__hssrc

  • Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser.
  • If this cookie does not exist when HubSpot manages cookies, it is considered a new session.
  • It contains the value “1” when present.
  • It expires at the end of the session.
  • If you are logged in to HubSpot, HubSpot will set additional authentication cookies. Learn more about cookies set in the HubSpot product. You can also see whether a contact accepted these cookies in their timeline.

Targeting cookies

Advertisement cookies are ad pixel cookies (such as Facebook, LinkedIn and Google) that you can opt to install using the HubSpot ads tool.

  • If you have the Facebook pixel code installed on your website, Facebook may set a cookie in a visitor’s browser.
  • If you use the HubSpot ads tool to select and install your Facebook pixel on pages with the HubSpot tracking code, HubSpot will link the placing of that pixel code to the cookie notification banner. If you require opt-in consent via this banner, the Facebook pixel will not be able to set any cookies until the visitor has have opted in.
  • If you manually placed the pixel code on pages (e.g., by editing your site header HTML), HubSpot will not be able to control the visitors Facebook is able to set cookies on.
  • For additional information, refer to Facebook’s business tools terms and Facebook’s cookie consent guide.

Functionality cookies

Chatflow cookie
This is the cookie used for the chatflows tool. If you’re a visitor, this allows you to chat with a representative on the site.

messagesUtk

  • This cookie is used to recognize visitors who chat with you via the chatflows tool. If the visitor leaves your site before they’re added as a contact, they will have this cookie associated with their browser.
  • If you chat with a visitor who later returns to your site in the same cookied browser, the chatflows tool will load their conversation history. The cookie is controlled by the Consent to collect chat cookies setting in your chatflow.
  • If this setting is disabled, the cookie is controlled by the Consent to process setting in your chatflow.
  • HubSpot will not drop the messagesUtk cookie for visitors who have been identified through the Visitor Identification API. The analytics cookie banner will not be impacted.
  • This cookie will be specific to a subdomain and will not carry over to other subdomains. For example, the cookie dropped for info.example.com will not apply to the visitor when they visit www.example.com, and vice versa.
  • It contains an opaque GUID to represent the current chat user.
  • It expires in 13 months.

Chatflow cookie consent text
With the Consent to collect chat cookies setting enabled, HubSpot will prompt visitors for consent to drop a cookie in their browser before the start a chat or when they attempt to the leave the page during a chat conversation. This cookie is used to interact with website visitors and provide a visitor’s chat history.

  • If you choose to display the banner before the visitor starts a chat and the visitor does not give consent, they will not be able to start the chat.
  • If you choose to display the banner upon exit intent, however, the visitor can start the chat, but if they don’t consent to cookies before navigating away from the page, the chat widget will reset and the conversation will end.
  • With this setting disabled, a visitor can start a chat and give consent to process their information via the Consent to process setting.
  • Visitors can also accept or decline cookies on the HubSpot cookie banner if it is enabled on your pages.
  • If a visitor accepts the cookie when they start a chat, but then clicks Decline on the HubSpot cookie banner, the cookie will be removed.
  • If a visitor clicks Decline on the HubSpot cookie banner before starting a chat, HubSpot will not drop a cookie or prompt them to consent to cookies in the chat widget.

Cookies associated with Google Analytics

Gama Aviation websites use Google Analytics so that we can improve the content, relevance and experience of the sites to our prospects and customers. These cookies, like those stated above, are included within your acceptance of the use of cookies as per the banner on our web properties. If you are uncertain about the use of these cookies then please decline the use of them.

gtag.js (Google Analytics 4) – cookie usage
For Google Analytics 4, the gtag.js JavaScript library uses first-party cookies to:

  • Distinguish unique users
  • Distinguish sessions for a user
  • When using the recommended JavaScript snippet cookies are set at the highest possible domain level. For example, if your website address is blog.example.co.uk, gtag.js will set the cookie domain to .example.co.uk. Setting cookies on the highest level domain possible allows measurement to occur across subdomains without any extra configuration.

Note: gtag.js does not require setting cookies to transmit data to Google Analytics.

gtag.js sets the following cookies:

  • _ga 2 years Used to distinguish users.
    _gid 24 hours Used to distinguish users.
    _ga_ 2 years Used to persist session state.
    _gac_gb_ 90 days Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

gtag.js and analytics.js (Universal Analytics) – cookie usage
The analytics.js JavaScript library or the gtag.js JavaScript library can be used for Universal Analytics. In both cases, the libraries use first-party cookies to:

  • Distinguish unique users
  • Throttle the request rate
  • When using the recommended JavaScript snippet cookies are set at the highest possible domain level. For example, if your website address is blog.example.co.uk, analytics.js and gtag.js will set the cookie domain to .example.co.uk. Setting cookies on the highest level domain possible allows measurement to occur across subdomains without any extra configuration.

Note: gtag.js and analytics.js do not require setting cookies to transmit data to Google Analytics.

gtag.js and analytics.js set the following cookies:

  • _ga 2 years Used to distinguish users.
  • _gid 24 hours Used to distinguish users.
  • _gat 1 minute Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_.
    AMP_TOKEN 30 seconds to 1 year Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.
  • _gac_ 90 days Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out.

ga.js – cookie usage

The ga.js JavaScript library uses first-party cookies to:

  • Determine which domain to measure
  • Distinguish unique users
  • Throttle the request rate
  • Remember the number and time of previous visit
  • Remember traffic source information
  • Determine the start and end of a session
  • Remember the value of visitor-level custom variables
  • By default, this library sets cookies on the domain specified in the document.host browser property and sets the cookie path to the root level (/). This library sets the following cookies:
  • __utma 2 years from set/update Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.
  • __utmt 10 minutes Used to throttle request rate.
  • __utmb 30 mins from set/update Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.
  • __utmc End of browser session Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.
  • __utmz 6 months from set/update Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.
  • __utmv 2 years from set/update Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.
  • _setDomainName – Sets the domain to which all cookies will be set.
  • _setCookiePath – Sets the path to which all cookies will be set.
  • _setVisitorCookieTimeout – Sets the Google Analytics visitor cookie expiration in milliseconds.
  • _setSessionCookieTimeout – Sets the new session cookie timeout in milliseconds.
  • _setCampaignCookieTimeout – Sets the campaign cookie expiration time in milliseconds.
  • _storeGac – Pass in false to disable the GAC cookie. Defaults to true

urchin.js – cookie usage
Historically, Google Analytics provided a JavaScript measurement library named urchin.js. When the newer ga.js library launched, developers were encouraged to migrate to the new library. For sites that have not completed the migration, urchin.js sets cookies identically to what is set in ga.js. Read the ga.js cookie usage section above for more details.

Optimize – cookie usage
For websites using Optimize, the following cookies are used in addition to the other cookies described in this document:

  • _gaexp Depends on the length of the experiment, but typically 90 days. Used to determine a user’s inclusion in an experiment and the expiry of experiments a user has been included in.
  • _opt_awcid 24 hours Used for campaigns mapped to Google Ads Customer IDs.
  • _opt_awmid 24 hours Used for campaigns mapped to Google Ads Campaign IDs.
  • _opt_awgid 24 hours Used for campaigns mapped to Google Ads Ad Group IDs
  • _opt_awkid 24 hours Used for campaigns mapped to Google Ads Criterion IDs
  • _opt_utmc 24 hours Stores the last utm_campaign query parameter.
  • _opt_expid 10 seconds This cookie is created when running a redirect experiment. It stores the experiment ID, the variant ID and the referrer to the page that’s being redirected.

For further information about online privacy:
https://ico.org.uk/for-the-public/online/cookies/

CHANGES TO THIS PRIVACY & COOKIE POLICY

We may update this policy from time-to-time by posting a new version on our website, please check regularly to be aware of any updates.