This policy explains how Blue Ribbon Corp. uses cookies and similar technologies on blueribboncorp.com, what each one is for, and how you can change your choices at any time. Our privacy policy explains what we do with the information we collect. You can read it at https://blueribboncorp.com/privacy-policy/.
A cookie is a small file that a website asks your browser to keep. When you come back, the site can read it again. Cookies are how a shop remembers what is in your basket, and how a measurement tool recognises that two page views came from the same visit.
Other techniques do the same job without a cookie file. This policy covers all of them:
Where we say "cookies" in the rest of this policy, we mean all of these. The table below shows which kind each entry is.
We only place cookies that are needed to run the site until you tell us what else you are happy with. Everything else — measurement, advertising, and content loaded from other companies — waits for your permission. You can say no, and you can change your mind later. Saying no costs you nothing and does not reduce what the site does for you, apart from the features that need those cookies to work.
The UK rules changed in February 2026. Most cookies still need your permission first. A short list does not:
For the last two, we have to tell you clearly what they are for and give you a simple, free way to say no. Where we rely on either of them, this policy says so and the "Change your cookie choices" section below is that simple way to say no.
California works the other way round: advertising and measurement cookies may load when you arrive, and you have the right to tell us to stop. You can do that with the cookie controls on this site, and with the "Do Not Sell or Share My Personal Information" route described below. We will not treat you differently for using either.
You can change what you allow at any time, and it is no harder than saying yes was. Use the "Preferences" control below. It opens the same panel you saw when you first arrived, with a switch for each group of cookies. Turn a group off, save, and we stop using those cookies from that moment.
You can also accept everything with "Accept All" or refuse everything that is not needed to run the site with "Reject".
We remember your choice for 30 days. After that we ask again, because a choice you made a long time ago is not a choice you are still making.
We remember it in a cookie of our own. That cookie only holds your choice. If you clear your cookies, or use a different browser or device, we no longer know what you chose and we will ask again.
Turning a group off stops us using it from that moment. It does not reach back and delete what is already stored. To clear what is there, use your browser's own settings — every browser has a way to see and delete cookies and site data, usually under privacy or history. Your browser can also refuse cookies before they are set, or clear them every time you close it. Refusing everything will break parts of this site and of most other sites.
These are the cookies the site cannot work without. They do things you asked for: keeping your basket, keeping you signed in, sending you safely to the payment page, blocking automated abuse, spreading load across our servers, and remembering the cookie choice you just made.
These come from CloudFlare, Comments, Formidable Forms and WooCommerce.
We do not ask your permission for these, because without them the site would not do what you came for. We still list them, so you can see exactly what is there.
You cannot switch these off in the cookie panel. The law lets us use them without asking, for exactly this reason: they are the ones the site needs to do what you requested.
These cookies count how the site is used so we can make it better: which pages people read, which ones they leave, where a checkout goes wrong, how long a page takes to load. They are about the site, not about you as a person, and we do not use them to advertise to you. These come from Google Analytics and WooCommerce Sourcebuster.
If you are in the EU or the EEA, these cookies wait for your permission. Nothing is counted until you allow it, and if you say no we do not count your visit at all.
If you are in the United Kingdom, these cookies wait for your permission, the same as in the EU. UK rules would let some counting cookies run without asking, but we do not rely on that here.
These follow what you look at, here and on other sites, so that the adverts you see are based on it. They also let another company know that you visited, count how many visitors came from an advert, and load things like videos and review widgets from other companies. These come from Google Ads. Some of them use pixels and tags rather than cookies, and some receive your IP address simply because your browser has to ask them for a file.
If you are in the EU, the EEA or the United Kingdom, none of these load until you allow them. There is no exception in either set of rules that would let us advertise to you without asking. If you say no, the adverts you see elsewhere are not based on this visit, and the content we load from other companies is replaced by a box you can click to load it.
We do not sell your personal information, and we do not share it for cross-context behavioural advertising, in the sense California gives those words. In the last twelve months we have not done so.
Because we do not sell or share your personal information, there is no separate "Do Not Sell or Share" page on this site. If you still want the advertising cookies off, open "Preferences" and turn that group off.
There is one table for each group. Each row is one cookie, or one other piece of storage. The columns are:
| Name | Provider | Purpose | Duration | Storage type |
|---|---|---|---|---|
| __cf_bm | CloudFlare | Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. | Until you close your browser | Cookie file |
| __cflb | CloudFlare | When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool. | Until you close your browser | Cookie file |
| __cfruid | CloudFlare | Used by the content network, Cloudflare, to identify trusted web traffic. | Until you close your browser | Cookie file |
| __cfseq | CloudFlare | Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies. | Until you close your browser | Cookie file |
| __cfwaitingroom | CloudFlare | The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active. | Until you close your browser | Cookie file |
| _cfuvid | CloudFlare | The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address. | Until you close your browser | Cookie file |
| cf_chl_rc_i | CloudFlare | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | Until you close your browser | Cookie file |
| cf_chl_rc_m | CloudFlare | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | Until you close your browser | Cookie file |
| cf_chl_rc_ni | CloudFlare | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | Until you close your browser | Cookie file |
| cf_clearance | CloudFlare | Whether a CAPTCHA or Javascript challenge has been solved. | Until you close your browser | Cookie file |
| cf_ob_info | CloudFlare | The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic | Until you close your browser | Cookie file |
| cf_use_ob | CloudFlare | The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds. | Until you close your browser | Cookie file |
| comment_author | Comments | Used to track the user across multiple sessions. | Until you close your browser | Cookie file |
| comment_author_email | Comments | Used to track the user across multiple sessions. | Until you close your browser | Cookie file |
| comment_author_url | Comments | Used to track the user across multiple sessions. | Until you close your browser | Cookie file |
| frm_form_ | Formidable Forms | Saves the ID of the form and the time the entry was submitted. | 2 hours | Cookie file |
| store_notice | WooCommerce | Allows customers to dismiss the Store Notice. | Until you close your browser | Cookie file |
| woocommerce_cart_hash | WooCommerce | Helps WooCommerce determine when cart contents/data changes. | Until you close your browser | Cookie file |
| woocommerce_dismissed_suggestions__ | WooCommerce | Count of suggestion dismissals, if enabled. | 1 month | Cookie file |
| woocommerce_items_in_cart | WooCommerce | Helps WooCommerce determine when cart contents/data changes. | Until you close your browser | Cookie file |
| woocommerce_recently_viewed | WooCommerce | Powers the Recent Viewed Products widget | Until you close your browser | Cookie file |
| woocommerce_snooze_suggestions__ | WooCommerce | Allows dashboard users to dismiss Marketplace suggestions, if enabled. | 2 days | Cookie file |
| wp_woocommerce_session_ | WooCommerce | Contains a unique code for each customer so that it knows where to find the cart data in the database for each customer. | 2 days | Cookie file |
| wpconsent_preferences | Blue Ribbon Corp. | This cookie is used to store the user's cookie consent preferences. | 30 days | Cookie file |
| Name | Provider | Purpose | Duration | Storage type |
|---|---|---|---|---|
| __utma | Google Analytics | ID used to identify users and sessions | 2 years after last activity | Cookie file |
| __utmb | Google Analytics | Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server. | 30 minutes after last activity | Cookie file |
| __utmc | Google Analytics | Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session. | Until you close your browser | Cookie file |
| __utmt | Google Analytics | Used to monitor number of Google Analytics server requests | 10 minutes | Cookie file |
| __utmv | Google Analytics | Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server. | 2 years after last activity | Cookie file |
| __utmx | Google Analytics | Used to determine whether a user is included in an A / B or Multivariate test. | 18 months | Cookie file |
| __utmz | Google Analytics | Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server | 6 months after last activity | Cookie file |
| _ga | Google Analytics | ID used to identify users | 2 years | Cookie file |
| _ga_ | Google Analytics | ID used to identify users | 2 years | Cookie file |
| _gac_ | Google Analytics | Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together. | 90 days | Cookie file |
| _gali | Google Analytics | Used by Google Analytics to determine which links on a page are being clicked | 30 seconds | Cookie file |
| _gat | Google Analytics | Used to monitor number of Google Analytics server requests when using Google Tag Manager | 1 minute | Cookie file |
| _gid | Google Analytics | ID used to identify users for 24 hours after last activity | 24 hours | Cookie file |
| sbjs_current | WooCommerce Sourcebuster | Traffic origin information for the visitor’s current visit to your store | Until you close your browser | Cookie file |
| sbjs_current_add | WooCommerce Sourcebuster | Timestamp, referring URL, and entry page for your visitor’s current visit to your store | Until you close your browser | Cookie file |
| sbjs_first | WooCommerce Sourcebuster | Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires) | Until you close your browser | Cookie file |
| sbjs_first_add | WooCommerce Sourcebuster | Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires) | Until you close your browser | Cookie file |
| sbjs_migrations | WooCommerce Sourcebuster | Technical data to help with migrations between different versions of the tracking feature | Until you close your browser | Cookie file |
| sbjs_session | WooCommerce Sourcebuster | The number of page views in this session and the current page path | 30 minutes | Cookie file |
| sbjs_udata | WooCommerce Sourcebuster | Information about the visitor’s user agent, such as IP, the browser, and the device type | Until you close your browser | Cookie file |
| Name | Provider | Purpose | Duration | Storage type |
|---|---|---|---|---|
| ADS_VISITOR_ID | Google Ads | Cookie required to use the options and on-site web services | 2 months | Cookie file |
| AEC | Google Ads | AEC cookies ensure that requests within a browsing session are made by the user, and not by other sites. These cookies prevent malicious sites from acting on behalf of a user without that user's knowledge. | 6 months | Cookie file |
| Conversion | Google Ads | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 days | Cookie file |
| FPGCLAW | Google Ads | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days | Cookie file |
| FPGCLGB | Google Ads | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days | Cookie file |
| __Secure-1PAPISID | Google Ads | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years | Cookie file |
| __Secure-1PSID | Google Ads | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years | Cookie file |
| __Secure-1PSIDCC | Google Ads | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years | Cookie file |
| __Secure-1PSIDTS | Google Ads | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years | Cookie file |
| __Secure-3PAPISID | Google Ads | Profiles the interests of website visitors to serve relevant and personalised ads through retargeting. | 2 years | Cookie file |
| __Secure-3PSID | Google Ads | Targeting cookie. Used to profile the interests of website visitors and display relevant and personalised Google ads. | 2 years | Cookie file |
| __Secure-3PSIDCC | Google Ads | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years | Cookie file |
| __Secure-3PSIDTS | Google Ads | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years | Cookie file |
| _gac_gb_ | Google Ads | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days | Cookie file |
| _gcl_au | Google Ads | Used by Google Ads to measure advertising effectiveness and track conversions from advertisements. | 3 months | Cookie file |
| _gcl_aw | Google Ads | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days | Cookie file |
| _gcl_gb | Google Ads | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days | Cookie file |
| _gcl_gs | Google Ads | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days | Cookie file |
1 of the 5 other companies on this site publish full details of what they collect and how long they keep it. For the rest we have shown what is available. Ask us and we will chase the detail you want.
We do not embed videos, maps, social feeds or review widgets from other companies on this site, so nothing of that kind sets cookies here.
Each of these companies sets or reads something on your device through this site, and decides for itself what it does with what it collects. Their own policies apply to that, not ours.
| Company | What it does here | Their privacy policy |
|---|---|---|
| CloudFlare | the technical operation of the site | https://www.cloudflare.com/privacypolicy/ |
| Comments | the technical operation of the site | |
| Formidable Forms | the technical operation of the site | |
| Formidable Forms | the technical operation of the site | |
| Google Ads | advertising and marketing | https://policies.google.com/privacy |
| Google Analytics | measuring how visitors use the site | https://policies.google.com/privacy |
We do not have a privacy policy link for Comments and Formidable Forms. Rather than guess at a web address, we have left it blank. Ask us and we will send you what we have.
We change this page when what we use changes. Adding a tool, dropping one, or changing what a tool is for means a change here, and the date at the top moves.
The tables update themselves after each scan of the site, so a new cookie appears here without us rewriting anything. The written parts change only when we change them.
If we start using cookies for something new that needs your permission, your old answer does not cover it: we ask you again. Even without a change, we ask again after 30 days.
We keep this page at the same web address, so a link to it keeps working. It is worth checking now and then.
Anything on this page, ask us. Our privacy policy at https://blueribboncorp.com/privacy-policy/ covers your wider rights and how to use them.
Email [email protected]. Phone (877) 774-4751. Write to Blue Ribbon Corp., 2770 Long Road
14072 Grand Island
United States (US).
Email us or call (877) 774-4751 or (716) 404-5884 (Outside US)
or find your Blue Ribbon Corp Factory Rep or Local Distributor using the links below.
We use cookies and process personal data to make our site work, for analytics, and for ads personalization. Some of this data is shared with our partners. Open the preferences panel to see which services we use and choose what you allow.
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
These cookies are needed for adding comments on this website.
Formidable Forms is a powerful WordPress plugin for creating advanced forms and data management solutions.
Google Tag Manager
WooCommerce is a customizable eCommerce platform for building online stores using WordPress.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: business.safety.google (opens in a new window)
SourceBuster is used by WooCommerce for order attribution based on user source.
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Google Ads is an online advertising platform that enables businesses to create targeted ads displayed on Google search results and partner sites.
Service URL: business.safety.google (opens in a new window)
You can find more information in our Cookie Policy and Privacy Policy.
Blue Ribbon Corp.
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside it.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers).
Despite our very best efforts to allow anybody to adjust the website to their needs. There may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to

