This Cookie Policy was updated on 4 November 2026.
This Cookie Policy describes how Dremio Corporation, 2028 E Ben White Blvd #240-6103, Austin, TX 78741, USA (“Dremio”, “we”, “us”, “our”) uses cookies and similar technologies to collect and store information when you visit our websites:
- www.dremio.com
- docs.dremio.com
- developer.dremio.com
- support.dremio.com
- university.dremio.com
Some forms on these websites are provided through hello.dremio.com, our marketing automation service.
Our community at community.dremio.com runs on a separate Discourse platform and is not included in the cookie list below.
Our secure file-transfer service at sendsafely.dremio.com is provided by SendSafely and is not included in the cookie list below.
Our Privacy Policy applies in addition to this Cookie Policy. It explains how we use, store and protect personal data, what your data protection rights are, and how to exercise them. We recommend that you read it: https://www.dremio.com/legal/privacy-policy/
What are cookies and similar technologies?
Cookies are small files placed on your device (computer, tablet or smartphone). When you access a website, a cookie is placed on your device and it will send information to the party that placed the cookie.
Other technologies perform a similar function to cookies. These include pixels, web beacons, clear GIFs, social plug-ins and your browser’s local storage. They are often used together with cookies to help a website owner understand its users better. In this policy, “cookies” includes these technologies.
What are first-party cookies?
Our websites contain first-party cookies. First-party cookies are specific to the website that created them. They let us operate an efficient service and track patterns of user behaviour on our websites.
What are third-party cookies?
The difference between a first-party cookie and a third-party cookie is who places the cookie on your device. We sometimes allow third parties to place cookies on your device. Third-party cookies are placed on your device by a third party (that is, not by Dremio).
Third-party services may collect information through cookies on our websites. We receive reports or data from some of these providers. Their privacy notices explain their information practices.
For more information about these cookies, select Cookie Settings on this page or in the website footer.
Analytics and digital marketing in the United States
In the United States, we routinely work with third-party analytics and digital marketing providers who help and support Dremio (and partner) marketing activities, including targeted communications. These activities may involve sharing limited personal information (personal identifiers and contact information, your interests and interactions with Dremio, and professional or employment information) for those specific business purposes. We may also share your personal data with other third parties, or for other business purposes, with your explicit consent.
If you are in California and your browser sends a Global Privacy Control (GPC) signal, we treat it as an opt-out: Performance and Targeting cookies are switched off for you. Functional cookies stay on (see “How can you manage and delete cookies?”).
What cookies are used?
We want you to be able to make an informed decision for or against the use of cookies that are not strictly necessary for the technical features of our websites. If you reject cookies used for advertising, you will see advertising that is less targeted to your interests. Some optional features and embedded services require the relevant cookie category to be enabled.
Where tracking and evaluating how people use our websites, by means of cookies or similar technologies, involves processing your personal data, we process it on the following legal bases:
- GDPR Article 6(1)(a), where we need to ask for your consent to process your personal data;
- GDPR Article 6(1)(b), where it is necessary to fulfil (pre-)contractual obligations with you;
- GDPR Article 6(1)(f), where it is necessary to fulfil (pre-)contractual obligations with the company or other legal body you represent as a customer contact (our legitimate interest in efficiently performing or managing our business operations);
- or equivalent legal permissions under other relevant national laws, where applicable.
We group cookies into four categories. The same descriptions appear in our cookie banner.
Strictly Necessary Cookies
These cookies are necessary for our websites to work. They cannot be switched off through Cookie Settings and are set when needed, for example when you set your privacy preferences, sign in or fill in a form. Some security cookies, which protect our websites against bots and attacks, are set automatically when you visit. You can set your browser to block or alert you about these cookies, but some parts of the websites will not then work. Some session cookies may be associated with your account, for example when you are signed in to our support or training site.
Performance Cookies
These cookies let us count visits and traffic sources and see how visitors move around and use our websites, so we can measure and improve them. Some of the tools we use for this give your browser a unique identifier. Without these cookies, these analytics tools cannot measure your visits and interactions.
Functional Cookies
These cookies let our websites provide enhanced functionality and personalisation, for example remembering your region, serving the page version suited to your browser, and loading services we embed in our pages. They may be set by us or by third-party providers whose services we have added to our pages. Blocking these cookies may prevent some enhanced features and embedded services from working.
Targeting Cookies
These cookies may be set by us or by our advertising and marketing providers. They are used to show you relevant adverts on other sites, measure our campaigns, attribute leads to marketing activities and understand which companies visit our websites. Some use identifiers to recognise your browser and may support interest profiles. Blocking these cookies can limit campaign measurement, company identification and how relevant the adverts you see are.
Cookie list
The list below describes the cookies we have identified, their categories, purposes and durations. Some of these services also store information in your browser’s local storage.
Durations are approximate: as configured, as observed in a browser, or the platform’s usual default where neither was available. “Session” means the cookie is deleted when the browser is closed. Providers can change their own durations; Zendesk’s session length is 8 hours by default.
Strictly Necessary Cookies:
| Cookie | Duration | Description |
| __cf_bm | 30 minutes | Cloudflare bot protection: helps tell people from bots to protect our websites and the services embedded in them (support portal, training site and course platform, website hosting, event registration, docs feedback widget). |
| _cfuvid | Session | Cloudflare rate limiting: tells visitors behind a shared IP address apart, to enforce rate limits on our websites and the services embedded in them. |
| _help_center_session | Session | Zendesk help centre session cookie: keeps your support portal session working. |
| _zendesk_authenticated | Session | Zendesk cookie that records whether the visitor is signed in to the Dremio support portal. |
| _zendesk_login_session | Session | Zendesk cookie that keeps a signed-in support user logged in during the session. |
| _zendesk_session | 8 hours by default | Zendesk session cookie for the support portal. |
| _zendesk_shared_session | 8 hours by default | Zendesk session cookie shared across Dremio support pages so a signed-in visitor stays signed in. |
| BIGipServersj22web-nginx-app_https | Session | F5 load balancer cookie: keeps your requests on the same server while you use our forms. |
| BIGipServerx | Session | F5 load balancer cookie: keeps your requests on the same server while you use our forms. |
| cf_clearance | 1 year | Cloudflare security cookie: records that your browser passed a security challenge. |
| csrftoken | 1 year | Security cookie used by the training site to help protect forms against cross-site request forgery. |
| OptanonAlertBoxClosed | 180 days | Records when you closed the cookie banner so it is not shown again. |
| OptanonConsent | 180 days | Stores your consent choice for each cookie category. |
| sessionid | 14 days | Session or security cookie the site needs to work. |
| slim_session | 2 days | Session or security cookie the site needs to work. |
Targeting Cookies:
| Cookie | Duration | Description |
| 6suuid | 400 days | 6sense visitor identifier, stored on 6sense's own domain, used for account-based marketing. |
| _gcl_au | 90 days | Google Ads: measures ad clicks and conversions and supports ad targeting. |
| _gcl_aw | 90 days | Google Ads: measures ad clicks and conversions and supports ad targeting. |
| _gcl_gs | 90 days | Google Ads: stores ad-click information for conversion tracking. |
| _gclxxxx | 90 days | Google Ads: stores ad-click information for conversion tracking. |
| _gd_session | 4 hours | 6sense session identifier. |
| _gd_svisitor | 400 days | 6sense persistent visitor identifier: recognises returning visitors and their company for account-based marketing. |
| _gd_visitor | 400 days | 6sense persistent visitor identifier: recognises returning visitors and their company for account-based marketing. |
| _rdt_uuid | 90 days | Reddit Ads identifier set by the Reddit pixel: measures ad conversions and ad performance and supports ad targeting. |
| GCL_AW_P | 90 days | Google Ads: measures ad clicks and conversions. |
| IDE | 390 days | Google Ads (DoubleClick): advertising identifier used to show and measure ads and to support ad targeting. |
| test_cookie | 15 minutes | Checks whether your browser accepts cookies, for Google's ad services. |
| utmscookie | 30 days | Stores campaign details from the link you arrived on, for marketing attribution. |
Performance Cookies:
| Cookie | Duration | Description |
| _ga | 180 days | Google Analytics: distinguishes visitors to count visits and measure how pages are used. |
| _ga_xxxxxxxxxx | 180 days | Google Analytics: stores session state to measure visits and page use. |
Functional Cookies:
| Cookie | Duration | Description |
| __Host-GAPS | 322 days | Google account sign-in cookie, set by Google when you use Sign in with Google. |
| dremio_region | 180 days | Remembers your region. |
| fixthedocs_language | Session | Remembers the language chosen in the Dremio documentation feedback widget (PushFeedback). |
| subsurface_browser_variant | 7 days | Records your browser type (Firefox, Safari or other) so the site can serve the page version prepared for it. Set only when Functional cookies are on. |
How can you manage and delete cookies?
You can choose whether we place Performance and Targeting cookies on your device, and, outside California, Functional cookies too. You can change your choice at any time. To open your cookie preferences, select Cookie Settings below, in the cookie banner, or in the website footer.
What happens depends on where you are:
- California: Functional cookies are on and cannot currently be switched off through Cookie Settings. All other optional cookies stay off until you opt in. A Global Privacy Control signal switches off Performance and Targeting cookies; it does not switch off Functional cookies.
- Everywhere else, including the European Economic Area, the UK and Switzerland: for new visitors, all optional cookie categories are off by default until you opt in.
Strictly Necessary cookies cannot be switched off through Cookie Settings.
You can review and change your saved choices in Cookie Settings.
Your choice is saved in this browser for up to 180 days and can be recognised by the other listed websites that use the same consent settings. We ask again when the stored choice expires, and may ask for a new choice sooner if we change how we use cookies.
Each browser also has settings that you, or your administrator, can use to block or delete cookies and to prevent the automatic download of images, pixels, beacons or other tracking technologies. If you limit cookies this way, you may not be able to use all the interactive features of our websites.
What are media plug-ins?
A media plug-in embedded on a website lets you watch content hosted by a third-party media provider. You can recognise a media plug-in as a video with a play button. Our websites use YouTube media plug-ins.
How do media plug-ins on our websites work?
On www.dremio.com, our YouTube videos are shown as a preview image, and the video player loads only when you click the play button. We use YouTube’s privacy-enhanced mode (youtube-nocookie.com). Clicking play connects your browser directly to YouTube’s servers, and the video streams from YouTube to your browser.
If you have a YouTube account and are logged in when you start a video, YouTube can link your visit to our websites with your account. In this situation, YouTube may also start and control data transfers itself. Your connection to YouTube, the data transfers between the network and your system, and your interactions on YouTube are governed solely by YouTube’s privacy and cookie policies. Personal data may also reach providers in countries outside the European Economic Area that may not guarantee an “adequate level of protection” for personal data under EU standards. If you do not want to share data through a media plug-in, do not click the play button.
Use of YouTube videos
Our websites contain plug-ins from YouTube, which belongs to Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA). When you start playing an embedded video, information such as your IP address and which of our web pages you visited is sent to YouTube. We have no influence over or control of how the media provider processes personal data on its own website.
On which legal basis do we make media plug-ins available?
We make media plug-ins available on the basis of our legitimate interest in making video content visible to you when you ask for it by clicking play (GDPR Article 6(1)(f), or the equivalent under applicable national law).
What web beacons are used and how can you manage them?
When we send you newsletters or other emails, we use web beacons (a small .gif image) to check whether you can receive email in HTML format. A web beacon is activated when you open an HTML email. This lets us track individual interactions with the content we sent.
Browsers and email clients have settings that you, or your administrator, can use to prevent the automatic download of images, pixels, beacons and other tracking technologies. If you want to stop your browser communicating directly with the sender of an email, you can change these settings.
Where can I get more information?
If you have questions about how we use cookies or similar technologies, email us at [email protected]. To exercise your data protection rights, see our Privacy Policy: https://www.dremio.com/legal/privacy-policy/
