Yes they are, and they must be compliant per the laws of the country where they are issued. Brickken studies the legality of each project before making an issuance. For example, in Spain, all Security Token Offerings, must have a whitepaper issued by an official Financial Advice Company, and registered before the Spanish National Stock Market Commission. Legality will always come first for Brickken.
| Cookie | Duration | Description |
|---|---|---|
| __hssrc | session | This cookie is set by Hubspot. According to their documentation, 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. |
| viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| Cookie | Duration | Description |
|---|---|---|
| _calendly_session | 21 days | This cookie is associated with Calendly, a meeting scheduler used by Brickken. This cookie allows the meeting scheduler to function within the website. |
| _OG_GDPR_COOKIE_ | session | No description available. |
| outbrain_cid_fetch | 5 minutes | This cookie determines how the user accessed the website. The website operator uses this information to measure the efficiency of its marketing. |
| Cookie | Duration | Description |
|---|---|---|
| __hstc | 1 year 24 days | This cookie is set by Hubspot and is used 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). |
| _ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
| _ga_0XE98K7J2M | 2 years | This cookie is installed by Google Analytics. |
| _hjAbsoluteSessionInProgress | 30 minutes | This cookie is configured to inform Hotjar if that visitor is included in the data sample defined by the daily limit of web sessions. |
| _hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
| _hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
| _hjIncludedInPageviewSample | 2 minutes | This cookie is set to inform Hotjar if that visitor is included in the data sample defined by the web page view limit. |
| _hjTLDTest | session | It checks if Hotjar can load the cookies on the site and they are deleted shortly thereafter. |
| hubspotutk | 1 year 24 days | This cookie is used by HubSpot to keep track of the visitors to the website. This cookie is passed to Hubspot on form submission and used when deduplicating contacts. |
| Cookie | Duration | Description |
|---|---|---|
| __hssc | 30 minutes | This cookie is set by HubSpot. The purpose of the cookie is to keep 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. |
Leave A Comment