Privacy Policy

Thank you for visiting Ate Up With Motor. This Privacy Policy explains what personal information we may gather through and/or in connection with this website (and/or, where applicable, related services such as the ateupwithmotor.com email addresses, except where we publish a separate private policy applying specifically to one or more of those services) and how we use that information. Please read this policy carefully. By using the Ate Up With Motor website and/or its related services, 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, December 11, 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.

You can also jump directly to the Financial Transactions Policy section.

Please note that your use of any third-party websites or services, including those linked from Ate Up With Motor 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. (The (currently deactivated) Ate Up With Motor Facebook® Page had its own privacy policy. Here is the archived version of that policy.)

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 purposes of this Privacy Policy, the terms “we,” “us,” and “our” shall be deemed to refer to Aaron Severson dba Ate Up With Motor, a U.S. citizen based in Los Angeles, California. We, along with our web host, DreamHost® (which also hosts the mail servers for our ateupwithmotor.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 originally 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 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 on you in three ways: automatically through this website; if and when you 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, user feedback forms, and the contribution button in the “Support Ate Up With Motor” box); 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 conduct research into the subjects of our articles, to better understand how (and how many) people access our content, to safeguard the integrity of this website and its data, to troubleshoot technical problems, and to appropriately respond to your inquiries regarding our work; or
  6. You have given us your consent.

Notice to Parents Regarding Children Under 16

The Ate Up With Motor website is not intended for and should not be accessed by children under 16. 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 16 (e.g., an email message, contact form submission, or comment), it is our policy to promptly delete such information or, where complete deletion is impossible or not practically feasible, to take whatever steps we reasonably can to de-identify or anonymize that information.

If you have questions, if you are a parent or legal guardian and believe that Ate Up With Motor may have collected personal 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 Sectigo (formerly Comodo CA), a commercial certificate authority (CA). 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.

When you access this website, your web browser may check whether the Ate Up With Motor certificate is valid by briefly connecting to the servers of the Sectigo public 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 those 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). Sectigo may log and use such data for operational, troubleshooting, and security purposes and/or in compiling de-indentified, aggregated statistics, as described in the Sectigo Privacy Policy.

Browser Tests

Each time you visit the Ate Up With Motor 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. Ate Up With Motor 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 Ate Up With Motor 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 Ate Up With Motor, 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 its web analytics service.)

When you first visit the Ate Up With Motor website, you’ll be asked if you consent to Google Analytics tracking.

Google Analytics is 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.

Ate Up With Motor 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.

Ate Up With Motor 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 have several options for opting out:

  1. Press the “Disable Google Analytics Tracking” button in the right sidebar or here: Disable Google Analytics Tracking. This will place a cookie on your device’s browser to prevent Google Analytics from tracking you on Ate Up With Motor. (This is a “persistent” cookie that will normally remain on your device for as long as your browser settings permit. Please note that the opt-out cookie only works on the Ate Up With Motor website, not any other website using Google Analytics.)
  2. 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.”
  3. Use your web browser to delete the ateupwithmotor.com cookie called cookieconsent_status (or all ateupwithmotor.com cookies). This will cause the analytics banner to reappear, at which point you can click “Disable Tracking.”

If you have any questions about the above methods or need additional assistance, please contact us via the Contact Form or by emailing admin (at) ateupwithmotor (dot) com.

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

Until June 3, 2019, Ate Up With Motor also used Majestic® SEO, a service of Majestic-12 Ltd., to analyze backlinks to this website. (See the Majestic SEO website for more information on this service. We closed our account on June 3, 2019.) Majestic-12 does not normally gather personal information about individual site visitors — they analyze hyperlinks and web page titles — but may occasionally collect incidental personal information; for example, the service might collect an individual’s name if the name is included in the title or URL of a particular article. You can learn more about what kind of information this service uses in their GDPR Compliance Statement. (Please note that where they refer to “customers,” they’re referring to account holders, which in this case meant Ate Up With Motor rather than you as a site visitor.)

Server and Error Logs

Like most websites, Ate Up With Motor 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; accesses the FTP folder(s); 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 Ate Up With Motor 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

Ate Up With Motor 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, data published in comments, or data contained in user-supplied images (see “Data in Submitted Images” below). 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 ateupwithmotor.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 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 certain incoming voice calls and/or text messages 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, Ate Up With Motor 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 to potential advertisers). However, such reports will not contain any personally identifying information on Ate Up With Motor visitors. Ate Up With Motor does not disclose personally identifying information other than as described in “Disclosure of Personally Identifying Information” below.

Embedded Content

Certain content on Ate Up With Motor, 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 Ate Up With Motor.

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 Ate Up With Motor 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 Ate Up With Motor 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.
  • The payment button that appears on the Ate Up With Motor website, and similar payment or donation buttons that some plugins place on the administrative dashboard, 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.) See “Financial Transactions” below for more information on our collection of transaction-related data. Note: You can now hide the payment button that appears in the “Support Ate Up With Motor” box (but not the donation buttons on the administrative dashboard) by disabling the PayPal Buttons cookies using the Privacy Tools. (This is still an experimental feature; if you have any problems with it, please let us know!)
  • 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.
  • 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. Some versions of Yoast SEO plugin have incorporated 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.

Ate Up With Motor 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.

Ads on Ate Up With Motor

As of July 26, 2013, advertisements (including sponsored links) appearing on Ate Up With Motor are served by us — that is, the advertisement content resides on our website server along with our other content.

As of July 26, 2013, we do not permit our advertisers to use scripts or cookies to collect information about you while you are on the Ate Up With Motor website. However, if you click through an ad to an external website, that website may collect personal information about you as described in the site’s privacy policy.

You may find additional information on our advertisers’ individual privacy policies at the following links:

Information You Provide to Us

If you send us money, contact us via the feedback forms, or interact with the site in certain other ways, we will collect various personal information that you provide to us. The type and amount of information, and what we do with it, will depend on the context, as described below.

You can refuse to supply personally identifying information, although doing so may prevent you from using certain functions, such as comments.

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.

Financial Transactions Policy

The following policy applies to financial transactions involving Ate Up With Motor.

Transaction-Related Information Gathering

If you make a payment to Ate Up With Motor, such as the purchase of advertisements or a contribution made via the payment button in the Support Ate Up With Motor box, we will record your name, company name (if applicable), address and contact information, and any other personal or payment information necessary to complete your transaction. We retain all transaction-related information for bookkeeping, tax reporting, and legal compliance purposes. This also applies to any tax documents you provide to us (e.g., Form 1099-MISC) or that we otherwise receive in connection with your transaction(s) with us.

If your payment is via PayPal® (including contributions made via the payment button in the Support Ate Up With Motor box), the transaction will be subject to PayPal’s User Agreement, Privacy Policy, and any other applicable PayPal policies or requirements. (Please note that these may differ depending on where you are.) PayPal may use cookies and/or “web beacons” (such as so-called “tracking pixels” and “pixel tags”) in the payment button and/or in the shopping cart to collect and track data about users. Ate Up With Motor does not have access to user data gathered by PayPal except for the information we receive in connection with a completed PayPal transaction, as described below.

When you make a payment or contribution to us via PayPal, Ate Up With Motor receives a standard transaction report (which is sent to us via email as well as being stored in our PayPal account) that contains various personally identifying information, including (though not necessarily limited to) your name, email address, mailing address, the date and amount of your payment, whether or not you are a Verified PayPal user, and any notes or additional instructions you provided. This report does NOT include your bank account or credit card numbers — PayPal does not provide and we do not have access to the credit card or bank information you use with your PayPal transactions. As with other types of transactions, Ate Up With Motor retains copies of these transaction reports for bookkeeping, tax reporting, and legal compliance purposes.

Please note that most cases, we must retain this transaction-related information even if we refuse and/or refund the applicable transaction.

Taxes

For certain types of transactions, we may be required to collect tax (such as sales or use tax) from you and pay it directly to the applicable tax agency. Please note that you may owe tax (e.g., sales/use tax, VAT, or other tax) on transactions with us even if we do not collect such tax from you. Any applicable taxes you may owe that we do not collect from you are your sole responsibility.

Refunds and Returns

Advertising Purchases: You may cancel your ad for a full refund within five days of your payment. If you choose to cancel your ad after five days but prior to the expiration date, we will credit the prorated remainder of the commitment period toward a future ad, but cannot provide a cash refund except where we are required to do so by the applicable payment processor(s) and/or financial institution(s) or as otherwise required by law. Notwithstanding the foregoing, we reserve the right to refuse and/or refund any individual advertising purchase or purchases at our sole discretion.
Contributions: You may request a full refund for any contributions to the site made via the payment button in the Support Ate Up With Motor box on this website within five days of your payment. After five days, contributions are nonrefundable except as otherwise required by the applicable payment processor(s) and/or financial institution(s) or otherwise required by law. Notwithstanding the foregoing, we reserve the right to refuse and/or refund any individual contribution or contributions at our sole discretion.
Other Purchases: Purchases of goods or services other than advertising are fully refundable prior to the delivery by us of the applicable good(s) or the performance by us of the applicable service(s). In the event you purchase tangible good(s) from Ate Up With Motor (e.g., a printed book), you may return the purchased good(s) for a full refund, less any applicable shipping costs, within 21 days of the date of your payment or the period allowed by the applicable payment processor(s), whichever is greater. Purchases of digital goods or services other than advertising (e.g., the purchase of an ebook) are nonrefundable once the applicable good(s) or service(s) have been delivered or performed (as applicable) by us, except as otherwise required by the applicable payment processor(s) and/or financial institution(s) or otherwise required by law. Notwithstanding the foregoing, we reserve the right to refuse and/or refund any individual purchase or purchases, and/or any applicable shipping costs, at our sole discretion.
Other Types of Transactions: For transactions that do not fit any of the above categories, eligibility for refunds or returns shall be determined on a case-by-case basis and shall be at our sole discretion, except as otherwise required by the applicable payment processor(s) and/or financial institution(s) or otherwise required by law. We reserve the right to refuse and/or refund any individual transaction at our sole discretion.

Information Sharing

By making a payment or contribution to Ate Up With Motor (whether by check, money order, via PayPal, or by any other means), you grant us express permission to disclose information associated with your transaction(s) with Ate Up With Motor, including copies of any applicable checks, the PayPal transaction reports described above, shipping records (if any), and/or (where applicable) any related tax documents:

  1. To the applicable common carrier or shipping agency, in the event we must mail, ship, or deliver anything to you in connection with your transaction; and/or:
  2. To our legal counsel, accountant/bookkeeper, tax preparer, and/or tax attorney, as we deem reasonably necessary to our routine business operations and/or for our legal protection; and/or:
  3. To our applicable payment processor(s) and/or bank(s)/financial institution(s); their legal counsel, auditors, and/or fraud protection services (for example, if we must provide information for a dispute or fraud investigation); and/or as otherwise required by our legal agreements with said payment processor(s) and/or bank(s)/financial institution(s); and/or:
  4. To any applicable federal, state, local, or other tax agency (whether within or outside the United States), where we deem it reasonably necessary to ensure our compliance with applicable tax laws and/or regulations (e.g., to calculate or estimate applicable tax rates and/or in connection with tax returns, filings, withholding, and/or estimated tax payments), or in connection with audits or other official investigations; and/or:
  5. As otherwise required by law (e.g., to comply with applicable government reporting or disclosure requirements, such as customs inspections; in connection with an audit or official investigation; or if we have received a subpoena or court order requiring us to disclose certain information); and/or:
  6. As otherwise described in “Disclosure of Personally Identifying Information” below.

By making a payment or contribution, you also grant us express permission to contact you via email or postal mail to complete or acknowledge your transaction and/or to address questions related to your transaction(s) with us.

Comments and Personal Information

If you post a comment on Ate Up With Motor, the 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 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 Comment Policy section of the Terms of Use. Naturally, this means that when your comment is published, the name/pseudonym you provided and any personal information you included in the text of 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 article you commented on. The contents of published comments may also appear in search results of the website’s search function.) If your comment includes a photo or other image, any EXIF information or other metadata contained in the image file may also become publicly accessible. (See “Data in Submitted Images” below.) Once your comment is published, Ate Up With Motor cannot control and takes no responsibility for what third parties may do with any personal information you may have included in the comment and/or image!

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 Ate Up With Motor 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 contact us via email (to admin (at) ateupwithmotor (dot) com), by using the Contact Form, or by leaving a comment elsewhere on the site asking us to disable the notifications or remove that comment.

Otherwise, Ate Up With Motor may record and use personal information in and associated with your comment (including, without limitation, the IP address, email address, and user agent information) to 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 relevant legal terms; use, record, manage, and where applicable appropriately credit you for any corrections, suggestions, information, and/or permissions you offer to us (for instance, if you suggest a useful resource or indicate that you are the owner of a car we’ve previously seen or photographed, we will usually record that fact in our notes); 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) ateupwithmotor (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 you delete your comment, copies of the original comment and its associated information may remain 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 (and any attached image(s)) may already have been accessed or used by third parties during the time the comment was publicly visible, which is beyond our control.

Contact and Image Authorization Forms

If you contact us via any of the feedback forms, including the Contact Form or Advertise with Us form, or if you submit an Image Authorization Form or Do Not Sell My Personal Information Opt-Out Form, we will record any data you enter into the form (including your name and email address) as well as the date and time of your submission, your Internet Protocol (IP) address (which may reveal your geographical location and in some cases also your Internet service provider), the date and time of your submission, and in some cases 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 the form, including your screen name, the email address you provided, and your IP address, will be automatically emailed to the site administrator.

When you press the “submit” button on any of our forms, our system will automatically send an email acknowledgment, including a copy of your message or submission, to the email address you provided. If you do not wish to receive future email messages from us, you may contact us via email (the simplest way is to reply to the notification email and type the word “REMOVE” in the subject line of your reply) or via a comment (although see the note above regarding comment notifications). Please note that if you submit a NEW message via one of the contact forms, you may still receive an automated response.

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 by us, our web host, and/or our mobile carrier.

If your message includes a question, correction, suggestion, or request for technical support, we will record that information for our internal reference and records. In some cases, we may also elect to publish your inquiry or excerpts of it on the Ate Up With Motor website or our associated social media accounts 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 (if applicable) you supply, such publication will not include your email address, mailing address, IP address, or other associated personal information unless you specifically authorize us to to so or as otherwise described in “Disclosure of Personally Identifying Information” below.

If we have published your inquiry as described above and you wish us to amend or redact any personal information it may include (for example, to remove your name and substitute a pseudonym), we will make all reasonable efforts to accommodate your request provided that it does not infringe on the rights of others or attempt to impersonate some other individual or organization.

Otherwise, Ate Up With Motor may record and use personal information in and associated with your form submission (including, without limitation, the IP address, email address, and user agent information) 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 and 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 relevant legal terms; use, record, manage, and where applicable appropriately credit you for any corrections, suggestions, information, and/or permissions you offer to us (such as a license to use your image or other content); and/or as otherwise described in “Disclosure of Personally Identifying Information” below.

Other Inquiries, Messages, and Support Requests

If you send us a message related to Ate Up With Motor via email, via one of our associated social media accounts/pages, or via some other third-party website or service (e.g., our account on an external photo hosting site or instant messaging service), we may collect the following personally identifying or potentially personally identifying information:

  1. Any information you provide to us as part of your message and/or its attachments, if any (which, if you send us images, may include the types of information described in “Data in Submitted Images” below), and
  2. Any other information in or associated with your message (including, without limitation, the metadata that typically appears in the headers of an email message, which may include information such as your return email address; the name and IP address of your email server; the user agent and sometimes the IP address from which you sent the message; the name(s) and certain contact information of the Internet service provider, mail host, and/or registrar for your email domain; various message routing information; and other technical and security-related details), and
  3. For messages sent via a third-party website or service:
    1. Any information the applicable third-party website or service provides to us in conjunction with your message (e.g., your username and profile picture on that website/service), and
    2. Any publicly visible information in your profile on that website or service.

As noted in the sections above regarding comments and feedback form submissions, if your message includes a question, correction, suggestion, or request for technical support, we will naturally record that information for our internal reference and records. In some cases, we may also elect to publish your inquiry or excerpts of it on the Ate Up With Motor website or our associated social media accounts 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 (if applicable) you supply, such publication will not include your email address, mailing address, IP address, or other associated personal information unless you specifically authorize us to to so or as otherwise described in “Disclosure of Personally Identifying Information” below.

If we have published your inquiry as described above and you wish us to amend or redact any personal information it may include (for example, to remove your name and substitute a pseudonym), we will make all reasonable efforts to accommodate your request provided that it does not infringe on the rights of others or attempt to impersonate some other individual or organization.

Otherwise, Ate Up With Motor may use the personally identifying or potentially personally identifying information in or associated with your message to respond to your inquiry or message; 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 this website and our accounts, systems, and devices against spam, fraud, abuse, or electronic attacks (for example, by blocking email and IP addresses associated with previous electronic attacks or spam); troubleshoot technical problems and improve the functionality of the site, its associated email systems/accounts, and/or where applicable our accounts or pages on third-party services/websites; 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); use, record, manage, and where applicable appropriately credit you for any corrections, suggestions, information, and/or permissions you offer to us (such as a license to use your image or other content); manage and, as applicable, publish any images you provide to us for use on Ate Up With Motor (see the “Use of User-Submitted Images” section of the Terms of Use or the Image Authorization Form, as applicable, and the “Data in Submitted Images” section below); and/or as otherwise described in “Disclosure of Personally Identifying Information” below.

If you send your message via social media or other non-email service, please be aware that some or all of this information may be transmitted to us via email, SMS/MMS text, or other message notification systems. As explained in “Security Scans” above, emails that you send to us — including notifications of messages sent via other sites or services — may also be automatically scanned for malware, spam, or other potential security issues by us, our web host, and/or our mobile carrier. If you send us a message via a third-party service or webmail account, that third-party provider may perform similar scans.

Please note that any messages you send to us via a third-party website or service are also subject to the applicable site/service’s terms and privacy policy, which are outside our control. This includes messages sent to our personal Google Gmail or Yahoo!® webmail accounts. (Although we now strive to avoid using those accounts for site-related business and have removed most email messages related to Ate Up With Motor from the Gmail and Yahoo Mail servers to offline archives, some site-related messages may occasionally be sent/received via and/or remain archived in those webmail accounts, which are subject to those services’ respective privacy policies. Gmail is a service of Google. (Gmail is a trademark of Google LLC.) Yahoo! is now part of Oath and subject to the Oath Privacy Policy. Until April 2018, Yahoo!/Oath also owned the photo-sharing service Flickr, on which we have an account and which we sometimes use to communicate with people who allow us to use their images on Ate Up With Motor. While Flickr now has its own privacy policy, messages we sent or received were previously subject to the privacy policies of Yahoo and later Oath. We initiated the closure of our Yahoo! account on November 11, 2019, although we retain our Flickr account.)

Also, keep in mind that on some third-party websites or services, certain means of contacting us (such as posting a comment on one of our photos on a social media page or photo hosting service) may be publicly visible; this obviously depends on the specific website/service and is typically beyond our control.

If we reply to your message, we will normally do so via the same email address or social media account/third-party service you used to contact us unless you indicate that you wish us to respond by some other means. However, if you have sent a site-related message to one of our personal (i.e., non-Ate Up With Motor) accounts or addresses, we typically prefer, to the extent possible, to forward the message to our applicable Ate Up With Motor account or address and respond from there instead.

Data in Submitted Images

Photographs and other images or media we collect for use on Ate Up With Motor and/or its related services — whether submitted by you in connection with a comment or Image Authorization Form; created by us; or obtained from some other source — may contain an assortment of personal information.

First, the recognizable likeness of any individual person in an image or video (and/or their recorded voice in a video or audio file) is usually considered to be personal information about that individual. The image might also include and/or allow us to infer other types of personal information. For example, if you submit a photo of yourself standing in front of your personal car in front of your home, the photo might show your face, your car’s license number, and the street address of your house, all of which would be considered personal information in at least some jurisdictions.

Second, digital files contain metadata (such as EXIF information) added by the camera or device that originally generated the file and/or by any software used to edit it, some of which may be personally identifying. At a minimum, metadata normally includes the filename, type, size, creation date/time, and the date/time of the most recent modification of that file. For digital photos, metadata typically also includes the make and model of the camera/device, camera and image settings (e.g., shutter speed, F-stop, color profile, whether the flash fired), and sometimes the type and version of any editing software used. Depending on the type of camera/device, the software used, and the individual settings, the metadata could also include other personal information, such as the photographer’s name and/or the location where the photo was taken, based on GPS coordinates (a common option on modern GPS-equipped cameras and mobile devices). The number of potential variations is too great to detail here, so you should consult the documentation and settings for your individual device.

Naturally, if you submit an image or other media file to us, you are providing us with any information contained in the image or media file and its metadata. When the image or media file is published on Ate Up With Motor, this information may be included, making it publicly available. Ate Up With Motor cannot control and takes no responsibility for what third parties may do with any personal information a published image/other media file or its metadata may contain.

If we use your photos and/or other media on Ate Up With Motor, we may also ADD metadata to the file(s) and/or alter the filename(s) to indicate your copyright and license information (e.g., “© 2018 John Doe; used with permission on Ate Up With Motor”). This helps us to keep track of the provenance of the media files we use, which may come from a variety of different sources.

We typically also gather additional information about the images we use and any subjects and/or settings they depict or illustrate so that we can correctly identify and describe them. This may include not only details about the car itself (such as its year, make, and model), but also potentially personally identifying information such as (without limitation) the license plate number, vehicle identification number, and/or other serial number(s) of a particular vehicle; other registration information (such as registration dates); and/or personal information about current or past owners, particularly if they include public figures such movie stars or famous race car drivers. If we know who currently owns a particular car/vehicle/object/property (which we frequently do not, unless you submit images of your own car or other property), we may also obtain the owner’s contact information.

Removing Personal Information from Images

If you submit an image or other media file to us, you are free to remove or redact any personally identifying metadata it may contain — and/or to obscure personal information in the image or media itself — prior to submitting it to us. (Certain types of metadata are necessary for an electronic file to function properly (such as the file type), but other metadata can be edited or redacted, either through your computer’s file system or by using appropriate editing tools.)

In some cases, we may be able, upon your request, to remove or obscure personal information from the images or media files you submit to us or from specifically previously submitted ones. However, please note that this is not always feasible: For example (but without limitation), if you submit a photo of you standing by your car near a well-known landmark, we could obscure your face and plate number, but we probably couldn’t remove the landmark from the background! Also, if the image is owned by someone else, we might need the rights holder’s advance permission to alter it.

If we remove or obscure information after an image or media file has already been published on the Ate Up With Motor website, copies of the original version (with personally identifying information intact) may remain for a time in cached pages and/or backup files created by us or our web host. Again, please keep in mind that any personal information contained in the earlier version of the image or media file may already have been accessed or used by third parties during the time it was publicly available, which is beyond our control.

If you have questions about image-related data, please contact us through one of the methods described in “Controllers, Questions, and How to Reach Us” below.

Other Information You Provide to Us

In some cases, you may provide us with personal information in connection with this website and/or its related services in ways not specifically mentioned above. For example (but obviously without limitation), if we meet you at car show or other public setting, we might talk to you about your vintage car, take pictures of the car for use in future articles, and/or jot down notes about it based on our conversation; naturally, such interactions may include a variety of personal information about you. If you send us a physical package via postal mail, it will likely include your mailing address as well as any information in the package 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.

Our use of personal information you provide to 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.

Acknowledgments of User Assistance and Information

If you provide us (whether via comment, contact form, email, or by other means) with significant assistance with Ate Up With Motor content (for example, if you supply images, suggest useful resources, or offer substantial factual corrections) or assist us in the resolution of a technical issue, we may elect to acknowledge you by name or applicable pseudonym, generally in the “Acknowledgments” or “Notes on Sources” section of the applicable article(s), unless you have specifically asked us not to or if the context of your communications with us reasonably suggests that you prefer not to be acknowledged or identified. This acknowledgment will be limited to your name/pseudonym and the nature of your assistance and will not include your email address or other personal information unless you expressly request that we publish such additional information. However, in some cases, certain personal information may be obvious or implicit in such an acknowledgment — for example, the nature of your assistance might indicate where you work, or identify you as the owner of a particular car.

In the event that you have received such an acknowledgment here or on Ate Up With Motor’s associated social media accounts and would like us to remove it, please contact us via email at admin (at) ateupwithmotor (dot) com or the Contact Form and we will promptly delete the applicable acknowledgment(s). If you wish to alter or correct the acknowledgment (for example, to replace a pseudonym with your real name or vice versa), we will make our best efforts to accommodate your request so long as it does not infringe on the rights of others or attempt to impersonate some other individual or organization.

Information We Receive from Other Sources

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

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, through the security components of the Microsoft® Windows® operating system, via the Mozilla Firefox browser, and/or through 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 routinely gather information about people involved in the auto industry as part of our research, which we may use and publish for journalistic purposes and historical documentation (including the creation of appropriate bibliographies and credits). Our research and writing process often involves discussing and sharing such biographical information with third parties such as subject matter experts, other automotive writers or historians, journalists, enthusiasts/collectors, librarians, and archivists, as well as looking up names and other relevant personal details in sources such as (without limitation) books; magazines; newspapers; films or other videos; audio recordings; and/or online or offline electronic resources such as search engines, library catalogs, websites, and/or databases. If you are or were involved with the auto industry, and/or are a public figure, some of the information we gather may be about you, your work, and your career. This may include images such as publicity photos or official portraits, and/or other media, such as (without limitation) videos, audio interviews, and/or podcasts. In some cases, we may look for your contact information so we can ask you questions related to our content, request an interview, and/or let you know about a content in which you were mentioned.

If we use an image or other content you have offered under a Creative Commons or similar license, we typically gather publicly available information about you for the purposes of properly attributing that content and otherwise complying with the applicable license terms. (Where appropriate, we sometimes do the same with content that is in the public domain in our jurisdiction, such as works created by U.S. federal employees in the context of their official duties.) This may include any creator information listed on the hosting service, archive, or repository from which we obtained the content as well as other relevant information we may find in various print or online sources.

Similarly, when we gather photographs and/or other images for our articles (including both images created by us and ones obtained from others), we may collect and record the names, and in some cases the contact information, of the owners of the cars/vehicles/objects depicted in those images (if we know who those owners are, which we frequently do not). We also typically gather information about the history and provenance of those cars/vehicles/objects (potentially including their license plate and vehicle identification numbers, if available/applicable) so that we can correctly identify and describe them. Such information may come from a variety of public and private sources and may sometimes include additional personal details about the car/vehicle/object’s past or current owners, if any, especially if they are or were public figures such as movie stars or famous race car drivers.

As noted in the “Financial Transactions Policy” above, if you make a contribution or other payment to Ate Up With Motor, the transaction report the applicable payment processor contains personal information about you; scroll up to that section for a description of what the transaction reports contain.

As noted in “Other Inquiries, Messages, and Support Requests” above, if you contact us via a third-party website or service, that site/service may provide us with additional information about you. For example, if you send us a direct message via a social media service, that service may automatically show us your profile picture and other publicly visible profile information along with your message.

Similarly, third-party websites or services may offer information or insights about people who interact with our Ate Up With Motor pages or accounts on those sites/services, such as sending us a notification if you view, share, or “Like” some content we have posted there. The nature of that information depends on the specific site/service.

In some cases, we may receive information about a site visitor from a different individual, whether intentionally or inadvertently. For example, an Ate Up With Motor reader might provide us with your contact information as an individual or firm that could assist us with research or images for an article, or submit a photo they have taken that depicts your car and/or that includes you in the background.

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, particularly people who contact us or leave comments on this website and/or its associated social media accounts. For example (but without limitation), if you send us a message via one of the feedback forms, we might look up your name in a search engine and/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.

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 the Ate Up With Motor website and/or, where applicable, its related services (including any associated social media pages/accounts for which we have not published separate page/account-specific privacy policies):

  • As part of journalistic or historical accounts (and/or in the course of researching and writing same), if you are or were involved with the subjects of one or more of our automotive articles. For example (but without limitation), if you are an automotive stylist, engineer, or executive, your name, certain biographical and professional details, and/or other personal information may be included in our articles about one or more cars you worked on (and potentially also in the bibliographies and/or metadata of that content, e.g., in snippets and/or keywords intended to help search engines find and index the content). In most cases, this information is drawn from sources that were already publicly available at the time of writing, but it may also include information, corrections, clarifications, and/or additional details either provided by you or obtained from third parties (which may include images and/or other media such as publicity photos or official portraits, videos, and/or recorded audio interviews). As noted in “Information We Receive from Other Sources” above, our research and writing process routinely involves sharing and discussing this type of biographical information with third parties such as (without limitation) subject matter experts, other automotive writers or historians, journalists, enthusiasts/collectors, librarians, and archivists, as well as looking up names and other relevant personal details in online or offline electronic resources such as search engines and library catalogs.
  • Where that information otherwise 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). For example (but without limitation), if you are or were involved with the automotive industry and/or are a public figure, we might refer automotive writers, historians, or others interested in or researching related topics to published books or articles about your work, direct them to your official website, share details from your published memoir or official bio, critique or otherwise comment on your published works, and/or mention that we once saw you speak at a car show or other public event. (Obviously, in some cases, your contact information may be publicly available, e.g., on your official website or as part of your company bio.)
  • In the case of photographs in which you (and/or information such as your car’s license plate number) may be visible. Photos we use on Ate Up With Motor — many of which were taken in public places, and which are not necessarily created by us — may contain visible bystanders and/or potentially personally identifying information about individuals (such as their car’s license plate number), whether in the image itself and/or in image filenames, titles, and/or metadata (see the “Data in Submitted Images” section above for more about what the metadata may include). For various reasons, it is not always practical or even feasible for us to completely obscure visible bystanders or potentially identifying information in photos (for example, the license terms under which we use photos owned by others may not permit us to modify those images in such a way). In most cases, we have no reasonable way to identify such individuals or associate the photos in which they appear with other information about them. If you have recognized yourself (or your information) in a photo on Ate Up With Motor and would like us to obscure or remove it, please contact us!
  • To publish photographs or other images you provide to us for use on Ate Up With Motor, as described in the “Use of User-Submitted Images” section of the Terms of Use or the Image Authorization Form, as applicable, and the “Data in Submitted Images” section above.
  • To appropriately credit you for the use of your photos, fonts, themes/plugins, or other content or intellectual property — particularly where such credit is required by the applicable license terms. As noted in “Data in Submitted Images” above, this may include adding your copyright and license information to the applicable filename and/or metadata to ensure that the attribution is clear. Also, if the version of your content we receive 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 Ate Up With Motor may retain that information. If you want to modify or remove that information, please contact us!
  • To publish your submitted comments, as described in “Comments and Personal Information” 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.
  • In the form of “Acknowledgments of User Assistance and Information,” as described above.
  • As part of a public response to an inquiry or support request, as described in “Contact and Image Authorization Forms” and “Other Inquiries, Messages, and Support Requests” above.
  • 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 personal information related to Ate Up With Motor and/or its related services 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.) Representative examples of our 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 Sectigo SSL/TLS Certificate Authority service described in the “Certificate Authority Service” section above (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); the Electronic Frontier Foundation (EFF), which may collect information about our use of their browser add-ons and/or other privacy tools as described in the EFF Privacy Policy: Software and Technology Projects; 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, Google Safe Browsing, and Gmail services described above; 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 which we may search for and/or purchase research materials and/or other 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; data and/or document destruction/shredding services; 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); Flickr (a photo-sharing service — owned until April 2018 by Yahoo!®/Oath and now owned by SmugMug, Inc.; see also SmugMug’s Privacy Policy — on which we have shared some site-related images and which we use to communicate with some of the people who have allowed us to use their images on Ate Up With Motor); Facebook®, Twitter, and/or other social media sites on which we have or have had Ate Up With Motor accounts and/or pages (the separate privacy policy for the Ate Up With Motor Facebook Page is archived here); 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); PayPal® (which serves the payment buttons that appear on the site and processes some payments for us); and/or our bank(s)/financial institution(s) and/or other 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) social media services, our bank(s)/financial institution(s), our payment processor(s), or as otherwise described under “Financial Transactions Policy” above. For example, if we are involved in a payment dispute or if our payment processor suspects a payment we received may have been fraudulent, their terms of service may require us to provide relevant information to their investigators. Similarly, third-party services such as social media websites may compel us to provide information related to suspected violations of their terms of service.
  • 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 the information is de-identified, anonymized, redacted, and/or aggregated such that it could not reasonably be used to identify you.
  • If you have asked or authorized us to do so.
  • If we sell or transfer control of the Ate Up With Motor 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 information about individual site visitors (or users of the site’s related services). However, we do sometimes license our writing and/or images to third parties (and/or offer images or other content we have created or modified/adapted — such as this policy! — under Creative Commons or similar licenses). Also, the proprietor of this website is a freelance writer/editor, so we regularly research, create, adapt, present, publish, and/or perform perform content, independently and/or for third parties (e.g., writing original articles, automotive or otherwise, for magazines, or talking about areas of automotive history for audiovisual productions). In the event we incorporate your name and/or other relevant personal information about you into our written content and/or bibliographies, and/or their metadata; if your name and/or information is incorporated into content we create, adapt, present, publish, and/or perform in or for some other format or medium, and/or the metadata of such content; and/or if you and/or your information are somehow visible in certain of our images and/or present in their metadata, we may share, publish, license, sell, and/or otherwise disclose it in that context. If you have questions about this, please contact us through one of the methods described in “Controllers, Questions, and How to Reach Us” below.

(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 (but 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!)

Also, 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, Ate Up With Motor takes 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 Ate Up With Motor 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, FTP folder access records, 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.

With the exception of obvious spam, which we promptly delete, we typically retain posted comments and their associated data indefinitely unless the person who submitted the comment asks us to remove it; we opt to delete it for some other reason (for instance, if it appears to be a duplicate or was in response to a post that has been deleted); or it is inadvertently deleted due to some technical mishap. As noted in the “Comments and Personal Information” section above, even if a comment is deleted, copies may remain in our backup files or other internal archives. (For instance, if a deleted comment contained a correction for an article, we might retain a copy of that correction for our future reference.)

Similarly, if we publish an excerpt of a support request or other inquiry you’ve submitted (as described in “Contact and Image Authorization Forms” and “Other Inquiries, Messages, and Support Requests” above) or publish an acknowledgment of some assistance you provided for an article (as described in “Acknowledgments of User Assistance and Information” above), those references generally remain public indefinitely unless you ask us to remove or redact them or we remove the applicable post for some other reason. Again, they may remain in our records and/or backup files even if they are removed or redacted.

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

We also customarily retain indefinitely:

  • Most site-related email and form submissions, 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.) The same applies to most site-related messages that you send to us via third-party websites or services, although in such cases, we typically retain local and/or offline copies of those messages (e.g., message notification emails and/or texts) in addition to (or instead of) leaving them on the applicable third-party website/service. We may delete certain specific messages, emails, and/or file attachments if we have some compelling technical, legal, or other reason to do so (e.g., we believe the message/attachment came from a child under age 18, it appears to be corrupted, or we have agreed to delete it).
  • Information we receive through our Ate Up With Motor accounts/pages on social media, such as direct messages and notifications or insights telling us that people have viewed, shared, or commented on content we’ve posted on that service. With many social media services, such insights and notifications can’t be easily removed and may remain in administrator activity summaries or notification lists even if the applicable content is removed (and some content cannot be completely deleted if other users have shared it). For this reason, most of that information is normally retained indefinitely. (Although we initiated the deletion of our Facebook® account on December 11, 2018, we downloaded and retain for archival purposes an offline copy of our Facebook data as of that date, including the Ate Up With Motor Facebook page and its associated messages and other data.)
  • Our research notes and information on past, current, or possible future articles or content, which may include suggestions, corrections, or references that site visitors provide to us. (If you send us some useful resource for future articles, we naturally prefer to retain that information for later reference, especially if it’s a suggestion we’re not able to follow up immediately!) As explained above, if you are or were involved with the auto industry, and/or if you’re a public figure, our research notes may also include information about you and your career. Also, since the proprietor of Ate Up With Motor is a freelance writer/editor, we normally also 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 other writing and editing work, which may occasionally include certain information related in some way to this website.
  • The contact information of individuals with whom we repeatedly or regularly correspond regarding Ate Up With Motor and/or related topics — e.g., other automotive enthusiasts, writers, archivists, photographers, editors, or publishers.
  • Any names and/or company/domain names we’ve entered into our spell-checking dictionaries (which we retain for what we hope are obvious reasons!).
  • Photographs and other images, whether created by us, used on Ate Up With Motor under license/with permission, or in the public domain. Although we can and often do modify the images that appear on the Ate Up With Motor website, it is our customary practice to indefinitely retain offline copies and archival backups of both the modified and original versions of each image (including our associated work files and editing stages, if any) unless we have some compelling reason not to (such as a specific contractual or other legal obligation to destroy the originals) or we suffer some technical mishap with the applicable image files. Also, if we have contact information and/or other relevant data pertaining to the creator(s) and/or subject(s) of a particular photograph or image (e.g., the name and email address of a pictured car’s owner), we customarily retain that data for at least as long as we retain the image itself.
  • Information pertaining to our licenses/authorizations for the use of photos or other intellectual property owned by others, including image authorization or release forms, Creative Commons attribution data (if applicable), and any relevant contact information. For legal reasons, we must usually retain records of such authorizations indefinitely, even if the license has been rescinded/terminated or the applicable content has been removed from the Ate Up With Motor website.
  • Information pertaining to any financial transactions or legal agreements involving Ate Up With Motor (such as the purchase of advertising on the website, or if we authorize a third-party to reprint or reuse an Ate Up With Motor article or image(s), especially if we receive a fee for such license), as well as records of purchases or payments we make in connection with the website, such as phone bills or the purchase of research materials, which we must retain indefinitely for legal and accounting purposes. For similar reasons, if you give or loan us some non-monetary tangible item, such as a book or magazine, we generally prefer to retain information pertaining to that as well, just to be on the safe side. Our financial and legal records often necessarily include some personal data. For example (but without limitation), if we speak to you by telephone, your phone number will probably appear on our phone bills, and if we enter a legal agreement with you, that agreement will obviously include your name and contact information.
  • Information pertaining to site-related technical or legal questions. For instance, if you provide insights or advice on implementing a new site feature, or communicate with us to clarify some legally significant point (e.g., whether a particular use of your content is allowed by the license under which you have offered it), we customarily retain that information for our future reference.
  • Information pertaining to any site-related disputes.
  • Backups of the now-defunct Ate Up With Motor LiveJournal blog (ateupwithmotor.livejournal.com), saved circa 2008. (Previously, we also retained a backup of the database of this website as it existed immediately prior to our migration to the WordPress content management system in October 2013, but we deleted our last copy of that database on November 5, 2019.) These backups, which we retain for archival purposes, necessarily include visitor comments and some administrative data as of the dates they were created. If you have questions about the contents of these backups, please contact us.

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, transferring the data to offline storage for greater security 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 the applicable government data protection authority. (California residents will have a similar right 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 from the website 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 Ate Up With Motor 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. Also, at present, it is not capable of retrieving feedback form submissions.)

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 secure this website and its data.

Your California Privacy Rights

California Do Not Track Disclosure

Currently, Ate Up With Motor does not respond to Do Not Track browser settings.

Information-Sharing Disclosures (Shine the Light Law)

California Civil Code § 1798.83–84 (the “Shine the Light” law) gives California residents who have established business relationships with certain businesses the right to request information about those businesses’ disclosure of the customer’s personal information to third parties for direct marketing purposes.

The law defines “direct marketing purposes” as “the use of personal information to solicit or induce a purchase, rental, lease, or exchange of products, goods, property, or services directly to individuals by means of the mail, telephone, or electronic mail for their personal, family, or household purposes.” An “established business relationship” is defined as “a relationship formed by a voluntary, two-way communication between a business and a customer” that is either ongoing or was established with a purchase or other transaction within the past 18 months.

Under the Shine the Light law, if you are a California resident and have an established business relationship with a business subject to the law’s requirements, you may request, once per calendar year, an Information-Sharing Disclosure that details:

  1. What categories of personal information about you, if any, that business shared with third parties for direct marketing purposes in the preceding calendar year, and
  2. The names/identities and addresses of such third parties.

(The law does not require the business to reveal which specific pieces of information may have been shared, only the categories of information, as defined by the applicable statutes.)

Although we believe we are exempt from the requirements of § 1798.83–84, since we have fewer than 20 employees, we will nonetheless make every reasonable effort to provide you with such a disclosure within 30 days of our receipt of your request. To submit a request, please contact us through one of the methods described in “Controllers, Questions, and How to Reach Us” below.

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.
  • Not be penalized for the exercise of these rights.
  • 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 Ate Up With Motor 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 this 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.

Do Not Sell My Personal Information

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 Ate Up With Motor, 11100 National Bl. #3, Los Angeles, CA 90064.

If you have questions about this policy, you can contact us via postal mail to the address above, via email at admin (at) ateupwithmotor (dot) com, or via the Contact Form. If you are a California resident and wish to submit a privacy-related request under the CCPA, please use one of the contact methods shown on the Do Not Sell My Personal Information page, NOT the regular Contact Form!

Privacy Policy Changes

Ate Up With Motor 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:

  • December 11, 2019: In Notice to Parents Regarding Children Under 16, changed “if you are a parent and believe that Ate Up With Motor may have collected personally identifying information about your minor child …” to “if you are a parent or legal guardian and believe that Ate Up With Motor may have collected personal information about your minor child …”
  • December 3, 2019: Added EFF to the list of examples of third-party service providers under Disclosure. In the GDPR and State Law section, changed the sentence “EU individuals also have the right to make a complaint to a government supervisory authority, as will California residents beginning in January 2020” to “EU individuals also have the right to make a complaint to the applicable government data protection authority. (California residents will have a similar right beginning in January 2020.)” Added a link to the European Commission’s directories of national data protection authorities to that section.
  • December 1, 2019: Revised the Data in Submitted Images section to arrange the text in more logical order, add a subheading, note that it applies to other media files as well as images, clarify a number of points, and add an internal anchor link to the contact section. Fixed a typo in this list.
  • November 27, 2019: Under Disclosure of Personally Identifying Information, changed “Examples of such third-party vendors/service providers …” to “Representative examples of our third-party vendors/service providers …” Updated Embedded Content to note that only some versions of the Yoast plugin use Algolia search functions (which have reportedly been removed in newer updates), changing “The Yoast SEO plugin incorporates some search tools …” to “Some versions of Yoast SEO plugin have incorporated search tools …”
  • November 25, 2019: Further adjusted the language of the Information-Sharing Disclosures (Shine the Light Law) section for greater clarity. Updated Information We Receive from Other Sources to change “videos and/or recorded audio interviews” to “videos, audio interviews, and/or podcasts.”
  • November 24, 2019: In Security Scans, changed the phrase “flag the phone numbers of certain incoming voice calls …” to “flag certain incoming voice calls and/or text messages …”
  • November 23, 2019: Completely overhauled the Information-Sharing Disclosures (Shine the Light Law) section to more accurately describe the law’s requirements, better explain how to make a request, and clarify how we respond to such requests. Updated Information We Receive from Other Sources to note that the security components of the Microsoft Windows operating system may also supply blacklists and/or other security-related data, and added the words “via the” before the reference to Safer-Networking in the same paragraph for grammatical flow.
  • November 22, 2019: Under Information We Receive from Other Sources, changed “… looking up names and other relevant personal details in online or offline electronic resources such as search engines and library catalogs” to “… looking up names and other relevant personal details in sources such as (without limitation) books; magazines; newspapers; films or other videos; audio recordings; and/or online or offline electronic resources such as search engines, library catalogs, websites, and/or databases.” Updated the Disclosure of Personally Identifying Information item regarding information that is/was already publicly available (changing “For example, if you are or were involved …” to “For example (but without limitation), if you are or were involved …”; adding “critique or otherwise comment on your published works” to the enumerated examples; and changing “or mention …” to “and/or mention …”).
  • 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”). Under Disclosure of Personally Identifying Information, amended “For instance, if you are an automotive stylist, engineer, or executive, your name and certain biographical and professional details …” to “For example (but without limitation), if you are an automotive stylist, engineer, or executive, your name, certain biographical and professional details, and/or other personal information &hellip” and change “… perform content for third parties …” “… perform content, independently and/or for third parties …
  • 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). In Disclosure of Personally Identifying Information, made some minor adjustments to the passage regarding Google services, for greater 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 retain information pertaining to privacy-related requests, to the extent required by applicable law and/or regulation.” Revised Controllers, Questions, and How to Reach Us to note that privacy-related requests for California residents should be submitted through the form on the Do Not Sell My Personal Information form rather than the regular Contact Form.
  • 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.”). 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, changed “we may disclose, publish, license, and/or sell it in that context” to “we may share, publish, license, sell, and/or otherwise disclose it in that context.”
  • 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: Renamed Information We Gather Automatically “Information We Collect Automatically. Added a new Certificate Authority Service subsection to that section and added Sectigo (formerly Comodo CA) to the list of examples of third-party service providers under Disclosure. 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. Further refined the Certificate Authority Service language and added another example to Other Information You Provide to Us, refining some language in that section (changing the phrase “Our use of these or other types of personal information you provide to us …” 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 Information We Receive from Other Sources to note that we may sometimes look for your contact information so we can ask you questions related to our content, request an interview, and/or let you know about a content in which you were mentioned. (This is not a new practice, but we thought it worth stating more expressly.) Updated Other Information You Provide to Us to add “in connection with this website and/or its related services” after “you may provide us with personal information.” Also revised the first example presented, added “(but obviously without limitation)” after “for example,” and changed “these or other types of information” to “these or other types of personal information.” 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 12, 2019: Updated the Embedded Content section to note that the option to hide the PayPal button in the Support Ate Up With Motor box is new and still an experimental feature. (If you have any problems with this feature, please let us know!)
  • November 11, 2019: Updated Other Inquiries, Messages, and Support Requests to note the closure of our Yahoo! account (although we retain our Flickr account) and 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 which we may search for and/or purchase research materials and/or other 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).” Restored the internal anchor link for “Controllers, Questions, and How to Reach Us,” which had been accidentally deleted. 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. In Data Retention, changed “contact information or other relevant data” to “contact information and/or other relevant data”; noted that we normally also retain indefinitely any research notes and other information related to our other 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.
  • November 7, 2019: Fixed a typo in Data in Submitted Images: The phrase “the phone may include …” was supposed to read “the photo may include …” Updated Information We Receive from Other Sources and Disclosure of Personally Identifying Information sections to note that the information we gather during our research may also include other media such as audio interviews or video and may be included in bibliographies as well as articles and metadata. (This is already indicated elsewhere in that section, but we want to be as clear as possible about this point.) Updated Data Retention to change “we believe the message/attachment came from a child under age 16” to “we believe the message/attachment came from a child under age 18” and remove a confusing reference to a now-deleted section of the preamble. Fixed a typographical error. 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. In Financial Transactions Policy, changed “on the webpage” to “on this website” for clarity. Added the Google Play Store and its related services to the list of examples of third-party service providers under Disclosure.
  • 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 Data Retention to indicate that we have deleted our backups of the pre-WordPress site database from October 2013. 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: Updated Financial Transactions Policy to note that the transaction-related information we disclose may also include tax documents and/or shipping records (if any) and remove part of that subsection’s preamble. Attempted to fix a technical issue with the bookmark/anchor links throughout and added an internal link from the top of the page to the Financial Transactions Policy section. 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 the text at the beginning of the Disclosure of Personally Identifying Information section to correspond to the revised preamble. Also, in the paragraph following the bullet pointed list in Disclosure, changed “individual site visitors” to “individual site visitors (or users of the site’s related services).” Made some clarifications to the language in Disclosure (the paragraph following the bullet pointed list) about information we publish or disclose as part of our professional work
  • 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 and Image Authorization Forms to also note that it applies to the Do Not Sell My Personal Information Opt-Out 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 and inconsistent spelling of “acknowledgment.”
  • 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. Fixed an accidentally repeated hyperlink in that section and reordered several items, 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.
  • October 30, 2019: Added the Guardian Project’s Orbot and Tor Browser to the list of examples of third-party service providers under Disclosure. Added NetGuard firewall/traffic monitor to the same list, which was accidentally deleted. 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 Other Inquiries, Messages, and Support Requests, and added Google Hosted Libraries to the list of examples of third-party service providers under Disclosure 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 3, 2019: Fixed the effective date (which had incorrectly described October 2, 2019, as a Tuesday rather than a Wednesday). Added data and/or document destruction/shredding services to the examples of third-party service providers under Disclosure.
  • 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 27, 2019: Under Disclosure, changed “Most of the photos we use on Ate Up With Motor were taken in public places, not always by us, and may include visible bystanders and/or potentially personally identifying information about them …” to “Photos we use on Ate Up With Motor — many of which were taken in public places, and which are not necessarily created by us — may contain visible bystanders and/or potentially personally identifying information about individuals …” and changed the sentence, “It is not always possible for us to completely obscure bystanders or potentially identifying information in photos, either for technical reasons or because we don’t have the legal right to modify that image” to “For various reasons, it is not always practical or even feasible for us to completely obscure visible bystanders or potentially identifying information in photos (for example, the license terms under which we use photos owned by others may not permit us to modify those images in such a way).” Removed some doubled HTML tags in that list item.
  • 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 25, 2019: In the Financial Transaction Policy, amended the Refund Policy section to note that we may opt to provide a refund on advertising purchases after five days at our sole discretion, to match the language of the rest of that section.
  • 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.
  • June 8, 2019: Minor amendments to the updated Financial Transaction Policy’s refund/return language, changing “Other Purchases and Services” subheading to “Other Purchases” and added an additional subheading for “Other Types of Transactions.” Updated text to change “decline” to “refuse” purchases/transactiosn, to avoid confusion, and noted that in most cases, we must retain transaction-related information even if we refuse and/or refund the transaction.
  • June 7, 2019: Corrected an inadvertent duplication of part of this page and updated some formatting. Updated Financial Transactions Policy, including adding information about refunds/returns and clarifying terms and conditions. Added subheadings to that section for easier reading. Further updated the description of “browser fingerprinting” under Embedded Content. Added Malwarebytes to the list of third-party service providers under Disclosure, updated the description of Avast in that list, and corrected a formatting error in that section.
  • June 3, 2019: Updated Online Tracking to indicate that we’ve discontinued the use of the Majestic service as of this date. 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.
  • April 9, 2019: Under the updated Disclosure language, changed “snippets or keywords” to “snippets and/or keywords.”
  • April 5, 2019: Updated Disclosure to note that information released/disclosed as part of our content may also be contained in metadata such as snippets and keywords intended to help search engines find and index that content, and clarified that images in which you may be visible may sometimes contain personally identifying information in their metadata (adding a link to Data in Submitted Images for further explanation).
  • 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 24, 2019: Under Comments and Personal Information; Contact and Image Authorization Forms; and Other Inquiries, Messages, and Support Requests, changed the wording about using, recording and crediting you for suggestions or permissions to “… use, record, manage, and where applicable appropriately credit you for any corrections, suggestions, information, and/or permissions you offer to us …” for consistency.
  • 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.) Further updated Other Inquiries, Messages, and Support Requests, rearranging and making minor amendments to the text for clarity and adding references to the Data in Submitted Images section and image use terms. Made a corresponding wording change to Contact and Image Authorization Forms regarding the publication of inquiries or excerpts thereof. Added a bullet point to Disclosure about publishing images you submit to us for that purpose. Rearranged some of the text of the Comments and Personal Information and Contact and Image Authorization Forms sections for consistency and logical flow.
  • March 22, 2019: Made a minor change to the preamble, changing “information we gather through this website and its related services …” to “information we may gather about visitors to this website (and/or, where applicable, users of related services …” and changing “Please read this policy before using the site. By using the Ate Up With Motor website …” to “Please read this policy carefully. By using the Ate Up With Motor website and/or its related services …” for consistency. Amended Other Inquiries, Messages, and Support Requests to clarify that that section is referring to personally identifying or potentially personally identifying information. Under Data in Submitted Images, changed “EXIF information and other metadata” to “EXIF information and/or other metadata.”
  • March 18, 2019: Tinkered further with the paragraph under Disclosure regarding licensing or selling information as part of our licensing of our work, changing “your image and/or information is” to “you and/or your information are.”
  • March 17, 2019: Tinkered further with the paragraph under Disclosure regarding licensing or selling information as part of our licensing of our work, changing “similar or related work” to “content”; striking the word “certain” ahead of “areas of automotive history”; and changing “a video” to “audiovisual productions.”
  • March 15, 2019: Further updated the paragraph under Disclosure about licensing or selling information as part of our licensing of our written work to note that this may also include work created by us for others and/or in other media.
  • March 14, 2019: Added some more ® 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. Made various wording changes and clarifications to the paragraph under Disclosure that begins, “In general, we do not sell or rent information about individual site visitors …” (in particular to replace the word “articles” with “writing” or “written content” and change “… we may provide it to others in that context” to “… we may license it to others in that context”).
  • March 13, 2019: Added some ® symbols and fixed the capitalization of “Facebook® Page.”
  • March 10, 2019: Under Other Inquiries, Messages, and Support Requests, clarified the bullet point about information associated with an email message to better explain what sort of information (metadata) that may include. 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 punctuation issues and tag closings. Under Data in Submitted Images, struck “from device to device” after “vary widely” for clarity (since the sentence is talking about both software and devices). Under Privacy Policy Changes, changed “the terms have changed” to “the policy has changed” for clarity.
  • March 3, 2019: Updated Contact and Image Authorization Forms section to add information about automatic filtering and spam prevention measures. 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.” Added the contribution button to the site function examples under Legal Bases for Collecting and Using Information and 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; change “accesses the site” to “accesses the site and its content”; 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 and Personal Information, changed “we may email you at that address to respond to your comment (or the associated comment thread, if any), particularly if it includes a question or offer of assistance, or if we need to clarify some aspect of your comment (for example, if you have posted two very similar comments, 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 Ate Up With Motor 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 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. Changed the wording of the WHOIS lookup services item under Disclosure to make it more generic. Fixed a punctuation error in Data Retention in the item about retaining financial transaction records and amended the text to emphasize that these records may include some user personal data.
  • 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; that to understand your comments or inquiries/messages, we may use information you submit to seek additional information from third-party sources; and that we may seek additional third-party information on submitted images and/or the subjects they depict. 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 (about looking up public information about site visitors) for clarity. In the latter section, changed “For example, an Ate Up With Motor reader might provide us with the contact information of an individual or firm that could assist us …” to “For example, an Ate Up With Motor reader might provide us with your contact information as an individual or firm that could assist us …” for clarity.
  • 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. Added data in user-supplied images as another example of areas where the Sucuri service might collect users’ personal data, including a link to the “Data in Submitted Images” subsection for further explanation of what information submitted images may contain.
  • 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.
  • 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. Under Other Inquiries, Messages, and Support Requests, changed “may also be subject …” to “are also subject …” Under Disclosure, changed the example “… mention that we once met you at a car show or other event” to “… mention that we once saw you speak at a car show or other public event.”
  • 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 “Most site-related email, excepting duplicate messages, obvious spam, malware, and automated notification and alert emails …” to “Most site-related email and form submissions, excepting duplicate messages, obvious spam, malware, and certain automated notification and alert emails …” Under Online Tracking, deleted the bullet point about turning off the Google Analytics tools via the Privacy Tools, as that function is not working properly at present. Reworded the bullet point about deleting the cookie through your browser for greater clarity.
  • January 27, 2019: Under Disclosure of Personally Identifying Information, changed “If that information otherwise was or is already publicly available, such as information published on your website or in news articles about you” to “If that information otherwise was or is already publicly available (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),” adding boldface for emphasis. 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. Clarified the preamble by changing “information we gather on this website and how we use it” in the first paragraph to “information we gather through this website and its related services (such as the ateupwithmotor.com email addresses) and how we use that information” and changing the provision about other websites to: “Your use of any third-party websites or services, including those linked from Ate Up With Motor or on which we may have accounts, is subject to the individual privacy policies and terms of use, if any, of those sites or services.” Put the following sentence in parentheses and changed “has” to “had.” Under Other Inquiries, Messages, and Support Requests, changed “we collect” to “we may collect; changed “as part of your message” to “as part of your message or its attachments”; and changed “via email and/or as SMS/MMS text notifications” to “via email, SMS/MMS text, or other message notification systems.” 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 23, 2019: Updated Online Tracking to clarify what kind of information the Majestic SEO service may gather.
  • January 22, 2019: Updated Financial Transactions Policy and 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 a tax rate for your address). Added common carriers/shipping agencies to the list of third-party service providers. Added additional language to Financial Transactions Policy about taxes, common carriers/shipping agencies, and legal compliance, and added customs inspections as an example of government reporting or disclosure requirements. 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. Clarified the description of our research in Information We Receive from Other Sources, borrowing some of the language from that bullet point in Disclosure (we also added the phrase “As noted in ‘Information We Receive from Other Sources’ above” to that bullet point to acknowledge the repetition).
  • 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 Financial Transactions Policy and 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. Further clarified Financial Transactions Policy by striking the phrase “personal and financial” (making the text simply “… disclose information associated with …”); changing “and for our legal protection” to “and/or for our legal protection” in the first bullet point; moving the text about banks and financial institutions to the second bullet point and adding “or as otherwise required by our legal agreements with the applicable payment processor and/or bank/financial institution” to that bullet point; changing the fourth bullet point to “As otherwise required by law (e.g., to comply with applicable government reporting or disclosure requirements; in connection with an audit or official investigation; or if we have received a subpoena or court order requiring us to disclose certain information) …”; and adding boldface to the bullet point leaders.
  • December 30, 2018: Added Startpage.com and DuckDuckGo to the list of third-party service providers under Disclosure. Minor editorial corrections to fix some typos in this list.
  • December 29, 2018: Updated Financial Transactions Policy to change the phrase “our bank” to “our bank(s)/financial institution(s), other applicable payment processor(s) …” and change “To the applicable payment processor and/or their legal counsel, auditors, and/or fraud protection services …” to “To the applicable payment processor and/or bank/financial institution’s legal counsel, auditors, and/or fraud protection services …” Fixed a typo in that section (a missing colon). Updated third-party service providers list under Disclosure to include our bank(s)/financial institution(s), and/or other applicable payment processor(s), and changed “Facebook and/or Twitter” to “Facebook, Twitter, and/or other social media services,” also fixing a typo involving the parentheses. Added “our bank(s)/financial institution(s)” to the bullet point on contractual obligations, fixed a minor wording issue (it should have said “… or as otherwise described under ‘Financial Transactions Policy’ above”), and inserted 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 …” Updated the preamble to note that the Ate Up With Motor Facebook page is currently deactivated. Updated Data Retention to note that we have downloaded our Facebook data, including data from the Ate Up With Motor page, for archival purposes, although we are deleting that account. 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: Clarified the first bullet point under Disclosure, changing “… may also include corrections, clarifications, or additional details …” to “… may also include information, corrections, clarifications, and/or additional details …” Added a link to the locally archived version of the policy for the Ate Up With Motor Facebook page under Disclosure and in the preamble, whose text we rearranged for greater clarity (and to restore the language about text style variations, which was inadvertently dropped). Fixed a typo in this list.
  • 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 5, 2018: Removed the links to our Facebook-specific privacy policy, as for the time being we have deactivated our account and the page on that service.
  • 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 29, 2018: Updated the Disclosure text regarding licensing articles/photos to change “However, we do sometimes license our articles and/or images to third parties” to However, we do sometimes license our articles and/or images to third parties (and/or offer images or other content we have created or modified/adapted under a Creative Commons or similar license).”
  • 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 messages we receive via third-party services like social media.
  • November 19, 2018: Fixed a typographical problem with the previous Effective Date. Updated Other Inquiries, Messages, and Support Requests and Disclosure to clarify our periodic use of Gmail, which is a service owned by Google.
  • November 17, 2018: Minor wording adjustments in Disclosure: changed “their own, comparably strict confidentiality policies” to “their own, comparably strict (or stricter) confidentiality policies.”
  • November 15, 2018: Clarified the preamble and Data Retention section regarding our work separate from the Ate Up With Motor website. Updated Data Retention to further clarify our retention of log data. Under Notice to Parents of Children Under 16, amended “if complete deletion is not possible …” to “where complete deletion is impossible or not practically feasible …”
  • 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 Personal Information; Contact and Image Authorization Forms; and Other Inquiries, Messages, and Support Requests 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 Flickr, Facebook, and Twitter to the list of third-party service providers under Disclosure and added “website development/improvement” to the list of possible functions of independent contractors. Updated Other Inquiries, Messages, and Support Requests with links to some third-party privacy policies and to note that Flickr was previously owned by Yahoo! (now part of Oath). Fixed a minor formatting error, clarified an item on this entry of the revision list, and made a capitalization change to the Google Fonts description under Embedded Content.
  • November 11, 2018: Updated Server and Error Logs to note that access to the FTP folders may be logged. Updated Data Retention to clarify that logs of some administrative functions (which contain no user data) may be retained for longer periods, as may records of FTP access.
  • November 9, 2018: Updated the first bullet pointed item in Disclosure of Personally Identifying Information to indicate that the research for our articles may involve sharing or discussing relevant personal information with third parties. Minor wording adjustment to the item in that section on bystanders in photos: changed “… or of associating the photos in which they appear …” to “… or associate the photos in which they appear …” for clarity.
  • 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 Personal Information, and Contact and Image Authorization 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 Ate Up With Motor, 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 and Personal Information, changing “… record and use information in and associated with your comment … ” to “… record and use personal information in and associated with your comment … “; “record and, if applicable, appropriately credit you … ” to “use, record, and if applicable appropriately credit you … “; and “… 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.” Updated Contact and Image Authorization Forms, changing “… record and use information in and associated with your form submission … ” to “… record and use personal information in and associated with your form submission … ” and “record and, if applicable, appropriately credit you … ” to “use, record, and if applicable appropriately credit you.” Updated Other Inquiries, Messages, and Support Requests to change “record and, if applicable, appropriately credit you … ” to “use, record, and if applicable appropriately credit you.”
  • October 22, 2018: Updated this page’s hyperlinks with “rel=noopener” or “noopener noreferrer” attributes for security purposes.
  • October 19, 2018: Clarified Data Retention language regarding photos and other images and intellectual property, including noting that we customarily retain our work files and editing stages, if any. Also, clarified some cumbersome wording about retention of anonymous or de-identified log data. 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: Fixed some inadvertently deleted text in the Online Tracking section and adding a note inviting users to contact us for assistance in opting out. Updated the Who We Are text at the beginning to emphasize that we’re based in the U.S. (and a U.S. citizen). Fixed some broken navigation links on this page.
  • October 14, 2018: Updated Data Retention to mention archival backups of the defunct Ate Up With Motor LiveJournal blog and the pre-WordPress version of this website. 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. Fixed a problem with this revision list not having been updated properly when we first posted this change.
  • 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 Other Information You Provide to Us and Disclosure language regarding information related to photos or other images. Clarified Disclosure provisions regarding business transfers. Updated Comments and Personal Information to note that special characters, HTML/PHP code, and emojis in comments may be removed.
  • October 4, 2018: Minor change in the Disclosure of Personally Identifying Information section, changing “and its associated social media pages” to “and/or, where applicable, its associated social media pages/accounts (except where we have created separate privacy policies for such pages/accounts, in which case the disclosure provisions of those policies will apply instead).” 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 explaining 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, repeating some of the links to third-party privacy policies, and fixing some awkward 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, including reordering two paragraphs.
  • October 2, 2018: Several minor formatting and punctuation changes to Data in Submitted Images, Other Information You Provide to Us, and Acknowledgements of User Assistance to improve readability. 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. Updated Comments and Personal Information and Information We Receive from Other Sources sections to note that we may obtain/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 and Personal Information section to mention the Recent Comments widget, rewording some of the adjacent text for clarity.
  • September 25, 2018: Further adjusted wording of Information We Receive from Other Sources. Updated Server and Error Logs and Data Retention to clarify the types of data the logs include and how long we retain it. Minor wording change in Other California Privacy Rights. Amended Disclosure to fix a readability problem with the item on business transfers. Updated Comments section to include a note about the Recent Comments widget.
  • September 24, 2018: Updated Other Information You Provide to Us and Information We Receive from Other Sources to describe information we may receive about the owners of cars we photograph (where we know who they are, which we often don’t!). Made some minor clarifications to those sections for readability with the new text.
  • September 21, 2018: Under Data Retention, changed “other, similar non-voice direct messages we receive on our phone” to “other, similar non-voice direct messages we send or receive via our phone”; “specific messages” to “certain specific messages”; and “if they contain some vital information” to “if we have some outstanding reason to do so” for clarity. Integrated California Privacy Rights information here, adding a hyperlink anchor to it and rearranging some headings and other text in the Your Rights section for ease of reading. (Also, updated the point about data portability to note (starting in 2020, California residents may request this up to twice per year).”) Under Controllers, Questions, and How to Reach Us, changed “would like to remove your data” to “would like to amend or remove your data.”
  • 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 added link to Your California Privacy Rights page to Your Rights section, changing the heading of that section accordingly. Added subheadings to that section and rearranged some text.
  • 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 Financial Transactions Policy to better describe the information in transaction reports.
  • 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: Amended Financial Transactions Policy to better describe the payment button, which is no longer actually called the “Contribute” button. Added link to AboutCookies.org under Cookies. Updated links to Google Privacy Policy, added YouTube to the list of Embedded Content, and rearranged the order of the Embedded Content list.
  • September 9, 2018: Further clarified Cookies section to better explain cookie duration. Updated Embedded Content and Financial Transactions Policy to clarify how the payment button is served, some of the ways it may gather information, and how to find more about PayPal policies (and added a note that those policies may differ depending on your location). Updated Cookies and Online Tracking to better explain how to change your mind about Google Analytics.
  • September 8, 2018: Updated Online Tracking to clarify that the opt-out cookie applies only to tracking on Ate Up With Motor, not any other site using Google Analytics. 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.
  • September 7, 2018: Further amended Cookies and Online Tracking to clarify cookie durations.
  • September 6, 2018: Amended Other Inquiries, Messages, and Support Requests to change “we will typically forward …” to “we typically prefer, where possible, to forward …” Added a link to Yoast’s GDPR page to Embedded Content. Updated Cookies to better explain how you can find out about the specific cookies the site uses and fixed an embarrassing typo. Added WordPress to Embedded Content.
  • 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. Clarified the duration of some cookies in Cookies section.
  • September 4, 2018: Further clarified Data Retention section about retention of messages received via third-party websites/services. Updated Embedded Content to indicate that some backend (administrative dashboard) features may be served by Yoast.
  • September 2, 2018: Updated Data Retention to clarify retention of messages received via third-party websites/services such as social media.
  • September 1, 2018: Updated Disclosure item about sale of the website and its assets to note that also applies if we transfer control of the website and/or in the event of our death or incapacity, in which case visitor information would be among the assets transferred to the acquirer or our applicable heirs, successors, and/or assigns. (Some of the updated language is again borrowed from the Automattic privacy policy noted in the preamble.) Updated the item under Data Retention about financial transactions and legal agreements to clarify that it includes records related to payments or purchases we make, such as phone bills or buying research materials.
  • August 31, 2018: Minor wording changes to Financial Transactions: changing heading to “Financial Transactions Policy”; changed “applicable payment processor and their legal counsel, auditors, or fraud protection services” to “applicable payment processor and/or their legal counsel, auditors, and/or fraud protection services”; changed “any applicable tax auditor or investigator” to “any applicable tax auditor or other government investigator”; added “otherwise” to “As described in ‘Disclosure …'”; and struck “specifically” from “… to address questions related to your transaction(s) with us.” Changed contact email to admin (at) ateupwithmotor (dot) com throughout.
  • August 18, 2018: Added additional information to Cookies and Data Retention regarding cookie duration. Noted under Other Inquiries, Messages, and Support Requests that some third-party contact methods (such as trying to reach us by commenting on a photo we’ve posted on a third-party website) may be publicly visible. Minor revisions to Disclosure to clarify the item about providing information to third-party service providers investigating a dispute, and to amend the language about disclosing information if we are required by law to do so: “(such as, without limitation, if we receive a subpoena, court order, or other government order requiring us to disclose certain information, or in connection with a tax audit or other official investigation).”
  • August 17, 2018: Updated Your Rights section to note that the data retrieval tool can’t presently retrieve feedback form submissions.
  • August 15, 2018: Updated Security Scans; Comments and Personal Information; Contact and Image Authorization Forms; and Other Inquiries, Messages, and Support Requests to note that those communications 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 …” Fixed a formatting error.
  • August 14, 2018: Updated Data Retention to clarify retention of log and scan result data, email alerts, and notifications. Further clarified the point in Disclosure about releasing information that is already publicly available (such as information in news articles or on your website).
  • 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 and Contact and Image Authorization Forms to add “without limitation” to the examples following “… the information in and associated with your comment” and drop the definite article (making it “… use information in and associated with your comment (including, without limitation …”). Also noted that comment notification emails to other users may sometimes include the website/URL you entered with your comment, and added a mention of the email notifications to 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: Added a point to Acknowledgments of User Assistance and Information section about personal details that may be implicit in the nature of the assistance provided. Updated Security Scans to note that security measures may automatically block certain suspicious actions or queries. Added anchor to Data in Submitted Images header, linked to it from the Comments section for easier reference, and amended the sample copyright line text slightly. Updated Cookies section to clarify that embedded third-party content may use cookies and noted in Embedded Content section that the PayPal button may place 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 and Personal Information and Data in Submitted Images to say clearly that we can’t control how others may use personal information you include in a publicly visible comment or submitted image and clarify the description of what metadata an image file may contain.
  • 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, that the feedback forms record the date/time of your submission, and some other minor clarifications. Updated and expanded Data Retention section. Updated Other Inquiries, Messages, and Support Requests section to better describe the information gathered and to clarify when we will respond via the same account or service. Clarified language about email scanning in Security Scans and added related notes to the Comments, Contact Forms, and Other Inquiries sections about our web host and/or mobile carrier scanning email for spam or malware. Added links to the DreamHost and T-Mobile privacy policies to the Disclosure section for ease of reference. Made some minor tweaks to Legal Bases for Collecting and Using Information. Clarified the info in the Disclosure section about publicly available information about public figures and people in the auto industry and added a stipulation about disclosing information where we are required to do so by an applicable third-party service in connection with a dispute or investigation. Updated and expanded Information We Receive from Other Sources. Added a note to the preamble at the top stressing that this policy doesn’t apply to business or professional relationships with the site’s proprietor independent of Ate Up With Motor. Changed the order of the Acknowledgments of User Assistance and Information section for better logical flow. Fixed a typo in Disclosure: “potentially personally identifying formation” was supposed to read “potentially personally identifying information.”
  • August 5, 2018: Updated Disclosure section to indicate that we may share already publicly available information about people in the automotive industry and/or public figures with other writers, researchers, journalists, etc.
  • July 26, 2018: Minor editorial revision: changed “Google” or “Google Inc.” to “Google LLC” where applicable.
  • July 18, 2018: Minor editorial revision to Other Inquiries, Messages, and Support Requests wording about Gmail and Yahoo Mail (saying “Google® and Yahoo!® webmail accounts” first and “Gmail and Yahoo Mail” second rather than the other way around for better usage).
  • July 17, 2018: Updated Other Inquiries, Messages, and Support Requests to note that some older site-related email may be contained in our personal Gmail or Yahoo Mail accounts. Minor editorial corrections.
  • July 16, 2018: Updated description of user agent information and that it typically includes browser settings such as language preferences.
  • July 15, 2018: Clarified Data in Submitted Images to explain that if we modify one of your images after it has been published on Ate Up With Motor, the original, unmodified version may linger for a while in cached pages as well as in backup files. Streamlined Embedded Content section to make it clearer and less repetitive.
  • July 12, 2018: Further clarified log retention periods based on update from Sucuri and made other minor adjustments to Data Retention. Restored Notice to Parents and updated the How to Reach Us section.
  • 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. Clarified Disclosure of Personally Identifying Information to note that (obviously) our mobile carrier may manage site-related texts as well as emails sent to or from our phone or phones, that PayPal processes certain financial transactions, and that the piece about publicly responding to support requests is further explained in Contact and Image Authorization Forms as well as Other Inquiries, Messages, and Support Requests.
  • July 10, 2018: Clarified that if we license one or more of our photos or other images to a third party, it’s conceivable that they may include personal info that “is somehow visible in certain of our images or present in their metadata.” Also clarified that, obviously, our and our web host’s security scans look for the presence of potentially malicious code, and corrected a minor editorial error in this list. Noted that the admin login page sets cookies and made minor clarifications to the Security Scans section.
  • July 4, 2018: Clarified some of the ways we may use personal information from comments, contact forms, and other communications. Changed “metadata and EXIF information” to “EXIF information and other metadata” for clarity and noted that we may add or alter filenames and metadata to indicate the provenance and attribution of an image or other content (as well as retaining any personal information that might already be contained in the content). Minor punctuation and formatting corrections.
  • 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; Contact Forms; and Other Inquiries, Messages, and Support Requests that we may use information associated with your message to verify your identity as well as determining whether or not you’re a bot. Clarified Data in Submitted Images to indicate that we may be able to remove information upon request. Provided a more representative example under Information We Receive from Other Sources.
  • June 20, 2018: Added link to Majestic-12 GDPR Compliance Statement to Online Tracking section.
  • June 19, 2018: Added comments to Disclosure of Personally Identifying Information, for completeness.
  • June 18, 2018: Clarified throughout that we may use information from our logs, comments, forms, and email submissions to prevent spam and electronic attacks directed at our system, devices, and accounts as well as the website itself (for example, by blocking email or IP addresses used to send us spam or viruses). Fixed a typo in the Contact Forms section (it should have said “associated with your submission” rather than “associated with your comment”).
  • June 16, 2018: Clarified Disclosure of Personally Identifying Information: Changed “To appropriately credit you for the use of your photos or other content” to “To appropriately credit you for the use of your photos, fonts, themes/plugins, or other content or intellectual property.” Also, changed “we do sometimes license our articles and/or photos” to “we do sometimes license our articles and/or images” and noted in Data Retention that we typically retain all information related to disputes or suggestions related to articles. Added note at the top clarifying that this policy does not apply to any third-party websites linked here and changed “the website” to “this website” in preamble and in Information We Collect. Fixed a few typos.
  • June 11, 2018: Updated Disclosure of Personally Identifying Information and Information We Receive from Other Sources sections to note that information we gather publish regarding people who are subjects of articles may include images such as publicity photos and official portraits. Corrected date error (June 10 update was accidentally dated June 11).
  • June 10, 2018: Updated Disclosure of Personally Identifying Information section to explain how we use information about people who may be the subjects of our articles, rearranged and made minor clarifications to the rest of the text of that section, and added a note about licensing articles or photos that may contain personally identifying information.
  • June 8, 2018: Revised Inquiries, Submissions, and Support Request section to clarify what information we gather and include contacts with us via third-party websites. Renamed that section Other Inquiries, Messages, and Support Requests. Corrected formatting error. Clarified Other Information You Provide to Us section. Updated Disclosure of Personally Identifying Information section to clarify that it refers to information about website visitors and to add note about people in photos. 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 Scans and Disclosure sections to reflect current Sucuri terms. Minor clarification to Google Analytics section. Clarified Embedded Content wording. Added link at the top to this revisions list.
  • May 25, 2018: Updated Google Analytics opt-in/opt-out language.
  • May 24, 2018: Various minor clarifications, including revised Cookies, Security Scan, Data Retention, and Revisions language. Updated Comment policy to clarify procedure for deleting comments.
  • May 23, 2018: Clarified Security Plugins section and renamed it Security Scans. Minor amendments to Server and Error Logs to correspond with these changes.
  • May 22, 2018: Clarified that PayPal transaction reports may be send to us via email, added name of mobile carrier, other minor clarifications.
  • May 21, 2018: Clarified third-party embedded content language and added note about Sucuri scanning. Clarified cookie language.
  • May 20, 2018: Further minor clarifications regarding GDPR compliance, including the use of logs and data from third parties. Added “Who We Are” header for clarity, noted that submitted photos may include identifying information, and noted that Google Fonts records your IP address.
  • 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).
  • May 10, 2018: Updated age restriction from 13 to 16.
  • 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.
  • April 4, 2017: Updated links from http to https.
  • February 11, 2016: Further clarified Contact and Image Authorization Forms section: changed “and/or appropriately attribute images you have provided for use on Ate Up With Motor” –> “and/or appropriately attribute images and/or factual information you have provided for use on Ate Up With Motor”.
  • February 10, 2016: Clarified Contact and Image Authorization Forms section: changed “We may record and use this information to …” –> “Ate Up With Motor may record and use the personally identifiable or potentially personally identifiable information associated with your submission to …”>; added “… ensure accurate records of our image usage rights and/or any related business transactions; and/or appropriately attribute images you have provided for use on Ate Up With Motor” to the list of uses; added note that “This information may also be stored in archives and backup files created by us or our web host”; and changed “we will not release that information except as described in “Disclosure of Personally Identifying Information” below” –> “we will not release personally identifiable information related to your submission except as described below” for clarity.
  • January 13, 2016: Added note to preamble clarifying that variations in text style have no legal significance.
  • January 11, 2016: Amended Contact and Image Authorization Forms to note that excerpts of inquiries may also be published on our associated social media accounts to respond to requests or support other users, and may include your name or pseudonym.
  • January 9, 2016: Added new Privacy Policy Changes language noting the new Policy Update Minder on the front page of the site.
  • January 8, 2016: In Disclosure of Personally Identifying Information section, moved “Discounting Acknowledgments of User Assistance and Information (as described above)” to a bullet-point item. Rearranged wording of item regarding contractors, service providers, and business partners for clarity. Changed the last paragraph of that section to: “Ate Up With Motor takes all reasonable and appropriate measures to protect against the unauthorized access, use, alteration, or destruction of potentially personally identifying and personally identifying information.” Added to Acknowledgments of User Assistance and Information section: “This acknowledgment will be limited to your name/username and the nature of your assistance and will not include your email address or other personal information unless you expressly request that we publish such additional information.” Changed “or other means” to “or by other means” and changed “replace a username” to “replace a username or pseudonym”. Minor editorial corrections.
  • 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, including 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 revision list. ETA: Editorial corrections. 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. Reworded Opting Out text (“Users may consider …” –> “However, users may wish to consider”) accordingly. Amended Server and Error Logs: “such as the IP address” –> “such as, but not limited to,”. ETA: In Embedded Content section, changed “Ate Up With Motor does not collect, receive, or have access to any user data related to these fonts” –> “Ate Up With Motor 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 and Personal Information section to note that we will assume you are authorizing us to publish any information you actually include in a comment you post (ETA: including the name/screen name you supply). (This should be obvious, but we note it here for the record.)
  • December 31, 2015: Editorial corrections.
  • December 29, 2015: Editorial corrections. Clarified that this entire policy is available under CC BY-SA 4.0. Amended Financial Transactions Policy: “We will not otherwise disclose your information … –> “We will not otherwise disclose personally identifiable information associated with your transaction …” Amended Contact and Image Authorization Forms: “we will NOT publish or release personally identifying information …” –> “we will NOT publish or release personally identifying information associated with your message …”
  • December 28, 2015: Added note about Automattic revision history.
  • December 26, 2015: Editorial correction.
  • December 25, 2015: Editorial correction.
  • December 24, 2015: Added link to Automattic Inc. main site. Reworded Server and Error Log language: “automatically generate access and error logs that include certain information” –> “maintain various logs that collect certain information”.
  • 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 notes for this policy.
  • December 19, 2015: Updated 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 10, 2015: Clarified that Google Fonts servers are located in the U.S.
  • December 9, 2015: Clarified Server and Error log information. Editorial changes, including rearranging some sections.
  • December 3, 2015: Editorial and formatting changes, including editorial and formatting changes to Financial Transactions Policy section.
  • October 23, 2015: Added “and/or” to Disclosure of Personally Identifying Information stipulations; editorial changes to Financial Transactions section.
  • October 10, 2015: Editorial and formatting changes; editorial changes to Financial Transactions section. 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.
  • August 10, 2015: Changed the order of the Embedded Content section. Updated license from BY-SA 2.5 to 4.0.

Please contact us if you need information on earlier revisions.

Updated: December 11, 2019 — 3:39 am