Cookie Policy
Control your
Effective Date: 08/17/2020
This Cookie Policy describes the different types of cookies and similar technologies that may be used on Building Engines, Inc. (“BE”) Sites using the following domains buildingengines.com, requestcom.com, awaremanager.com, realaccess.com, synlio.com.
We may change this Cookie Policy at any time in order to reflect, for example, changes to the cookies we use or for other operational, legal or regulatory reasons. If you have questions regarding this Cookie Policy, please contact our Chief Security Officer (CSO) by email at privacy@buildingengines.com, or write to us at the following address: 33 Arch Street, Boston, MA 02110 ATTN: Chief Security Officer.
1. What are Cookies?
Cookies are a standard feature of websites that store small amounts of data on your computer about your visit to a website. Cookies help us to learn which areas of a website are useful and which areas need improvement. Cookies also improve your experience by, for example, remembering your preferences.
You can prevent the use of certain cookies by adjusting the settings on your browser (see your browser Help for how to do this). Be aware that disabling cookies will affect the functionality of this and many other websites that you visit. Disabling cookies will usually result in also disabling certain functionality and features of websites. Therefore, it is recommended that you do not disable cookies.
2. Why do we use Cookies?
Our websites use both 1st party cookies and 3rd party cookies (which are set by a server located outside the domain of a website). We use 1st party and 3rd party cookies for several reasons. Some cookies are required for technical reasons in order for the websites to operate, and we refer to these as “Absolutely Necessary” cookies. Some cookies allow us to count visits and traffic sources so we can measure and improve the performance of our websites, and we refer to these as “Performance” cookies. Some cookies enable us to provide enhanced functionality and personalization on the Sites and we refer to these as “Usability” cookies. The specific types of 1st and 3rd party cookies served through the Sites and the purposes they perform are described in the table below.
Absolutely Necessary Cookies
Name | Purpose | Duration | 1st/3rd Party |
---|---|---|---|
A | Refers to the user’s session and is utilized on each transaction | Session | 1st |
B | Refers to the user’s session and is utilized on each transaction | Session | 1st |
cookie-consent | Tracks user level consent of BE privacy policy. | 6 months | 1st |
PRISM_TOKEN | Refers to the user’s session and is utilized on each transaction | Session | 1st |
Performance Cookies
Name | Purpose | Duration | 1st/3rd Party |
---|---|---|---|
__utm* | Tracks visitor behavior and measure site performance plus visitor origination. | 2 years | 3rd |
_biz_* | Used for marketing analytics tracking by Bizable.com | 11 months | 3rd |
_fbp | This cookie will help deliver our advertising to people who have already visited our website when they are on Facebook or a digital platform powered by Facebook Advertising | Session | 3rd |
_ga | Used to track individual users within Google Analytics | 2 years | 3rd |
_gid | Tracks pages visited by users. | 1 day | 3rd |
_hjid | Set by Hot Jar Ltd and provide aggregated site analytics | 1 year | 3rd |
_hjIncludedInSample | Set by Hot Jar Ltd and provide aggregated site analytics | 1 year | 3rd |
_mkto_trk | Tracks user and provides enriched content based on choices made on the site. | 2 years | 3rd |
AWSALB | The cookie is set by the hosting environment to track the users session | 1 Week | 3rd |
AWSALBCORS | The cookie is set by the hosting environment to track the users session | 1 Week | 3rd |
DFTT_END_USER_PREV_BOOTSTRAPPED | To indicate that the user has previously been authenticated. | 2 years | 3rd |
drifft_* | Anonymous identifier token or token to track the actions within a specific browser session | 2 years | 3rd |
ei_client_id | Engagio analytics and | 2 years | 3rd |
fs_uid | Targeting Cookie – Tracks user session to enable Full Story functionality | 1 year | 3rd |
sliguid | Third party cookie from Salesloft, provides an anonymous user identifier across multiple requests. It is set for every request that comes in. | Session | 3rd |
slirequested | Third party cookie from Salesloft, once the sliguid cookie has been confirmed against a central server, this cookie is set for every request that comes in. | Session | 3rd |
__utm* | Tracks visitor behavior and measure site performance plus visitor origination. | 2 years | 3rd |
_biz_* | Used for marketing analytics tracking by Bizable.com | 11 months | 3rd |
Usability Cookies
Name | Purpose | Duration | 1st/3rd Party |
---|---|---|---|
BEI_usehttps | Records the user choice on login to use a secure connection | 1 Month | 1st |
gdpr | Indicator if user is from a country requiring GDPR | 1 year | 1st |
gussy | User Preference | 3 years | 1st |
has_js | Holds results if user can user JavaScript | Session | 1st |
hblid | Identifies a unique visitor between visits | 1 year | 3rd |
incap_ses_*_* | Imperva/Incapsula session cookie to filter out malicious requests. The information generated cannot identify you as an individual. | Session | 3rd |
M | Search | Session | 1st |
nlbi_* | Imperva/Incapsula cookies are placed to ensure that user interactions with the website are sent to the the correct server. The information generated cannot identify you as an individual. | Session | 3rd |
obc | User Preference | Session | 1st |
olfsk | Maintains message history across pages | 1 year | 3rd |
orc | User Preference | Session | 1st |
prism-lng | Holds user level choice of language chosen at login. | Session | 1st |
SATA | Search Home Page | Session | 1st |
unc | Records the username if the user selects remember me | 1 Month | 1st |
upref | User Preference | 3 Years | 1st |
visid_incap_* | Imperva/Incapsula session cookie to filter out malicious requests. The information generated cannot identify you as an individual. | 1 year | 3rd |
wcsid | Cookie set by Olark Live Chat software. A session identifier used to keep track of a single chat session | 1 year | 3rd |
BEI_usehttps | Records the user choice on login to use a secure connection | 1 Month | 1st |
3. Web Beacons
In addition to cookies, we may use other, similar technologies from time to time, like web beacons. These are tiny graphics files that contain a unique identifier that enable us to recognize when someone has visited our Sites or opened an e-mail that we have sent them. This allows us, for example, to monitor the traffic patterns of users from one page within our Sites to another, to deliver or communicate with cookies, to understand whether you have come to our websites 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.
4. How Do I Manage Cookies?
In addition to the options provided above, you have the right to refuse or accept cookies from the Sites at any time by activating settings on your browser. Information about the procedure to follow in order to enable or disable cookies can be found on your Internet browser provider’s website via your help screen. You may wish to refer to http://www.allaboutcookies.org/manage-cookies/index.html for information on commonly used browsers. Please be aware that if cookies are disabled, not all features of the Sites may operate as intended.
You can adjust your cookie preferences by adjusting your browser so that it notifies you when cookies are sent to it or you can refuse cookies altogether. The Help function within your browser should explain how to do this. Alternatively, you may visit www.aboutcookies.org or www.allaboutcookies.org to obtain detailed information on how to prevent cookies from being set on your particular browser.
You may also wish to review the Online Tracking Opt-Out Guide for additional options available for managing cookies. Note that because many of these mechanisms are specific to the device or browser on which they are exercised, you may need to perform these on every browser and device that you use.