Cookie | Cookie indicates any technology - e.g cookies, unique identifiers, web beacons, embedded scripts, e-tags and fingerprinting - that enables the tracking of you, for example by accessing or storing information on your device. |
Personal Data (or Data) | means any information relating to an identified or identifiable physical person - an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the identity of that natural person. |
Data Controller (or Lightyear) | means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data. |
Website | The means by which your Personal Data is collected and processed. |
Cookie policy of Lightyear
Introduction
Version 3.2
This applies from 28.10.2024.
We are Lightyear, an investment platform that is operated by two companies:
- Lightyear Financial Ltd, a company registered in England and Wales with company number 12925823, Information Commissioner’s Office number ZA839140 and registered address at 256-260 Old Street, London EC1V 9DD;
- Lightyear Europe AS, a company registered in Estonia with company number 16235024 and registered address at Volta 1, Tallinn 10412, Estonia.
We use technologies that allow us to access and store information or use resources on your device as they interact with this Website. For simplicity, all such technologies are defined as "Cookies" within this document.
Some of the purposes for which Cookies are used may also require your consent. Whenever consent is given, it can be freely withdrawn at any time following the instructions provided in this document.
This Website uses Cookies managed directly by us (so-called “first-party” Cookies) and Cookies that enable services provided by a third-party (so-called “third-party” Cookies). Unless otherwise specified within this document, third-party providers may access the Cookies managed by them.
The validity and expiration periods of Cookies may vary depending on the lifetime set by us or the relevant provider. Some of them expire upon termination of your browsing session.
Definitions
Cookies that we use
Below, we’ve explained how and why we use Cookies, and what each of them do:
- Essential cookies — These cookies are essential for you to browse the website and use its features, such as accessing secure areas of the site.
- Measurement cookies — Measurement cookies help collect data that allows us to understand how you interact with our particular service. These insights allow us to both improve content and build better features that enhance your experience.
- Marketing cookies — Marketing cookies track visitor web activity to provide targeted advertisement. These cookies are used to support online marketing by collecting information about the users to promote products through partners and other platforms.
The Cookies that we use are presented in detail in Annex 1. Additionally, you may find more precise and updated information regarding lifetime specification as well as any other relevant information — such as the presence of other Cookies — in the linked privacy policies of the respective third-party providers or by contacting us.
How to manage preferences and provide or withdraw consent
There are various ways to manage Cookie related preferences and to provide and withdraw consent, where relevant.
You can manage preferences related to Cookies from directly within their own device settings, for example, by preventing the use or storage of Cookies.
Additionally, whenever the use of Cookies is based on consent, You can provide or withdraw such consent by setting your preferences within the cookie notice or by updating such preferences accordingly via the relevant consent-preferences privacy widget available .
It is also possible, via relevant browser or device features, to delete previously stored Cookies including those used to remember your initial consent preferences.
Other Cookies in the browser’s local memory may be cleared by deleting the browsing history.
With regard to any third-party Cookies, you can manage their preferences via the related opt-out link (where provided), by using the means indicated in the third party's privacy policy, or by contacting the third party.
Consequences of denying the use of Cookies
You are free to decide whether or not to allow the use of Cookies. However, please note that Cookies help this Website to provide a better experience and advanced functionalities to you (in line with the purposes outlined in this document). Therefore, if you choose to block the use of Cookies, we may be unable to provide related features. Please also note that certain essential cookies will be activated without your consent (as permitted by law). Such cookies are essential for us to provide basic functions on the Website or to access particular features of it.
Data Controller
Lightyear Financial Ltd,
256-260 Old Street,
London EC1V 9DD,
United Kingdom
Our contact email: dpo@lightyear.com
Since the use of third-party Cookies through this Website cannot be fully controlled by us, any specific references to third-party Cookies are to be considered indicative. In order to obtain complete information, you are kindly requested to consult the privacy policies of the respective third-party services listed in this document.
Given the objective complexity surrounding tracking technologies, you are encouraged to contact us should you wish to receive any further information on the use of such technologies by this Website.
Annex 1 - the Cookies we use
| Cookie name | Lifespan | Provider | Description/Purpose | Privacy information |
|---|---|---|---|---|
| Essential cookies | ||||
| currentAccount | 1 year | Lightyear | Current account ID for the logged in user. | Privacy Policy |
| authToken | 15 minutes | Token to communicate with Lightyear API as a logged in user. | ||
| refreshToken | 30 days | Token to refresh the authToken. | ||
| rememberMeToken | 30 days | Token to remember the user. | ||
| guestId | 30 days | Unique identifier set for the guest user. | ||
| ly-cookie-consent | 1 year | Cookie used to remember the Cookie consent response from the user. | ||
| branch_url | session | URL for mobile signups that is based on which page a user landed on. | ||
| app_locale | 1 year | Language for the user in authenticated web application. | ||
| site_locale | 1 year | User picked language on public web pages. | ||
| AWSALB AWSALBCORS | 1 week | Amazon Web Services, Inc. | Set to provide load balancing functionality. | Privacy Policy |
| Measurement | ||||
| referrer_id | 1 day | Lightyear | Referrer ID used when a user lands on a referred page and used when user signs up to link the referral. | Privacy Policy |
| _hjCachedUserAttributes | duration of the session | Hotjar Heat Maps & Recordings (Hotjar Ltd.) | Stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. | Privacy Policy |
| _hjClosedSurveyInvites | 1 year | This cookie is set once a visitor interacts with a survey invitation modal popup. We use it to ensure that the same invite does not reappear if it has already been shown. | ||
| _hjDonePolls | 1 year | This cookie is set once a visitor completes a poll using the Feedback Poll widget. We use it to ensure that the same poll does not reappear if it has already been filled in. | ||
| _hjFirstSeen | duration of the session | Used to identify a new user’s first session. | ||
| _hjIncludedInSessionSample | 30 minutes | Set to let Hotjar know whether that visitor is included in the sample, which lets us generate funnels. | ||
| _hjLocalStorageTest | duration of the session | Checks if the Hotjar Tracking Code can use Local Storage. | ||
| _hjMinimizedPolls | 1 year | Set when a user minimises an on-site Survey. This cookie ensures that the Survey stays minimised when the user navigates through our site. | ||
| _hjSession* | 30 minutes | Used to hold current session data only. | ||
| _hjSessionRejected | duration of the session | If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connect- ing to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues. | ||
| _hjSessionResumed | duration of the session | Used to store and combine pageviews by a user into a single session recording. | ||
| _hjSessionTooLarge | 1 hour | Causes Hotjar to stop collecting data if a session becomes too large. | ||
| _hjSessionUser* | 1 year | Set when a user first lands on a page and is used to store a unique user ID. | ||
| _hjSessionUser_* | 2 years | Set when a user first lands on a page and is used to store a unique user ID. | ||
| _hjShownFeedbackMessage | 1 year | Set when a visitor minimizes or completes Incoming Feedback. We do this so that the form will be minimised immediately if they navigate to another page where it is set to show. | ||
| _hjTLDTest | duration of the session | Used when the Hotjar script executes and we try to determine the most generic cookie path we should use, instead of the page hostname. We do this so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. | ||
| _hjUserAttributesHash | duration of the session | Used as user attributes are sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. | ||
| _hjViewportId | duration of the session | Stores user viewport details such as size and dimensions. | ||
| _hjid | 1 year | Used to see the user’s behaviour for our own statistical and monitoring purposes. >This cookie lets us identify which users have been randomly selected to take part in a sample to monitor those users’ behaviour on our site. >Hotjar also provides us with a heatmap of the site which allows us to monitor, for example, how far you’ve scrolled down a page and where you may have hovered. >With session and screen recording, we’re able to get more context for complicated problems — by observing users going through our flows in an uninterrupted manner, in their real life setting. This helps us identify subconscious thought patterns users have, which helps us pin-point where customers might struggle in our product. | ||
| _hjAbsoluteSessionInProgress | 30 minutes | The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. | ||
| ajs_anonymous_id | 1 year | Twilio Inc. | An anonymous ID generated by Analytics.js, used for Segment calls. | Privacy Policy |
| ajs_group_id | 1 year | A group ID that can be specified by making a group() call with Analytics.js. | ||
| ajs_user_id | 1 year | A group ID that can be specified by making a group() call with Analytics.js. | ||
| AMP_* | 1 year | Amplitude, Inc. | Used for tracking in Amplitude. | Privacy Policy |
| Marketing | ||||
| fbp fbc | 3 months | Meta Platforms Ireland Limited | Used by Facebook to deliver advertising. The cookie contains an encrypted Facebook user ID and browser ID. It will receive information from this website to better target and optimise advertising. >Information collected includes IP addresses, information about the web browser, page location, document, referrer and device, button clicks, pages visited and page metadata. | Privacy Policy |
_ssid _fbp _ga _ga_5TD64ET6CX _rdt_em _rdt_uuid _uetsid _uetvid ajs_anonymous_id ajs_user_id csrf_token csv edgebucket loid reddit_session session_tracker token_v2 | up to 1 year | Reddit, Inc. | Set by Reddit for marketing purposes. | Privacy Policy |