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 right is subject to certain 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 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.

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, or to exercise the other rights provided by the CCPA, such as the Right to Know, the Right to Access, and/or the Right to Delete your personal information, you or your authorized agent can submit a request using this California Privacy Request Form or one of the other methods listed 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 need not be physically present in California to exercise your CCPA rights provided that you have a current California residence. For more information about these rights, see the “California Privacy and Data Protection Rights” section of the Privacy Policy.)

California Privacy Request Form

 

Anti-Spam Test

Alternatively, you or your authorized agent may 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. If you are acting as an agent for 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. If you are making a request on behalf of your household (in which case all members 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 Know, the Right to Access, the Right to Delete, and/or the Right to Opt-Out), 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 rights provided by the CCPA are subject to certain exemptions, exceptions, and restrictions provided by the applicable statutes and/or associated regulations issued by California’s Office of the Attorney General. Applicable law and/or regulations also stipulate the maximum time allowed for acknowledging and/or responding to requests.

There is no charge for for making a request.

I may share information related to CCPA requests to the extent required and/or otherwise permitted by applicable law/regulations for administrative and/or compliance purposes; to respond to subpoenas or other court orders; 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, Right to Access, or Right to Delete requests, the current 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 at least two data points) or “a reasonably high degree of certainty” (based on at least three data points, including your signed declaration, under penalty of perjury, that you are either the person whose information is the subject of the request or are duly authorized to act on their behalf), depending on the specific type of request, the nature of the 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, I may not use that information for any other purpose and must delete it after processing your request (except as otherwise required for compliance with applicable record-keeping requirements). If the request pertains to a household rather than an individual consumer, I may be required to verify the identities of all household members to whom 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 information in connection with an access request. For example (but without limitation), if I possessed your Social Security Number, I could not provide you with the actual number I possessed.

Opt-out requests do not require these verification steps, although I may refuse requests if I have reasonable, documented, good faith belief that they are 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.) The cookie normally expires in about 10 days and is 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 by YouTube (which is now owned by Google, superseding the now-defunct Google Video hosting service) in connection with embedded videos, 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 (but 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). 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 cookies Google sets in connection with your Google account and/or advertising served through YouTube (which may include others not listed here) are persistent cookies that may remain in your browser for as long as your individual browser settings permit. See Google's "Types of Cookies Used by Google" page for more information about the functions of their various cookies. To learn more about how Google uses the information they collect, see the Google Privacy Policy. (YouTube, Google Videos, and DoubleClick are trademarks of Google LLC. Google is a registered trademark 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 by Vimeo in connection with embedded videos, 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 Google Analytics (which is subject to the Google Privacy Policy); the ones whose names begin with "_ceg" are associated with the Crazy Egg web analytics service (which is subject to the Crazy Egg Privacy Policy); the ones that begin with "optimizely" are associated with the Optimizely digital experience optimization service (which is subject to the Optimizely Privacy Policy); and the ones beginning with "adsense" or listed in all caps are associated with Google AdSense and/or other Google advertising services (which are also subject to the Google Privacy Policy). The Vimeo Cookie Policy does not currently disclose the normal durations of their cookies, but some are persistent cookies that may remain in your browser for as long as your individual browser settings permit; some Google Analytics cookies can persist for up to two years. For more information about how Vimeo uses the information they collect, see the Vimeo Privacy Policy. (Vimeo is a trademark of Vimeo, Inc. AdSense and Google Analytics are trademarks of Google LLC; Google is a registered trademark of Google LLC. Crazy Egg is a trademark of Crazy Egg, Inc. Optimizely is a trademark of Optimizely, Inc., registered in the United States, EU, and elsewhere.)

_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®. Those buttons may set the third-party cookies PYPF (via paypalobjects.com), 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 stores certain technical information about your device and browser, probably 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, PayPal sets 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 on what data PayPal collects and what they do with it, visit their Legal Agreements for PayPal Services page to review the PayPal Privacy Statement and Statement on Cookies and Tracking Technologies that apply in your location. (PayPal is a registered trademark of PayPal, Inc. All button icons, custom graphics, logos, page headers, and scripts related to the PayPal services are service marks, trademarks, and/or trade dress of PayPal or PayPal's licensors.)

PYPF, 01A1

Administrative and Login Cookies

These functionality cookies are used to manage user logins and other WordPress administrative functions, such as post editing. If you are not an administrative user, they shouldn'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 places the wordpress_test_cookie (a session cookie that tests whether your browser will allow the cookies needed to log in and expires when you close your browser) and the itsec-hb-login-xx cookie (which expires after about one hour and helps protect the site against "brute force" attempts to hack user passwords).

Logging in sets the wordpress_logged_in_xx, wordpress_sec_xx, and/or wordpress_xx cookies, which store your user login credentials to allow access to the administrative dashboard and other administrative functions; these cookies expire in about 15 days if you click "Remember Me" when logging in, but if you don't, they normally expire when you close your browser (or, failing that, within about two days). The wp-settings-UID cookies store a logged-in user's configuration settings, while the wp-settings-time-UID cookies store the time those configuration settings were set; these cookies normally expire after about one year. One or more wp-saving-post cookies may be placed 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, may be set by accessing the dashboard menu for the WP DoNotTrack plugin (if I currently have that plugin enabled); this cookie normally expires in about one year.

For all of these administrative and login cookies, the "xx" will be a cryptographic hash while "UID" will be the administrative user's user ID number in this website's WordPress database. (WordPress is a registered trademark of the WordPress Foundation.)

wordpress_test_cookie, itsec-hb-login-xx, 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
Contrast Mode (Note: This option sets cookies to save your settings)