Privacy and Cookies Policy

This privacy policy sets out how Michael Matthews Jewellery Ltd uses and protects any information that you give Michael Matthews Jewellery Ltd when you use this website.

Michael Matthews Jewellery Ltd is committed to ensuring that your privacy is protected. Should we ask you to provide certain information by which you can be identified when using this website, then you can be assured that it will only be used in accordance with this privacy statement.

Michael Matthews Jewellery Ltd may change this policy from time to time by updating this page. You should check this page from time to time to ensure that you are happy with any changes. This policy is effective from 25th May 2018

What we collect

We collect personally identifiable information that is volunteered during the registration process or the guest checkout process.

We may collect the following information:

  • Name

  • Contact information including email address

  • Demographic information such as postcode

What we do with the information we gather

We require this information in order to complete the transaction and in particular for the following reasons:

  • Internal record keeping.

  • We may use the information to improve our products and services.

  • We may use the information to customise the website according to your interests.

  • We also require certain details in order to complete the delivery process. I.e. name and address.

Security

We are committed to ensuring that your information is secure. In order to prevent unauthorised access or disclosure, we have put in place suitable physical, electronic and managerial procedures to safeguard and secure the information we collect online.

Links to other websites

Our website may contain links to other websites of interest. However, once you have used these links to leave our site, you should note that we do not have any control over that other website. Therefore, we cannot be responsible for the protection and privacy of any information which you provide whilst visiting such sites and such sites are not governed by this privacy statement. You should exercise caution and look at the privacy statement applicable to the website in question.

Controlling your personal information

You may choose to restrict the collection or use of your personal information in the following ways:

  • whenever you are asked to fill in a form on the website, look for the box that you can click to indicate that you do not want the information to be used by anybody for direct marketing purposes

  • if you have previously agreed to us using your personal information for direct marketing purposes, you may change your mind at any time by writing to or emailing us at lee@michaelmatthewsjewellery.com

We will not sell, distribute or lease your personal information to third parties.

You may request details of personal information which we hold about you under the Data Protection Act 1998. A small fee will be payable. If you would like a copy of the information held on you please write to Michael Matthews Jewellery, 17 Westover Road, Bournemouth, Dorset, BH1 2BY.

If you believe that any information we are holding on you is incorrect or incomplete, please write to or email us as soon as possible at the above address. We will promptly correct any information found to be incorrect.

Cookies

We use Cookies to keep track of your current shopping session to personalise your experience and so that you may retrieve your shopping basket at any time - if you do not accept Cookies you will be unable to use this Website for shopping purposes, only for browsing and research.

What are Cookies?

Cookies are small files which are stored on your computer. They are designed to hold a modest amount of data specific to your website visit on our site.

Cookies help to improve your visit to our website by helping with the following:

  • Remembering settings, so you don’t have to keep re-entering them whenever you visit a new page

  • Remembering information you’ve given (e.g. your email address) so you don’t need to keep entering it

  • Measuring how you use the website so we can make sure it meets your needs

Please note that cookies can't harm your computer and we do not store personally identifiable information in cookies we use on this website.

We're giving you this information as part of our initiative to comply with UK legislation, and to make sure we're honest and clear about your privacy when using our website.

The Cookies we use:

General Website Cookies

This website is built using Microsoft’s ASP.Net web technologies, as part of that we use the built in session cookie (ASP.Net_SessionID) to manage your session. When you navigate to the site, the server establishes a unique session that lasts for the duration of your visit.

Measuring website usage - Google Analytics

Google Analytics uses cookies to define user sessions, as well as to provide a number of key features in the Google Analytics reports. Google Analytics sets or updates cookies only to collect data required for the reports. Additionally, Google Analytics uses only first-party cookies. This means that all cookies set by Google Analytics for your domain send data only to the servers for your domain. This effectively makes Google Analytics cookies the personal property of this website domain, and the data cannot be altered or retrieved by any service on another domain.

The following table lists the type of information that is obtained via Google Analytics cookies and used in Analytics reports.

Functionality

Description of Cookie

Cookie Used

Setting   the Scope of Your Site Content

Because   any cookie read/write access is restricted by a combination of the cookie   name and its domain, default visitor tracking via Google Analytics is   confined to the domain of the page on which the tracking code is installed.   For the most common scenario where the tracking code is installed on a single   domain (and no other sub-domains), the generic setup is correct. In other situations   where you wish to track content across domains or sub-domains, or restrict   tracking to a smaller section of a single domain, you use additional methods   in the ga.js tracking code to define content scope. See Domains & Directories in the Collection API   document for details.

All   Cookies

Determining   Visitor Session

The Google   Analytics tracking for ga.js uses two cookies to establish a session. If   either of these two cookies are absent, further activity by the user   initiates the start of a new session. See the Session article in the Help Center for a   detailed definition and a list of scenarios that end a session. You can   customize the length of the default session time using the setSessionCookieTimeout() method.

This   description is specific to the ga.js tracking   code for web pages. If you use Analytics tracking for other environments—such   as Flash or mobile—you should check the documentation for those environments   to learn how sessions are calculated or established.

__utmb
  __utmc

Identifying   Unique Visitors

Each   unique browser that visits a page on your site is provided with a unique ID   via the __utmacookie. In this way, subsequent visits to your   website via the same browser are recorded as belonging to the same (unique)   visitor. Thus, if a person interacted with your website using both Firefox   and Internet Explorer, the Analytics reports would track this activity under   two unique visitors. Similarly if the same browser were used by two different   visitors, but with a separate computer account for each, the activity would   be recorded under two unique visitor IDs. On the other hand, if the browser   happens to be used by two different people sharing the same computer account,   one unique visitor ID is recorded, even though two unique individuals   accessed the site.

__utma

Tracking   Traffic Sources & Navigation

When   visitors reach your site via a search engine result, a direct link, or an ad   that links to your page, Google Analytics stores the type of referral   information in a cookie. The parameters in the cookie value string are parsed   and sent in the GIF Request (in the utmccvariable).   The expiration date for the cookie is set as 6 months into the future. This   cookie gets updated with each subsequent page view to your site; thus it is   used to determine visitor navigation within your site.

__utmz

Custom   Variables

You can   define your own segments for reporting on your particular data. When you use   the _setCustomVar() method   in your tracking code to define custom variables, Google Analytics uses this   cookie to track and report on that information. In a typical use case, you   might use this method to segment your website visitors by a custom   demographic that they select on your website (income, age range, product   preferences).

___utmv

Website   Optimizer

You can   use Google Analytics with Google Website Optimizer (GWO), which is a tool   that helps determine the most effective design for your site. When a website   optimizer script executes on your page, a _utmx cookie is written to the   browser and its value is sent to Google Analytics. See the Website Optimizer Help Center for more   information.

___utmx

Once the cookies are set/updated on the web browser, the data they contain that is required for reporting purposes is sent to the Analytics servers in the GIF Request URL via the utmccparameter.

Cookies Set By Google Analytics

Google Analytics sets the following cookies as described in the table below. A default configuration and use of Google Analytics sets only the first 4 cookies in the table.

Name

Description

Expiration

__utma

This   cookie is typically written to the browser upon the first visit to your site from   that web browser. If the cookie has been deleted by the browser operator,   and the browser subsequently visits your site, a new __utma cookie is written   with a different unique ID. This cookie is used to determine unique visitors   to your site and it is updated with each page view. Additionally, this cookie   is provided with a unique ID that Google Analytics uses to ensure both the   validity and accessibility of the cookie as an extra security measure.

2 years   from set/update.

__utmb

This   cookie is used to establish and continue a user session with your site. When   a user views a page on your site, the Google Analytics code attempts to   update this cookie. If it does not find the cookie, a new one is written and   a new session is established. Each time a user visits a different page on   your site, this cookie is updated to expire in 30 minutes, thus continuing a   single session for as long as user activity continues within 30-minute   intervals. This cookie expires when a user pauses on a page on your site for   longer than 30 minutes. You can modify the default length of a user session   with the _setSessionCookieTimeout() method.

30 minutes   from set/update.

__utmc

This   cookie is no longer used by the ga.js tracking code to determine session   status.

Historically,   this cookie operated in conjunction with the __utmb cookie to determine   whether or not to establish a new session for the user. For backwards   compatibility purposes with sites still using the urchin.js tracking code,   this cookie will continue to be written and will expire when the user exits   the browser. However, if you are debugging your site tracking and you use the   ga.js tracking code, you should not interpret the existence of this cookie in   relation to a new or expired session.

Not set.

__utmz

This   cookie stores the type of referral used by the visitor to reach your site,   whether via a direct method, a referring link, a website search, or a   campaign such as an ad or an email link. It is used to calculate search   engine traffic, ad campaigns and page navigation within your own site. The   cookie is updated with each page view to your site.

6 months   from set/update.

__utmv

This   cookie is not normally present in a default configuration of the tracking   code. The __utmv cookie passes the information provided via the _setVar() method, which you use to create a   custom user segment. This string is then passed to the Analytics servers in   the GIF request URL via the utmcc parameter. This cookie is only written if   you have added the _setVar() method for the tracking code on your website   page.

2 years   from set/update.

__utmx

This   cookie is used by Website Optimizer and only set when the Website Optimizer   tracking code is installed and correctly configured for your pages. When the   optimizer script executes, this cookie stores the variation this visitor is   assigned to for each experiment, so the visitor has a consistent experience   on your site.  See the Website Optimizer Help Center for more   information.

2 years   from set/update.

For further information about the Cookies Google uses please visit this Cookie Information Page.

First Party cookies – These cookies are set by this website that you are visiting.

Impressions

Cookies are also created to identify when a user has viewed an advert for this website on an external site.

The cookie contains a unique identifier and nothing else. if you subsequently visit this website, then we link that cookie (and hence the advert) to your visit, but if you never visit the website, the cookie is meaningless and will expire automatically, 90 days after you last saw one of the adverts.

First Party Cookies Information

These cookies are written to track website usage of this site:

Cookie Name

Description

Expiry

_#srchist

Stores the   history of traffic sources the user has arrived to the site by

1000 days

_#sess

Stores   information about the session

1000 days

_#vdf

Stores the   visit definition – ts type, number of visits, expiry

1000 days

_#uid

Stores a   user identifier (only within a site)

1000 days

_#slid

Unique   sale ID

1000 days

_#clkid

Unique   identifier for a click generating a landing

1 year

_#lps

Flags that   the last page was secure and therefore has no referrer

20 min

_#tsa

Stores the   referrer details to avoid duplicate Landing events

10 min

_#env

Flags   whether the environment variables (screen size, browser etc) need to be   collected again

30 days

For further information about the Cookies DC Storm uses please visit their Cookie Information page.

Other 3rd Party Cookies we may use

When you visit our website, you may notice some cookies that are collecting information for other websites. For example, if you visit a page that has video content, cookies from YouTube may be served. We do not control the setting of these cookies and we recommend you visit the third party websites for more information.

Please find a list of some third party cookies you may find present on this website and links to their specific cookie information

Microsoft

Google Adwords

Clicktale

How do I Control or Delete Cookies?

If cookies are not enabled on your computer is could mean that your experience with our website will be impacted. However, if you want to control or delete cookies you can do so.

Information on deleting cookies or controlling cookies is available at www.aboutCookies.org. To reiterate though, by deleting our cookies or disabling future cookies you may not be able to access certain areas or features of our site.

Please check back frequently to see any updates or changes to our privacy policy.

Questions regarding this Policy should be directed as follows:

Customer Services
The Bullion Centre Ltd
363 Wimborne Road
Winton
Bournemouth
BH9 2AD