Do Not Sell My Personal Information

Your Right to Opt-Out of Sale of Your Personal Information

Under the California Consumer Privacy Act of 2018 (CCPA), beginning January 1, 2020, California residents have the Right to Opt-Out of the sale of personal information about them or their household, such as (though not limited to) their name, postal or email address, IP address, and/or other personally identifying information.

This opt-out right is subject to certain restrictions and exemptions. For example, it does not apply to information that I share with certain third-party service providers so that they can perform business functions for me and/or on my behalf, or to de-identified or aggregated data.

While I believe I do not technically meet any of the applicability thresholds specified by this California law, I am committed to providing visitors with as many privacy choices as I reasonably can.

The laws of certain other U.S. states, such as Nevada (see the “Nevada Consumer Opt-Out Rights” section of the Privacy Policy), may provide residents of those states with similar rights with respect to the sale of their personal information. However, other states’ laws may differ significantly from California law in the types of information to which such opt-out rights apply, in what is considered a “sale” of personal information subject to such rights, and in the restrictions and exemptions that may apply. Requests to exercise your rights under the privacy and/or data protection laws of a U.S. state OTHER than California, or of a country outside the U.S., should be submitted via any of the methods described in the “Controller/Responsible Party, Questions, and How to Reach Me” section of the Privacy Policy.

How to Opt-Out or Exercise Your Other California Privacy Rights

If you are a California resident and would like to opt-out of the sale of your personal information, and/or to exercise any of the other privacy rights provided by California law, such as the Right to Know (sometimes described as the right to access) and/or the Right to Delete your personal information, you or your authorized agent can submit a request via the California Privacy Request Form or any of the other methods specified below. Once I have reviewed your submission, I will contact you to discuss the next steps involved in processing your request, which may require me to verify your identity (see the “Identity Verification Requirements” section below).

(You generally don’t need to be physically present in California to exercise your California privacy rights provided that you are a current California resident. For more information about these rights, see the “Your California Privacy Rights” section of the Privacy Policy.)

Requests to exercise your rights under the privacy and/or data protection laws of a U.S. state OTHER than California, or of a country outside the U.S., should be submitted via any of the methods described in the “Controller/Responsible Party, Questions, and How to Reach Me” section of the Privacy Policy.

California Privacy Request Form

 

Anti-Spam Test

If you cannot or prefer not to use the above California Privacy Request Form, you or your authorized agent should email me at admin (at) aaronseverson (dot) com or contact me via postal mail at the following address:

Aaron Severson
Attn: Privacy Requests
11100 National Bl. #3
Los Angeles, CA 90064

Mail or email requests should indicate:

  1. Who you are, and:
  2. Whether your request is:
    1. For yourself, or,
    2. On behalf of someone else (in which case you’ll also need to provide proof that that person has authorized you to act on their behalf, or that you have the right to do so for some other reason, such as if you are a parent or legal guardian acting on behalf of your minor child), or,
    3. On behalf of your household (in which case all members of the household may need to make the request jointly), and:
  3. What right or rights you wish to exercise (e.g., the Right to Opt-Out, the Right to Know, and/or the Right to Delete), and:
  4. The best way(s) to contact you so that I can respond to your request and take any steps that may be required to verify your identity (see the “Identity Verification Requirements” section below).

(Except as otherwise required by law, requests pertaining to children under 18 should be submitted by a parent, legal guardian, or other authorized adult representative.)

Keep in mind that, as with the Right to Opt-Out, the other privacy rights provided by California law are subject to certain exemptions, exceptions, and restrictions provided by the applicable statutes and/or the associated regulations. Applicable law and/or regulations may also stipulate the maximum time allowed for acknowledging and/or responding to requests.

There is no charge for for making a request.

The CCPA and its associated regulations impose strict limits on the use and/or disclosure of information related to privacy requests. However, I may share information related to such requests to the extent permitted — and/or required — by applicable law/regulations for administrative and/or compliance purposes; to fulfill legal obligations (e.g., to respond to a subpoena or other court order); and/or to publish de-identified and/or aggregated information about requests I receive, as described in the “Reports and Aggregated Statistics” section of the Privacy Policy (e.g., statistics on how many requests of a particular type I received in a given period).

(To learn more about what kinds of information I gather in connection with this website, please consult the Privacy Policy.)

Identity Verification Requirements

Please note that, in order to better safeguard your privacy and the privacy of others, I may be required to verify your identity before processing certain requests pertaining to your personal information. I may be unable to fulfill your request if I cannot verify your identity to the degree of certainty applicable law and/or regulations require.

For Right to Know and Right to Delete requests, the current CCPA regulations issued by California’s Office of the Attorney General require me to verify your identity to either “a reasonable degree of certainty” (based on matching at least two data points I have determined to be reliable for identity verification purposes) or “a reasonably high degree of certainty” (based on matching at least three data points I have determined to be reliable for identity verification purposes, together with your signed declaration, under penalty of perjury, that you are the consumer whose personal information is the subject of the request), depending on the specific nature of the request, the nature and sensitivity of the personal information involved, and the likelihood of harm in the event of unauthorized access or deletion. If I ask you to provide me with additional personal information I did not already possess in order to verify your identity, the regulations prohibit me from using that additional personal information for any other purpose; after processing your request, I am only permitted to retain such additional personal information to the extent necessary to comply with the CCPA regulations’ record-keeping requirements. For a request that pertains to a household rather than an individual consumer, I may be required to verify the identities of all household members to whose personal information the request pertains.

Even if I verify your identity to “a reasonably high degree of certainty,” the regulations prohibit me from disclosing certain types of extremely sensitive personal information in response to a request to know. For example (but without limitation), if I possessed your Social Security Number, I could not provide you with the actual number I possessed, only the fact that I possessed that information.

California opt-out requests do not require these verification steps, although I may refuse an opt-out request if I have a reasonable, documented, good faith belief that it is fraudulent. (The current regulations require me to respond to opt-out requests I believe are fraudulent and explain why I believe them to be fraudulent.)

Privacy Preference Center

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

gdpr, gdpr[allowed_cookies], gdpr&5Bprivacy_bar&5D, 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.

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

Age Verification

Viewing certain site content may require you to first verify your age by entering your date of birth. If your birth date indicates that you are 18 or older, the website places the age_gate cookie (whose value is "1," meaning "yes, passed") to allow you to access age-restricted content. The cookie remains active for up to 14 days if you click the "Remember me" check box when you enter your birth date; otherwise, the cookie normally expires when you close your browser. If the birth date you entered indicates that you are NOT 18 or older, the website may place the age_gate_failed cookie (whose value is also "1") to prevent you from trying again to access age-restricted content. (The website does not retain your birth date or your age. See the "Age Verification" section of the Privacy Policy for more information about how the age verification system works.)

age_gate, age_gate_failed

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

These third-party cookies may be set in connection with embedded video players for content hosted on the YouTube video platform (which is owned by Google LLC), for purposes such as (without limitation) managing video settings (such as tailoring the playback to your connection speed), storing video preferences, providing certain functionality such as allowing you to stop and restart a video without losing your place, showing you advertisements, associating your video viewing and other activity with your Google account (if any), ensuring proper functioning of the service, and/or compiling user analytics data. The cookies may be set by various domains, including (though not necessarily limited to) youtube.com, youtube-nocookie.com, googlevideo.com, ytimg.com, google.com, accounts.google.com, and/or doubleclick.net (which is part of the DoubleClick advertising service, also owned by Google LLC). Some are session cookies that expire when you close your browser; others may remain on your device as long as your browser settings permit. Some of the cookies that may be set in connection with your Google account and/or advertisements served through the YouTube platform (which may include other cookies not listed here) are persistent cookies that may remain in your browser for as long as your individual browser 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 that information may be used, see the "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 the "Google Privacy & Terms" pages. For more information about Google advertising, see the "Advertising" section of the "Google Privacy & Terms" pages, which also discusses the use of cookies by Google advertising services. (Google, DoubleClick, YouTube, and other related marks and logos are trademarks of Google LLC.)

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

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 (such as 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, and/or compiling user analytics data. The cookies whose names begin with "_ga" and "_ut" are associated with the Google Analytics service (see the "Information for Visitors of Sites and Apps Using Google Analytics" section of the Google Analytics "Safeguarding your data" help page, the "How Google Uses Information from Sites or Apps That Use Our Services" page, and the Google Privacy Policy for more information about how data gathered by this service may be used; the "Google Analytics Cookie Usage on Websites" page provides additional technical information about the cookies the analytics service may use). 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 the "Cookies and localStorage in the Optimizely snippet" help page provides additional technical information about the cookies and/or similar technologies used by that platform). Cookies whose names begin with "adsense" or that are listed in all caps are associated with the Google AdSense advertising service and/or other Google advertising services (which are also subject to the Google Privacy Policy; for more information about Google advertising services, see the "How Google Uses Information from Sites or Apps That Use Our Services" page and the "Advertising" section of the "Google Privacy & Terms" pages, which also discusses the use of cookies by Google advertising services). The Vimeo Cookie Policy does not currently disclose the normal durations of the cookies and similar technologies that platform uses, but it appears that some may persist for as long as your individual browser settings permit; some cookies set by the Google Analytics service can persist for up to two years. 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. Google, AdSense, Google AdSense, Google Analytics, and other related marks are trademarks of Google LLC. Crazy Egg is a trademark of Crazy Egg, Inc. Optimizely is a registered trademark of Optimizely, Inc.)

_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

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

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

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