We may update this notice from time to time to add or remove cookies or categories of cookies and/or to clarify or amend the descriptions. (We may also periodically reorder the contents for easier reference.) This version was last updated Tuesday, September 21, 2021.
Cookies and Similar Technologies
A cookie is a small text file — a string of information — that a website or online service places (or “sets” — these terms are used synonymously) on your browser or device and that your browser or device then provides to that site or service when you access it. (It is sometimes also possible for a website or service to detect cookies set by other sites/services.)
Cookies may be used in many different ways, but the most common uses are to save your settings or preferences, to manage logins, and to help identify specific users or devices for analytics and/or advertising purposes. Most cookies are specific to each browser and device; if you access a website from multiple browsers and/or multiple devices, the website may place cookies on each browser on each device. A cookie set by the website or service you are currently visiting is called a “first-party” cookie, while cookies set by other services or domains (e.g., the cookies set when you access an embedded video player) are known as “third-party” cookies. You can learn more about how cookies work and how you can manage or delete them in different browsers by visiting AboutCookies.org. (We are not affiliated in any way with that website or with the law firm that runs it, Pinset Masons LLP, and offer this link purely for your information.)
Although some cookies are necessary or cannot currently be disabled for technical reasons, you may have the option to disable certain types of cookies by category. To review your available choices, click the “Access Your Privacy and Cookie Preferences” button below and review the summaries under “Cookie Settings”:
(You can also access this button via the Privacy Tools page.)
You are free to use your browser and/or browser add-ons to block or remove any cookies set by the Ate Up With Motor website or its embedded content providers. However, please note that some site features and/or site content may not function without cookies. For example, you may not be able to hide the notification banners or change certain accessibility settings, and previously saved preferences may be lost. (Again, if you use multiple devices and/or browsers, deleting or blocking cookies on one device or browser does not usually affect cookies on the others.)
Categories of Cookies Used
Some of the cookies set by Ate Up With Motor or our embedded content providers are “session cookies” that expire (cease to function) when you close your browser. Others are “persistent cookies” that remain on your device and expire after a certain amount of time, such as 30 days or one year. Certain cookies will persist for as long as your browser permits unless you manually delete them.
The durations described below are the normal durations of these cookies. (They are approximate because while the duration of a persistent cookie is theoretically very precise, variations in time zone settings, clock accuracy, and/or the time of day when the cookie is set can sometimes cause the cookie to remain or appear to remain for somewhat more or less time than its nominal duration.) You should keep in mind that your actions or choices on this website (e.g., changing or updating your accessibility settings) may set additional cookies, change the duration of current ones, and/or remove certain cookies entirely. Also, your individual browser settings may affect how long cookies remain on your device/browser. For example, if your browser is set to automatically clear your browsing history each time you close the browser, doing so may remove all saved cookies, regardless of their normal duration.
As noted above, you can also review this information and/or fine-tune your available choices by going to the Privacy Tools page and clicking “Access Your Privacy and Cookie Preferences.” Please note that while the cookie descriptions presented in this Cookie Notice and the ones listed in the Cookie Settings menu accessed through the “Access Your Privacy and Cookie Preferences” button are intended to be substantially the same (save for minor variations in formatting and text style), in the event of any substantive discrepancy between those versions, the Cookie Notice version(s) below shall govern.
How they are used:
Accessing certain posts or pages on this website may require you to enter a specific password. If you correctly enter the password, the site saves this cookie on your device to allow you access to the password-protected post or page. (For this cookie, “xx” will be a cryptographic hash.) There may be more than one of these cookies, particularly if you access several password-protected posts with different passwords. The cookies normally expire in about 10 days, and are not set at all if you do not access any password-protected content.
comment_author_xx, comment_author_email_xx, comment_author_url_xx
How they are used:
When you submit a comment, you may have the option save your information for future comments, storing the info in these cookies. (For each of these cookies, “xx” will be a cryptographic hash.) The cookies are not set at all unless you select that option when submitting a comment. They normally expire in just under one year, but you can delete the cookies in your browser at any time. (These cookies are not usually set for administrative users, since comments they submit while logged in are associated with their user ID number and user profile information rather than a manually entered name and email address.)
Privacy and Cookie Preferences
gdpr, gdpr[allowed_cookies], gdpr&5Bprivacy_bar&5D, gdpr[consent_types]
How they are used:
These cookies manage your cookie and privacy preferences. There will typically be several such cookies, each beginning with “gdpr” (e.g., gdpr[allowed_cookies], gdpr&5Bprivacy_bar&5D, and gdpr[consent_types]). They normally expire after about one year. If you delete or disable these cookies, your existing preferences will be lost and you may not be able to save your privacy settings for this website. (These cookies may not be set at all for administrative users unless they access the publicly visible portions of the website.)
cookieconsent_status, _ga, _gid, _gat, _gat_gtag_UA_6113964_2
How they are used:
These first-party cookies enable the Google Analytics service to gather information about visitors and how they use the Ate Up With Motor website. The cookieconsent_status cookie records whether or not you’ve consented to analytics tracking and tells the website to hide the notification banner; the cookie normally expires after about one year. The _ga and _gid cookies, which are only placed if you click “Accept/Enable” in the notification banner, are used by the Google Analytics service to track your activity on the site. They may persist for up to two years. The _gat cookie, which may appear as _gat_gtag_UA_6113964_2, is sometimes set along with the _ga and _gid cookies; it is a short-lived “throttling” cookie, typically persisting for only a few minutes at a time, that is used to control how frequently requests are sent to the Google Analytics servers. (These cookies may not be set at all for administrative users unless they access the publicly visible portions of the website, as we do not currently use the Google Analytics service on the site’s administrative dashboard or login page.)
Disable Google Analytics Tracking
How they are used:
This cookie is set when you click the “Disable Google Analytics Tracking” link. If you set the cookie, the Google Analytics service will no longer track your use of the Ate Up With Motor website, even if you previously consented to analytics tracking. (Please note that this cookie affects only your current device/browser; works ONLY on the Ate Up With Motor website, not on other websites or online services; and cannot prevent our third-party embedded content providers from using the Google Analytics service in connection with content such as embedded video players.) The cookie normally remains on your device for as long as your browser settings permit. (Google, Google Analytics, and other related marks are trademarks of Google LLC.)
wahFontColor, wahBgColor, a11y-desaturated, a11y-high-contrast, a11y-larger-fontsize
How they are used:
If you change certain aspects of the site’s appearance using the accessibility sidebar, it may set these cookies to manage and remember your settings. The wahFontColor and wahBgColor cookies, which are set if you alter the site’s color scheme, normally expire after about 14 days, but you can remove them immediately by clicking the “Restore Defaults” button on the sidebar.
We may sometimes present an alternative version of the sidebar offering different options, which may set the a11y-desaturated, a11y-high-contrast, and/or a11y-larger-fontsize cookies if you change those settings. These a11y cookies normally expire after about seven days, but are removed immediately if you restore the applicable settings to their default values.
How they are used:
The payment button in the “Support Ate Up With Motor” box (and similar payment or donation buttons that may appear on portions of the administrative dashboard, which is not normally accessible except to logged-in administrative users) contains embedded content served by PayPal® services. If the payment button is visible, it may set the third-party cookies PYPF (via paypalobjects.com, which is owned by PayPal), which appears to check whether or not you are a logged-in PayPal user and is probably used to facilitate the PayPal user login process, and/or 01A1 (via abmr.net, which is owned by Akamai Technologies), which stores certain technical information about your device and browser, possibly to facilitate the login and shopping cart functions. The PYPF cookie normally expires in approximately four weeks, the 01A1 cookie in approximately one year.
If you use the buttons to make a payment or donation, the PayPal services will set additional cookies (not listed here) to manage your PayPal login and transaction data (and potentially also for various other purposes, such as user analytics and/or advertising). For more information about what data PayPal services collect and how that data may be used, visit the “Legal Agreements for PayPal Services” page to review the PayPal Privacy Statement and Statement on Cookies and Tracking Technologies that apply in your location (the Statement on Cookies and Tracking Technologies that applies to each region is linked from within the applicable PayPal Privacy Statement). For more information about how Akamai may collect, process, and/or use personal data, visit the Akamai “Privacy and Policies” page and Privacy Trust Center. (PayPal.com, PayPal, and all logos related to the PayPal services are either trademarks or registered trademarks of PayPal, Inc. or its licensors. In addition, all page headers, custom graphics, button icons, and scripts related to the PayPal services are service marks, trademarks, and/or trade dress of PayPal. Akamai is a registered trademark or service mark of Akamai Technologies, Inc. in the United States (Reg. U.S. Pat. & Tm. Off.).)
You can hide the “Support Ate Up With Motor” box and prevent the loading of its embedded content by going to the Privacy Tools page, clicking “Access Your Privacy and Cookie Preferences” (or by clicking the “Privacy Preferences” link in the banner that appears at the bottom of your screen when you first arrive on Ate Up With Motor) and switching the toggle switch for this category to “OFF.” (At present, this setting does NOT affect the donation or payment buttons that may appear on portions of the site’s administrative dashboard, nor does hiding the box affect any cookies that may have already been set). This setting is stored in your browser in the gdpr[allowed_cookies] cookie described in “Privacy and Cookie Preferences” above, so if you delete that cookie or access the Ate Up With Motor website from a different device/browser, you will need to adjust the setting again if you still wish to hide the box.
yt.innertube::nextId, yt.innertube::requests, yt-remote-cast-installed, yt-remote-connected-devices, yt-remote-device-id, yt-remote-fast-check-period, yt-remote-session-app, yt-remote-session-name, recently_watched_video_id_list, use_hotbox, demographics, GPS, LOGIN_INFO, PREF, VISITOR_INFO1_LIVE, YSC, AID, ANID, APISID, CONSENT, DSID, FLC, GAPS, IDE, NID, HSID, OTZ, SID, SNID, SIDCC, TAID, exchange_uid, 1P_JAR
How they are used:
_abexps, aka_debug, clips, continuous_play_v3, embed_preferences, has_logged_in, is_logged_in, jsessionID, player, search_click_position, Searchtoken, stats_end_date, stats_start_date, sst_aid, uid, v6f, vimeo, vuid, _ga, _gads, _utma, _utmb, _utmc, _utmv, _utmz,_ceg.s, _ceg.u, optimizelyBuckets, optimizelyEndUserId, optimizelySegments, adsense, adsenseReferralSourceId, adsenseReferralSubId, adsenseReferralUrl, adsenseReferralUrlQuery, S_adsense, APISID, GAPS, HSID, NID, N_T, PREF, SAPISID, SID, SNID, SSID
How they are used:
Administrative and Login Cookies
wordpress_test_cookie, itsec-hb-login-xx, itsec_interstitial_browser, wordpress_sec_xx, wordpress_logged_in_xx, wordpress_xx, wp-settings-UID, wp-settings-time-UID, wp-saving-post, wp-donottrack_feed
How they are used:
These first-party cookies are used to manage user logins and certain other administrative functions of the WordPress content management system, such as post editing. These cookies are necessary for the site’s administrative users (who wouldn’t even be able to log in without them), but if you are not an administrative user, these cookies aren’t normally be placed on your device at all unless you somehow access the login area, which is off-limits to non-administrators.
Accessing the login page sets the wordpress_test_cookie, a session cookie that tests whether the user’s browser will allow the cookies needed to log in to the administrative dashboard; this cookie normally expires when the user closes their browser. The iThemes Security plugin may also set the itsec-hb-login-xx cookie, which helps to protect the site against “brute force” hacking attempts; that cookie normally expires in about one hour. In certain cases, multiple iterations of either or both of these cookies may be set.
Logging in sets the wordpress_logged_in_xx, wordpress_sec_xx, and/or wordpress_xx cookies, which store the user’s login credentials to allow access to the administrative dashboard and other administrative functions; there may be multiple iterations of each cookie. These cookies expire in about 15 days if the user clicks “Remember Me” when logging in; if not, the cookies normally expire at the end of the browser session (or, failing that, within about two days). If we have enabled two-factor authentication (which requires an authentication code as well as a password to log into the administrative dashboard), the iThemes Security plugin may also set the itsec_interstitial_browser cookie during the login process. This is a session cookie that verifies that the user has entered a valid authentication code; the cookie normally expires when the user closes their browser.
After logging in, the wp-settings-UID cookies store the logged-in user’s configuration settings, while the wp-settings-time-UID cookies record the time those configuration settings were last set; again, there may be multiple iterations of each of these cookies, which normally expire after about one year. One or more wp-saving-post cookies may be set while creating and/or editing posts or pages, to help manage version control and the autosave feature; these cookies normally expire after about 24 hours. The wp-donottrack_feed cookie, which controls a blog feed, was set by accessing the dashboard menu for the WP DoNotTrack plugin (which we do not currently use on this website); this cookie normally expires in about one year.
For all the administrative and login cookies described here, “xx” will be a cryptographic hash while “UID” will be the administrative user’s user ID number in this website’s WordPress database. (WordPress and the WordPress logos are registered trademarks of the WordPress Foundation in the United States and other countries. iThemes is one of the Liquid Web family of brands; iThemes and Liquid Web are trademarks of Liquid Web, LLC.)
The results of such tests may be stored in your browser’s web storage and/or saved in cookies (e.g., the wordpress_test_cookie described in the “Administrative and Login Cookies” category above). The site may also show you specific messages or other content based on this information, such as (again without limitation) displaying a warning notification that your current browser is incompatible with certain site features. Some such stored information remains on your device only for the length of your current visit to this website, although certain information may remain in your browser’s web storage until the end of your browser session (that is, until you close your browser). Cookies that store the results of such browser tests typically expire when you close your browser.