Pedal It values your privacy. We will only share your information with third parties (i) if we have your express permission, or (ii) for statistical and analytical purposes with selected partners who will maintain your information in accordance with the Data Protection Act 1998, maintain it securely and neither contact you nor share your information with anyone else without your express consent. We will only use the information that we collect about you lawfully in accordance with the Data Protection Act 1998. For the purpose of the Data Protection Act 1998, the data controller is Pedal It, 290 Lee High Road, London, SE13 5PJ.
We will collect any information given at the time of the ordering process only to enable us to input and process your order, unless you have given us your consent to use that information more broadly (see below). When you pay for goods your details are passed through our payment service provider system purely for payment processing and anti-fraud purposes, for your protection.
You have the right to access any information that we hold about you. Your right of access can be exercised in accordance with the UK Data Protection Act 1998. Any access request may be subject to a fee of £10 to meet our costs in providing you with details of the information we hold about you.
Cookies are used on this shopping site to keep track of the contents of your shopping cart once you have selected an item, to store delivery addresses when you register. To understand visitor behaviour on our website and to provide relevant and targeted advertising messages to our site visitors
What is a cookie?
A cookie is a small text file which we transfer to your device through your web browser when you visit our website or open certain emails. It enables our own system to recognise you when you visit our website again and improve our service to you. This information can be used to enhance the content of our website and make your use of it easier. For more information about cookies please visit www.allaboutcookies.org.
Three types of cookie may be used during your visit to pedal-it.london, pedal-itservicemybicycle.london and pedal-it-secondhandbicycle.london
Session cookies – Which allow the site to ‘remember’ content from page to page and are deleted after each visit.
Evanscycles.com persistent cookies – Which are saved on your computer for a fixed period (usually a year or longer) and are not deleted when the browser is closed. Persistent cookies are used where we need to know who you are for more than one browsing session. An example of when we might use these cookies would be to store your preferences, so that they are remembered for the next visit. Persistent cookies are not deleted after each visit.
Third party cookies – Which are used by our partners, for example, to help us measure site visitors.
How to control or delete cookies?
See a list of our main cookies here. For instructions on how to control or delete cookies from your computer please visit http://www.aboutcookies.org.
Used to recognise repeat visitors to the site and in conjunction with other information we hold to attempt to record specific browsing information (that is, about the way you arrive at the site, pages you view, options you select, information you enter and path you take through the site) against an individual customer profile.
evans-uiExperience determines desktop or mobile site based on device.
• urchin.js – oldest version of GA tracking code (not used by Evans)
• ga.js – used in Classic Google Analytics
• analytics.js – used in Universal Analytics
• _ga cookie – Used to identify unique users and expires after 2 years.
• _gat cookie – Doesn’t store information but instead limits the number of requests that have to be made to advertising reporting features e.g. DoubleClick. Expires after 10 minutes.
• __utma – Unique visitor cookie which expires after 2 years. GA assign unique ID’s to each visitor to the site. This ID is called the visitor ID and it is made up of a random unique ID and the first time stamp (also known as the time of initial visit)
• __utmb – Identifies web session, stores info about the session and refreshes automatically every 30 minutes from the date it was last refreshed
• __utmc – Session cookie that historically worked along with _utmb cookie to identify a web session, although not really used anymore.
• __utmt – works just like _gat cookie
• __utmv – Visitor segmentation cookie which essentially identifies a visor as male, female, sign in and so on. This cookie expires after 2 years from the date of last refresh.
• __utmx – Used to determine a user’s inclusion in an experiment i.e. A/B testing of different versions of a site. This cookie expires after 18 months from the date of last refresh.
• __utmz – Campaign cookie used to store campaign info that expires after 6 months from date of last refresh.
This keeps track of session stats, such as how many times the visitor has visited the site, and how many pages have been viewed. This is solely used to determine which (if any) feedback forms should be shown to the visitor.
This keeps track of when feedback forms were last shown to the visitor, so that the same feedback form is not repeatedly shown.
Optimizely uses persistent visitor level cookies to uniquely identify users and track their actions. It sets a number of cookies, each storing a different set of data:
FIRST PARTY COOKIES
What: Contains the end user’s unique identifier. It is a combination of a timestamp and random number. No information about you or your customer is stored in it.
Expiration: 10 years
What: Stores JSON of the experiments and variations that a user has been bucketed into. This ensures the user consistently sees the same variation, even over multiple sessions.
Expiration: 10 years
In a multivariate test, the variations a visitor sees are concatenated with an underscore, like this:
What: Stores JSON of the user’s audience and dimension information (e.g., browser, campaign, mobile, source type, custom dimensions).
Expiration: 10 years
What: In case of a redirect experiment, stores the variation-ID of the redirect experiment. Optimizely uses it to run any applicable integration code after the redirect is done. This helps us get around the problem of an experiment not being “active” on a redirect page. This is not to be confused with the optimizelyReferrer cookie that is responsible for storing the user’s original referring URL.
Expiration: 5 seconds
What: Used as a cache of a user’s actions between tracking calls. When the tracking call is made the cookie will be wiped. This is to ensure that all events are tracked even if the user is committing actions in rapid succession.
Expiration: 15 seconds
THIRD PARTY COOKIES
This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown.
This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in.
This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.
This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in.
This cookie is set once a visitor minimizes a Recruit User Testers widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.
_hjDoneSurveys This cookie is set once a visitor completes a survey. It is used to only load the survey content if the visitor hasn’t completed the survey yet.