About the Author
Novels: The Los Angeles Cycle
Short Stories

About the Author
Cookie Notice
Novels: The Los Angeles Cycle
Do Not Sell My Personal Information
Older Privacy Policy Revisions
Privacy Policy
Privacy Tools
Recent Entries
Terms of Use
Short Stories
- The Femme Fatale Who Failed to Be Fatal

my other writing

The E.P. Ingersoll Award

my other writing / Aaron Severson / October 14, 2012

I’m pleased to announce that my automotive website, Ate Up With Motor, has been named the winner of the 2012 E.P. Ingersoll Award for excellent in non-print media by the Society of Automotive Historians. For more information, see the Society’s website at https://autohistory.org/.

The E.P. Ingersoll Award Read More »

Administrative Pages

Terms of Use
- Reprint/Reuse Policy
- Financial Transactions Policy
Privacy Policy
Privacy Tools

Most Recent Policy Updates

For California Residents

Your California Privacy Rights
Information Collection and Sharing Notice
Do Not Sell My Personal Information

Except as otherwise indicated, all site content is copyright © Aaron Severson. This website is not intended for children and should not be accessed by anyone under 18.
(Terms of Use – Reprint/Reuse Policy – Financial Transactions Policy – Privacy Policy – Cookie Notice – Your California Privacy Rights – Do Not Sell My Personal Information)

This website and its embedded content providers may use cookies and/or similar technologies and collect personal information about site visitors as described in the Privacy Policy and Cookie Notice. To learn more about the specific cookies used and/or to fine-tune your available choices, click Privacy Preferences at the right. (If you need to review or change these settings after you accept, you can do so from the Privacy Tools page.) California residents also have the Right to Opt-Out of the sale of their personal information — see the Do Not Sell My Personal Information page.

Privacy Preference Center

Consent Management

Required

You agree to the Privacy Policy. (If you do not accept the Privacy Policy, you should not access or use this website.)

Privacy and Cookie Preferences

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

Cookies Used

Required

gdpr[allowed_cookies], gdpr[privacy_bar], gdpr[consent_types]

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.

Cookies Used

Required

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.

Cookies Used

Required

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

Cookies Used

Required

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

Cookies Used

Required

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

Cookies Used

Required

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

Cookies Used

Required

PYPF, 01A1

Administrative and Login Cookies

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

Cookies Used

Required

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

Change Font Size

Change Background Color (Note: This option sets cookies on your device to manage your color settings; see the Cookie Notice for details.)

Accessibility by WAH