Cookie Policy
Updated September 11, 2024
To make our websites and products work we place small data files called Cookies on your device.
What are Cookies?
A cookie is a small text file that a Website or App stores on your computer or mobile device when you visit a Website or App.
First party cookies are cookies set by the Website or App you’re visiting. Only this Website or App can read them. In addition, a Website or App might potentially use external services, which also set their own cookies, known as third-party cookies.
Persistent cookies are cookies saved on your computer and that are not deleted automatically when you quit your browser, unlike a session cookie, which is deleted when you quit your browser.
The Bkper Website and Bkper App make use of all these types of Cookies.
The purpose is to enable the Website and App to remember your preferences (such as user name, language, etc.) and your current position (in App navigation) for a certain period of time.
That way, you don’t have to re-enter them or re-start at a point zero when browsing around the Website or App during the same visit or a future visit.
Cookies can also be used to establish anonymised statistics about the browsing experience on our Website and App (specially by third party Cookies).
How do we use Cookies?
Bkper Websites and App use first-party cookies.
These are cookies set and controlled by the Bkper team, and are used purely for the purpose of providing a great user experience and to continuously improve that experience.
These are not accessed or controlled in any way by any external organisation.
However, our Websites and App also make use of third party Cookies that you will have to accept from external organisations (listed below).
Since our Website, App and Business aren’t operable without the use of Cookies, You, by accessing and using our Website and App agree with this Cookie policy.
List of Cookies we use
Name | Service | Purpose | Type & Duration | Details |
---|---|---|---|---|
Source | app.bkper.com | Store http referer to know where the user came from | First, 2 years | Anonymised, for statistical purposes |
visitedLP | app.bkper.com | Know the journey through the Bkper website to login | First, 2 years | |
already-logged | app.bkper.com | Store if you already logged in the app | First, 2 years | |
__utma | ga.js | Used to distinguish users and sessions | third, 2 years | Google Analytics |
__utmc | ga.js | determine whether the user was in a new session/visit | third, session | Google Analytics |
__utmz | ga.js | Stores the traffic source or campaign that explains how the user reached us. | third, 6 months | Google Analytics |
__utmt | ga.js | Used to throttle request rate. | third, 10 minutes | Google Analytics |
__utmb | ga.js | Used to determine new sessions/visits. | third, 30 minutes | Google Analytics |
_ga | gtag.js | Used to distinguish users. | third, 2 years | Google Analytics |
_gid | gtag.js | Used to distinguish users. | third, 24 hours | Google Analytics |
_gat | gtag.js | Used to throttle request rate. | third, 1 minute | Google Analytics |
_gaexp | Optimize | Used to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in. | third, as long as experiments run (normally 14 days) | Google Analytics |
_gaexp | Optimize | Used to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in. | third, as long as experiments run (normally 14 days) | Google Analytics |
SSID | Google collects visitor information for videos hosted by YouTube on maps integrated with Google Maps. | third, persistent | ||
SID | Security cookie to confirm visitor authenticity, prevent fraudulent use of login data and protect visitor data from unauthorized access. | third, 2 years | ||
DSID | Used to link your activity across devices if you’ve previously signed in to your Google Account on another device. | third, 1 years | ||
HSID | Security cookie to confirm visitor authenticity, prevent fraudulent use of login data and protect user data from unauthorized access. | third, 2 years | ||
LSID | Used to remain connected to your Google Account when you visit the service again. | third, 2 years | ||
SIDCC | Security cookie to confirm visitor authenticity, prevent fraudulent use of login data and protect visitor data from unauthorized access. | third, 3 months | ||
SAPISID | Google collects visitor information for videos hosted by YouTube. | third, persistent | ||
APISID | Personalizes Google ads on websites based on recent searches and interactions. | third, 2 years | ||
intercom-session-muankhdn | Intercom | Keep track of sessions | third, 1 week | Intercom |
__Secure-3PSID | Builds a profile of website visitor interests to show relevant and personalized ads through retargeting. | third, 2 years | ||
__Secure-3PSIDCC | Builds a profile of website visitor interests to show relevant and personalized ads through retargeting. | third, 2 years | ||
__Secure-3PAPISID | Builds a profile of website visitor interests to show relevant and personalized ads through retargeting. | third, 2 years | ||
JSESSIONID | J2EE | session management in the J2EE web application for HTTP protocol | third, 2 years | |
__stripe_mid | Stripe | Fraud prevention and detection | third, 1 year | Stripe |
GWT_LOCALE | Google Web Toolkit | Store locale settings | third, 2 years | |
IDE | Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user. | third | ||
1P_JAR | Based on recent searches and previous interactions, custom ads are shown on Google sites. | third, 1 week | ||
NID | Stores visitors’ preferences and personalizes ads on Google websites based on recent searches and interactions. | third, 6 months | ||
ANID | Lists ads on Google sites based on recent searches. | third, persisitent | ||
OTZ | Links activities of website visitors to other devices that are previously logged in via the Google account. In this way, advertisements are tailored to different devices. | third, 1 month | ||
UULE | Google Analytics | User behaviour on websites | third, 1 day | |
G_ENABLED_IDPS | Google Authentication | Google Login | third, persisitent | |
G_AUTHUSER_H | Google Authentication | Google Login | third, session | |
__Host-GAPS | Pending | third, 2 years | ||
ACCOUNT_CHOOSER | Google Accounts login | third, variable | ||
__Host-3PLSID | Required for the use of the options and services of the website | third, 2 years | ||
SMSV | Google Accounts login | third, variable | ||
LSOLH | Required for the use of the options and services of the website | third, 1 year |
Third Party Cookies
Our Website and App make use of content from external providers, e.g. YouTube, Intercom, and Stripe.
To view this third-party content, you have to accept their specific terms and conditions. This includes their cookie policies, which we have no control over.
But if you do not view this content, no third-party cookies are installed on your device.
Third party providers on Bkper websites and Bkper App
Google.com
Intercom.com
Stripe.com
Youtube.com
These third-party services are outside of the control of Bkper. Providers may, at any time, change their terms of service, purpose and use of cookies, etc.
How can you manage cookies?
You can manage/delete cookies as you wish - for details, see aboutcookies.org.
Removing cookies from your device
You can delete all cookies that are already on your device by clearing the browsing history of your browser. This will remove all cookies from all websites you have visited.
Be aware though that you may also lose some saved information (e.g. saved login details, site preferences).
Managing site-specific cookies
For more detailed control over site-specific cookies, check the privacy and cookie settings in your preferred browser.
Blocking cookies
You can set most modern browsers to prevent any cookies being placed on your device, but you may then have to manually adjust some preferences every time you visit a Website or App. And some services and functionalities may not work properly at all (e.g. profile logging-in).