Back to top

Cookie Policy

Last updated January 30, 2023

 

This Cookie Policy explains how Detroit Labs, LLC (“Company”, “we”, “us”, and “our”) uses cookies and similar technologies to recognize you when you visit our websites at https://www.detroitlabs.com, (“Websites”), our mobile application, our Octocart product, or other digital communications we may provide (collectively, “Digital Services”). It explains what these technologies are and why we use them, as well as your rights to control our use of them.

In some cases we may use cookies to collect personal information, or that becomes personal information if we combine it with other information.

 

What are cookies?

Cookies are small data files that are placed on your computer or mobile device when you visit a website. Cookies are widely used by website owners in order to make their websites work, or to work more efficiently, as well as to provide reporting information.

Cookies set by the website owner (in this case, Detroit Labs, LLC) are called “first party cookies”. Cookies set by parties other than the website owner are called “third party cookies”. Third party cookies enable third party features or functionality to be provided on or through the website (e.g. like advertising, interactive content and analytics). The parties that set these third party cookies can recognize your computer both when it visits the website in question and also when it visits certain other websites.

 

Why do we use cookies?

We use first and third party cookies for several reasons. Some cookies are required for technical reasons in order for our Websites to operate, and we refer to these as “essential” or “strictly necessary” cookies. Other cookies also enable us to track and target the interests of our users to enhance the experience on our Online Properties. Third parties serve cookies through our Websites for advertising, analytics and other purposes. This is described in more detail below.

The specific types of first and third party cookies served through our Websites and the purposes they perform are described below (please note that the specific cookies served may vary depending on the specific Online Properties you visit):

 

How can I control cookies?

You have the right to decide whether to accept or reject cookies. You can exercise your cookie rights by setting your preferences in the Cookie Consent Manager. The Cookie Consent Manager allows you to select which categories of cookies you accept or reject. Essential cookies cannot be rejected as they are strictly necessary to provide you with services.

The Cookie Consent Manager can be found in the notification banner and on our website. If you choose to reject cookies, you may still use our website though your access to some functionality and areas of our website may be restricted. You may also set or amend your web browser controls to accept or refuse cookies. As the means by which you can refuse cookies through your web browser controls vary from browser-to-browser, you should visit your browser’s help menu for more information.

In addition, most advertising networks offer you a way to opt out of targeted advertising. If you would like to find out more information, please visit http://www.aboutads.info/choices/ or http://www.youronlinechoices.com.

The specific types of first and third party cookies served through our Websites and the purposes they perform are described in the table below (please note that the specific cookies served may vary depending on the specific Online Properties you visit):

 

Essential website cookies: These cookies are strictly necessary to provide you with services available through our Websites and to use some of its features, such as access to secure areas.

__cf_bm

  • This cookie is set by HubSpot’s CDN provider and is a necessary cookie for bot protection.
  • Duration: 30 minutes.

__cfruid

  • This cookie is set by HubSpot’s CDN provider because of their rate limiting policies.
  • It expires at the end of the session.

__hs_initial_opt_in

  • This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode.
  • It expires in 7 days.

__hs_opt_out

  • This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. This cookie is set when you give visitors the choice to opt out of cookies.
  • It expires in 6 months.

HeaderPayload

  • The header and payload portions of the JWT token used for authentication. This portion of the cookie is not http only and can be accessed by JavaScript to obtain information about the currently authenticated user.
  • It expires at the end of the session.

OCTOCART_ID

  • Used to maintain a user session by Octocart web applications. It is a necessary cookie that expires at the end of a session.
  • It expires at the end of the session.

Signature

  • The signature portion of the JWT token used for authentication. This portion of the cookie is http only and cannot be viewed by JavaScript.
  • It expires at the end of the session.

 

Analytics and customization cookies: These cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customize our Websites for you.

__hssc

  • “This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.”
  • It expires in 30 minutes.

__hssrc

  • Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session.
  • It expires at the end of the session.

__hstc

  • The main cookie for tracking visitors. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
  • It expires in 6 months.

_ga

  • Used by Google Analytics to distinguish users.
  • It expires in 2 years.

_ga_XK6VPW61GJ

  • Used by Google Analytics to persist session state.
  • It expires in 2 years.

AnalyticsSyncHistory

  • A LinkedIn cookie used to store information about the time a sync took place with the lms_analytics cookie.
  • It expires in 30 days.

hubspotutk

  • This cookie keeps track of a visitor’s identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor.
  • It expires in 6 months.

_hjSessionUser_511834

  • Used by Hotjar to ensures data from subsequent visits to the same site are attributed to the same user ID.
  • It expires in 365 days.

_hjid

  • Set when a user first lands on a page.
  • It expires in 365 days.

_hjFirstSeen

  • Used by Hotjar recording filters to identify new user sessions.
  • It expires at the end of the session.

_hjUserAttributesHash

  • Used by Hotjar to know when an attribute has changed and needs to be updated.
  • It expires at the end of the session.

_hjCachedUserAttributes

  • Stores User Attributes sent through the Hotjar Identify API, whenever the user is not in the sample.
  • It expires at the end of the session.

_hjViewportId

  • Used by Hotjar to store user viewport details such as size and dimensions.
  • It expires at the end of the session.

_hjSession_511834

  • Used by Hotjar to hold current session data.
  • It expires after 30 minutes.

_hjSessionTooLarge

  • Causes Hotjar to stop collecting data if a session becomes too large.
  • It expires at the end of the session.

_hjSessionRejected

  • If present, set to ‘1’ for the duration of a user’s session, when Hotjar has rejected the session from connecting to our WebSocket due to server overload.
  • It expires at the end of the session.

_hjSessionResumed

  • Set when a session/recording is reconnected to Hotjar servers after a break in connection.
  • It expires at the end of the session.

_hjLocalStorageTest

  • Checks if the Hotjar Tracking Code can use local storage.
  • It expires in under 100ms.

_hjIncludedInPageviewSample

  • Used by Hotjar to determine if a user is included in the data sampling defined by your site’s pageview limit.
  • It expires in 30 minutes.

_hjIncludedInSessionSample

  • Used by Hotjar to determine if a user is included in the data sampling defined by your site’s daily session limit.
  • It expires in 30 minutes.

_hjAbsoluteSessionInProgress

  • Used by Hotjar to detect the first pageview session of a user.
  • It expires in 30 minutes.

_hjTLDTest

  • Used by Hotjar to try to store the _hjTLDTest cookie for different URL substring alternatives until it fails.
  • It expires at the end of the session.

 

Functionality cookies:

_GRECAPTCHA

  • This cookie is set by Google reCAPTCHA, which protects our site against spam enquiries on contact forms.
  • It expires in 6 months.

bcookie

  • Browser Identifier cookie used by LinkedIn for diagnostic purposes.
  • It expires in 1 year.

bscookie

  • Used by LinkedIn for remembering that a logged in user is verified by two factor authentication.
  • It expires in 1 year.

lang

  • Used by LinkedIn to remember a user’s language setting to ensure LinkedIn.com displays in the language selected by the user in their settings.
  • It expires at the end of the session.

li_gp

  • Stores privacy preferences for guests to LinkedIn.
  • It expires in 1 year.

lidc

  • Used by LinkedIn to facilitate data center selection.
  • It expires in 24 hours.

ln_or

  • Used by LinkedIn to determine if Oribi analytics can be carried out on a specific domain.
  • It expires in 1 day.

 

Advertising cookies: These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

li_sugr

  • Used by LinkedIn to make a probabilistic match of a user’s identity outside the Designated Countries.
  • It expires in 90 days.

UserMatchHistory

  • LinkedIn Ads ID syncing.
  • It expires in 30 days.

 

What about other tracking technologies, like web beacons?

Cookies are not the only way to recognize or track visitors to a website. We may use other, similar technologies from time to time, like web beacons (sometimes called “tracking pixels” or “clear gifs”). These are tiny graphics files that contain a unique identifier that enable us to recognize when someone has visited our Websites or opened an e-mail including them. This allows us, for example, to monitor the traffic patterns of users from one page within a website to another, to deliver or communicate with cookies, to understand whether you have come to the website from an online advertisement displayed on a third-party website, to improve site performance, and to measure the success of e-mail marketing campaigns. In many instances, these technologies are reliant on cookies to function properly, and so declining cookies will impair their functioning.

 

Do you use Flash cookies or Local Shared Objects?

Websites may also use so-called “Flash Cookies” (also known as Local Shared Objects or “LSOs”) to, among other things, collect and store information about your use of our services, fraud prevention and for other site operations.

If you do not want Flash Cookies stored on your computer, you can adjust the settings of your Flash player to block Flash Cookies storage using the tools contained in the Website Storage Settings Panel. You can also control Flash Cookies by going to the Global Storage Settings Panel and following the instructions (which may include instructions that explain, for example, how to delete existing Flash Cookies (referred to “information” on the Macromedia site), how to prevent Flash LSOs from being placed on your computer without your being asked, and (for Flash Player 8 and later) how to block Flash Cookies that are not being delivered by the operator of the page you are on at the time).

Please note that setting the Flash Player to restrict or limit acceptance of Flash Cookies may reduce or impede the functionality of some Flash applications, including, potentially, Flash applications used in connection with our services or online content.

 

Do you serve targeted advertising?

Third parties may serve cookies on your computer or mobile device to serve advertising through our Websites. These companies may use information about your visits to this and other websites in order to provide relevant advertisements about goods and services that you may be interested in. They may also employ technology that is used to measure the effectiveness of advertisements. This can be accomplished by them using cookies or web beacons to collect information about your visits to this and other sites in order to provide relevant advertisements about goods and services of potential interest to you. The information collected through this process does not enable us or them to identify your name, contact details or other details that directly identify you unless you choose to provide these.

 

How often will you update this Cookie Policy?

We may update this Cookie Policy from time to time in order to reflect, for example, changes to the cookies we use or for other operational, legal or regulatory reasons. Please therefore re-visit this Cookie Policy regularly to stay informed about our use of cookies and related technologies.

The date at the top of this Cookie Policy indicates when it was last updated.

 

Where can I get further information?

If you have any questions about our use of cookies or other technologies, please email us at hello@detroitlabs.com or by post to:

Detroit Labs, LLC
1520 Woodward Ave
Detroit, MI 48226
United States
Phone: (US)(313) 473-0607