Privacy Policy

This Privacy Policy explains what personal information we may gather through and/or in connection with the 6200 Productions website and how we use that information. Please read this policy before using the site. By using this website, you indicate your acceptance of the policy described below.

(If you are a California resident and would like to exercise your right to opt out of the sale of your personal information, please visit our Do Not Sell My Personal Information page. For more information about California privacy rights, jump to the “Your California Privacy Rights” section below.)

EFFECTIVE DATE: This version of the Privacy Policy is effective Wednesday, November 20, 2019. If this policy has changed since you last reviewed it, or if you received a notice indicating that the Privacy Policy has changed, you may want to jump directly to the “Recent Revisions” section at the bottom of this page, which summarizes recent modifications by date.

Please note that your use of any third-party websites or services, including ones linked from the 6200 Productions website or on which we may have accounts, is subject to the individual privacy policies and terms of use/terms of service, if any, of those sites or services.

Variations in text style (such as different font weights, sizes, or colors) are used throughout this Privacy Policy to improve readability, but have no legal significance or effect.

Who We Are

For the purposes of this Privacy Policy, the words “we,” “our,” and “us” shall be deemed to refer to Aaron Severson dba 6200 Productions, a U.S. citizen based in Los Angeles, California. We, along with our web host, DreamHost® (which also hosts the mail servers for our 6200productions.com email addresses — here’s DreamHost’s Privacy Policy), and many of the vendors and third-party service providers we use in connection with this website, are located in the United States and are subject to U.S. law, which may differ from the laws of your area. Click here to jump to our contact info.

License for This Policy

Portions of this Privacy Policy were adapted from the Automattic Inc. Privacy Policy under a Creative Commons Attribution-ShareAlike 4.0 International license. This policy (including our adaptation of the Automattic terms and our additions) is offered under the same license. If you elect to use or further adapt our version, please credit Automattic Inc. as well as us. We also strongly recommend that you note the effective date shown above and include that date in your attribution if it is reasonably practical to do so. (See the change log at the bottom of the Automattic policy linked above for their revision history; both the original and this document have been modified many times!)

Information We Collect

We may collect information about visitors to the 6200 Productions website in three ways: automatically through the website; if and when visitors supply information to us; and from other sources. Each of these three types of data collection, and our use of that information, will be further explained below.

Legal Bases for Collecting and Using Information

Our legal grounds for collecting and using your information are as follows:

  1. The use is necessary for compliance with a legal obligation (such as our need to maintain reasonable records of financial transactions and image usage rights); or
  2. The use is necessary to provide the functions of the website (such as comments and user feedback forms); or
  3. The use is necessary to fulfill a contractual obligation (such as complying with the terms of a Creative Commons or other license for the use of your content); or
  4. The use is necessary in order to protect your vital interests or those of another person; or
  5. We have a legitimate interest in using your information — for example, to safeguard the integrity of this website and its data, to troubleshoot technical problems, to better understand how (and how many) people access our content, and to appropriately respond to your inquiries regarding our work; or
  6. You have given us your consent.

Notice to Parents Regarding Children Under 18

The 6200 Productions website is not intended for and should not be accessed by children under 18. Unless otherwise required by law, if we receive any personally identifying information through this website that we know to be from a child under the age of 18 (e.g., an email message, Contact Form submission, or comment), it is our policy to promptly delete such information or, if complete deletion is not possible, to take whatever steps we reasonably can to de-identify or anonymize that information.

If you have questions, if you are a parent and believe that the 6200 Productions website may have collected personally identifying information about your minor child, or if you wish to exercise your right to remove or delete such information, please contact us via one of the methods shown under “Controllers, Questions, and How to Reach Us” below.

Information We Collect Automatically

Certificate Authority Service

To allow visitors (and us!) to connect to the site securely (via HTTPS rather than HTTP), this website uses domain validation (DV) certificates issued by Let’s Encrypt®, a certificate authority (CA) service of the nonprofit Internet Security Research Group™. These encryption certificates enable your browser to confirm that it has an SSL/TLS (Secure Sockets Layer/Transport Layer Security) connection to the correct website, an important security measure. (For a further explanation, see the Let’s Encrypt How It Works page.)

When you access this website, your web browser may check whether the 6200 Productions certificate is valid by briefly connecting to the servers of the Let’s Encrypt certificate repository to perform an Online Certificate Status Protocol (OCSP) check (sometimes called an OCSP request or an OCSP query &mdash: these terms are synonymous). This OCSP check provides the repository servers with your IP address and user agent information (which typically includes, among other things, what type/version of web browser or other software your computer/device is using to access online content, the operating system type/version in which that software is running (which frequently reveals what type of computer/device is being used), and sometimes certain software settings such as preferred language). Let’s Encrypt may log and use such data for operational, troubleshooting, and security purposes and/or in compiling de-indentified, aggregated statistics, as described in the Let’s Encrypt Privacy Policy.

Browser Tests

Each time you visit the 6200 Productions website, the site may perform certain automated tests (using tools such as, but not necessarily limited to, the Modernizr plugin for WordPress) to determine your web browser’s specific technical capabilities, allowing the website to adjust certain styles and site functions to be more compatible with your browser. The tests do not gather any personal information about you, and the browser information they gather is not retained beyond your current visit. If you’d like further technical information on Modernizr, please consult the Modernizr documentation. (Please note that we are not affiliated with the Modernizr development team in any way and offer this link purely for your convenience.)

Cookie Policy

This website uses cookies, which are small text files — strings of information — that a website stores on your computer or device and that your browser then provides to the website when you access that site. 6200 Productions uses cookies to record your privacy preferences, such as your acceptance of this Privacy Policy, and when you perform certain actions, such as saving your information when making a comment. Some accessibility features offered on this website (such as tools to let you adjust the appearance of the site and its content) may use cookies to save your settings/preferences. We may also use cookies to determine which content to show you (for example, whether to display banners intended for first-time visitors), and/or to check whether or not you have consented to Google Analytics tracking (see “Online Tracking” below). The login page, which is not normally accessible to visitors, also uses cookies to manage our logins and other administrative functions and help ensure that administrative areas of the website are not accessible to unauthorized visitors.

If you visit some portion of the website that contains embedded third-party content (see “Embedded Content” below), that content may also place cookies on your computer or device.

Cookies are specific to each device and web browser. Therefore, if you access this website from multiple devices (for example, from your home computer and also from your smartphone), or from different browsers on the same device, each device and each browser may store its own set of cookies.

Some of the cookies this website places on your computer or device are “session cookies” that automatically remove themselves when you close your current browser. Others are “persistent cookies” that remain on your device, but automatically expire and cease to function after a certain period of time, such as one year. A few, such as the Google Analytics opt-out cookie described in “Online Tracking” below, will remain active for as long as your browser settings permit. Some web browsers automatically delete any expired cookie while others don’t, but either way, expired cookies no longer work — your browser will no longer supply them to websites.

For more specific information about the cookies we may use, what purposes they serve, and how long they normally last, see the Cookie Notice page or 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.)

Keep in mind that your subsequent actions or choices on this website may set additional cookies or change the duration of the existing ones. For instance, saving your comment information where you hadn’t previously done so will place additional cookies, and changing or updating your privacy preferences (such as accepting changes to this policy) may effectively “reset the clock” on the cookies that store that information. Your individual browser settings may also affect how long cookies remain on your computer or device.

You can delete some or all of the saved cookies through your web browser. Most browsers also have settings to allow them to automatically delete all saved cookies whenever you close the browser. However, if you delete saved cookies and then return to the 6200 Productions website, the website may place new cookies on your device — for instance, to again record your privacy preferences. (Also, please keep in mind that if you use multiple devices or browsers, the deletion or expiration of cookies on one browser does not affect cookies on the others!)

You are free to block or remove any cookies set by 6200 Productions, either through your browser or using the Privacy Tools. However, please note that some site features may not function without cookies. For example, you may not be able to hide notification banners. Also, if you have previously saved privacy preferences for this website, such as opting out of analytics tracking, those preferences will be lost once you delete the cookie(s). (Again, please note that if you use multiple devices or browsers, deleting or blocking cookies on one browser does not affect cookies on the others!)

You can find more information about how cookies work and how you can manage or delete them on different browsers by visiting AboutCookies.org. (We are not affiliated with that site, which is run by the law firm Pinset Masons LLP, and offer this link purely for your convenience.)

Online Tracking

(Note: Portions of this section were adapted from language previously suggested and/or required by Google for users of their web analytics service.)

6200 Productions uses Google Analytics, a web analytics service provided by Google. (Google Analytics is a trademark of Google LLC.) The service uses cookies (specifically, first-party “tracking cookies”) and scripts to gather information about site visitors, such as (though not necessarily limited to) their Internet Protocol (IP) address; device type; operating system type/version; certain device settings; browser type and version; language preference; the referring site (if any); and the date, time, and length of each visit. Google Analytics can typically also identify a visitor’s Internet service provider (particularly with mobile devices) and/or, if the visitor is using a mobile device, the mobile device model/version.

The analytics service uses this data to generate reports and statistics on traffic and visitors to this website. The service also uses a process called “IP geolocation” to identify visitors’ geographical locations based on their IP addresses.

Please note that Google Analytics does not provide your IP address or other personal information to us except in the form of anonymous, aggregate statistics. For example, Google Analytics tells us what percentage of our visitors come from a particular country and what percentage use a particular type of browser, not what country a specific visitor comes from.

Google Analytics also compiles information and insights such as (without limitation) what pages or posts visitors most frequently land on; how often specific Google search keywords lead visitors to this website; which other websites refer visitors to this website via hyperlink(s); and how long the average visitor remains on the site. (These examples are just a sampling of the analytics results; the service offers a great variety of reports and insights, and regularly adds new ones.)

The reason we collect this type of aggregate, anonymous user information is to better understand how many visitors the website has and how they use the site (for example, to determine which articles are the most popular). We may use this aggregate data for the purpose of selling advertising on the site (for example, to inform potential advertisers how many unique visitors the site has in an average month), to help us identify and diagnose potential performance issues and technical problems (for example, to troubleshoot a technical issue that affects only one specific type of browser), and to otherwise improve the functionality of the site.

6200 Productions does not use this analytics service or the data it gathers to personally identify our visitors, nor do we link or associate such information with personally identifying or potentially personally identifying information. Furthermore, we have configured Google Analytics to partially anonymize the data it gathers by automatically omitting a portion of each tracked visitor’s IP address. We have NOT enabled the Google Analytics User-ID tracking features, and as of April 11, 2018, we have disabled the User Analysis metrics in Google Analytics reporting.

The data Google Analytics gathers is transmitted to and is stored and processed on Google servers located in the United States and elsewhere. Google may also subcontract some analytics data processing and related tasks to third parties (subprocessors), such as K. K. Teledirect Japan, who may be located in other regions; click here for a complete list of Google’s third-party subprocessors and their respective locations.

6200 Productions has not authorized Google to share Google Analytics data with other Google products or services, although Google may access, use, or transfer the data to third parties for subcontracted data processing and related tasks (such as support, troubleshooting, or service improvement) or for legal reasons. You can learn more about how Google uses the information collected by the Google Analytics service in their “Safeguarding your data: Information of Visitors of Sites and Apps Using Google Analytics” page and the “How Google Uses Information from Sites or Apps That Use Our Services” section of the Google Privacy Policy. You may also wish to review Google’s “Businesses and Data” pages (and in particular the page on restricted data processing), which provide additional information about how Google processes data from their business users.

We have also accepted the Google Ads Data Processing Terms, which apply to data from areas subject to European data protection rules and/or, beginning January 1, 2020, new California privacy laws; see the “Your Rights (GDPR and California Privacy Rights)” section below for more information about these privacy laws. Although we do not use Google Ads, these terms also apply to data from the Google Analytics service. (Google Ads is a trademark of Google LLC.)

If you consent to Google Analytics tracking and later decide you no longer wish to be tracked, you can click the “Disable Google Analytics Tracking” link on the Privacy Tools page or here: Disable Google Analytics Tracking. This will place a cookie on your device’s browser to prevent Google Analytics from tracking you on the 6200 Productions website. This is a “persistent” cookie that will normally remain on your device for as long as your browser settings permit. The opt-out cookie only works on the 6200 Productions website, not any other website using Google Analytics.

If you see a small black box in the upper right-hand corner of the screen (next to the accessibility button), hovering over it with your cursor should display a link reading “Reopen Analytics Banner.” Clicking this link should cause the banner to reappear, at which point you can click “Disable Tracking.”

Alternatively, you can use your browser to delete the 6200 Productions cookieconsent_status cookie (or all 6200productions.com cookies). This should cause the notification banner to reappear, at which point you can click “Disable Tracking.”

If you prefer, Google offers an add-on for many common web browsers that allows you to opt out of transmitting information to Google Analytics. You can find the add-on at this link: https://tools.google.com/dlpage/gaoptout. (The use of this add-on may be subject to any terms and conditions set by Google as well as Google’s Privacy Policy. We take no responsibility for those terms, or for the functionality of this or any other tools offered by Google, which are entirely outside our control — this link is provided purely as a convenience for our users and is not an endorsement.)

Server and Error Logs

Like most websites, 6200 Productions and our web host maintain various logs that may collect certain information about each computer or device that (as applicable, but without limitation) accesses the site and its content; uses certain site features, such as the Contact Form; is redirected from an outdated link to a current one; generates an error (such as attempting to access a nonexistent page or file); or attempts to interact with the site in any unusual or suspicious way (such as trying to access the site’s administrative area or run an unauthorized script). (These examples are a representative sampling, but not an exhaustive list; we may also use or add other logs not specified here, and not all logs are necessarily in use at any given time.)

The types of information these logs collect may include, but is not necessarily limited to, the IP address of the computer/device, which may reveal the device’s geographical location and in some cases also its Internet service provider; the user agent information (which typically includes, among other things, what type/version of web browser or other software the computer/device is using to access online content, the operating system type/version in which that software is running (which frequently reveals what type of computer/device is being used), and sometimes certain software settings such as preferred language); and in some cases the referring site, if any. These logs are part of the routine operation of the website and its host and are not in any way connected to or associated with the Google Analytics service or data described above.

We, and/or where applicable our web host, may use the information in these logs to troubleshoot technical problems such as broken or outdated internal links; to improve the functionality of the site; to block spam and hotlinking or other unauthorized use of 6200 Productions images or other content; and/or to prevent, resist, or recover from electronic attacks or intrusion attempts (which may involve our temporarily or permanently blocking certain IP addresses). We may also show you specific messages or other content based on this information, such as displaying a warning notification that your current browser is incompatible with some site features. We do not release the log data except as described in “Disclosure of Personally Identifying Information” below.

Security Scans

6200 Productions and our web host use a variety of security measures to help protect this website and its data. These measures may include (without limitation) monitoring the site’s operation for unusual or suspicious actions, automatically blocking suspicious actions or queries, and periodically scanning the site’s various files and components for unauthorized changes or potentially malicious code. If these security measures detect a possible intrusion attempt or the presence of suspected malware, the security system typically records the type of suspicious action and any associated IP address and user agent information. This information may be sent via email to the administrator in the form of an alert.

For example, if an unauthorized visitor attempts to access an administrator-only area of the website, we may receive an automated email alert warning us of the attempted access. That alert would typically include the unauthorized visitor’s IP address (which may reveal their geographical location and in some cases also their Internet service provider) and possibly their user agent information (which typically includes, among other things, what type/version of web browser or other software the computer/device was using to access online content, the operating system type/version in which that software was running (which frequently reveals what type of computer/device was being used), and sometimes certain software settings such as preferred language), allowing us to investigate and take appropriate action to prevent electronic attacks or intrusions.

As with the server and error logs, we may use this information to troubleshoot technical problems (such as a broken link accidentally sending legitimate users to non-public pages); to improve the functionality of the site; to prevent and/or resist electronic attacks or intrusion attempts (such as by blocking the IP address associated with the specific action); to recover from an actual attack or intrusion; and to ensure that legitimate users are not inadvertently blocked or locked out. We do not release such data except as described in “Disclosure of Personally Identifying Information” below.

Among the security measures we use is the Sucuri Security plugin, provided by Media Temple, Inc. d/b/a Sucuri, a subsidiary of Go Daddy Operating Company (Sucuri), which includes security activity auditing, notifications, and a remote scanning feature that can detect security vulnerabilities and some forms of malware by scanning the files and public areas of the website. (A complete list of the features of the plugin can be found in the “WordPress plugin & API Key” section of the Sucuri Security Terms of Service.) These scans and associated security audits may sometimes capture users’ personal data, such as (without limitation) IP addresses that perform certain actions such as accessing the administrator login page, or data published in comments. Data gathered through this service, which may be processed and/or stored by Sucuri as well as us, is subject to the Sucuri Security Privacy Policy and the Data Processing Addendum to their Terms of Service. As explained in the Sucuri Privacy Policy, their service complies with the EU-US Privacy Shield framework.

Some Sucuri components are also served via Cloudflare®; see the applicable section of “Embedded Content” below. However, this generally applies only to back-end administrative functions, not any publicly facing component.

Naturally, we also use a variety of security measures to protect our local and offline system(s), devices, and data against malware and other potential security threats, including (but not limited to) antivirus and anti-spyware monitoring and/or scanning.

Additionally, email messages sent to or from any of our 6200productions.com email addresses, and in some cases text messages we send or receive, may be automatically scanned for malware, spam, or other potential security issues by us, our web host, and/or our our mobile carrier — currently T-Mobile® (T-Mobile USA, Inc.; here is the T-Mobile privacy statement). For example, incoming email messages may be filtered or flagged if they appear to be spam, contain potentially malicious code, or were sent from email addresses or domains associated with spam or malware. (T-Mobile may also sometimes flag the phone numbers of certain incoming voice calls with warnings such as “scam likely.”)

As is customary with most modern electronic security and spam prevention systems, these security scans may include submitting messages, file attachments, their respective metadata, and/or other relevant data to third-party services such as (without limitation) cloud-based malware-detection services and/or web-based malware/spam databases.

Reports and Aggregated Statistics

From time to time, 6200 Productions may compile or release aggregated, non-personally identifying information about users of the website. For example, we may publish a report on trends in the usage of the website such as total page views, the average number of unique visitors per month, the most popular pages on the site, or the average time visitors spend on the site. We may display this information publicly or provide it to others (including potential advertisers). However, such reports will not contain any personally identifying information on 6200 Productions visitors. 6200 Productions does not disclose personally identifying information other than as described in “Disclosure of Personally Identifying Information” below.

Embedded Content

Certain content on 6200 Productions, such as fonts, scripts, images, and videos, may be hosted on and served by third parties, such as content delivery networks (CDNs) or video hosting services. This “embedded content” may place cookies on your computer or device, incorporate so-called “tracking pixels” or “pixel tags” (small image files that allow the hosting site to track when a webpage containing that image is loaded), and/or use other mechanisms that enable the third-party site to gather information about you. For example, an embedded video player may read your Internet Protocol (IP) address to determine if you are permitted to view a particular video in your country or region.

In general, if you access a portion of this website that contains embedded content, the third party that serves that content can gather information about you in the same manner as if you accessed the third-party provider’s website(s) or service(s) directly. Not all embedded content providers use cookies, but even the ones that don’t will typically gather certain information about any computer or device that loads and/or interacts with the embedded content.

The information third-party embedded content providers gather may include, but is not necessarily limited to, your device’s IP address, your geographical location and Internet service provider (both determined based on the IP address), and your user agent information (which typically includes, among other things, what type/version of web browser or other software you are using to access online content, the operating system type/version in which that software is running (which frequently reveals what type of computer/device you are using). In some cases, the third-party provider may also be able to detect other information about your browser, such as, again without limitation, whether or not you have certain cookies on your browser/device (for example, to determine whether you are separately logged into that third-party provider’s website(s) or service(s)); whether your browser is using certain add-ons, such as ad blockers; and/or other browser settings and configuration details (such as preferred language and/or time zone). Such information is collected and processed by the applicable third-party provider’s systems, not by 6200 Productions.

Since embedded content on this website is served through secure (HTTPS) connections, your browser may also contact the embedded content provider’s certificate authority to check the validity of their encryption certificate. (The “Certificate Authority Service” section above describes how these certificate checks work, although embedded content providers may use different certificate authorities than the one used by the 6200 Productions website.)

You should be aware that third-party embedded content providers can sometimes recognize or identify you based on your specific combination of browser settings and other information, even if none of those details are personally identifying by themselves — a technique called “browser fingerprinting.” The Electronic Frontier Foundation (EFF) has created a website called Panopticlick offering more information about this complicated subject, including a tool that lets you test what “fingerprints” your browser may have. (We are not affiliated in any way with the EFF and offer this link purely for your convenience.)

In some cases, you may be able to hide or disable certain types of embedded content on this website (for example, by using the Privacy Tools or other options we may provide, or through your web browser). Disabling embedded content will prevent that content from functioning, but may also prevent it from gathering information about you at least as long as the content remains disabled. Please note that this does not remove any data the embedded content previously gathered about you or any cookies it may have placed on your device. If you re-enable the embedded content (such as by deleting the cookies in which you saved your privacy settings), or if you visit the website from a different device or browser on which that content is not disabled, the embedded content provider may again be able to gather information about you.

Third-party embedded content on the 6200 Productions website may include, but is not limited to:

  • Fonts from the Google Fonts API and/or scripts from the Google Hosted Libraries API, which are sets of resources hosted on and served by content distribution networks (i.e., remote servers and data centers) operated by Google and/or its subprocessors, which may be located in the United States or elsewhere. The Google Fonts service does not place cookies on your computer, but may record certain information about your computer or device, including your IP address and user agent information, when you visit a page that uses one or more of those fonts. The service may also store (cache) certain font data and stylesheet requests in your browser for faster loading. For more information, visit the privacy section of the Google Fonts FAQ. The Google Hosted Libraries service may set cookies in addition to logging certain information about your computer or device, including your IP address and user agent information. That service may also store (cache) one or more scripts and/or associated data in your browser for faster loading. For more information, see the “What does using the Google Hosted Libraries mean for the privacy of my users?” section of the Google Hosted Libraries Terms of Service. For both of these services (and other Google services we may periodically offer, such as embedded maps served by Google Maps), you can also review the “How Google Uses Information from Sites or Apps That Use Our Services” section of the Google Privacy Policy to learn more about what information Google collects and how they use it. Click here for a complete list of Google’s third-party data subprocessors and their respective locations. (Google Fonts, Google Hosted Libraries, and Google Maps are trademarks of Google LLC.)
  • Fonts, styles, scripts, or icons served by BootstrapCDN, a service of StackPath (formerly MaxCDN) in the United States. Each time you access a portion of the site that includes such elements, BootstrapCDN records certain information about your computer or device, including the IP address and user agent information. BootstrapCDN may use this data for security, troubleshooting, and/or service improvement purposes. For more information, see the BootstrapCDN Privacy Policy and StackPath’s GDPR page.
  • Certain scripts or functions served by the content distribution network Cloudflare®. Cloudflare may collect visitors’ IP address, user agent information, and security-related data. See their GDPR page and Privacy Policy for more information.
  • Videos (either posted by us or displayed by certain plugins may display on portions of the administrative dashboard, which is not normally visible or accessible to site visitors) hosted by YouTube, which is now owned by Google. The embedded video player may place cookies on your device as well as recording your IP address and user agent information (which YouTube may use to, among other things, determine if you are allowed to view a specific video in your location) and in some cases checking whether you are currently logged into a Google account so that videos you watch through the player may be associated with that account and any relevant account settings (such as advertising preferences) may be applied. Visit the “How Google Uses Information from Sites or Apps That Use Our Services” section of the Google Privacy Policy to learn more about what information Google collects and how they use it. Google’s “Businesses and Data” pages also include additional information about what data they may share with YouTube content creators/publishers.
  • Videos (either posted by us or displayed by certain plugins may display on portions of the administrative dashboard, which is not normally visible or accessible to site visitors) served by Vimeo. The embedded video player may place cookies on your device as well as recording your IP address and user agent information (which Vimeo may use to, among other things, determine if you are allowed to view a specific video in your location) and in some cases checking whether you are currently logged into a Vimeo account so that videos you watch through the player may be associated with that account and any relevant account settings may be applied. Visit the Vimeo Privacy Policy to learn more about what information Vimeo collects and how they use it.
  • The payment or donation buttons that some plugins place on the administrative dashboard — not normally accessible to site visitors — which contain content served by PayPal® that may be used to collect and track data about users who access any portion of the site containing that button. It may also place cookies on your device. For more information on what data PayPal collects and what they do with it, visit their Legal Agreements page to review the PayPal Privacy Policy and Statements on Cookies and Tracking Technologies that apply in your location. (Please note that the terms may different depending on where you are.)
  • Certain back-end (i.e., administrative dashboard) features — which are not normally visible or accessible to site visitors other than us as the administrator — served by the SEO firm Yoast BV, which provides one or more plugins we use on the site. See the Yoast Privacy Policy and their “Yoast and your privacy (GDPR)” page for more information. The Yoast SEO plugin incorporates some search tools provided by Algolia to allow administrative users to search the Yoast knowledge base; the Yoast development team says this search functionality does not gather or transmit users’ personal data.
  • Blog feeds placed by certain plugins on portions of the administrative dashboard (which is not normally visible or accessible to site visitors) that are served by FeedBurner, an RSS (Really Simple Syndication) service now owned by Google. (FeedBurner is a trademark of Google LLC.) Please review the “How Google Uses Information from Sites or Apps That Use Our Services” section of the Google Privacy Policy to learn more about what information Google collects and how they use it. Please note that accessing areas of the dashboard containing these blog feeds may also place cookies on your device. These cookies are used for bookmarking purposes, allowing you to return to the same point in the feed where you previous left off. Again, these cookies and this type of data collection normally affect only administrative users, not site visitors.
  • Administrative dashboard menus that may load icons or other images from Gravatar via secure.gravatar.com. Although we have disabled support for user avatars, some administrative dashboard menus may use them, and the loading of those images may allow Gravatar to record a user’s IP address, user agent information, and in some cases their hashed email address, which the Gravatar service uses to check for a current Gravatar or WordPress.com account. (We believe we have limited this information-gathering to backend administrative pages not normally accessible to site visitors and we are endeavoring to remove it there as well.) Gravatar — like WordPress.com, with which it’s now apparently being integrated — is a service of Automattic Inc. and is subject to their Privacy Policy and the same Terms of Service as WordPress.com.
  • Portions of the administrative dashboard (which is not normally accessible to site visitors) that periodically communicate with WordPress.org and/or other domains owned by WordPress, such as s.w.org, ps.w.org, and ts.w.org, to check for updates, announcements, warnings, or other WordPress-related messages; to install, remove, or update plugins, themes, or other add-ons available through WordPress.org; and/or to serve certain images, scripts, and other elements on the administrative back-end. While this communication primarily involves WordPress-specific information (such as the current version numbers of the WordPress installation and any installed plugins and themes), WordPress may also collect the IP addresses and user agent information of users who access the site’s administrative dashboard. For more information on how WordPress.org uses the information they gather, please consult the WordPress Privacy Policy. (Again, this data collection normally only affects us as the administrator, not our visitors.)

From time to time, we may post embedded content hosted and served by other third-party websites or services not listed above — for example, an embedded player showing an externally hosted video or audio file, or an embedded map provided by some external mapping service. To learn more about what user information such third-party websites gather and how they use it, click the links on the applicable player or display window to go to that hosting site and review their privacy policy and associated terms and conditions.

6200 Productions does not receive or have access to user data gathered through embedded content hosted by third parties, nor do we have any control over their use of this data.

Information You Provide to Us

Visitors may choose to interact with the 6200 Productions website in ways that require the 6200 Productions website to gather personally identifying information: for example, posting a comment or submitting an inquiry via the Contact Form. The amount and type of information that the site gathers depends on the nature of the interaction. In each case, 6200 Productions collects such information only insofar as is necessary or appropriate to fulfill the purpose of the visitor’s interaction with this website.

Visitors can always refuse to supply personally identifying information, with the caveat that doing so may prevent them from engaging in certain website-related activities (such as commenting or using the Contact Form).

Consents and Agreements

When you click “Accept” on the privacy banner(s) and/or use certain site functions, the website may automatically log your acceptance of this Privacy Policy and/or, where applicable, other applicable legal terms such as the Terms of Use and/or your consent to our gathering certain other types of personal information. Some consent-related information may also be saved in cookies placed on your computer or device (see “Cookie Policy” above).

We may use this information to record and manage your saved consents and permissions (and as applicable your consent to changes in terms or policies you previously accepted); to show or hide certain messages and/or site content (such as notification banners or content that requires your prior consent to specific terms); to enable or disable specific site functions (such as the Google Analytics service described in “Online Tracking” above); for troubleshooting purposes and/or to otherwise improve or enhance the functionality of this website; to insure our compliance with applicable legal requirements; in the resolution of site-related disputes; and/or as otherwise described in the applicable sections below.

We may disclose this saved consent information as described in “Disclosure of Personally Identifying Information” below.

Comments

If you post a comment on 6200 Productions, this website will record the name or pseudonym, email address, and website/URL (if any) you provide along with your Internet Protocol (IP) address (which may reveal your geographical location and in some cases also your Internet service provider) and your user agent information (which typically includes, among other things, what type/version of web browser or other software you are using to access online content, the operating system type/version in which that software is running (which frequently reveals what type of computer/device you are using), and sometimes certain software settings such as preferred language). A copy of your comment, including your name/pseudonym, email address, website/URL, and in some cases your IP address, will then be automatically emailed to the site administrator. Copies of your comment, including the name/pseudonym and in some cases the website/URL (if any) you entered, may also be emailed to other users who have requested email notifications of replies or follow-up comments.

This website may perform certain automated tests on any submitted comments in order to filter out spam, malware, and/or comments left by automated bots. For example (but without limitation), if your IP address was previously used to spam this website; if your IP address and/or user agent appear on ban lists/blacklists supplied by our security and/or anti-spam plugins; if your comment contains hyperlinks, common spam keywords (such as the trade names of certain well-known prescription pharmaceuticals), or suspicious code; or if you posted the comment using an automated script rather than the normal comment form, your comment may be flagged as spam or automatically deleted. Also, if your comment contains HTML/PHP code (including hyperlinks), emojis, and/or special characters, they may be removed. This automatic filtering is in addition to human moderation of submitted comments; we routinely delete comments if they appear to be spam or contain suspicious code.

As noted in “Security Scans” above, the administrator notification emails we receive when you submit a comment may also be automatically scanned for malware, spam, or other potential security issues by us, our web host, and/or our mobile carrier. (This doesn’t affect the comments on the website, but may affect whether we receive notifications about them.)

By submitting a comment, we will assume that you are expressly authorizing us to publish and use the contents of that comment as described in the Terms of Use. Naturally, this means that when your comment is published, the name/pseudonym you provide and any personal information you include in your comment will become publicly visible. (Note also that if the site’s “Recent Comments” widgets are enabled, your name/pseudonym and a link to your comment may be visible on the home page and other areas of the website as well as the specific post or page you commented on. The contents of published comments may also appear in search results of the website’s search function.) Once your comment becomes public, we cannot control and take no responsibility for what third parties may do with any personal information you included in it!

If you include a valid email address with your comment, we may respond via email in addition to or instead of publishing the comment on the 6200 Productions website, particularly if your comment includes a question or offer of assistance or if we have questions about any pertinent details — for example, if you have submitted two very similar comments, we might email you to ask which one you want us to publish.

As noted in “Cookie Policy” above, when you submit a comment, you may have the option to save your name/email/website for use in future comments. Doing so places a set of cookies on your device to store that information; these cookies are browser-specific (that is, they work only in the web browser in which you set them) and normally remain on your device for a little less than one year unless otherwise deleted. These cookies are not placed at all unless you click the appropriate box when submitting a comment and you are free to delete them at any time through your web browser.

When you submit a comment, you may have the option to request email notifications each time a reply and/or follow-up comment is posted. If you have previously requested such notifications and wish to stop receiving them, please leave another comment, email us at admin (at) 6200productions (dot) com, or send us a message via the Contact Form asking us to disable the notifications or remove that comment.

Otherwise, 6200 Productions may record and use personal information in and associated with your comment (including, without limitation, the IP address, email address, and user agent information) publish and/or respond to your comment; better understand your comment and its context (which may involve seeking additional information from third-party sources, as noted in “Information We Receive from Other Sources” below); verify your identity and confirm that you are a human being and not a “bot” or automated system; secure the website and our accounts, systems, and devices against spam, fraud, abuse, or electronic attacks (for example, by blocking email or IP addresses associated with previous electronic attacks or spam); troubleshoot technical problems and improve the functionality of the site; help ensure that we correctly spell your name (for example, by adding your first name, last name, company name, and/or domain name to our spell-checking dictionaries); record your acceptance of this Privacy Policy, the Terms of Use, and other applicable legal terms; automatically and/or manually index the contents of your comment to control how (or whether) it appears and/or can be found using the website’s search function and other internal indexing tools; send email notifications to you and/or other users who have requested notifications of replies/follow-up comments; and/or as otherwise described in “Disclosure of Personally Identifying Information” below.

If you would like to edit or remove any of your published comments, please let us know by leaving another comment, emailing us at admin (at) 6200productions (dot) com, or sending us a message via the Contact Form, specifying the comment(s) in question and explaining what you want us to do with them. (Please note that we may reply via email to clarify or confirm your request before making the change or deletion, especially if we aren’t sure exactly what you want us to do.)

Please note that if a comment is deleted from the website, archival copies of the original comment and its associated information may be retained in our records or in backups or archives created by us or our web host. However, once the comment is marked as deleted, we will not publish or otherwise release any associated personal information except as described in “Disclosure of Personally Identifying Information” below. Again, please be aware that if a previously published comment is deleted, any information in the comment may already have been accessed or used by third parties during the time the comment was publicly visible, which is beyond our control.

Contact Form

If you contact us via the Contact Form, or send us a Privacy Request Form from the Do Not Sell My Personal Information page, this website will record any data you enter into the form (including your name and email address) and send it via email to the site administrator. The website will automatically send a copy of your message to the email you provided for your records.

In addition to the data you enter into the form, the 6200 Productions website may also record your Internet Protocol (IP) address (which may reveal your geographical location and in some cases also your Internet service provider), your user agent information (which typically includes, among other things, what type/version of web browser or other software you are using to access online content, the operating system type/version in which that software is running (which frequently reveals what type of computer/device you are using), and sometimes certain software settings such as preferred language), and the date and time of your submission.

This website may perform certain automated tests on form submissions in order to filter out spam, malware, and/or submissions made by automated bots. For example (but without limitation), if your IP address was previously used to spam this website; if your IP address and/or user agent appear on ban lists/blacklists supplied by our security and/or anti-spam plugins; if your submission contains hyperlinks, common spam keywords (such as the trade names of certain well-known prescription pharmaceuticals), or suspicious code; if you submit the form using an automated script; if you incorrectly answer a captcha or math challenge; and/or if you fill in certain “honeypot” fields not intended to be completed by human users, your submission may be flagged as spam or automatically deleted. Also, if your form submission contains HTML/PHP code, emojis, and/or special characters, they may be removed. This automatic filtering is in addition to human moderation of form submissions; we routinely delete submissions that appear to be spam or contain malicious code.

As noted in “Security Scans” above, the administrator notification email we receive when you submit a Contact Form may also be automatically scanned for malware, spam, or other potential security issues by us, our web host, and/or our mobile carrier.

If your message includes a question about our business, a correction, or a request for technical support, we may record that comment offline for our internal reference and records. We may also elect to publish your inquiry or excerpts of it on the 6200 Productions website in order to help us respond to your questions or comments or support other users with similar concerns. However, other than the name or pseudonym you supply, such publication will not include your email address, mailing address, IP address, or other associated personal information unless you specifically ask us to to so or as described in “Disclosure of Personally Identifying Information” below.

Otherwise, 6200 Productions may record and use personal information in and associated with your submission to respond to your inquiry; better understand your message/inquiry and its context (which may involve seeking additional information from third-party sources, as noted in “Information We Receive from Other Sources” below); verify your identity and confirm that you are a human being and not a “bot” or automated system; secure the website and our accounts, systems, and devices against spam, fraud, abuse, or electronic attacks (for example, by blocking email or IP addresses associated with previous electronic attacks or spam); troubleshoot technical problems and improve the functionality of the site; help ensure that we correctly spell your name (for example, by adding your first name, last name, company name, and/or domain name to our spell-checking dictionaries); record your acceptance of this Privacy Policy, the Terms of Use, and other applicable legal terms; and/or as otherwise described in “Disclosure of Personally Identifying Information” below.

Other Information You Provide to Us

In certain cases, you may provide us with personal information through or in connection with this website in ways not specifically mentioned above. For example (but without limitation), if you send us an inquiry about this Privacy Policy via postal mail, it will likely include your mailing address as well as any information in your inquiry itself; if for some reason you visit our home and connect your mobile device to our personal wireless network (which is not available to the general public), our wireless router may log certain information about your device and/or its Internet connections. (These are just a few hypothetical possibilities.)

Our use of personal information you provide us in such ways will depend on the nature of the information and the context in which we received it, although in general, we only disclose such information as described in “Disclosure of Personally Identifying Information” below.

Information We Receive from Other Sources

From time to time, we may receive information about site visitors from third-party sources.

For example, if you send us a message about the 6200 Productions website via one of the proprietor’s social media accounts, that social media service may automatically show us your profile picture and other publicly visible profile information along with your message. Similarly, if you make a payment to 6200 Productions (such as purchasing an ad on this website), we may receive a transaction report from the applicable payment processor that provides additional information about you, such as your mailing address. We might also receive information about you from other site visitors or from our clients (for example, in the form of a referral).

Some of the security measures we use, such as security and/or anti-spam software and plugins, may supply us with ban lists/blacklists of information such as IP addresses, email addresses/domains, and/or user agents associated with spam, malware, or intrusion attempts. We may also obtain similar information or lists from other external sources such as (without limitation) HackRepair.com, the MVPS HOSTS file, Perishable Press, The Spamhaus Project, via the Mozilla Firefox browser, and/or Safer-Networking Ltd.‘s Spybot® software. We may use this information to help prevent spam and/or safeguard this website, its data, and/or our system and devices, such as (without limitation) by selectively blocking access to certain site features or the site as a whole, filtering incoming email, and/or otherwise blocking access to our system and/or devices.

We may sometimes perform WHOIS or similar lookups on visitors’ IP addresses and/or domains, especially if those IP addresses have been used for unusual activity, abuse, and/or spam on this website. Such lookups may enable us to determine information such as (though not limited to) the owner of a particular domain registration or the geographic location associated with a particular IP address. Our firewalls and/or other security applications/services may provide us with similar information about any online servers or resources to which our devices connect or try to connect.

We may also obtain other publicly available information about individual site visitors. For example (but without limitation), if you send us a message via the Contact Form, we might look up your name in a search engine or consult your website to better understand who you are and the nature and context of your inquiry. If someone calls us from an unfamiliar telephone number, we might look up that phone number using a search engine and/or reverse-lookup directories.

Also, if we use an image or other content you have offered under a Creative Commons or similar license, we will customarily gather publicly available information about you (such as whatever creator name and details were listed on the hosting service, archive, or repository from which we obtained the content) for the purpose of properly attributing that content and otherwise complying with the applicable license terms.

Whenever we install software/apps, services, themes, and/or add-ons to use in our management of this website, site-related data, and/or our other work — particularly software/apps/services/themes/add-ons we use under open source licenses — the installation files (and/or the website or other source from which we obtained them) may provide us with personal information about the developer/development team (e.g., names, contact information, digital signatures), which we may use for security purposes, to ensure our license compliance, and/or if we have support questions and/or comments. (Software licenses typically prohibit redacting or altering any attribution information.)

(Please note that the above scenarios are just some representative examples, not an exhaustive list.)

Our use of information we gather from these or other sources will depend on the nature of the information and the context in which we received it, although we only disclose such information as described in “Disclosure of Personally Identifying Information” below.

Disclosure of Personally Identifying Information

We may release or disclose personal information we gather through and/or in connection with this website:

  • To publish your submitted comments, as described in “Comments” above. As explained in that section, this may include emailing copies of your comment to other users who have requested email notifications of replies/follow-up comments.
  • As part of a public response to an inquiry or support request, as described above.
  • To appropriately credit you for the use of your content or intellectual property (such as photographs, fonts, or themes/plugins) — particularly where such credit is required by the applicable license terms. This may include adding your copyright and license information to the applicable filename and/or metadata to ensure that the attribution is clear. Please note that if your content includes personal information (for instance, if you’ve published a photo under a Creative Commons license and the photo shows your address or includes your GPS coordinates in the metadata), the version of the content that appears on this website may retain that information. If you want to modify or remove that information, please contact us!
  • Where that information is or was already publicly available (such as — without limitation — information that’s available on your website; that you’ve included in your published memoirs, books, articles, or other published works, or in public posts or public comments you’ve made on this or other websites; that appears in published interviews or in books, articles, or other works about you; and/or that is otherwise part of the public record, such as court records or transcripts of public hearings).
  • To our independent contractors and/or employees (if any) that need to know the information in order to perform services for us or on our behalf (such as, without limitation, accounting, tax preparation, legal services, translation, transcription, technical troubleshooting, website development/improvement, or malware recovery/removal) and that have agreed to follow this Privacy Policy (or that have their own, comparably strict (or stricter) confidentiality policies) regarding any personal information that we share with them. Such contractors and/or employees may be located outside your home country and/or the European Economic Area; by using this website, you consent to our transfer of such information to them.
  • To our third-party vendors and/or service providers that need to know that information in order to provide services available on this website, support our business operations, or otherwise perform services for us or on our behalf. (This may include, but is not limited to, services, software, apps, and/or electronic devices we may use that could gather site-related personal information through telemetry and/or other integrated information-gathering and/or surveillance features, some of which cannot be disabled without simply ceasing to use that service, software, app, or device.) Examples of such third-party vendors/service providers may include (as applicable, but without limitation) Microsoft® (which provides some of the software, apps, tools, and services we use — including, but not limited to, the operating systems for some of our devices — and gathers certain information about such use as described in the Microsoft Privacy Statement); our Internet service provider, Spectrum Internet® (formerly Time Warner Cable®) (which processes and thus has information about much of our online activity); our mobile carrier, T-Mobile® (which provides our mobile voice, text, and data plan and processes certain emails sent to and from our phone(s), and thus has information about voice calls, texts, and online activity made, received, or otherwise conducted on our mobile device(s)); our web host, DreamHost® (which also hosts the mail servers for our associated email addresses); the Let’s Encrypt® SSL/TLS certificate authority service described in the “Certificate Authority Service” section above (which is subject to the Let’s Encrypt Privacy Policy) and/or other certificate authorities we may use or access; TCL Communication Limited (a.k.a. TCT), the manufacturer of our BlackBerry® KEY² LE smartphone and its associated suite of BlackBerry apps and services, which may gather information about the use of that device and/or its apps and services as described in the BlackBerry Mobile Privacy Policy; ASUS (ASUSTeK Computer Inc.) and/or Netgear Inc. (the manufacturers of our wireless routers and their associated software/services); Cloudflare® and APNIC (whose recursive domain name system (DNS) resolver services Cloudflare 1.1.1.1, the 1.1.1.1 App (and/or its associated WARP mobile security/encryption service) (which are subject to the Cloudflare Privacy Policy), and/or Cloudflare Resolver for Firefox® (which has its own privacy policy) we may use on some or all of our devices and/or browsers); Avast Software s.r.o and/or their subsidiary Piriform (CCleaner®) (whose security tools we may use on some or all of our systems and devices); Safer-Networking Ltd. (whose Spybot® security and privacy software/tools we may use on some or all of our systems and devices); Bitdefender® (whose Bitdefender Mobile Security app and associated services we may use on some of our devices); Malwarebytes (whose security tools we may use on some or all of our systems and devices); Internet firewall applications/services, such as (though not limited to) the NetGuard mobile firewall and Internet traffic monitor (you can read the NetGuard privacy statement here) and/or TinyWall; the Guardian Project, through our use of their Orbot app and Tor Browser apps (which connect to the Tor® network developed by The Tor Project, Inc.), which is subject to the project’s Data Usage and Protection Policies; Mozilla Corporation (which may gather certain information about our use of their Firefox®, Firefox Focus, and/or Fennec F-Droid web browsers as described in the Mozilla Privacy Policy; the Phishing and Malware Protection features of these browsers may also use the Google Safe Browsing service, which is subject to the Google Privacy Policy — Google Safe Browsing is a trademark of Google LLC); WordPress.org (which, as explained in “Embedded Content” above, provides the content management system in which this website runs and may gather certain information about users who access the site’s administrative dashboard in the course of managing the site and its various plugins, themes, and add-ons); Sucuri (which provides the Sucuri Security plugin described in the “Security Scans” section above); Google (which provides the Google Analytics, Google Fonts, Google Hosted Libraries, and Google Safe Browsing services described above; the Gmail webmail service (Gmail is a trademark of Google LLC); Google Play and its related services (Google Play is a trademark of Google LLC); and other services and/or tools we may use and/or offer, and which also owns YouTube, as noted in “Embedded Content” above); Adobe® (which provides some of the apps, software, and other services or tools we may use and/or offer and may collect related and/or associated data in accordance with their Privacy Policy); CompanionLink Software, Inc. and their associated subprocessors (through our use of their CompanionLink®, DejaOffice®, and/or DejaDesktop products/services) — see also the CompanionLink Data Processing Agreement, which applies to data that may be subject to European Union data protection laws; the Open Camera open-source mobile app; the OpenKeychain open-source mobile encryption app and/or other encryption software/services we may use; Artifex Software, Inc. (which may gather certain information about our use of their SmartOffice® mobile app as described in their Privacy Policy); DuckDuckGo and/or StartPage.com (the search engines we most commonly use); Hidden Reflex Inc. (through our use of their Epic Privacy Browser, integrated proxy/VPN service, and associated Epic Search Engine (which submits anonymized queries to the Yandex search engine), which we may use on some or all of our systems and devices); libraries, archives, and/or databases, public or otherwise (through our use of their computers, catalogs, databases, and/or other systems, and/or our communication with their librarians, archivists, and/or other staff); bookstores and/or other retailers or vendors through whom we may search for and/or purchase site-related materials; HP®, which may gather certain information about our use of HP printer, scanner, and/or copier devices and their associated software and/or services as described in the HP Privacy Statement; other printers/print services; providers of public computers and/or wireless networks we may periodically use; photo development, photo processing, video conversion, and/or other processing services for audiovisual materials; transcription and/or translation services, automated or otherwise; mapping and/or navigation services such as (though not limited to) OsmAnd B.V.’s OsmAnd mobile app; WHOIS lookup providers (if we need to look up an IP address or a domain registration using tools such as ICANN‘s WHOIS Lookup); WebAIM (Web Accessibility in Mind) (whose WAVE Accessibility Tool we may use to improve the accessibility of this website and its contents); website speed testing services/tools (which examine the publicly accessible/visible portions of the website to analyze how quickly they load and identify technical issues that may affect loading speed and/or other functionality); messaging services, apps, and/or clients such as Signal, a service of Signal Messenger LLC and its associated service providers and/or subprocessors (which may include, but are not necessarily limited to, services provided by Google and/or Amazon Web Services), if we communicate with you through such means; common carriers and/or shipping agencies (which we may use if we need to correspond with you via postal mail and/or send or receive packages); and/or our bank(s)/financial institution(s) and/or applicable payment processor(s) (which process — and may sometimes audit or otherwise investigate — site-related financial transactions). Some or all of our third-party vendors/service providers (and/or any third-party subcontractors, data subprocessors, vendors, and/or partners those entities may employ or utilize in providing their respective services) may be located outside your home country and/or the European Economic Area; by using this website, you consent to our transfer of such information to them. Cloudflare, Google, HP, and Sucuri comply with the EU-US Privacy Shield framework, which governs the privacy and security of data U.S. companies process from residents of the European Economic Area.
  • If we are required by law to do so, such as (without limitation) pursuant to a subpoena, search warrant, or other court order or administrative order; in connection with tax returns or other legally required filings, reports, registrations, or disclosures; or in connection with an audit, civil or criminal trial, or other official investigation or proceeding. In some cases, we may disclose certain information if we deem it reasonably necessary to ensure our compliance with applicable law or regulation, even if the specific disclosure is not expressly required. For example (again, without limitation), if we enter into a financial transaction with you that is subject to sales/use tax, we might provide your address to the applicable tax agency in order to determine the correct tax rate.
  • If we are contractually required to do so in connection with a dispute, investigation, or audit involving a third-party service such as (without limitation) our bank(s)/financial institution(s), payment processor(s), or social media services. For example, if our payment processor investigates a payment we received that they suspect of being fraudulent, their terms of service may require us to provide relevant information to their investigators.
  • If we believe in good faith that such disclosure is reasonably necessary to protect our property, rights, and/or safety, and/or the property, rights, and/or safety of third parties and/or the public at large.
  • If you have asked or authorized us to do so.
  • If the information is de-identified, anonymized, redacted, and/or aggregated such that it could not reasonably be used to identify you.
  • If we sell or transfer control of the 6200 Productions website or its assets, or if we enter bankruptcy or cease operation due to our death or incapacity, personal information we have gathered would likely be among any assets transferred to third-party purchaser(s) or acquirer(s) (including, where applicable, our heirs, successors, and/or assigns), who could continue to use that information only as set forth in this policy.

In general, we do not sell or rent personal information about individual visitors to the 6200 Productions website. However, the proprietor of this website is a freelance writer/editor, so it is conceivable that from time to time, personal information about a site visitor may be included in content that we obtain, publish, and/or otherwise disclose in other professional contexts. For example (but without limitation), if you are a public figure, it is possible that a client may hire us (or has previously hired us) to research and write a profile about you for a magazine; similarly, if you attend car shows, it is possible you may be visible in the background of photos we take, obtain, publish, and/or otherwise share in connection with our automotive website, Ate Up With Motor. (There are many such possibilities — these are only a few representative examples.)

Where we become aware of such a case, we will take all reasonable efforts to keep separate any non-public information we have gathered through or in connection with the 6200 Productions website and only disclose that site-related non-public information as described in this section. However, please note that in many cases, we have no way of associating data gathered through this website with information we may have obtained about you in other contexts. For example (again without limitation), your IP address being recorded in our server logs or by Google Analytics doesn’t necessarily mean that we know your name or can recognize your face in the background of a photo! (If you have questions about this, please contact us through one of the methods described in “Controllers, Questions, and How to Reach Us” below.)

Additionally, some providers of embedded content used on this website (see “Embedded Content” above) may use information they gather through such embedded content for advertising and/or marketing purposes, which is beyond our control.

While no online website or Internet-accessible device can be 100 percent secure, we take appropriate and reasonable measures to protect against unauthorized access, use, or destruction of visitors’ personal information, including, but not limited to, the use of encryption and encrypted (https) connections, online and offline virus and spyware scanning, and appropriate password protection.

Data Retention

The duration of cookies placed on your computer or device by the 6200 Productions website is discussed in “Cookie Policy” above.

As of May 25, 2018, we have configured Google Analytics to automatically delete saved user and event data from the analytics service after twenty-six (26) months. Aggregate analytics data (which is not personally identifying) may be retained for longer.

Most of the routine server, error, and security logs collected by us or our web host for this website are retained on a rolling basis — that is, we customarily retain only the most recently collected data. For the Sucuri Security scanning service described in “Security Scans” above, security audit logs are normally retained for about 90 days. Most other routine server, error, and security log data for this website is normally retained for 30 days or less before either being automatically overwritten by newer data or otherwise deleted. However, associated email alerts or notifications, user consent/privacy logs, logs of certain administrative functions that contain no user data, and certain anonymous/non-identifying and/or de-identified log data (e.g., hit counters or last access dates) may be retained for longer periods.

Naturally, we may retain for longer periods any log or scan data we still need for some specific purpose, such as security, spam prevention, troubleshooting, or otherwise maintaining the various technical functions of this website. For example, in the event of an attempted or actual security breach, we may retain relevant log data and scan results for ongoing security measures such as blacklisting IP addresses associated with the intrusion attempt. Also, some recent log data may be captured in backups created by us or our web host, which may be retained for a year or more.

Where we compile logs of user consents and/or privacy choices (such as acceptance of the Privacy Policy or changes to it), those logs are usually maintained indefinitely unless a user requests removal of their data (after which we may retain some related records for audit and compliance purposes). However, we may periodically delete stored consents and privacy choices if they appear to have come from bots rather than human users.

Site-related SMS/MMS text messages or other, similar non-voice direct messages we send or receive via our phone are typically retained for up to two months (although we may delete them sooner than that if they are no longer needed/relevant, appear to be spam, or contain malware). However, we may retain certain specific messages (and/or their attachments, if any) for longer periods if we have some ongoing need for them, and data we receive via text may be transferred to other records before the original text is deleted. (For example, but without limitation, if you send us a text message asking us to contact you via postal mail, we will separately record your mailing address in order to comply with and retain records of your request.) Also, recent messages may be captured in periodic phone backups, which we may retain for a year or more.

Excepting obvious spam, which we promptly delete, posted comments and their associated information are normally retained indefinitely unless the person who posted a comment asks us to remove it or we delete the comment for some other specific reason (e.g., because it appears to be a duplicate, was on a post that has been taken down or deleted, or was in reply to another deleted comment). Similarly, if we have published a portion of your inquiry or support request (as described in the “Contact Form” section above), that post will generally remain public indefinitely unless you ask us to remove it or we elect to take it down for other reasons. In both cases, copies of that information may remain in our backup files or other non-public records.

We usually retain indefinitely most site-related email and Contact Form submissions (which we normally receive via email), excepting duplicate messages, obvious spam, malware, and certain automated notification and alert emails (which we may delete if they are no longer needed and/or relevant). (This generally also includes any files/file attachments included with those messages, again excepting spam or suspected malware.) However, we may delete certain specific emails and/or file attachments if we have some compelling technical, legal, or other reason to do so (e.g., to delete a Contact Form submission we believe to have come from a person under the age of 18, or to remove a message and/or attachment that appear to be corrupted or that we have agreed to delete).

For obvious reasons, we usually also retain indefinitely any names company name, and/or domain names we’ve entered into our spell-checking dictionaries.

It is our normal practice to retain indefinitely any images or photographs we create or obtain for use on this website, including offline copies and archival backups of the original and any modified versions of each image (except where we have some specific obligation to delete such files); our associated work files and editing stages, if any; and any relevant data regarding the creator(s) and/or subject(s) of those images and our usage rights (e.g., the contact information of the original photographer(s) and our correspondence with them regarding the use of their photo(s)), which we normally retain for at least as long as we retain the images themselves. However, we may delete such images and/or information if we have some specific technical or legal reason to do so (e.g., if the image file is irretrievably corrupt or if we have agreed to destroy all copies).

We must retain indefinitely any information pertaining to site-related disputes, financial transactions (such as the purchase of advertising on the site), or legal agreements (such as licensing agreements). If you have given us permission to use your intellectual property on the 6200 Productions website, we generally must retain records of that authorization or license indefinitely, even if that content is removed from the website. Our legal and financial records often necessarily include some personal data; for example (but without limitation), if we enter a legal agreement with you, the agreement will obviously include your name and contact information, and if you contact us by phone, your telephone number will probably appear in our phone bills.

For compliance purposes, we must also retain information pertaining to privacy-related requests, to the extent required by applicable law and/or regulation.

If you have offered information or suggestions pertaining to the operation of this website (such as informing us of a technical problem or providing technical advice or insights on implementing a new site feature or other change), we customarily retain that information for future reference and troubleshooting.

Since the proprietor of this website is a freelance writer/editor, we normally retain indefinitely — except as otherwise stipulated by a specific client or employee agreement and/or other applicable legal requirement(s) — any research notes, drafts, research materials, and/or other information related to our writing and editing work, which may occasionally include certain information related in some way to this website.

Any other type of data we may gather through or in connection this website that is not specifically mentioned here is normally retained only as long as we reasonably need that information, which is determined on a case-by-case basis depending on the nature of the information and how and why we received it. As noted above, if such data is captured in backup files created by us or our web host, those backup files may be retained for a year or more.

Even where it is our normal practice to retain visitors’ information, we periodically remove certain personal data about our visitors from the website’s online database(s) and mail servers for greater security, transferring the data to offline storage and/or deleting portions of the data that we no longer need.

Your Rights (GDPR and California Privacy Rights)

GDPR and State Law

If you are located in certain countries, including those that fall under the scope of the European General Data Protection Regulation (aka the “GDPR”), or in some U.S. states, such as California starting in January 2020 (see “California Privacy and Data Protection Rights” below), data protection laws give you rights with respect to your personal data, subject to any exemptions provided by the law, including, among others, the rights to:

  • Request access to your personal data
  • Request correction or deletion of your personal data
  • Object to our use and processing of your personal data, and in some regions to the sale of your personal data
  • Request that we limit our use and processing of your personal data; and
  • Request portability of your personal data (starting in 2020, California residents may request this up to twice per year).

EU individuals also have the right to make a complaint to a government supervisory authority, as will California residents beginning in January 2020.

If you have questions or would like to exercise these rights, you can contact us through one of the methods described in “Controllers, Questions, and How to Reach Us” below. We’ve also added a Privacy Tools page that will let you automatically retrieve your data based on your email address. (Please note that the data you obtain through this tool does not include personal data not associated with your email address, such as server and error log data; data not stored on the 6200 Productions website itself (like emails you send us directly); non-electronic data (like physical copies of letters or photographs); or analytics results, which are not accessible to us on a user-specific basis.)

Please note that, in order to better safeguard your privacy and the privacy of others, we may (to the extent permitted — and/or required — by applicable law/regulation) ask you to provide additional information to verify your identity and/or residency before processing any data-related requests.

Also, please note that we may be obligated to retain certain data (such as financial transaction records) for legal or administrative purposes or to ensure the security of this website and its data.

Your California Privacy Rights

California Do Not Track Disclosure

6200 Productions does not currently respond to Do Not Track browser settings.

Information-Sharing Disclosures (Shine the Light Law)

If you’re a resident of California, California Civil Code § 1798.83–84 (the “Shine the Light” law) gives you the right to request from us, once per calendar year, a free Information-Sharing Disclosure detailing any personal information (as defined in the applicable statute) we gathered through this website in the past calendar year that we shared with third parties for their direct marketing purposes, along with the names/identities of those third parties.

Although we believe that we are technically exempt from the requirements of § 1798.83, we will nonetheless be happy to provide you with such a disclosure within 30 days of our receipt of your request.

Please note that this disclosure only covers information shared for direct marketing purposes. See the other sections of this Privacy Policy to learn more about other types of information we gather and how we use it.

California Privacy and Data Protection Rights

Starting January 1, 2020, California’s state data protection laws, including the California Consumer Privacy Act of 2018 (CCPA), give California residents additional rights with respect to their personal data, including, among others, rights similar to those listed in the “GDPR and State Law” section above. These rights include (subject to any exemptions and/or exceptions provided by the law and/or its associated regulations) the right to:

  • Request access to your personal data from the preceding 12 months in “a readily usable format” (which you may request up to two times in a given 12-month period).
  • Request deletion of your personal data.
  • Opt out of the sale of your personal information.
  • Make a complaint to a state government supervisory authority.
  • Take private legal action in the event of a data breach that exposes your unredacted personal information to theft or unauthorized access.

You need not be physically present in California to exercise these rights provided that you have a current California residence.

While we believe 6200 Productions does not technically meet any of the applicability thresholds specified by this California law, we are committed to providing visitors with as many privacy choices as we reasonably can.

The Privacy Tools page will let you automatically retrieve your data from the website based on your email address. There are limitations on the types of data this tool can retrieve; see the the Privacy Tools page for more details. (You need not use the tool to make a request.)

You can exercise your California privacy rights through the Do Not Sell My Personal Information page or by contacting us through one of the methods described in “Controllers, Questions, and How to Reach Us” below. Applicable statutes and/or associated regulations issued by California’s Office of the Attorney General may stipulate the maximum time allowed for acknowledging and responding to a request. There is no charge for making privacy-related requests.

Please note that, in order to better safeguard your privacy and the privacy of others, we may be required to verify your identity before processing certain data-related requests. Although the regulations governing the verification requirements are not yet final, the currently proposed regulations (summarized in this article) would require us to verify your identity “to a reasonable degree of certainty” based on at least two points of data we already possess about you before we can disclose what categories of personal information we have collected about you. Before disclosing any specific pieces of personal information, the proposed regulations would require us to verify your identity “to a reasonably high degree of certainty” based on at least three points of data we possess about you, including a signed declaration, under penalty of perjury, that you are who you say you are (and/or, if you act through an agent or representative, that the agent/representative is truly representing you). In the event we must request additional information we did not already possess in order to verify your identity, the proposed regulations would allow us to use and retain that additional information only as required for verification and/or compliance purposes. The proposed regulations would not require verification for opt-out requests, although those proposed regulations would permit us to refuse a request we believe to be fraudulent.

In some cases, we may be unable to fulfill your request because we have no way to verify your identity to the standard the law and/or its associated regulations require. For example (but without limitation), if you have visited our website, but never left a comment, submitted a Contact Form, completed a financial transaction with us, or interacted with us via email or other means, we probably do not have enough information to confirm your identity to even a “reasonable degree of certainty” (as the applicable regulations may define that term). Also, applicable law and/or regulation may provide certain exemptions to the rights provided by the CCPA (particularly with regard to the deletion of your personal information), and we may be unable to delete certain information (e.g., our web host’s server and error logs) for technical reasons.
If you are a California resident and would like to exercise your right to opt out of the sale of your personal information, please visit our Do Not Sell My Personal Information page.

Controllers, Questions, and How to Reach Us

The controller for processing personal information is Aaron Severson dba 6200 Productions, 11100 National Bl. #3, Los Angeles, CA 90064. You can reach us via postal mail to that address or via email to admin (at) 6200productions (dot) com. (Note: As of November 19, 2019, the Contact Form is currently offline due to persistent problems with spam and malicious activity.)

Privacy Policy Changes

6200 Productions may change its Privacy Policy from time to time, at our sole discretion. Your continued use of this site after any change in this Privacy Policy will constitute your acceptance of such changes, whose effective date is shown near the top of this page. If the policy has changed since your last visit, the website may prompt you to review and accept the changes.

Recent Revisions


Here is a list of recent changes to this Privacy Policy, in reverse order by date:

  • November 20, 2019: Further updated the California Privacy and Data Protection Rights language regarding verification requirements (noting the restrictions the proposed regulations impose on our use and retention of any additional data we may request to verify your identity; clarifying that the term “reasonable degree of certainty” is as the applicable regulations may define that term; changing “may permit certain exemptions” to “may provide certain exemptions”; changing “the law and it associated regulations” to “the law and/or its associated regulations”; and changing “or, if you act through an agent or representative” to “and/or, if you act through an agent or representative”).
  • November 19, 2019: Updated the language in Online Tracking about the Google Ads Data Processing Terms (which from January 1, 2020, also apply to data subject to new California privacy laws as well as to data subject to European data protection rules), separating it into its own paragraph for readability and fixing a technical problem with one of the existing hyperlinks. Added a note to that section indicating that the Your Rights (GDPR and California Privacy Rights) section contains more information about these privacy laws. Added links in Online Tracking and the Embedded Content bullet point on YouTube videos to Google’s “Businesses and Data” pages, which contain further information on how Google handles data from business customers (and what data they may provide to YouTube content creators/publishers). Updated Disclosure of Personally Identifying Information to include Google Analytics among the specific Google services enumerated there, making some minor adjustments to that passage for clarity. Updated the California Privacy and Data Protection Rights section to clarify the language about identity verification, note that we may be unable to respond to a request if we are unable to adequately verify your identity, and emphasize that (in addition to any other exemptions the law and associated regulations may permit) we may be unable to delete certain types of information for technical reasons. Updated Data Retention to note, “For compliance purposes, we must also retain information pertaining to privacy-related requests, to the extent required by applicable law and/or regulation.” Updated Controllers, Questions, and How to Reach Us to note that the Contact Form is currently offline.
  • November 18, 2019: Updated Embedded Content to note that when you access embedded content, your browser may also contact a certificate authority to check the validity of the embedded content provider’s encryption certificate. Updated the reference under Disclosure to our certificate authority to add “and/or other certificate authorities we may use or access.”
  • November 17, 2019: Further clarified the language about service/software/app/device telemetry in Disclosure of Personally Identifying Information (changing the phrase “that could gather personal information through telemetry” to “that could gather personal information related to Ate Up With Motor and/or its related services through telemetry”). Updated the bullet point about situations where we may be legally required to disclose information (changing “in connection with an audit or other official investigation or proceeding” to “in connection with an audit, civil or criminal trial, or other official investigation or proceeding”). Updated the bullet point about disclosures to protect rights, safety, and/or property (changing “to protect our property, rights, and/or safety, or the property, rights, and/or safety of third parties or the public at large” to “to protect our property, rights, and/or safety, and/or the property, rights, and/or safety of third parties and/or the public at large.”). Added boldface to additional items on that list to aid readability. Clarified the language in the preamble about California privacy rights (changing “or jump to” to “For more information about California privacy rights, jump to …” and making the latter a separate sentence). In the Disclosure section, clarified the example about car shows (changing “obtain, publish, and/or otherwise disclose” to “take, obtain, publish, and/or otherwise share”).
  • November 16, 2019: Fixed the capitalization of Online Certificate Status Protocol. Under Disclosure of Personally Identifying Information, changed the phrase “the makers of software/apps and/or electronic devices we use that incorporate information-gathering telemetry or other surveillance features, some of which cannot be completely disabled without simply ceasing to use that software, app, or device” to “services, software, apps, and/or electronic devices we may use that could gather personal information through telemetry and/or other integrated information-gathering and/or surveillance features, some of which cannot be disabled without simply ceasing to use that service, software, app, or device.” Further refined the language of the Certificate Authority Service section. Updated the reference to our Internet service provider in the Disclosure of Personally Identifying Information section from “Spectrum/Time Warner Cable®” to “Spectrum Internet® (formerly Time Warner Cable®).” Updated the description of our mobile carrier in that same bullet point and rearranged its order. Also updated the description of Bitdefender Mobile Security in the same bullet point to note that this includes the app’s associated services.
  • November 15, 2019: Further updated the Certificate Authority Service section to define OCSP requests. Added Bitdefender to the list of examples of third-party service providers under Disclosure. Under Embedded Content, clarified the language about Google Hosted Libraries to better match the description of Google Fonts in the same bullet point.
  • November 14, 2019: Added a new “Certificate Authority Service” section to Information We Gather Automatically and added Let’s Encrypt to the list of examples of third-party service providers under Disclosure. Fixed an erroneous reference to Ate Up With Motor in the Browser Tests section. Updated the reference to Signal in Disclosure to note that Signal uses subprocessors/service providers that may include (without limitation) services provided by Google and/or Amazon Web Services, and added links to the relevant privacy information pages as well as fixing a punctuation error. Further refined the Certificate Authority Service language (also updating the reference to Let’s Encrypt in the Disclosure of Personally Identifying Information section) and added another example to Other Information You Provide to Us, refining some language in that section (adding “(but without limitation)” after “for example”; noting that the examples are just a few hypothetical possibilities; and changing the phrase “Our use of such site-related information …” to “Our use of personal information you provide us in such ways …”). Updated Information We Receive from Other Sources to note that our firewall software and/or router(s) may provide us with information about any online servers or resources to which our devices connect or try to connect.
  • November 13, 2019: Updated Other Information You Provide to Us section to remove a reference to now-deleted language in a previous version of the preamble, revising that text to better reflect the framing of the current preamble, changing “site visitors may provide us with personal information” to “you may provide us with personal information through or in connection with this website” and changing “inquiry about this website” to “inquiry about this Privacy Policy.” Added ASUS and Netgear (the manufacturers of our wireless routers) to the list of examples of third-party service providers under Disclosure. Added an internal anchor link in the preamble to the California section of this policy.
  • November 11, 2019: Updated Data Retention to clarify that our retention of email and/or text messages generally also includes files/file attachments (other than spam or suspected malware), change “some outstanding reason to do so” to “some ongoing need for them,” and add “but without limitation” to the example given in the SMS/MMS language. Added OsmAnd as an example of mapping/navigation services in the list of examples of third-party service providers under Disclosure. Updated Information We Receive from Other Sources to note that we may receive personal information about the developers of software/apps/services/themes/add-ons we install for use in our work and/or the management of this website. Added bookstores and/or other retailers or vendors through whom we may search for and/or purchase site-related materials to the list of examples of third-party service providers under Disclosure. In the same section, changed “libraries and/or archives” to “libraries, archives, and/or databases.” Added Perishable Press and the Mozilla Firefox browser to the examples of sources of third-party security-related data under Information We Receive From Other Sources.
  • November 10, 2019: Updated the reference in Disclosure to TCL Communications to note that they make not only the BlackBerry device, but also its suite of associated BlackBerry apps and services. Added OpenKeychain (and/or other encryption software/services) and Open Camera to the list of examples of third-party service providers under Disclosure.
  • November 9, 2019: Added libraries and archives (including librarians/archivists/their staff) and providers of public computers and/or wireless networks we may periodically use to the list of examples of third-party service providers under Disclosure. Fixed some typos in that section and changed “Examples of our third-party vendors/service providers may include” to “Examples of such third-party vendors/service providers may include …” In the California Privacy and Data Protection Rights section, changed “starting in January 2020” to “starting January 1, 2020” and “will give” to “give.” Also in the Your California Privacy Rights section, changed the heading “Information-Sharing Disclosures” to “Information-Sharing Disclosures (Shine the Light Law).” Under Disclosure, revised the language about information we may be required by law to disclose in order to streamline the language and better reflect the range of possible scenarios. Updated Data Retention to note that we normally retain indefinitely research notes and information related to our freelance writing and editing work, and changed the phrase “Any other type of data we may gather on visitors to this website …” to “Any other type of data we may gather through or in connection this website …”
  • November 8, 2019: Updated Disclosure to note that third-party service providers may include the makers of software/apps and/or electronic devices we use that incorporate information-gathering telemetry or surveillance features, rearranging the text of that bullet point to make it easier to decipher and emphasize that the examples listed are not an exclusive list. Rearranged the first paragraph of the preamble for clarity.
  • November 7, 2019: Updated Data Retention to remove a confusing reference to a now-deleted section of the preamble. Made some adjustments to the list under Embedded Content to fix some grammatical issues, clarify the text, and arrange the items in a slightly different order. Added the Google Play Store and its related services to the list of examples of third-party service providers under Disclosure. Added the Google Play Store and its related services to the list of examples of third-party service providers under Disclosure, rearranging the list of Google-provided services in that section for better grammatical flow.
  • November 5, 2019: Further updated Disclosure of Personally Identifying Information section to clarify that we may not always be aware of having gathered information about a site visitor in some other context. Fixed a spelling error in this revision list. Revised Online Tracking to updated the possible means of reopening the banner and opting out of analytics tracking. Revised Security Scans to update description of the EU-US Privacy Shield framework in that section to match the reference under Disclosure of Personally Identifying Information and slightly clarified the description of the Sucuri Security plugin’s functions. Updated Comments and Personal Information to change “you can choose to save …” to “you may have the option to save …” (regarding saving the information you enter for future comments, an option that may not always be offered), change “URL” to “website,” and change “each time a reply or follow-up comment is posted” to “each time a reply and/or follow-up comment is posted.”
  • November 4, 2019: Attempted to fix a technical issue with the bookmark/anchor links throughout. In Disclosure of Personally Identifying Information, changed “de-identified or aggregated” to “de-identified, anonymized, redacted, and/or aggregated.” Changed several instances of “… and as otherwise described” to “… and/or as otherwise described.” Updated Information We Receive from Other Sources to note that we also get blacklist information via Spybot. Updated and simplified the preamble and revised text of the Disclosure of Personally Identifying Information section to add language about information we may gather or release that is NOT obtained through/in connection with this website.
  • November 3, 2019: Added TinyWall to the list of examples of third-party service providers under Disclosure and updated the Information We Receive from Other Sources section to add the MVPS HOSTS file to the examples of third-party blacklists we may use and note that we may also use that information to block access to our system and/or devices as well as the website. Updated the Your California Privacy Rights section to enumerate the list of CCPA rights rather than referring to the GDPR section, changing the “Other California Privacy Rights” heading to “California Privacy and Data Protection Rights,” and making some minor clarifications to the language of that section (including noting that California Civil Code § 1798.83–84 is known as the “Shine the Light” law). Updated the GDPR section wording to refer to the Controllers, Questions, and How to Reach Us section rather than just “below” and updated the internal anchor links to that section. Updated Contact Form section to also note that it applies to the Do Not Sell My Personal Information Privacy Request Form. Updated Notice to Parents section to clarify that the references to children refer to minor children and that parents have the right to request the removal or deletion of information about their minor children. Fixed a couple of very minor grammatical issues.
  • November 2, 2019: Added HP to the list of examples of third-party service providers under Disclosure, noting that they comply with the EU-US Privacy Shield framework. Reordered several items in that section, also adding the word “other” to “printers/print services” and placing it immediately after HP. Updated Security Scans to note that security/anti-spam scans of messages we send or receive may be performed on text messages as well as email, and that security scans may include submitting the messages, file attachments, and/or other relevant data to third-party services such as cloud-based malware-detection services.
  • November 1, 2019: Fixed the date formatting and a capitalization problem in the previous entry on this list. Added Piriform (CCleaner), a subsidiary of Avast, to the list of examples of third-party service providers under Disclosure.
  • October 31, 2019: Added Artifex (maker of the SmartOffice app), Mozilla (maker of the Firefox web browser(s)), and Safer-Networking Ltd. (maker of Spybot) to the list of examples of third-party service providers under Disclosure. Added Google Safe Browsing to the list of examples of Google services we may use/offer and fixed a grammatical error in that language.
  • October 30, 2019: Added the Guardian Project’s Orbot and Tor Browser to the list of examples of third-party service providers under Disclosure. Clarified the description of Cloudflare 1.1.1.1 in that section, adding links to the applicable privacy policies in addition to the privacy statement links. Updated Online Tracking section to note that Google Analytics may also identify what type/model of device visitors are using, certain device settings, their operating system, their browser version (as well as the type), and their Internet service provider (especially for mobile devices). Added link to the Google Analytics “Safeguarding your data: Information of Visitors of Sites and Apps Using Google Analytics” page and clarified some wording.
  • October 27, 2019: Added trademark notice language for the Google services specified herein, adjusting some adjacent language for readability. Clarified the wording of the reference to Gmail in the list of examples of third-party service providers under Disclosure, and added Google Hosted Libraries there in addition to the existing description under Embedded Content. Added a link to the Google Ads Data Processing Terms in the Online Tracking section.
  • October 25, 2019: Added Cloudflare’s WARP service (associated with the Cloudflare 1.1.1.1 service already listed), NetGuard firewall/traffic monitor, and CompanionLink to the list of examples of third-party service providers under Disclosure. Fixed some incorrect punctuation in that section.
  • October 19, 2019: Added TCL Communication Limited (current owner of BlackBerry) to the list of examples of third-party service providers under Disclosure.
  • October 17, 2019: Moved Effective Date to the top of the document to make it easier to see. Reworded the Privacy Policy Changes section, preamble, and License for This Policy text accordingly, also fixing a capitalization inconsistency. Added a new heading, “Recent Revisions,” for this list and updated the description of this list for clarity.
  • October 16, 2019: Updated the description of Yoast under Embedded Content to indicate the presence of the Yoast SEO plugin’s Algolia search functions.
  • October 14, 2019: Updated the description of Epic Privacy Browser in the list of examples of third-party service providers under Disclosure to reflect that the browser also has an associated Epic Search Engine (which submits anonymized queries to Yandex) and to change “in connection with their …” to “through our use of their …” for greater clarity.
  • October 9, 2019: Updated the Cookie Policy section to include a link to the Cookie Notice, which is now a separate page as well as being incorporated into the privacy preferences tool. Slightly adjusted the description of that list to note that these are cookies we may use.
  • October 2, 2019: Amended the Your Rights (GDPR and California Privacy Rights) section to note that we may ask you to verify your identity and/or residency before processing data-related requests and that you need not be present in California to exercise your CCPA rights provided that you have a current California residence. Made few minor wording adjustments in that section to accommodate the new language and changed the phrase “… and its associated regulations” to “… and/or its associated regulations.” Revised the “Do Not Sell My Personal Information” and preamble text wording to match the wording on the Privacy Tools page.
  • September 29, 2019: In the list of examples of third-party service providers, changed several instances of the phrase “we may use or offer” to “we may use and/or offer” (since in some instances we may do both). In the language about Adobe in that section, changed the phrase “may collect data about such use” to “may collect related and/or associated data” to avoid confusion. Update the Your California Privacy Rights and added links to the Do Not Sell My Personal Information page. Added Hidden Reflex’s Epic Privacy Browser to the list of examples of third-party service providers under Disclosure.
  • September 15, 2019: Added website speed testing services/tools to the list of examples of third-party service providers under Disclosure.
  • September 14, 2019: Added Adobe to the list of examples of third-party service providers under Disclosure.
  • September 7, 2019: Added printers/print services, photo development, photo processing, video conversion, and other audiovisual material processing services to the list of examples of third-party service providers under Disclosure. In the description of the WAVE accessibility tool in that subsection, changed “are using” to “may use.” Struck the phrase “as we have no employees” from the Information-Sharing Disclosures section.
  • August 24, 2019: In the Data Retention paragraph regarding SMS/MMS retention, changed “… are typically retained for up to 60 days” to “… are typically retained for up to two months.”
  • August 11, 2019: Under Disclosure, clarified that third-party service providers may use their own subcontractors, data subprocessors, or other third-party vendors or partners, who may be located in other countries or regions. Under Embedded Content, struck the phrase “in the United States” in the bullet point regarding BootstrapCDN/Stackpath.
  • July 8, 2019: Under Disclosure, added transcription and translation to the examples of independent contractors/employees and added translation, transcription, mapping, and navigation services to the examples of third-party service providers.
  • June 20, 2019: Clarified that the section of Data Retention dealing with log data refers specifically to logs for this website. Fixed a typo in that section.
  • June 7, 2019: Added Malwarebytes to the list of third-party service providers under Disclosure and updated the description of Avast in that list. Further updated the description of “browser fingerprinting” under Embedded Content.
  • June 3, 2019: Made some updates to the wording of Embedded Content to better explain what other information third party content providers may be able to detect (the process of so-called “browser fingerprinting”) and add a link to the EFF’s Panopticlick website. Corrected accidental duplication of Avast in the list of third-party service providers under Disclosure.
  • April 2, 2019: Updated Legal Bases for Collecting and Using Information to add the item about protection of vital interests (taken directly from the latest version of Automattic’s Privacy Policy). Made a minor amendment to Browser Tests to note that such tests are primarily but not necessarily exclusively conducted via the Modernizr plugin.
  • March 25, 2019: Updated Security Scans to make clearer that some Sucuri data and logs may be processed and/or stored by Sucuri as well as by us.
  • March 23, 2019: Under Online Tracking, struck the sentence, “This information does not include users’ names or email addresses.” (Google Analytics does not provide that information to us, but we don’t know whether or not they can determine such things from the analytics data and would prefer not to speculate.) Under Contact Form, in the text regarding publishing inquiries or excerpts thereof, changed “we will not publish or release …” to “such publication will not include …” for clarity. Rearranged some other text in that section the Comments Section for more logical flow.
  • March 14, 2019: Added some ® symbols. Amended “Dreamhost, LLC” to just “DreamHost” (removing duplicate text were applicable) and the second instance of “T-Mobile USA, Inc.” to just “T-Mobile.” Throughout, slightly clarified the descriptions of what user agent information may include.
  • March 10, 2019: Under Information We Receive from Other Sources, added The Spamhaus Project as another example of where we may obtain block lists for spam and malware prevention, and added links to that and HackRepair.com.
  • March 4, 2019: Fixed some tag closing issues. Under Privacy Policy Changes, changed “the terms have changed” to “the policy has changed” for clarity.
  • March 3, 2019: Updated Contact Form section to add information about automatic filtering and spam prevention measures. Fixed a couple of punctuation errors. Updated Embedded Content to note that you may be able to selectively disable some forms of embedded content. Fixed some inconsistent usage of “administrator dashboard” vs. “administrative dashboard.” Under Legal Bases for Collecting and Using Information, changed “financial transactions or image usage rights” to “financial transactions and image usage rights.”
  • February 27, 2019: Moved the first references to DreamHost and the link to the DreamHost privacy policy from the Server and Error Logs section to the Who We Are section, adding a note that DreamHost also hosts our email servers.
  • February 26, 2019: Updated Online Tracking to note that Google Analytics also compiles information such as (without limitation) visitors’ landing pages and keyword searches that led visitors to this website. Updated Server and Error Logs to add the phrase “(as applicable, but without limitation)” before the listed examples; add “that uses certain site features, such as the Contact Form”; add the following text after the list: “(These examples are a representative sampling, but not an exhaustive list; we may also use or add other logs not specified here, and not all logs are necessarily in use at any given time.)”; delete superfluous uses of the word “that”; and split the rest of that paragraph into a separate paragraph for readability. Moved the language about logging privacy consents and acceptance of terms to a new subsection under Information You Provide to Us called “Consents and Agreements.”
  • February 22, 2019: Under Comments, changed “we may email you at that address to respond to your comment (or the associated comment thread, if applicable), particularly if it includes a question or offer of assistance, or if we need to clarify some pertinent details. (For example, if you have posted two very similar comments back to back, we may email you to ask which one you want us to publish.)” to “we may respond via email in addition to or instead of publishing the comment on the 6200 Productions website, particularly if your comment includes a question or offer of assistance or if we have questions about any pertinent details — for example, if you have submitted two very similar comments, we might email you to ask which one you want us to publish” to match the language in the Terms of Use.
  • February 19, 2019: Under Disclosure of Personally Identifying Information, changed “If we have received your express authorization to do so” to “If you have asked or authorized us to do so.”
  • February 18, 2019: Added Cloudflare DNS resolver services to the list of third-party service providers under Disclosure. Fixed some link relationship errors in that section and noted that Cloudflare also complies with the EU-US Privacy Shield framework. Under Online Tracking, changed “… partially anonymize visitors’ locations by removing the final octet of each IP address” to “… partially anonymize the data it gathers by automatically omitting a portion of each visitor’s IP address” and then changing “each visitor’s IP address” to “each tracked visitor’s IP address” for clarity.
  • February 14, 2019: Made an editorial revision to the previous item on this revision list to better explain what we changed (i.e., the language about looking up public information on site visitors). Made a further amendment to Information We Receive from Other Sources to add another example of looking up public information on site visitors and reiterate that the examples presented in this section are not an exhaustive list. Also changed “Our use of information we receive from other sources … to “Our use of information we gather from these or other sources …” Changed the wording of the WHOIS lookup services item under Disclosure to make it more generic. Amended Data Retention language to clarify and reiterate that legal and financial transaction records often necessarily include some personal data; split part of that paragraph into a separate paragraph for clarity (amending its text slightly to avoid confusion).
  • February 13, 2019: Added spell-checking to the listed ways we may use personal information we collect from or about you and updated Data Retention to note that we typically retain indefinitely names we add to our spelling dictionaries, and that to understand your comments or inquiries/messages, we may use information you submit to seek additional information from third-party sources. Added ICANN and other WHOIS lookup services to the third-party service providers under Disclosure and inserted a note about WHOIS lookups under Information We Receive from Other Sources, also amending the subsequent paragraph of the latter section for clarity (about looking up public information about site visitors).
  • February 7, 2019: Updated the Sucuri description in Security Scans to add the phrase “(without limitation)” after “such as,” since the listed examples are not an exhaustive list.
  • February 6, 2019: Added Google Hosted Libraries to Embedded Content (in the same bullet as Google Fonts, since they operate similarly), revising/restructuring that bullet point’s language accordingly and adding a link to the Google Developers Google Fonts page.
  • February 3, 2019: Under Disclosure of Personally Identifying Information, revised the item on information that was already public, changing the first word of that bullet from “If” to “Where”; changing “was or is” to “is or was”; changing “e.g., …” to “such as — but without limitation — …”; and adding to and clarifying the listed examples. Also adjusted the text style of that item and moved it higher on the list. Revised the preamble of that section.
  • February 2, 2019: Updated Cookie Policy section to note that some accessibility features may use cookies to save your settings/preferences, striking the word “those” from the following sentence to avoid confusion. At the beginning of that section, also replaced the words “each time” with “when.” Added a new section under Information We Collect Automatically called Browser Tests, describing the function of the Modernizr plugin we use.
  • February 1, 2019: Fixed some typos, updated text styles, and edited link titles and anchor text on this page for better accessibility. Added WebAIM to the list of third-party service providers under Disclosure.
  • January 31, 2019: Under Data Retention, amended “We usually retain most site-related emails indefinitely …” to “We usually retain indefinitely most site-related email and Contact Form submissions (which we normally receive via email) …” for clarity. Under Online Tracking, deleted the language about turning off the Google Analytics tools via the Privacy Tools, as that function is not working properly at present.
  • January 27, 2019: Under Disclosure of Personally Identifying Information, changed “(such as information that you have published on your official website or that is included in published interviews or news articles about you)” to “(e.g., information that’s available on your website; that you included in public comments or public posts on this or other websites; or that appears in published interviews, books, or news articles about you).” Updated Embedded Content to note that the Google Fonts servers may be operated by Google’s subprocessors as well as Google and that they may not necessarily be in the U.S., adding a link to their list of subprocessors. Made a slight change to the preamble to put the sentence about third-party websites on a separate line and reworded that sentence as: “Your use of any third-party websites or services, including ones linked from the 6200 Productions website or on which we may have accounts, is subject to the individual privacy policies and terms of use/terms of service, if any, of those sites or services.” Added “messaging services, apps, and/or clients” to the list of third-party providers under Disclosure.
  • January 25, 2019: In the California Do Not Track Disclosure section, under Your California Privacy Rights, added spaces to “Do Not Track.”
  • January 22, 2019: Updated Disclosure of Personally Identifying Information language about legal requirements to clarify that we may disclose information where we deem it reasonably necessary to ensure our compliance with applicable law or regulation, even if the specific disclosure isn’t expressly required (e.g., to look up an applicable tax rate for your address). Added common carriers/shipping agencies to the list of third-party service providers. Clarified Other California Privacy Rights by putting “subject to any exemptions provided by the law” in parentheses and moving that phrase to earlier in the applicable sentence.
  • January 15, 2019: Updated Online Tracking to note that Google may have servers and/or third-party subcontractor data processors outside the U.S. and that Google may transfer analytics data to third parties for subcontracted support and data processing as well as troubleshooting and service improvement. Added a link to the list of Google’s subprocessors. Rearranged some text for clarity.
  • January 3, 2019: Updated Disclosure of Personally Identifying Information to clarify that the circumstances under which we may be legally required to disclose information may include (without limitation) providing certain information to relevant government agencies (e.g., tax or customs agencies) for compliance purposes or in connection with audits or official investigations, as well as in connection with a subpoena or court order.
  • December 30, 2018: Added Startpage.com and DuckDuckGo to the list of third-party service providers under Disclosure.
  • December 29, 2018: Updated third-party service providers list under Disclosure to include our bank(s)/financial institution(s), and/or applicable payment processor(s), also adding those entities to the bullet point on contractual obligations and inserting the phrase “(without limitation)” ahead of the list of examples (since the examples shown may not be an all-inclusive list). Minor editorial correction to remove some unnecessary spaces.
  • December 19, 2018: Updated Embedded Content to note that WordPress may gather information in the course of installing, removing, or updating plugins, themes, and add-ons from WordPress.org. Updated Disclosure’s list of third-party vendors and service providers to include Microsoft and WordPress.org. Slightly amended the description of our mobile provider to change “emails and texts sent to and from … to “emails, texts, and other messages sent to and from …” ETA: Amended the Microsoft description from “software, apps, and tools” to “software, apps, tools, and services” and the Spectrum/Time Warner Cable description from “and thus has access to …” to “and thus has information about …”
  • December 10, 2018: Rearranged the text of the preamble for clarity.
  • December 9, 2018: Made a minor clarification to Data Retention regarding consent logs: changed “… after which we may retain some logs for audit and compliance purposes” to “… after which we may retain some related records for audit and compliance purposes” and put that phrase in parentheses.
  • December 2, 2018: Updated Information We Receive From Other Sources to clarify what kind of information we may receive in connection with security and anti-spam measures and how we use it (adding email filtering as an additional example).
  • November 27, 2018: Updated Embedded Content to add Vimeo to the list of content providers and updated Disclosure to add our Internet service provider with a link to their customer privacy policy.
  • November 25, 2018: Clarified Data Retention regarding the retention of email and image files, and changed “although we usually delete comments on deleted posts or that were in reply to another comment that has been deleted” to “or we delete the comment for some other specific reason (e.g., because it appears to be a duplicate, was on a post that has been taken down or deleted, or was in reply to another deleted comment).”
  • November 19, 2018: Updated Disclosure to note that we may periodically use Gmail, which is owned by Google. Minor clarification in Contact Form: changed “… you type into the form” to “… you enter into the form.”
  • November 17, 2018: Minor wording adjustments in Disclosure: changed “or is included in published interviews or news articles about you” to “or that is included in published interviews or news articles about you” and changed “their own, comparably strict confidentiality policies” to “their own, comparably strict (or stricter) confidentiality policies.”
  • November 15, 2018: Clarified the preamble, Other Information You Provide to Us, and Data Retention sections regarding our work and professional relationships separate from this website. Updated Data Retention to further clarify our retention of log data.
  • November 13, 2018: Changed references to Google LLC to just “Google” to avoid confusion with their shifting corporate usage. Updated Data Retention to clarify retention of privacy/consent logs. Updated Online Tracking; Server and Error Logs, Security Scans, Comments, and Contact Form to make clear that we may also use the data to troubleshoot technical problems and improve the functionality of the site (and if applicable our accounts/pages on third-party sites/services). Added “website development/improvement” to the list of possible functions of independent contractors under Disclosure. Made a capitalization change to the Google Fonts description under Embedded Content.
  • November 11, 2018: Updated Data Retention to clarify that logs of some administrative functions (which contain no user data) may be retained for longer periods.
  • November 8, 2018: Moved the reference to displaying specific notifications or content based on IP address or user agent from the WordPress section of Embedded Content to Server and Error Logs, since that function appears to mostly be performed locally (i.e., by this website rather than an external one). Added notes to Server and Error Logs, Security Scans, Embedded Content, Comments, and Contact Forms sections indicating that your IP address may reveal your geographical location and in some cases also your Internet service provider.
  • November 7, 2018: Updated Embedded Content to better describe information gathered by WordPress. Added an item to that section about FeedBurner blog feeds on the administrative dashboard.
  • November 5, 2018: Updated Disclosure to change “… the property, rights, and/or safety of 6200 Productions, third parties, or the public at large” to “… our property, rights, and/or safety, or the property, rights, and/or safety of third parties or the public at large.” Fixed typographical errors in this revision list (corrected the inadvertent substitution of em dashes for ellipses).
  • November 4, 2018: Updated Comments, changing “… record and use information in and associated with your comment … ” to “… record and use personal information in and associated with your comment … “; “… it can be found using the website’s search function” to “… it appears and/or can be found using the website’s search function and other internal indexing tools”; and “publish and/or respond to your comment” to “publish and respond to your comment.” Updated Contact Form section to change “… record and use information in and associated with your submission … ” to “… record and use personal information in and associated with your submission.”
  • October 22, 2018: Updated this page’s hyperlinks with “rel=noopener” or “noopener noreferrer” attributes for security purposes.
  • October 19, 2018: Updated Data Retention section with information about photos or other images we obtain or create for use on this website (revising some related existing language for clarity). Also, clarified some cumbersome wording about retention of anonymous or de-identified log data. Clarified the language in Information We Receive from Other Sources. Rearranged the order of the Legal Bases for Collecting and Using Information, changed “… to safeguard the integrity of this website” to “… to safeguard the integrity of this website and its data,” and changed “to better understand how many people access our content” to “to better understand how (and how many) people access our content.”
  • October 16, 2018: Updated Who We Are text to emphasize that we’re based in the U.S. (and a U.S. citizen and resident). Fixed a mechanical problem with the hyperlinks to our contact information that was keeping them from working properly.
  • October 14, 2018: Updated Embedded Content to change “… that loads the embedded content” to “… that loads and/or interacts with the embedded content”; “and/or include other mechanisms that allow the third-party hosting site to gather certain information about you” to “and/or use other mechanisms that enable the third-party site to gather information about you”; and “geographical location” to “your geographical location” for clarity. Updated the YouTube description in that section to note that YouTube players may check whether you are logged into a Google account and added an extra link to their privacy policy.
  • October 12, 2018: Updated Embedded Content and Disclosure to indicate that we may also use or offer other Google tools or services.
  • October 10, 2018: Clarified Disclosure section to note that our web host also hosts the mail servers for our associated email addresses.
  • October 7, 2018: Further clarified Disclosure provisions about contractors/employers and third-party vendors/service providers. Minor editorial correction to this revision list. Revised Data Retention language to clarify the retention of anonymous or de-identified log data. Clarified Disclosure provisions regarding business transfers. Updated Comments to note that special characters, HTML/PHP code, and emojis in comments may be removed.
  • October 4, 2018: Added a note about T-Mobile’s scam warnings to Security Scans and noted in Disclosure that our mobile carrier also, obviously, processes our phone calls.
  • October 3, 2018: Amended the independent contractors/employees and third-party vendors/service providers language in Disclosure of Personally Identifying Information for greater clarity, including that the purposes for which we may share information with such contractors/employees/vendors/service providers may also addressing technical and/or legal issues (as well as the other purposes already specified), noting that some independent contractors may have their own comparable confidentiality policies, and repeating some of the links to third-party privacy policies. Minor stylistic update to remove some unnecessary boldface and fix some inconsistent punctuation. Inserted “(see “Other California Privacy Rights” below)” to the text of GDPR and State Law. Minor change to Server and Error Logs, changing “We, or where applicable our web host …” to “We, and/or where applicable our web host …” Made some minor clarifications to the language in the Cookie Policy section. Made some minor clarifications to the language in the Cookie Policy section, including reordering two paragraphs.
  • October 2, 2018: Added a separate sub-section, “Other Information You Provide to Us.” Minor clarification in Data Retention regarding text message retention.
  • October 1, 2018: Clarified language about ban lists/blacklists, noting that some may include email addresses and which we may use to protect our system and devices as well as preventing spam and protecting the site and its data.
  • September 30, 2018: Renamed Cookies section “Cookie Policy” and added a hypertext anchor to it. Added a Your California Privacy Rights header to the California rights section and added a hypertext anchor to it for easier navigation. Updated Comments and Information We Receive from Other Sources to note that we may obtain or receive ban lists of IP addresses and/or user agents commonly associated with spam and/or malware.
  • September 29, 2018: Updated the Comments section to note that published comments may appear in search results made using the website’s search function and that we may index them for that purpose. Clarified Disclosure and California Information-Sharing Disclosure sections to note that embedded content providers may use the information they gather for advertising/marketing purposes.
  • September 28, 2018: Updated and clarified the Comments section (and the Comments item in Disclosure) to reflect recent updates to the Terms of Use, including hopefully clearer language about email notifications and modifying/deleting comments.
  • September 26, 2018: Updated the Comments section to mention the Recent Comments widget.
  • September 25, 2018: Updated Server and Error Logs and Data Retention to clarify the types of data the logs include and how long we retain it. Added Other California Privacy Rights section. Minor revisions to Disclosure, rearranging the item about sale/transfer and changing the wording of that item for readability.
  • September 21, 2018: Under Data Retention, changed “Site-related SMS/MMS text messages or other, similar non-voice direct messages we receive on our phone are typically retained for up to 60 days. However, we may retain specific messages for longer periods if they contain some vital information” to “Site-related SMS/MMS text messages or other, similar non-voice direct messages we send or receive via our phone are typically retained for up to 60 days. However, we may retain certain specific messages for longer periods if we have some outstanding reason to do so.” Updated GDPR and State Law bullet point on data portability to add “(starting in 2020, California residents may request this up to twice per year).”
  • September 20, 2018: Changed “SMS” to “SMS/MMS” and, under Data Retention, changed “other, similar direct messages we receive on our phone” to “other, similar non-voice direct messages we receive on our phone” for clarity. Under Legal Bases for Collecting and Using Information, struck “Under European Union (EU) data protection law.”
  • September 18, 2018: Added information about SMS texts to Data Retention and note about California’s information-sharing disclosures to Your Rights section (altering the heading of that section accordingly), rearranging some text and adding subheadings to the latter section. Updated Disclosure to clarify that we don’t share information for direct marketing purposes.
  • September 17, 2018: Updated Your Rights section to note that some of these rights apply to residents of some U.S. states, including California. Updated Disclosure section regarding security measures. Updated Information We Receive from Other Sources to note that we may received information from the applicable payment processor about people who make a payment to 6200 Productions.
  • September 16, 2018: Amended Embedded Content to change “The third-party host may also detect …” to “In some cases, the third-party website may also be able to detect …” and “This information is collected and processed …” to “Such information is collected and process …” Fixed error in link tags.
  • September 15, 2018: Added links to Gravatar and their TOS under Embedded Content and noted that Gravatar may now be integrated with WordPress.com. Noted that Embedded Content providers may also test for the presence of cookies or certain add-ons present on your device/browser, added the phrase “without limitation” to the examples of information those providers may gather, and noted that user agent information often reveals what type of computer or device you’re using.
  • September 14, 2018: Updated Embedded Content to include Gravatar and note that Google Fonts may cache data on your device browser as well as gathering certain information about your device.
  • September 13, 2018: Updated Embedded Content to note that there may be PayPal-served content on the administrative dashboard. Struck the item in that section about Google Drive and Amazon Web Service embedded graphics, which have now been removed. Clarified WordPress data-collection language, including noting that back-end content may be loaded from several domains owned by WordPress.org (e.g., s.w.org, ps.w.org, and ts.w.org).
  • September 12, 2018: Updated Embedded Content to include remotely served Google Drive and Amazon Web Services graphics. Clarified that some back-end administrator components also embed YouTube videos.
  • September 10, 2018: Added link to AboutCookies.org under Cookies. Updated links to Google Privacy Policy and added YouTube to the list of Embedded Content.
  • September 9, 2018: Further clarified Cookies section to better explain cookie duration. Updated Cookies and Online Tracking to better explain how to change your mind about Google Analytics.
  • September 8, 2018: Updated Cookies and Online Tracking to add Google Analytics opt-out cookie. Renamed the button to access privacy/cookie settings from “Change Your Privacy Preferences” to “Access Your Privacy and Cookie Preferences” for clarity and added that button here rather than simply a link to it. Updated Comments section to include note about saving your information with cookies for future comments and fix some unclear language about comment notifications.
  • September 7, 2018: Further amended Cookies to clarify cookie durations.
  • September 6, 2018: Updated Embedded Content with a link to Yoast’s GDPR page. Updated Cookies to better explain how you can find out about the specific cookies the site uses. Added WordPress to Embedded Content list.
  • September 5, 2018: Updated links to external privacy policies/statements (including adding links to the Google Privacy Policy); updated the ownership descriptions for BootstrapCDN/MaxCDN (which are now part of StackPath), DreamHost, and T-Mobile; added a smattering of ® symbols throughout; hyphenated “back-end” for editorial consistency; and fixed some inconsistent capitalization and other minor editorial issues. Clarified the duration of some cookies in Cookies section.
  • September 4, 2018: Updated Embedded Content to indicate that some backend (administrative dashboard) features may be served by Yoast.
  • September 1, 2018: Updated Disclosure to note that the stipulations on selling/transferring the site or going out of business also apply to our death or incapacity (in which case our applicable heirs, successors, and/or assigns might acquire the site’s assets, including visitor information). (Some of the new language is again from recent versions of the Automattic privacy policy noted in the preamble.)
  • August 18, 2018: Added additional information to Cookies and Data Retention regarding cookie duration.
  • August 15, 2018: Updated Security Scans, Comments, and Contact Forms to note that emails, including comment or contact form notifications, may also be scanned by our security tools for spam or malware. Added a note to Disclosure about Avast, the current provider of some of our security, antivirus, privacy, and administrative tools, including a link to their privacy policy. Minor tweak to Security Scans to note that Sucuri “can detect security vulnerabilities and some forms of malware by scanning the files and public areas …”
  • August 14, 2018: Updated Data Retention to clarify retention of log and scan result data, email alerts, and notifications. Updated Disclosure to note that we may share information that’s already publicly available.
  • August 13, 2018: Updated Server and Error Logs to note that the website also keeps logs to record your consent to the Privacy Policy, other legal terms, and/or to our gathering certain types of personal information. Added “where applicable” to the use of information (making it, “We, or where applicable our web host, may use …”). Also added a note about retention of consent logs to Data Retention. Updated Security Scans to note that we also use various measures to secure our local and/or offline systems, devices, and data against malware and other security threats.
  • August 12, 2018: Updated Comments to add “without limitation” to the examples following “… may use the information in and associated with your comment …” and note that comment notification emails may include the website/URL you listed in your comment. Updated that section and the similar language in and Contact and Image Authorization Forms to drop the definite article (making it “… may use information in and associated with your comment …”). Added a mention of the email notifications for comments to the applicable point under Disclosure. Updated the language about the Google Analytics opt-out browser add-on to emphasize that separate conditions may apply to its use.
  • August 11, 2018: Updated Security Scans to note that our security measures may automatically block certain suspicious actions or queries. Updated Cookies section to clarify that embedded third-party content may use cookies. Minor edit in Disclosure section: changed “third-party vendors” → “third-party vendors or service providers” (and “vendors/service providers”) and added “(without limitation)” to the list. Updated Comments section to reiterate that we take no responsibility for what third parties do with any personal information contained in posted comments.
  • August 10, 2018: Updated Comments section to explain that the website may perform automated tests on comments to filter spam and comments left by bots. Rearranged and made some minor amendments to the text of that section for clarity, and changed “By posting a comment …” to “By submitting a comment …” Updated both Comments and Contact Form sections to explain that we may use data associated with comments and Contact Form submissions to record your acceptance of the Privacy Policy and other legal terms, and that our web host and/or mobile carrier may scan the notification emails associated with comments or Contact Form submissions for spam or malware. Made some other minor clarifications to the Contact Form section and changed “we may record that comment for our internal reference …” to “we may record that comment offline for our internal reference …” for clarity. Clarified the language in Security Scans about our web host/mobile carrier scanning emails for spam and malware. Clarified and expanded Data Retention section. Added links to the DreamHost and T-Mobile privacy policies to the Disclosure section for ease of reference. Added an item to Disclosure about situations where we are contractually obligated to disclose information related to an investigation or dispute. Made the capitalization of “Contact Form” more consistent. Made some minor tweaks to Legal Bases for Collecting and Using Information and expanded Information We Receive from Other Sources.
  • July 26, 2018: Minor editorial revision: changed “Google” or “Google Inc.” to “Google LLC” where applicable.
  • July 16, 2018: Updated description of user agent information and that it typically includes browser settings such as language preferences.
  • July 15, 2018: Streamlined Embedded Content section to make it clearer and less repetitive and strike some language not applicable to the current 6200 Productions website.
  • July 14, 2018: Further adjustments to preamble wording. Minor editorial corrections.
  • July 13, 2018: Clarified some language to make clearer that this privacy policy applies ONLY to the 6200 Productions website.
  • July 12, 2018: Clarified log retention periods based on a response from Sucuri. Removed inadvertently duplicated section and fixed some minor formatting problems. Updated Notice to Parents and How to Reach Us. Minor update to data retention language.
  • July 11, 2018: Clarified how long we retain logs and that some security audit logs may be retained by us or Sucuri for longer than 30 days. Added notes about our web host and mobile carrier conducting security and anti-spam scans of email, and clarified Disclosure of Personally Identifying Information to note that (obviously) our mobile carrier may manage site-related texts as well as emails. Clarified Notice to Parents language.
  • July 10, 2018: Clarified that, obviously, our and our web host’s security scans look for the presence of potentially malicious code. Noted that the admin login page sets cookies and made minor clarifications to the Security Scans section.
  • July 4, 2018: Clarified that we may also use information from comments or the contact form for the other purposes outlined in Disclosure of Personally Identifying Information. Noted that we may add or alter filenames and/or metadata to indicate the provenance and attribution of images or other content (as well as retaining any personal information that might already be contained in that content).
  • June 24, 2018: Clarified that comments and contact form submissions may record your browser’s user agent information (browser and operating system type/version) as well as your IP address. Changed description of user agent info from “browser type/version and operating system” to “browser and operating system type/version” throughout for clarity.
  • June 21, 2018: Noted in Comments and Contact Form that we may use information associated with your message to verify your identity as well as confirming that you’re not a bot.
  • June 19, 2018: Added comments to Disclosure of Personally Identifying Information, for completeness.
  • June 18, 2018: Updated Comments section to clarify that notifications emailed to the administrator include your IP address, a point inadvertently dropped in an earlier revision. Updated Comments and Contact Forms sections to clarify that we may use your information to protect our accounts, systems, and devices (as well as the website itself) against spam, fraud, abuse, or electronic attacks. Fixed an editorial error in Contact Forms (which was supposed to say “your submission” rather than “your comment”)
  • June 16, 2018: Updated Disclosure of Personally Identifying Information section to note that we may disclose personal information to appropriately credit people for the use of their content or intellectual property. Updated Data Retention to note that we also retain dispute-related data indefinitely. Added note at the top clarifying that this policy does not apply to any third-party websites linked here.
  • June 8, 2018: Updated Disclosure of Personally Identifying Information section to clarify that it refers to information about website visitors or gathered through this site. Added note about disclosure to Information We Receive from Other Sources section. Minor editorial corrections.
  • May 30, 2018: Minor editorial clarification in Security Scans: “That alert would typically include the unauthorized visitor’s IP address, browser type/version, and possibly their operating system …” –> “That alert would typically include the unauthorized visitor’s IP address and possibly their user agent information (browser type/version and possibly operating system) …”
  • May 26, 2018: Updated Security Scan and Disclosure sections to reflect current Sucuri terms. Updated Google Analytics section. Wording clarification to Embedded Content. Added link at the top to this revisions list.
  • May 24, 2018: Various minor clarifications, including revised Cookies, Security Scan, Data Retention, and Revisions language and the removal of Other Information You Provide to Us.
  • May 23, 2018: Updated Comments and Comment Form sections. Various minor text edits. Clarified Security Plugins section and renamed it Security Scans. Minor amendments to Server and Error Logs to correspond with these changes. Temporarily deleted Google Analytics opt-out while finalizing appropriate settings.
  • May 22, 2018: Added name of mobile carrier, minor editorial corrections. Updated http links to https.
  • May 21, 2018: Clarified embedded content language, adding Cloudflare, and added note about Sucuri scanning. Corrected URI for the Automattic links to https. Updated cookie language. Added Google Analytics opt-out.
  • May 20, 2018: Added further clarifications, including location and mobile carrier notes. Fixed grammatical and formatting problems, eliminated duplicate text.
  • May 19, 2018: Extensive clarifications and some rearrangement of text for ease of reading. Added GDPR information (based in part on latest Automattic terms effective May 25, 2018). Changed age limit to 18.
  • May 10, 2018: Changed age limits from 13 to 16.
  • May 1, 2018: Clarified that the Disclosure of Personally Identifying Information section applies to information gathered through this website or its associated social media pages.
  • April 11, 2018: Updated Online Tracking section to note that as of May 25, 2018, Google Analytics will automatically delete user and event data after 26 months. Also clarified that we have NOT enabled the User-ID tracking settings and that as of April 11, 2018, we have disabled the Users metric in our Google Analytics reports.
  • February 11, 2016: Corrections to recent revisions list. Added note to Comment Form section: “This information may also be stored in archives and backup files created by us or our web host.”
  • January 13, 2016: Added note to preamble clarifying that variations in text style have no legal significance.
  • January 8, 2016: In Disclosure of Personally Identifying Information, changed “contractors, business partners, and affiliated organizations …” –> “contractors, service providers, business partners, and affiliated organizations …” and “Some of those contractors and affiliated organizations may be located … –> “Some of those contractors, service providers, business partners, and affiliated organizations may be located …”
  • January 7, 2016: Added BootstrapCDN info to Embedded Content section. Updated Server and Error Logs: “(such as, but not limited to, the IP address and in some cases the browser type and referring site, if any)” –> “(such as, but necessarily not limited to, the IP address; the user agent information supplied by the browser, which typically includes the browser type/version and operating system; and in some cases the referring site, if any)” and added “to improve the functionality of the site” to the list of uses.
  • January 6, 2016: Clarified previous revision information. ETA: Slight rewording of Google Analytics information (“and the date and time of each visit” –> “and the date, time, and length of each visit”). Moved the link to the Google Analytics opt-out plugin from the Opting Out section to the Online Tracking section and amended Opting Out text accordingly. Amended Server and Error Logs: “such as the IP address” –> “such as, but not limited to,”. ETA: In Embedded Content section, changed “6200 Productions does not collect, receive, or have access to any user data related to these fonts” –> “6200 Productions does not collect or receive any user data related to these fonts” and changed “to learn more about how Google uses this information” –> “to learn more about what information Google collects and how they use it”. Struck the word “layout” in that paragraph.
  • January 2, 2016: Clarified Comments section to note that we will assume you are authorizing us to publish any information you include in a comment you post (ETA: including the name/screen name you supply). (This really should be obvious, but we note it here for the avoidance of doubt.)
  • December 31, 2015: Editorial corrections.
  • December 29, 2015: Editorial corrections. Clarified that this entire policy is available under CC BY-SA 4.0 and clarified licensing language. Amended Contact Form policy: “we will not release your personally identifying information …” –> “we will not release personally identifying information associated with your message or submission …” Disclosure of Personally Identifying Information: “will not publish or release personally identifying information …” –> ” will not publish or release personally identifying information associated with your message or comment …”
  • December 28, 2015: Added note about Automattic revision history; editorial corrections. Clarified licensing language
  • December 25, 2015: Editorial correction.
  • December 24, 2015: Added link to Automattic Inc. main site. Reworded Server and Error Log language: “As part of their normal operations, 6200 Productions’ web host (which is located in the United States) and the security systems of this website automatically generate access and error logs” –> “Like most websites, the 6200 Productions site and our web host (which is located in the United States) maintain various logs”.
  • December 23, 2015: Minor change in Server and Error Log: “to block spam and unauthorized “hotlinking” to … –> “to block spam and hotlinking or other unauthorized use of …” Editorial corrections.
  • December 22, 2015: Editorial and formatting changes; added more detailed recent revision list. Clarified licensing language.
  • December 21, 2015: Minor editorial changes. Clarified licensing language.
  • December 19, 2015: Clarified language regarding use of information related to comments and form submissions. Updated language clarifying that log information may be used to prevent hotlinking and/or electronic attacks.
  • December 16, 2015: Updated language regarding use of personally identifiable information related to comments and form submissions.
  • December 10, 2015: Clarified that Google Fonts servers are located in the U.S. Added credits to note about WP DoNotTrack.
  • December 9, 2015: Clarified Server and Error log information. Editorial changes, including rearranging some sections. Editorial and formatting changes.
  • October 23, 2015: Added “and/or” to Disclosure of Personally Identifying Information stipulations.
  • October 10, 2015: Editorial and formatting changes. Clarified Online Tracking section and noted that Google Analytics servers are located in the U.S.
  • August 24, 2015: Added Server and Error Logs information; editorial changes. Changed “court order” to “court order or other government order” in Disclosure of Personally Identifying Information. Added bankruptcy to Ownership Transfers. Updated license from BY-SA 2.5 to 4.0.

Please contact us if you need information on earlier revisions.


Updated: November 20, 2019 — 3:02 am