What is a Cookie?
A cookie is a small file placed onto your browser that enables us to enhance your experience on BrowserStack by remembering your preferences.
What types of cookies does BrowserStack use?
We use two types: persistent cookies and session cookies. A persistent cookie helps us recognize you as an existing user, so it’s easier to return to BrowserStack or interact with our products without signing in again. After you sign in, a persistent cookie stays in your browser and will be read by us when you return to one of our products. Session cookies only last for as long as the session (usually the current visit to a website or a browser session).
What are cookies used for?
Cookies can be used to recognize you when you visit BrowserStack, remember your preferences, and give you a personalized experience that’s in line with your settings. Cookies also make your interactions with BrowserStack faster and more secure. Additionally, cookies allow us to bring you advertising off the BrowserStack website, and bring customized features. As of today, BrowserStack does not generally respond to “do not track” signals.
How are cookies used for advertising purposes?
Cookies and other ad technology such as beacons, pixels, and tags help us serve relevant ads to you more effectively. They also help us provide aggregated auditing, research, and reporting for advertisers, understand and improve our service, and know when content has been shown to you. Your web browser may request advertisements and beacons directly from third party ad network servers, these networks can view, edit, or set third party cookies, just as if you had requested a web page from their site. Ads served by BrowserStack may also set third party cookies.
Unless you clear these cookies from your browser, we may use this information to:
- provide more relevant, interest-based advertising
- provide aggregate reports of ads activity to advertisers and websites hosting the ads
- improve our products
Further, Our cookie table lists some of the cookies on our website (set by our products or third parties). Please note that the names of cookies, pixels and other technologies may change over time. You can opt-out of our advertising cookies here.
|tracking_id||We set this when user visits BrowserStack. Used to log any activity related to Pricing.||5 years|
|screensizeSet||We set this cookie if user tries to set the screen size when using the Responsive product.||1 year|
|screensize||We set this cookie when user tries to start the Live Session on a Real Mobile for the first time. Here, all we ask the user is to feed in the screen size, so that later, we can use it render the real devices in real size to enhance the user's testing experience.||1 year|
|bs_force_local||We set this if user enables force-local option from the live dashboard.||1 year|
|_session_id||Session cookie set by Rails.||Never expires|
|bs_local, bs_local_hostPort, bs_local_originalUrl, bs_local_val, bs_local_name||We set these Cookies for storing information used for Local Testing.|
|previous_session_os||We set this cookie when user starts a session on Live. We set the OS name which user recently started the session on, to enhance the user's testing experience.||1 year|
|history||We set this cookie when user starts a session on Live. We set the the following parameters to enhance user's testing experience, which are later used to set some default configurations when user visits the Live product next time.||1 year|
|dockPosition||We set this cookie when user tries to drag the dock in Live session. The value of this cookie is used to enhance user's testing experience. We position the dock where the user had dragged in the previous session when he starts a new live session.||Never expires|
|downtime_notified||We set this cookie to remember if we showed the scheduled downtime message to the users. Once the user see's the message, we set this cookie so that we do not show the same notification to the user again on his next visit.||24 hours|
|cmd_tunnel, cmd_tunnel_kind, cmd_tunnel_type||We set these cookies when user connects Local Binary or Local app.|
|quick_launch_extension_installed||We set this cookie once the user installs our Quick Launch Extension.||1 year|
|extension_started||We set if the Local extension is installed.||1 year|
|firefox_extension_just_installed||We set the cookie if the user installed our Firefox extension||1 year|
|skipped_extension_install_*||We set this cookie if user visits the Live dashboard and he skips the Local Extension installation modal. We store the user ID in the place of (*) in the cookie name.||1 year|
|clear-extension-cache||We set this cookie when user adds a new browser to the quick launch. This enables us to clear the cached browsers from the Quick Launch extension and request for the updated ones.||1 year|
|bs_deviceId||We use this for Analytics purpose||30 days|
|invite_users||We store the product names when user tries to invite other users.||1 year|
|__stripe_mid||This cookie is set by the third party service - Strip, which we use for the payments. More on this at https://stripe.com/cookies-policy/legal||1 year||Stripe|
|_ga||This is set by the third party service - Google Analytics for identifying unique sessions.||Google Analytics|
|_gid||This is set by third party library of Google Analytics. More on use case: Refer here (last answer)||Google Analytics|
|xs, sb, c_user, datr, pl, dpr, fr, wd||Facebook social plugin which is integrated using Google Tag Manager. It sets these cookies for tracking user conversions on the website.|
|1P_JAR, APISID, CONSENT, HSID, NID, OTZ, SAPISID, SID, SSID, SIDCC||This is set by Google using Google Tag Manager to track conversions.|
|amplitude_idatlasbiomed.com||This is set by the third party service - Amplitude to analyze the user behavior within our website and our own products and services.||10 years||Amplitude|