Cookie Notice

As indicated in the “Cookies and Similar Technologies” section of the Privacy Policy, the aaronseverson.com website and/or its embedded content providers may use cookies and/or similar technologies for a variety of purposes.

This Cookie Notice, which forms part of the Privacy Policy and uses the same Definitions, describes the cookies that are typically used on this website. This notice also constitutes the “cookie policy” for this website, for jurisdictions that specifically require such a policy. (This notice does NOT attempt to list or describe cookies used by third-party websites or services outside of the aaronseverson.com website (e.g., cookies that may be set when you register with or log into a third-party service). The use of cookies and/or similar technologies by third-party websites or services is subject to those sites or services’ respective privacy policies, cookie policies, and/or terms of service/terms of use, and in most cases is outside of my control.)

I 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. (I may also periodically reorder the contents for easier reference.) Changes to this Cookie Notice will be summarized in the “Recent Revisions” section of the Privacy Policy, along with other Privacy Policy changes. The current version of this notice was last updated on January 17, 2023.

Variations in text style (e.g., different font weights, sizes, or colors) are used throughout this Cookie Notice to improve readability, but have no legal significance or effect.


NOTE: Because certain portions of this Cookie Notice, like portions of the Privacy Policy of which it is a part, were adapted from the Automattic Privacy Policy (which you can also find at their Legalmattic repository), which is licensed under a Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license, the entire aaronseverson.com Privacy Policy, including this Cookie Notice, is also licensed under CC BY-SA 4.0, as the terms of that license require. (If you elect to use or further adapt this Cookie Notice and/or the rest of the Privacy Policy, please credit Automattic as well as me (Aaron Severson). Automattic and Legalmattic are trademarks or registered trademarks of Automattic (or Automattic’s licensors). I am not affiliated with or endorsed by Automattic in any way.)


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.

Some websites and/or online services may also use similar technologies, e.g., storing information in your browser’s web storage and/or plugins. Data items stored in your browser (or other user agent) and/or on your device in such ways aren’t cookies in the usual sense, but they may perform similar functions and may be used instead of or in addition to cookies. Such technologies are often used to manage functional details, e.g., settings and preferences, but are sometimes also used to help websites and/or services identify you. Online services may also use “web beacons,” which are small code blocks or tiny image files (sometimes called “tracking pixels” or “pixel tags”) that transmit certain information about you and your user agent (a term explained in the “Definitions” section of the Privacy Policy) to the service from which the web beacon is loaded. Web beacons (which are a form of embedded content, another term explained in the “Definitions” section of the Privacy Policy) are sometimes also used instead of or in conjunction with cookies to identify users and track their behavior online.

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.), AdChoices in Canada (for Canada), or Your Online Choices (for the EU, Switzerland, and the UK). (I am 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.)

How This Website Uses Cookies and Similar Technologies

In general, this website sets cookies and/or stores information in your browser (or other user agent) in circumstances where I need to identify a specific device and/or store visitor choices/preferences, including, though not limited to, certain accessibility settings and privacy choices like your acceptance of this Privacy Policy. The use of cookies also allows me to determine which content to show you (e.g., whether to display or hide banners intended for first-time visitors), control access to age-restricted content, and help prevent unauthorized visitors from accessing administrative areas of the website. Certain other site functions and/or site content may require the use of cookies and/or similar technologies to function properly.

If you visit some portion of the website that contains third-party embedded content (as described in the “Embedded Content” section of the Privacy Policy), that content may also place cookies on your device.

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 aaronseverson.com 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. (I am 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.

Please note that this shouldn’t be regarded as an exhaustive list of all the specific cookies that might be used on this website. First, if I have just added or am testing some new plugin or other site component, it may set additional cookies that aren’t yet listed. Second, the cookies set by embedded content providers may vary: Some such cookies may be set only in certain circumstances (not all of which I may have recognized), and providers may periodically add new cookies and/or retire older ones, which is outside of my control. (The “Embedded Content” section of the Privacy Policy includes a list of many — though not necessarily all — of the embedded content providers I may use on this website, along with links to their respective privacy policies and cookie policies.)

Cookies set by this website or its embedded content providers may be “session cookies,” which normally expire and cease to function at the end of your session — that is, when you close your browser (or other user agent), or “persistent cookies,” which remain on your device and expire after a certain amount of time, e.g., 30 days or one year. Some persistent cookies are designed to remain on your device for as long as the settings of your browser (or other user agent) permit, typically by setting their expiration dates far in the future.

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, I 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 identical (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

Cookies used:

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 and/or update their consent settings — e.g., by accepting an updated version of the Privacy Policy.)

Accessibility Settings

Cookies used:

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.

I 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.

Password-Protected Posts

Cookies used:

wp_postpass_xx

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.

Commenting

Cookies used:

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.)

YouTube Videos

Cookies used:

VISITOR_INFO1_LIVE, VISITOR_INFO1_LIVE__k, VISITOR_INFO1_LIVE__default, YSC, YEC, _Secure-YEC, PREF, GED_PLAYLIST_ACTIVITY, CGIC, DV, CONSENT, SOCS, AEC, exchange_uid, id, pm_sess, pm_sess_NNN, aboutads_sessNNN, remote_sid, test_cookie, use_hitbox, _gac_gb_, __gads, _gcl_, _gcl_au, _gcl_aw, _gcl_dc, _gcl_gb, _gcl_gf, _gcl_ha, __gpi, __gpi_optout, __gsas, Conversion, 1P_JAR, ACLK_DATA, GPS, NID, ENID, ANID, AID, TAID, IDE, APIS, SAPISID, DSID, HSD, SID, HSID, SSID, SNID, SIDCC, FCCDCF, FCNEC, FLC, FPGCLAW, FPGCLDC, FPAU, GAPS, GLC, N_T, OTZ, PAIDCONTENT, RUL, TAID, UULE, LOGIN_INFO (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:

Embedded video players for content hosted on the YouTube video platform (which is owned by Google LLC) may set these third-party cookies and/or use similar technologies to store data in your browser (or other user agent) for purposes such as (without limitation) managing video settings (e.g., tailoring the playback to your connection speed), storing video preferences, providing certain functionality (e.g., allowing you to pause a video at a particular point), showing you advertisements, associating your video viewing and other activity with your Google account (if any), ensuring proper functioning of the service, preventing abuse, and/or compiling user analytics data. Such cookies and/or stored data items may be set by various domains (such as, though not necessarily limited to, youtube.com; youtube-nocookie.com; googlevideo.com; ytimg.com; google.com; accounts.google.com; www.googleadservices.com; and/or doubleclick.net, which is part of the DoubleClick advertising service, also owned by Google LLC). Not all the listed cookies and/or data items are necessarily set in all instances, and there may sometimes be others not listed above, particularly if you are logged into a Google account. Some persist for only a few minutes, or until you close your browser (or other user agent); others may remain in your browser (or other user agent) as long as your individual settings permit. To learn more about what information the YouTube platform and other Google services may collect through and/or in connection with embedded video players and how Google may use that information, see their “How Google uses information from sites or apps that use our services” page and the Google Privacy Policy. For additional information about how Google uses cookies and/or other technologies that may collect and/or process personal information, see the “Technologies” section of their Google Privacy & Terms site and the “Our advertising and measurement cookies” section of their Google Business Data Responsibility site, which includes a detailed list of cookies associated with Google advertising and measurement products. (Those pages do not currently discuss the storage of data in your browser (or other user agent) using technologies other than cookies, e.g., in web storage.) For more information about Google advertising, see the “Advertising” section of their Google Privacy & Terms site. (Google, DoubleClick, YouTube, and other related marks and logos are trademarks of Google LLC.)

Vimeo Videos

Cookies 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 (Vimeo cookies); _ceir, _ceg.s, _ceg.u (Crazy Egg cookies); optimizelyBuckets, optimizelyEndUserId, optimizelySegments (Optimizely cookies); _ga, _ga_, _gac_, _gaexp, _gaexp_rc, _gat_, _opt_awcid, _opt_awgid, _opt_awkid, _opt_awmid, _opt_utmc, _opt_expid, __utma, __utmb, __utmc, __utmt, __utmv, __utmz, _dc_gtm_, AMP_TOKEN, FPID, GA_OPT_OUT (Google Analytics cookies); adsense, adsenseReferralSourceId, adsenseReferralSubId, adsenseReferralUrl, adsenseReferralUrlQuery, S_adsense, Conversion, _gac_gb_, __gads, _gcl_, _gcl_au, _gcl_aw, _gcl_dc, _gcl_gb, _gcl_gf, _gcl_ha, __gpi, __gpi_optout, __gsas, id, pm_sess, pm_sess_NNN, aboutads_sessNNN, test_cookie, CONSENT, SOCS, GED_PLAYLIST_ACTIVITY, 1P_JAR, ACLK_DATA, GPS, NID, ENID, ANID, AID, TAID, IDE, APIS, SAPISID, DSID, HSD, SID, HSID, SSID, SNID, SIDCC, FCCDCF, FCNEC, FLC, FPGCLAW, FPGCLDC, FPAU, GAPS, GLC, N_T, OTZ, PAIDCONTENT, RUL, TAID, UULE (other Google advertising and measurement cookies)

How they are used:

These third-party cookies may be set in connection with embedded video players for content hosted on the Vimeo video platform, for purposes such as (without limitation) managing video settings, storing video preferences, providing certain functionality (e.g., allowing you to pause a video at a particular point), associating your video viewing and other activity with your Vimeo account (if you have one), showing you advertising, ensuring proper functioning of the service, preventing abuse, and/or compiling user analytics data. Cookies whose names begin with “_ceg” are associated with the Crazy Egg web analytics service (which is subject to the Crazy Egg Privacy Policy and Cookie Policy). Cookies whose names begin with “optimizely” are associated with the Optimizely digital experience platform (which is subject to the Optimizely Privacy Policy; the “Privacy” section of the Optimizely Trust Center provides additional information about Optimizely privacy practices, including a link to the Data Processing Agreement that applies to personal data the Optimizely services process on customers’ behalf that may be subject to certain regional privacy and/or data protection laws, while their “Cookies and localStorage in the Optimizely snippet” help page provides additional technical information about the cookies and/or similar technologies used by that platform). Many of the other listed cookies are associated with the Google Analytics service, the Google AdSense advertising service, and/or other Google advertising and measurement products, which are subject to the Google Privacy Policy; see their “How Google uses information from sites or apps that use our services” page, the “Information for Visitors of Sites and Apps Using Google Analytics” section of the Google Analytics “Safeguarding your data” help page, the “Technologies” section of their Google Privacy & Terms site, and the “Our advertising and measurement cookies” section of the Google Business Data Responsibility site (which includes a detailed list of cookies associated with Google advertising and measurement products) for more information. The Vimeo Cookie Policy does not currently disclose the normal durations of the cookies and similar technologies the Vimeo platform uses, but it appears that some may remain in your browser (or other user agent) for as long as your settings permit. To learn more about what information the Vimeo platform collects and how that information may be used, see the Vimeo Privacy Policy. The Vimeo Cookie Policy also provides information about how Vimeo users can control the use of third-party analytics and/or advertising cookies in connection with embedded Vimeo video players. (Vimeo and the Vimeo logos are trademarks of Vimeo.com, Inc., registered in the U.S. and other countries. Crazy Egg is a trademark of Crazy Egg, Inc. Optimizely is a registered trademark of Optimizely, Inc. in the United States, EU, and elsewhere. Google, AdSense, Google AdSense, Google Analytics, and other related marks and logos are trademarks of Google LLC.)

Administrative and Login Cookies

PayPal® Buttons

Cookies used:

PYPF, 01A1

How they are used:

The payment or donation buttons that may appear on portions of the administrative dashboard (which is not normally accessible except to logged-in administrative users) contain embedded content served by PayPal® services. Those buttons 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 identifiable 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.).)

Administrative and Login Cookies

Cookies used:

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 I 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 I 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.)


Browser Tests

As explained in the “Browser Tests” section of the Privacy Policy, each time you visit this website, the site may perform certain automated tests to determine the specific technical capabilities of your browser (or other user agent), allowing the website to adjust the presentation and functionality of the site appropriately. The site’s administrative login page (which is off-limits except to authorized administrative users) may perform similar tests, e.g., testing whether the user’s browser will allow the cookies required to log into the site’s administrative dashboard. The site may also show you specific messages or other content based on the results of such tests, e.g., displaying a warning notification that your current browser is incompatible with certain site features.

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.)

Privacy Preference Center

Accessibility Settings

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.

I 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.

wahFontColor, wahBgColor, a11y-desaturated, a11y-high-contrast, a11y-larger-fontsize

Password-Protected Posts

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.

wp_postpass_xx

Commenting

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.)

comment_author_xx, comment_author_email_xx, comment_author_url_xx

YouTube Videos

Embedded video players for content hosted on the YouTube video platform (which is owned by Google LLC) may set these third-party cookies and/or use similar technologies to store data in your browser (or other user agent) for purposes such as (without limitation) managing video settings (e.g., tailoring the playback to your connection speed), storing video preferences, providing certain functionality (e.g., allowing you to pause a video at a particular point), showing you advertisements, associating your video viewing and other activity with your Google account (if any), ensuring proper functioning of the service, preventing abuse, and/or compiling user analytics data. Such cookies and/or stored data items may be set by various domains (such as, though not necessarily limited to, youtube.com; youtube-nocookie.com; googlevideo.com; ytimg.com; google.com; accounts.google.com; www.googleadservices.com; and/or doubleclick.net, which is part of the DoubleClick advertising service, also owned by Google LLC). Not all the listed cookies and/or data items are necessarily set in all instances, and there may sometimes be others not listed above, particularly if you are logged into a Google account. Some persist for only a few minutes, or until you close your browser (or other user agent); others may remain in your browser (or other user agent) as long as your individual settings permit. To learn more about what information the YouTube platform and other Google services may collect through and/or in connection with embedded video players and how Google may use that information, see their "How Google uses information from sites or apps that use our services" page and the Google Privacy Policy. For additional information about how Google uses cookies and/or other technologies that may collect and/or process personal information, see the "Technologies" section of their Google Privacy & Terms site and the "Our advertising and measurement cookies" section of their Google Business Data Responsibility site, which includes a detailed list of cookies associated with Google advertising and measurement products. (Those pages do not currently discuss the storage of data in your browser (or other user agent) using technologies other than cookies, e.g., in web storage.) For more information about Google advertising, see the "Advertising" section of their Google Privacy & Terms site. (Google, DoubleClick, YouTube, and other related marks and logos are trademarks of Google LLC.)

VISITOR_INFO1_LIVE, VISITOR_INFO1_LIVE__k, VISITOR_INFO1_LIVE__default, YSC, YEC, _Secure-YEC, PREF, GED_PLAYLIST_ACTIVITY, CGIC, DV, CONSENT, SOCS, AEC, exchange_uid, id, pm_sess, pm_sess_NNN, aboutads_sessNNN, remote_sid, test_cookie, use_hitbox, _gac_gb_, __gads, _gcl_, _gcl_au, _gcl_aw, _gcl_dc, _gcl_gb, _gcl_gf, _gcl_ha, __gpi, __gpi_optout, __gsas, Conversion, 1P_JAR, ACLK_DATA, GPS, NID, ENID, ANID, AID, TAID, IDE, APIS, SAPISID, DSID, HSD, SID, HSID, SSID, SNID, SIDCC, FCCDCF, FCNEC, FLC, FPGCLAW, FPGCLDC, FPAU, GAPS, GLC, N_T, OTZ, PAIDCONTENT, RUL, TAID, UULE, LOGIN_INFO, 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

Vimeo Videos

These third-party cookies may be set in connection with embedded video players for content hosted on the Vimeo video platform, for purposes such as (without limitation) managing video settings, storing video preferences, providing certain functionality (e.g., allowing you to pause a video at a particular point), associating your video viewing and other activity with your Vimeo account (if you have one), showing you advertising, ensuring proper functioning of the service, preventing abuse, and/or compiling user analytics data. Cookies whose names begin with "_ceg" are associated with the Crazy Egg web analytics service (which is subject to the Crazy Egg Privacy Policy and Cookie Policy). Cookies whose names begin with "optimizely" are associated with the Optimizely digital experience platform (which is subject to the Optimizely Privacy Policy; the "Privacy" section of the Optimizely Trust Center provides additional information about Optimizely privacy practices, including a link to the Data Processing Agreement that applies to personal data the Optimizely services process on customers' behalf that may be subject to certain regional privacy and/or data protection laws, while their "Cookies and localStorage in the Optimizely snippet" help page provides additional technical information about the cookies and/or similar technologies used by that platform). Many of the other listed cookies are associated with the Google Analytics service, the Google AdSense advertising service, and/or other Google advertising and measurement products, which are subject to the Google Privacy Policy; see their "How Google uses information from sites or apps that use our services" page, the "Information for Visitors of Sites and Apps Using Google Analytics" section of the Google Analytics "Safeguarding your data" help page, the "Technologies" section of their Google Privacy & Terms site, and the "Our advertising and measurement cookies" section of the Google Business Data Responsibility site (which includes a detailed list of cookies associated with Google advertising and measurement products) for more information. The Vimeo Cookie Policy does not currently disclose the normal durations of the cookies and similar technologies the Vimeo platform uses, but it appears that some may remain in your browser (or other user agent) for as long as your settings permit. To learn more about what information the Vimeo platform collects and how that information may be used, see the Vimeo Privacy Policy. The Vimeo Cookie Policy also provides information about how Vimeo users can control the use of third-party analytics and/or advertising cookies in connection with embedded Vimeo video players. (Vimeo and the Vimeo logos are trademarks of Vimeo.com, Inc., registered in the U.S. and other countries. Crazy Egg is a trademark of Crazy Egg, Inc. Optimizely is a registered trademark of Optimizely, Inc. in the United States, EU, and elsewhere. Google, AdSense, Google AdSense, Google Analytics, and other related marks and logos are trademarks of Google LLC.)

_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, _ceg.s, _ceg.u, optimizelyBuckets, optimizelyEndUserId, optimizelySegments, _ga, _ga_, _gac_, _gaexp, _gaexp_rc, _gat_, _opt_awcid, _opt_awgid, _opt_awkid, _opt_awmid, _opt_utmc, _opt_expid, __utma, __utmb, __utmc, __utmt, __utmv, __utmz, _dc_gtm_, AMP_TOKEN, FPID, GA_OPT_OUT, adsense, adsenseReferralSourceId, adsenseReferralSubId, adsenseReferralUrl, adsenseReferralUrlQuery, S_adsense, Conversion, _gac_gb_, __gads, _gcl_, _gcl_au, _gcl_aw, _gcl_dc, _gcl_gb, _gcl_gf, _gcl_ha, __gpi, __gpi_optout, __gsas, id, pm_sess, pm_sess_NNN, aboutads_sessNNN, test_cookie, CONSENT, SOCS, GED_PLAYLIST_ACTIVITY, 1P_JAR, ACLK_DATA, GPS, NID, ENID, ANID, AID, TAID, IDE, APIS, SAPISID, DSID, HSD, SID, HSID, SSID, SNID, SIDCC, FCCDCF, FCNEC, FLC, FPGCLAW, FPGCLDC, FPAU, GAPS, GLC, N_T, OTZ, PAIDCONTENT, RUL, TAID, UULE

PayPal® Buttons

The payment or donation buttons that may appear on portions of the administrative dashboard (which is not normally accessible except to logged-in administrative users) contain embedded content served by PayPal® services. Those buttons 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 identifiable 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.).)

PYPF, 01A1