Skip to main content

Trust Center - Essential Cookies

This article contains information on the essential cookies SafeBase utilizes and a description of how each cookie is used.

Ashley Hyman avatar
Written by Ashley Hyman
Updated over 2 months ago

Overview

SafeBase uses several essential cookies to collect information to improve and enhance the customer experience, and to provide the data required for dashboard statistics, user rate limiting, and session tracking.

Note: Enterprise customers have access to enable custom cookie banners. Please reach out to your dedicated CSM if you are interested in learning more about this.

If using a tool to scan our platform for current cookies

To ensure that SafeBase's cookies are represented as securely as possible, please note the following:

  • These cookies will be present on both the platform (app.safebase.io) and on the Trust Center's public facing URL, e.g. trust.company.com.

  • When scanning and using a browser-based tool, ensure that this is done from a fresh incognito or private browser session to make sure that other cookies are not poisoning the results.

  • If any cookies are found in a scan that are present in this list, please contact the SafeBase Support team for clarification.

Non-Essential Cookies

SafeBase utilizes Fullstory, a customer experience tracking platform.
​Fullstory adds two cookies, fs_lua & fs_uid.
​
If any organization would like non-essential cookies turned off for the Trust Center, please contact the SafeBase Support team.

Cookie Name

Purpose

First / Third Party

Essential

sb.anonymousId2

Segment session tracking cookie to track unique views. Used for dashboard statistics such as # of views over a period of time.

First-Party

Yes

ajs_anonymous_id

Segment session tracking cookie to track unique views. Used for dashboard statistics such as # of views over a period of time.

Third-Party

Yes

GAESA

Google Cloud Platform session affinity

Third-Party

Yes

__cf_bm

Cloudflare Bot Management

Third-Party

Yes

_cfuvid

Cloudflare Rate Limiting, could cause issues behind NATs if disabled

Third-Party

Yes

cf_clearance

Cloudflare - proof of managed challenge

Third-Party

Yes

fs_lua

Used for Full Story user session tracking and error debugging

Third-Party

No

fs_uid

Used for Full Story user session tracking and error debugging

Third-Party

No

Did this answer your question?