Cookies Policy

Last Updated: 24/06/2021
  1. Introduction

    1. This Cookie Policy explains how Myphizz (“company”, “we”, “us” and “our”) uses cookies on our website: (“website”, “service”).
    2. In some cases, we may use cookies to collect personal information, or that it becomes personal information if we combine it with other information.
    3. Our Cookies Policy explains what cookies are, how we use cookies, other cookies that we may use, your choices regarding cookies, any further information about cookies, any changes to our Cookies Policy and our details.
  2. What are Cookies?

    1. Cookies are simple data files stored in your browser by websites you visit either on your computer or mobile device, allowing the service or a third-party to recognise you.
  3. How Myphizz uses Cookies

    1. When you access and use the service, several cookie files are placed onto your web browser for our website to operate, these are also known as “essential” and “strictly necessary” cookies.
    2. These cookies are used for the following purposes: to enable certain functions of the service, to provide analytics, to authenticate users and prevent fraudulent use of the users. These cookies are known as:

      1. Essential Cookies – used to carry out or facilitate the transmission of communications over a network.
      2. Strictly Necessary Cookies – enable you to use our service and use the features available, such as accessing log ins or secure areas
      3. Session Cookies – also known as a memory cookie, exists only in temporary memory while the user navigates the website. Web browsers normally delete session cookies when the user closes the browser.
      4. Persistent Cookies – these are stored on a user’s device to remember information, settings, preferences, or sign on credentials that a user has previously saved.

    3. Typical data that we store include:

      1. Authorisation Token.
      2. Current User ID.
      3. Current Organisation ID.
      4. Return to Path.
      5. Branding to Use.
  4. Table of Cookies

    Cookie Name Default expiration time Description
    Google Analytics
    _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_<property-id>
    AMP_TOKEN 30 seconds to 1 year Contains a token that can be used to retrieve a Client ID from AMP
    _gac_<property-id> 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.
    __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.
    CognitoIdentityServiceProvider.* Indefinitely (user can remove it manually if they wish) Strictly necessary. Identifies logged in user / stores session info to keep user logged in between visits
  5. Other Cookies

    1. With our cookies, we may also use third-party cookies to report usage of the service and to track how you use our website, for example what pages you visit on and how much time you spend on them for.
    2. Please note that we have no control over third-party cookies, these cookies are likely to be analytical/performance cookies or targeting cookies.
    3. Other cookies may be stored on your computers hard drive by external vendors when this externally hosted content (e.g., videos, input forms) are embedded on the platform.
  6. How to disable Cookies

    1. If you would like to restrict or block the cookies that are set by our website, this can be done through your browser setting.
    2. Essential cookies cannot be rejected as they are strictly necessary to provide you with the services.
    3. Please note, if you do block or restrict cookies, all the features that we use on our service may not be accessible to use.
    4. We do not keep any data; the data is securely stored in the client’s browser environment.
  7. Changes to our Cookie Policy

    1. If the Cookie Policy changes, the revised policy will be updated and include a new date and will be posted on here.
    2. Check back regularly for any updates.
    3. If we make major changes in our Cookie Policy, we will take additional steps to ensure that you are informed of these changes.
  8. Our Details

    1. Our principal place of business is at 27 Bennetthorpe, Doncaster, DN2 6AA
    2. If you have any questions about this policy or our use of cookies, you can contact us:

      1. Email:
      2. Telephone: 01302 239060