Jingdong Retail (UK) Limited, Jingdong Retail (Netherlands) B.V., Jingdong Retail (France) SAS, and Jingdong Retail Germany GmbH ("Joybuy", "we", "us" or "our") attaches great importance to the protection of its users' and customers' privacy and personal information. We use cookies and other similar technologies when you visit our website (www.joybuy.com) or use the Joybuy app ("Services").
This Joybuy Cookie Policy ("Policy") explains how we and other members of our group use cookies and similar technologies when you, or business users acting on your behalf (your “Personnel”), use(s) our Services.
Please read the Joybuy Cookie Policy carefully. If you have any questions, please feel free to contact us.
For more detailed information about how we process your Personal Data, please see our Privacy Policy. For information on using the Services, please see our Term of Use.
This Policy covers:
1 Scope
1.1 We will only use cookies and similar technologies in accordance with this Policy.
2 What are cookies?
2.1 Cookies and other similar technologies are small text files that can be placed on your computer, tablet, smartphone or other electronic device with which you can use to surf the internet via a web browser (“Device”). Websites or apps can place cookies on your Device via your web browser if you visit such website or use an app – this typically involves storing pieces of information or code transferred to or accessed from your Device to store and, sometimes, record information about your interaction with online services from your Device. Examples of web browsers are: Internet Explorer, Firefox, Safari, Google Chrome and Opera.
2.2 After a cookie is placed on your Device, your Device can be recognised as you surf through the website via the same web browser or use an app. This will for instance enable the website or app to ‘remember’ your language settings, which pages you visited and the items in your shopping chart. If such cookies are placed by a third-party, such third-party can (also) recognise your device (third-party cookies). It is also possible that cookie information is shared with third-parties. For more information on cookies, please be referred to the website www.allaboutcookies.org.
2.3 Lifecycle cookies: after a cookie is placed on a device, it is only valid for a certain period.
a. After the validity period of a cookie lapses, the cookie is automatically removed by the web browser. The validity period varies per cookie. For example, some cookies are only valid during the browser session. Other cookies can also recognise your Device if you visit the website or app during a new browser session, e.g. for a year after being placed on your Device.
b. Early deletion/refusal of cookies: you can choose to delete a cookie manually before its validity period has lapsed. You can also decide to refuse cookies which may only be placed with your consent, in the first place. For more information on this, please see the section “How can you delete cookies or change your cookie setting?” below.
2.4 Similar technologies: in addition to cookies, other techniques are also used for similar purposes:
a. HTML5 Local Storage and Flash cookie: HTML5 Local Storage and local shared objects (LSOs, also called “Flash cookies”) can be used for the same purposes as cookies.
b. Web beacons: Web beacons (also called “tags”) are bits of programming code that can be included in web pages, emails, and ads. Web beacons can notify the user when those web pages, emails, or ads have been viewed or clicked on by you.
c. Embedded scripts: Embedded scripts (also called “JavaScript”), are sections of programming code that can be included in web pages to measure how those web pages are used by you, e.g. by registering which links you click on.
d. Device fingerprints: information collected about software or hardware of a device for identification and security purposes. This information is collected for two main purposes, namely (i) ensuring the security of your account by detecting hacking activities, security threats and related abnormal statuses of your account, and (ii) ensuring fair dealing and protecting your and our interests by detecting and blocking cybercrime or online deceptive activities.
e. Event tracking: an event is your interaction or activity with a page, which will be tracked through the tracker. This information is collected for the following main purpose, namely identifying which ads or pages have led to purchases and calculating the conversion rate in order to optimize performance levels.
f. SDKs (software development kits) provided by our suppliers and embedded in our app, These SDKs help us with analytics (including understanding how are users our interacting with our Services), with online advertising (including analysing how effective advertising on the apps has been and recording which ads you have seen and interacted with) and with stability monitoring which helps us ensure the app is performing as it should.
2.5 We use cookies, either alone or in combination with each other, to create a unique ID which corresponds to you.
2.6 When you first interact with our Services, you will be notified that we use cookies and we will ask for your consent to use non-essential cookies. This banner will also allow you to decide which non-essential cookies you want to accept. We also give you information about how to disable cookies below. Where you change your browser settings to generally disable all cookies, you may not be able to take full advantage of our Services; some aspects may not work without some cookies being used.
We use these cookies on the basis that they are necessary for the performance of a contract with you, or because using them is in our legitimate interests (where we have considered that these are not overridden by your rights) or where you have consented to their use.
3 What types of cookies do we use?
3.1 We use four types of cookies on this Site: (i) essential cookies (ii) functional cookies, (iii) analytical and performance cookies, (iv) targeting and advertising cookies. More information on this is provided below.
3.2 Essential cookies:
a. These are cookies that are essential for the operation of our Services and under our terms with you. They include, for example, cookies that enable you to log into secure areas of our Services, use a shopping cart, take steps to deliver our Services to you and preserve the proper layout and navigation of a Services. If you disable these cookies, certain features of the Services may not work.
b. Essential cookies may be placed without your consent.
3.3 Functional cookies:
a. These are used to recognise you when you return to our Services. This enables us, subject to your choices and preferences, to personalise our content, greet you by name and remember your preferences (for example, your choice of language or region).
3.4 Analytical and performance cookies:
a. Analytical and performance cookies are used to analyse and map the use of our Services, so that the quality and/or effectiveness can be improved. These types of cookies will, for example, capture the number of users and see how they engage with our Services, including specific content and features. This helps us for our legitimate interests of improving the way our website works (for example, by ensuring that users are finding what they are looking for easily).
b. We will not place analytical and performance cookies without your consent.
3.5 Targeting / advertising cookies:
a. Tracking cookies are used to follow the behaviour of website visitors across multiple websites. If such cookies are placed by another party, these are called third party tracking cookies.
b. We will not place tracking cookies without your consent.
For a full overview of all the cookies we use, please be referred to the paragraph “What cookies and techniques do we use? Full overview”, below.
4 What cookies and similar technologies do we use?
4.1 On our Site, we use the following cookies and techniques:
|
Name cookie |
Purpose of the cookie |
Is this cookie placed by a third-party or is the cookie information shared with third parties by Joybuy? |
Validity period |
|
Essential |
|||
|
redirectUrl |
Stores user's latest url visited before logged in, so that user can be redirect to the url after logged in |
First party |
365 days |
|
deviceId |
The random string used to identify the user when not logged in |
First party |
365 days |
|
hasCookieAggreementRead |
Identifies if user has read our cookie policy |
First party |
365 days |
|
storeId |
The store id |
First party |
365 days |
|
lighting-nl |
The user login token |
First party |
365 days |
|
cookieVer |
The cookie agreement version |
First party |
365 days |
|
_jda |
Temporarily saves information on the user's session (website visit). |
First party |
180 days |
|
_jdb |
Temporarily saves information on the user's session (website visit). |
First party |
30 minutes |
|
App IOS (SDK) |
· Identifying the device · Securing the network and account · Carrying out login risk checks · Identifying the hardware · Identifying the network identity · Gathering application information |
Apple |
5-6 years |
|
App (IOS and Android) (SDK) |
· Identifying the device · Securing the network and account · Identifying the location · Identifying the network identity |
Third party |
5-6 years |
|
Web (SDK) |
· Identifying the device · Securing the network and account · Carrying out login risk checks · Identifying the hardware · Identifying the network identity |
Third party |
5-6 years |
|
App Android (SDK) |
· Identifying the device · Securing the network and account · Carrying out login risk checks · Identifying the hardware · Identifying the network identity · Logging operations |
|
5-6 years |
|
Functional |
|||
|
mca |
Stores user's selected address id so that user does not need to select this again while using Service |
First party |
365 days |
|
i18n_language |
Stores user's language preference |
First party |
365 days |
|
searchHistory |
User's history of keywords |
First party |
365 days |
|
_lsa_ |
After login or registration, stores the current email or phone number for determining if the user has logged in before when reopening the login popup |
First party |
15 days |
|
VISITOR_UUID |
Visitor UUID, generated and set when a user first visits the page |
First party |
30 days |
|
_currency |
Currency |
First party |
30 days |
|
_lang |
Language |
First party |
30 days |
|
_country |
Country site |
First party |
30 days |
|
_timezone |
Time zone |
First party |
30 days |
|
CASCADE_ADDRESS_AREA_KEY |
Postcode and four-level address ID |
First party |
30 days |
|
USER_ADDRESS_AREA_KEY |
User address information (address ID, four-level address ID, postcode, longitude, latitude, etc.) |
First party |
30 days |
|
mfs_session |
User token (unique login session identifier) |
First party |
400 days |
|
pin |
User login pin, used for search recommendations |
First party |
400 days |
|
__cf_bm |
Used for Cloudflare Bot Management |
Third party |
30 minutes |
|
_cfuvid |
Rate limiting rules |
Third party |
No expiration |
|
jnos-tenant-code |
Tenant code |
First party |
No expiration |
|
o2State |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
ssa.global.ticket |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
__jdu |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
areaId |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
PCSYCityID |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
shshshfpa |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
shshshfpx |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
ipLoc-djd |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
3AB9D23F7A4B3C9B |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
3AB9D23F7A4B3CSS |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
shshshfpb |
From JD main site, appears because joybuy.com references JavaScript files from jd.com |
Third party |
18 months |
|
Analytics |
|||
|
_ga |
Used to distinguish users |
|
2 years |
|
_gid |
Used to distinguish users |
|
24 hours |
|
_gat |
Used to distinguish users |
|
1 minute |
|
_gac_<property-id> |
Contains campaign related information for the user. |
|
90 days |
|
_utma |
Used to distinguish users and sessions. |
|
2 years after updating |
|
_utmt |
Used to throttle request rate |
|
10 minutes |
|
_utmb |
Used to determine new sessions/visits. |
|
session |
|
_utmc |
This Cookie operates in conjunction with the __utmb cookie to determine whether the user is in a new session/visit. |
|
session |
|
_utmv |
Used to store visitor-level custom variable data. |
|
2 years after updating |
|
_utmx |
Used to determine a user's inclusion in a study. |
|
18 months |
|
_utmxx |
Used to determine the expiry of studies that a user has been included in. |
|
18 months |
|
_gaexp |
Used to determine a user's inclusion in a study and the expiry of experiments a user has been included in. |
|
90 days |
|
_opt_awcid |
Used for campaigns mapped to Google Ads Customer IDs. |
|
24 hours |
|
_opt_awmid |
Used for campaigns mapped to Google Ads Customer IDs. |
|
24 hours |
|
_opt_awgid |
Used for campaigns mapped to Google Ads Customer IDs. |
|
24 hours |
|
_opt_awkid |
Used for campaigns mapped to Google Ads Customer IDs. |
|
24 hours |
|
_opt_utmc |
Stores the last utm_campaign query parameter. |
|
24 hours |
|
__jda |
Domain hash.UUID.First visit time.Last visit time.Current visit time.Visit times |
Third party |
180 days |
|
__jdb |
Domain hash.Visit order number.Session ID.Current visit time |
Third party |
30 minutes |
|
__jdv |
Identifies user's domain hash |
Third party |
15 days |
|
Targeting / Advertising |
|||
|
AMP_TOKEN |
Contains a token that can be used to retrieve a Client ID from AMP Client ID service. |
Third party |
30s – 1 year |
|
_utmz |
Stores the traffic source or campaign that explains how the user reached the site. |
|
6 months after updating |
5 How can you delete cookies or change your cookie settings?
5.1 You can you change your cookie settings in general – for all websites you visit – via your browser settings. You can also change your cookie setting just for our Site.
5.2 Within your browser you can change your cookie preferences and choose whether you wish to accept cookies or not. The choices you can make and how you make them differs per browser, such as denying all third-party cookies. For further information on how you can change your browser settings, please see: www.aboutcookies.org/how-to-control-cookies/
6 Contact Details
6.1 Jingdong Retail (UK) Limited (Company number: 15830555), Jingdong Retail (Netherlands) B.V. (Company number 80456774), Jingdong Retail (France) SAS (Company number 947844197 ), and Jingdong Retail Germany GmbH (Company number HRB 277115 B) are joint controllers which administer and host the Services and from which global and strategic decisions are made. The four data controllers operate the website of Joybuy in different UK and EU states. For any questions, comments or requests, you may contact us via support@joybuy.com. Please let us know by e-mail if you prefer to have further contact over the phone.
6.2 Our address is: Jingdong Retail (UK) Limited, Floor 3, 20 King Street, London SW1Y 6QY, for other controllers, Floor 12, Boompjes 40, 3011 XB Rotterdam, the Netherlands.
6.3 Our data protection officer can be contacted at DPO@jd.com.
7 Changes to this Policy
7.1 Joybuy reserves the right to change this Policy on a regular basis. Where required, Joybuy will inform you of updates made to this Policy. The current version is always available on our website and in our app. This Policy was last amended and revised in August 2025.