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) in your browser (or other user agent) or device and that your browser, other user agent, 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 (or other user agent) and device; if you access a website using multiple browsers (and/or other user agents) and/or multiple devices, the website may place cookies in each browser (and/or other user agent) 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 KnowCookies.com. You can find additional tools for controlling certain cookies and/or similar technologies used for behavioral advertising purposes (e.g., to show you personalized ads based on your online activity and/or interests) at YourAdChoices (for the U.S.) or Your Online Choices (for the EU, Switzerland, and the UK). (We are not affiliated in any way with these websites or the organizations that run them, and offer these links purely for your information. The names of these websites, and/or other related names, terms, slogans, logos, and/or icons, may be (and/or may incorporate) trademarks or registered trademarks; such marks are the property of their respective owners and are used here strictly for purposes of identification.)
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 or user agent’s settings and/or 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, multiple browsers, and/or multiple other user agents, deleting or blocking cookies on one device, browser, or user agent does not usually affect cookies on the others.)
The article “How to enable, disable, or clear your browser’s ‘Web Storage’ cache” explains how to manage or delete web storage data in various common browsers. Please note that while it may be possible to disable web storage and/or otherwise block technologies other than cookies from storing data on your browser (or other user agent), doing so may cause many functional problems and is not recommended. (We are not affiliated in any way with the above website or the business that runs it, and offer this link purely for your information. The name of the website, the name of the business, and/or other related names and/or logos may be trademarks or registered trademarks; such marks are the property of their respective owners and are used here strictly for purposes of identification.)
Categories of Cookies Used
Below are descriptions of the categories of cookies that may be used on this website. Not all of these cookies are necessarily set for all visitors — for example, some cookies are only placed when you perform certain actions, and the cookies set for administrative users may differ from the ones set for visitors to the publicly visible portions of the site.
The durations described in the categories below are the normal durations of these cookies. They should be considered approximate, particularly for cookies set by third parties; embedded content providers don’t necessarily offer detailed information about the cookies they use, and in some cases, we couldn’t find any consensus on the normal duration of a particular cookie (or even its precise function).
You should keep in mind that your actions and/or choices on this website (e.g., changing or updating your accessibility settings) may set additional cookies, change the durations of current ones, and/or remove certain cookies entirely. Also, the settings of your browser (or other user agent) may affect how long cookies remain on your browser, other user agent, or device. For example (but without limitation), 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 durations. Additionally, if your browser (or other user agent) crashes rather than being closed properly, session cookies may not be deleted as they ordinarily would be.
Data stored in your browser (or other user agent) using technologies other than cookies — e.g., web storage — doesn’t have an expiration date like a cookie does. Such data is normally either automatically deleted at the end of your session or retained indefinitely unless you take steps to manually delete it.
As noted above, you can also review these cookie categories 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 below shall govern and control.
Privacy and Cookie Preferences
gdpr[allowed_cookies], gdpr&5Bprivacy_bar&5D, gdpr[consent_types]
How they are used:
cookieconsent_status, _ga, _gid, _gat, _gat_gtag_UA_6113964_2
How they are used:
Disable Google Analytics Tracking
How they are used:
This cookie was set if you clicked the “Disable Google Analytics Tracking” link to prevent the Google Analytics service from tracking your use of the Ate Up With Motor website. Now that we have DISCONTINUED our use of Google Analytics tracking on this website, this cookie no longer functions — no additional analytics data will be collected, with or without the cookie. However, the cookie may remain on your device for as long as the settings of your browser (or other user agent) permit.
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 (or other user agent) 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.)
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, Inc.), which appears to check whether or not you are a logged-in PayPal user, possibly 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 (or other user agent), 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.
Each PayPal payment or donation button may also incorporate a tracking pixel called “pixel.gif” (which loads from paypalobjects.com). A tracking pixel, sometimes known as a web beacon, is a tiny image file that loads from a remote server; it’s a type of embedded content (as is the button itself, which loads from the same domain). The image file itself contains no personally identifying information, but the loading of that file may be used to help identify and/or track you.
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, e.g., 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 payment or donation 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 (or other user agent) 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, or user agent, you will need to adjust the setting again if you still wish to hide the box.
VISITOR_INFO1_LIVE, YSC, 1P_JAR, CONSENT, GED_PLAYLIST_ACTIVITY, GPS, PREF, LOGIN_INFO, remote_sid, use_hitbox, NID, IDE, ANID, APIS, SAPISID, DSID, HSD, SID, SSID, SNID, SIDCC, AID, CGIC, GAPS, GLC, N_T, OTZ, TAID, exchange_uid, test_cookie (cookies); Permission, yt.innertube::nextId, yt.innertube::requests, yt-html5-player-modules::subtitlesModuleData::display-settings, yt-html5-player-modules::subtitlesModuleData::module-enabled, ytidb::LAST_RESULT_ENTRY_KEY, yt-player-autonavstate, yt-player-bandaid-host, yt-player-bandwidth, yt-player-headers-readable, yt-player-lv, yt-player-quality, yt-player-volume, yt-remote-cast-available, 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, application_server_key, AuthKey, DeviceId, Endpoint, HighPriorityNotificationShowCount, HomePromptCount, HomePromptTime, IDToken, IndexedDBCheck, LogsDatabaseV2, P256dhKey, Permission, PromptTags, RegistrationTimestamp, shell_identifier_key, TimestampLowerBound, yt-serviceworker-metadata (other data items that may be stored in your browser or other user agent)
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, e.g., 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 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 (or other user agent) will allow the cookies needed to log in to the administrative dashboard; this cookie normally expires when the user closes their browser (or other user agent). 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 when the user closes their browser (or other user agent), or, failing that, within about two days. If we have enabled multi-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 valid user credentials pending receipt of the correct authentication code; the cookie normally expires when the user closes their browser (or other user agent).
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 some such tests (which generally don’t contain any personally identifying information) are stored only in your device’s memory, and only for the length of your current visit. If any such test results are stored in your browser (or other user agent), whether in cookies (e.g., the wordpress_test_cookie described in the “Administrative and Login Cookies” category above) and/or using other technologies (e.g., in web storage), that data normally expires and is automatically removed at the end of your current session — that is, when you next close your browser (or other user agent). (WordPress is a registered trademark of the WordPress Foundation in the United States and other countries.)