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 pertaining to such 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.

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 deactivated Ate Up With Motor Facebook® Page had its own privacy policy. Here is the archived version of that policy at the time the page was deactivated.)

EFFECTIVE DATE: This version of the Privacy Policy is effective Sunday, January 26, 2020. 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.

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.

Table of Contents

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 toward the bottom of this page.

License for This Policy

Portions of this Privacy Policy were adapted from the Automattic Inc. Privacy Policy under a Creative Commons Attribution-ShareAlike 4.0 International license. This policy (including our adaptation of the Automattic terms and our additions) is offered under the same license. If you elect to use or further adapt our version, please credit Automattic 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

If you are in an area that is subject to European data protection laws, our legal grounds for collecting and using your information are that:

  1. 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
  2. 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
  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/or 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 personal information through this website that we know to be from a child under the age of 16 (e.g., an email message, feedback 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.

Definitions

To help simplify and clarify the rest of this policy, the following definitions will be used throughout this document:

  • User(s) and visitor(s): For the purposes of this policy, we use the terms “visitor” and “user” to mean any individual who accesses our website and/or uses its related services. This policy assumes that you, the reader, are such a visitor/user.
  • Personal information/personally identifying information: Different jurisdictions have different definitions of “personal information” and “personally identifying information” (terms this policy uses synonymously), but in general, it means any information that could be used to individually identify you and/or your “household” (another term that may have different legal meanings depending on the jurisdiction). Information doesn’t have to identify you by name to be considered personal information or personally identifying; information that describes or could be associated with you can also constitute personal information. In this policy, we also use the term “potentially personally identifying information” to describe information that might identify you and/or your household in certain contexts (or in combination with certain other information).
  • Identifiers: “Identifiers” are pieces of personal information that expressly identify an individual, household, or specific device, such as (though not limited to) real names, postal mailing addresses, email addresses, driver’s license numbers, Social Security Numbers, or unique device ID numbers. Some jurisdictions also consider IP addresses to be personal identifiers.
  • Protected classifications: Some pieces of personal information are characteristics of one or more classifications that are protected by civil rights law and/or other nondiscrimination laws, such as race, religion, gender, or medical conditions.
  • IP address: An Internet Protocol (IP) address is the numerical address of any device capable of accessing the Internet. If you use several different Internet-capable devices, their individual IP addresses are typically all different (although if you have several devices connected to the same router or tethered together, they might share the same IP address so long as they remain connected or tethered). An IP address typically reveals the Internet service provider or mobile carrier the device is using. A given device’s IP addresses may change periodically (especially if the device is configured to use “dynamic” IP addresses assigned by the Internet service provider or mobile carrier). It is possible to hide a device’s IP address and Internet service provider/mobile carrier by using a virtual private network (VPN) or proxy service; with these services, you first connect to a computer server provided by the VPN/proxy service and that proxy server then connects to other Internet sites and resources, which “see” only the IP address of the proxy server. For the purposes of this policy, when we refer to IP addresses, we mean the IP address that actually connects to our website and/or services or that we otherwise receive, whether that is your device’s actual IP address or a proxy. (In many cases, we have no way to tell the difference.)
  • User agent information: A “user agent” is any software program, service, or system that allows a user to access web content. This can mean a web browser, an email client, or a web “crawler” of the kind used by search engines. User agents automatically reveal certain information about themselves — and therefore about the user — to any online resource they access, enabling that resource to deliver its content in a way the user agent can correctly handle. At a minimum, a browser’s user agent information typically reveals the browser type and version, the operating system in which the browser is running, and certain settings such as preferred language and time zone; if you’re using a mobile browser, the user agent information may also reveal the specific type of mobile device you’re using. User agent information is typically not personally identifying by itself, but it is sometimes possible to identify an individual user based on their specific combination of browser characteristics, a technique called “browser fingerprinting.” The Electronic Frontier Foundation (EFF) has created a website called Panopticlick that offers 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 information.)
  • Domain name: A domain name is the name of an online resource such as an email server or a website; for example, “ateupwithmotor.com” is a domain name. The ownership of domain names is registered through the Internet Corporation for Assigned Names and Numbers (ICANN), which maintains a directory of registered owners and their contact information. Most websites have a domain name, as do nearly all email addresses. When you access an online resource by its domain name, your device first accesses a domain name system (DNS) server, which is a directory that looks up that resource’s IP address so your device can connect to it. Mechanisms that collect website visitors’ IP addresses sometimes also record a domain name in connection with that IP address; this is typically the domain name of the Internet service provider or mobile carrier with which that IP address is associated.
  • Embedded content: Most web pages consist of many different elements, including not only the HTML code, but also various images, other media files, fonts, and scripts. For this website, most of those elements reside on and are served (i.e., loaded and run in your browser) by web servers owned by our web host, DreamHost®; this policy describes such elements as “local,” “locally served,” or “locally hosted” content (these terms are used synonymously). Certain elements of the website, such as scripts, fonts, or video players, may reside on and be served by systems not owned by DreamHost, such as third-party hosted libraries or content delivery network (CDN) servers; this policy describes such elements as “embedded content.” Whenever you access a page that includes embedded content, the page instructs your browser to contact the servers of the embedded content provider to retrieve and load those elements.
  • Visitor activity: For purposes of this policy, “visitor activity” refers to any information we may collect about our visitors’ online activity and/or actions, whether on this website or elsewhere online, such as (without limitation) web pages they’ve visited, links they’ve clicked, or search terms they have looked for.
  • Malicious activity: We define “malicious activity” as any activity or action intended to harm, abuse, compromise, or disrupt the functions of this website, its related services, their data, our web host, our embedded content providers, our visitors/users, our system and device(s), and/or us, or defraud or attempt to defraud us, our service providers and/or vendors, and/or our visitors/users.
  • Errors and suspicious activity: For purposes of this policy, “errors” means any error messages your visits to this website and/or use of its related services may generate, such as when some of the images or elements that should appear on a particular page fail to load. (“Error” doesn’t necessarily mean that you’ve done anything wrong!) “Suspicious activity” means any access to or actions involving this website and/or its related services that could be a sign of malicious activity. Of course, not all suspicious activity is actually malicious; often, it results from an error beyond the visitor’s control or from a harmless mistake.
  • Names: Unless otherwise specified, where we refer to “names” in this policy, it includes both real, legal names and pseudonyms/aliases. In general, we only require your legal name in certain circumstances (such as financial transactions or legal agreements). Otherwise, you are free to communicate with us using only a pseudonym or alias, although if you do so, we may have no way of associating those communications with information we may have about you under your real name and/or other pseudonyms or aliases. (Also, if your pseudonym or alias looks like a real name, we may have no way to know it isn’t one!)
  • Email address(es): Email is the main means by which we respond to visitor/user questions and inquiries, as well as how this website associates posted comments with the people who made them. For purposes of this policy, we assume that email addresses naturally include domain names even where we don’t expressly specify “domain names” in the list of information collected. (We may sometimes collect domain names that are not associated with a single email address.)
  • Email header information: All email messages include email headers (sometimes called “Internet headers”) that contain not only the sender and recipient email addresses, but also the names and IP addresses of the mail servers that sent and received the message, routing information, encryption and security protocols, and other technical details. (The precise details vary depending on your email client and provider.) Although email headers always include your email address, there are situations where we may have your email address, but not your email header information, usually because we have never actually exchanged any email messages with you.
  • Other contact information: This means any contact information other than email, such as a telephone number or postal mailing address.
  • Images or other media: “Images” is hopefully self-explanatory; for purposes of this policy, “other media” (or “other media files”) is a blanket term intended to encompass any audiovisual or multimedia content that is not an individual image, including, but not limited to videos, audio recordings, broadcasts or streams, and slide shows.
  • Other documents/materials: This includes any type of physical or electronic document or material, such as books, magazines, letters sent via postal mail, newsletters, or clippings.
  • Metadata: Any electronic file, document, or communication contains metadata, which is data about that file, document, or communication, such as its file size, type, creation date, and technical details such as bit rate or pixel dimensions. The information in telephone records (such as the phone numbers of the callers, the date and time of each call, the call durations, etc.) can also be considered metadata. Metadata is not necessarily personally identifying in and of itself, but may sometimes contain personal information (e.g., the author’s name or contact information) and/or potentially personally identifying information.
  • Geolocation data: Geolocation data generally means information about an individual or household’s geographical location other than a mailing address or street address, e.g., a particular city or region, or a public place such as a park or fairgrounds. We may receive geographical location data when you tell us your location in a comment or other communication, but we (and/or our service providers, where applicable) may also determine or estimate your approximate geographical location based on other data such as your IP address, the area code of your telephone number, or GPS coordinates in the metadata of your submitted images. Although some jurisdictions regard geolocation data as personal information, it doesn’t necessarily reveal where you live or work, and in some cases may not reflect your actual location at all, particularly if you use a VPN or proxy service.
  • Websites/URLs: “URL” (an acronym for Uniform Resource Locator) is the technical term for a web address. A website URL isn’t necessarily personally identifying, at least by itself, but the URL such as your social media profile or online resume/CV would probably be considered personal information. Where this policy refers to “websites/URLs” as a category of personal information, we mean URLs that may contain (or that link to) personally identifying information about individuals or households.
  • Referring site: Whenever your browser or other user agent connects to some online resource — such as when you click a link or access embedded content on a web page or in an email message — that online resource can generally see the website or other online location, if any, from which the request originated, which is known as the “referring site” or “referer” [sic — some sources use the correct spelling, referrer, although the actual name of the HTTP header is (mis)spelled “referer”]. If the referer is the results of a search query (for example, when you click on a link from search engine results), the online resource you access can typically see not only the referring site, but also the specific search terms you were looking for. (Some privacy-focused search engines take steps to remove this referer information so the destination site can’t see it, but most popular search engines do not.)
  • Other personal information: This includes any other information about an individual or household that could be considered personal information or personally identifying information. As noted above, some jurisdictions now regard nearly any piece of data about an individual or household as “personal information,” from the career history of a public figure to the fact that a website visitor once owned a car of a particular model.
  • Special: This policy uses this term to denote certain unusual categories of information not easily categorized, which may or may not be personally identifying.
  • Administrative dashboard/backend: Like most modern websites, this site has both a public-facing (“front-end”) portion and a “backend” administrative area that includes various controls for managing the site and its content. The content management system WordPress, which this website uses, describes the administrator backend as the “dashboard,” so this policy uses “administrative backend” and “dashboard” synonymously. The administrative dashboard is not normally accessible to visitors other than authorized administrators (meaning us!), and we take various measures to guard against unauthorized access to it.
  • Cookies: A cookie is a small text file — a string of information — that a website or online service places (or “sets” — these terms are used synonymously) on your browser or device and that your browser or device then provides to that site or service when you access it. (It is sometimes also possible for a website or service to detect cookies set by other sites/services.) Cookies may be used in many different ways, but the most common uses are to save your settings or preferences and to manage logins. Most cookies are specific to each browser and device; if you access a website from multiple browsers and/or multiple devices, the website may place cookies on each browser on each device. You can learn more about how cookies work and how you can manage or delete them on different browsers by visiting AboutCookies.org. (We are not affiliated in any way with that website, which is run by the law firm Pinset Masons LLP, and offer this link purely for your information.)

Categories of Information and Purposes for Collection

In each of the sections below, we indicate the categories of personal information we may collect and the categorical purpose or purposes for which we may collect that information.

Those possible purposes include:

  • Functionality: We use the listed information so that this website (and/or its related services), or certain specific functions thereof, can work properly. For example (but without limitation), none of the pages or content on this website will load if the web server doesn’t have a valid IP address to which to transmit the necessary data.
  • Providing a service: We use the information to provide some service or perform some action you ask (or have asked) us to perform. For example (but without limitation), we probably couldn’t send you a physical document without your mailing or delivery address.
  • Completing a transaction: We use the information to conduct or complete financial transactions with you, such as a contribution made through the payment button.
  • Fulfilling a contractual obligation: We use the information to meet the requirements of some contract or legal agreement, whether with you or a third party.
  • Legal compliance or audit: We use the information to ensure our compliance with applicable laws or regulations, and/or so that we can demonstrate our compliance to an auditor or investigator if needed.
  • Research and publishing: We use the information as part of the research involved in creating and publishing our content (e.g., our automotive articles and/or associated images), our other writing/editing work, and/or other creative endeavors, and/or to help us decide what content to create and/or publish. For example (but without limitation), data about which past articles have been most popular helps us decide what content to publish in the future.
  • Security, troubleshooting, quality control, and technical improvement: We use the information to help us protect this website (and/or its related services), its data, its users, and us from malicious activity; troubleshoot and resolve technical problems; and/or improve the quality and functionality of the site and/or its related services.
  • Advertising and other commercial purposes: We use the information to promote or advertise our content or services, sell advertising on this website, monetize the site and its content in other ways, and/or achieve some other commercial purpose(s).

In many cases, information we collect may have several purposes or possible purposes. Obviously, not every individual piece of information in a particular category will necessarily be used or even useful for a given purpose.

(Where the sections below list multiple purposes or possible purposes, separated by semicolons, the order does not signify any comparative priority or significance.)

In some cases, we may gather certain types of information in certain circumstances and not in others. In those cases, the information category shown below will be followed by a single asterisk (*). (For example, but without limitation, we generally don’t need your postal mailing address except in connection with certain financial transactions or if you ask us to send you some physical letter or parcel, so we only collect mailing addresses from certain visitors, not from everyone.)

Keep in mind that the categories of information listed in each section below are just the types of information we may collect in the specific context described in that section. Depending on how you use our website and/or related services, several or all of these sections may apply to you.

Cookies

The Ate Up With Motor website uses cookies for a variety of purposes. Some cookies are placed on your device/browser automatically while others are only set when you perform certain actions.

In general, we set cookies in circumstances where we need to identify a specific device and/or store visitor choices/preferences, including certain accessibility settings and privacy choices like your acceptance of this Privacy Policy and whether or not you have consented to analytics tracking (which also involves the use of cookies — see “Online Tracking” below). The use of cookies also allows us to determine which content to show you, such as whether to display or hide banners intended for first-time visitors, and to ensure that administrative areas of the site are not accessible to unauthorized visitors.

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

Some of the cookies set by Ate Up With Motor or our embedded content providers are “session cookies” that expire (cease to function) when you close your browser. Others are “persistent cookies” that remain on your device and expire after a certain amount of time, such as 30 days or one year. Certain cookies will persist for as long as your browser permits unless you manually delete them.

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

(While the list shown in the above pages describes the specific cookies that are typically used on this website, embedded content providers may sometimes change the cookies they use or add new ones not currently listed, which is outside of our control. Also, certain portions of the website’s administrative dashboard (which is not normally accessible except to logged-in administrative users) might sometimes set additional cookies not included in these lists, especially if we have just added or are testing some new plugin or other site component.)

Please 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 configuration may also affect how long a particular cookie remains on your computer or device; for instance, most browsers can be set to automatically delete cookies each time you close your current browser session, regardless of the cookies’ normal duration.

You are free to block or remove any cookies set by Ate Up With Motor. However, please note that some site features may not function without cookies. For example, you may not be able to hide the notification banners or change certain accessibility settings, and previously saved preferences may be lost. (Again, if you use multiple devices or browsers, deleting or blocking cookies on one browser does not usually affect cookies on the others.)

Information We Collect Automatically

Certificate Authority Checks

  • Categories of information gathered: IP addresses; user agent information; visitor activity (referring site); geolocation data (estimated from IP addresses and/or inferred from other data)*; special: mobile phone types/models (determined from user agent information)*
  • Purpose(s): Functionality; legal compliance or audit; security, troubleshooting, quality control, and technical improvement
  • Data retention: To our knowledge, Sectigo has not disclosed how long it typically retains public repository server logs.

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; for obvious reasons, it also informs those servers that you have accessed Ate Up With Motor. Sectigo may log and use such data for operational, troubleshooting, security, and service improvement purposes, and/or as otherwise described in the Sectigo Privacy Policy. Any further questions about their use and/or retention of public repository log data should be directed to Sectigo, as it is outside of our control.

Browser Tests

  • Categories of information gathered: User agent information; special: browser technical capabilities and/or settings
  • Purpose(s): Functionality
  • Data retention: Your current visit.

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 the presentation and functionality of the site to be more compatible with your browser. (Different browsers, and even different versions of the same browser, may handle certain content in different ways, which can create problems if content is not correctly tailored for that browser.) 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.

If you’d like further technical information on the Modernizr plugin, 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 information.)

Online Tracking

  • Categories of information gathered: IP addresses; user agent information; visitor activity; errors and suspicious activity; geolocation data (estimated from IP addresses and/or inferred from other data); URLs/websites*; special: mobile phone types/models (determined from user agent information)*
  • Purpose(s): Research and publishing; security, troubleshooting, quality control, and technical improvement; advertising and other commercial purposes
  • Data retention: User and event data: 26 months; aggregate data and reports: indefinite.

(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 tracking by Google Analytics, a web analytics service provided by Google. (Google Analytics is a trademark of Google LLC.) We may use this service 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); to help us sell advertising on the site (for example, to inform potential advertisers how many unique visitors the site has in an average month); and for troubleshooting and service improvement purposes.

The service uses cookies (specifically, first-party “tracking cookies”) and scripts to gather information about site visitors, such as (without limitation) their IP address; user agent information; certain other browser and/or device information (such as the brand and model of their mobile device); the date, time, and length of each visit; the referring site, if any; and any related search terms or queries.

The analytics service then uses this data to generate reports and statistics on visitors to this website, such as (without limitation) how many visitors we received during a given period, their approximate geographical locations (estimated based on a process called “IP geolocation”), what pages they most commonly landed on or visited, what search terms have led visitors to this website, and how long the average visitor remained 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.)

Please note that Google Analytics does not provide visitors’ IP addresses or other personal information to us except in the form of 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. (The analytics service’s statistics also presume that the IP addresses recorded reflect a visitor’s actual location and not a proxy server. For example, if a visitor in Texas accesses the site through a proxy server in Switzerland, the analytics service will treat that visitor as coming from Switzerland, not the U.S.)

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 redacting 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 processed by the Google Analytics service. (Google Ads is a trademark of Google LLC.)

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 and reports (which are not personally identifying) may be retained indefinitely, allowing us to track historical trends in website usage.

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, on the Privacy Tools page, or here: Disable Google Analytics Tracking. This will place a cookie on your device’s browser to prevent Google Analytics from tracking you on 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 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 notification 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 the Google 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.)

Website Server, Error, and Security Logs

  • Categories of information gathered: IP addresses; user agent information; visitor activity; errors and suspicious activity; geolocation data (estimated from IP addresses and/or inferred from other data); URLs/websites*; special: mobile phone types/models (determined from user agent information)*; special: other technical details*
  • Purpose(s): security, troubleshooting, quality control, and technical improvement
  • Data retention: Varies, but typically no more than about 90 days, except for recent data captured in backups or specific data for which we have some ongoing need.

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.) Most such logs also include the date and time each logged event took place. 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 described above.

Most of the routine website log data we collect is retained on a rolling basis — that is, we customarily retain only the most recently collected data. Typically, website log data is retained for no more than 30 days (and often only a fraction of that time) before being automatically overwritten by newer data or otherwise deleted. Security audit log data stored by the Sucuri Security plugin (further described in the “Security Scans” section below) is normally retained for about 90 days. Certain website logs that contain only anonymous and/or administrative data (e.g., hit counters) may be retained for longer periods. For example (but without limitation), logs showing the last access dates of certain resources may remain unchanged until that resource is accessed again or we manually delete the logs.

Naturally, we may retain certain specific information from the website’s logs if we still need it for ongoing security, troubleshooting, and/or technical improvement purposes. For example, but without limitation, if the logs indicate that a specific IP address has been used in repeated attempts to attack this website, we may take steps to block that IP address or otherwise impede future malicious activity from it.

Also, some recent log data may be captured in backups created by us or our web host, which in some cases may be retained for a year or more.

Certain events may trigger automated email alerts that are sent to us as the site administrator, notifying us of potential threats, errors, or the status of some automated operation. If the event is a potential threat, it may include the IP address of the device involved (which is also recorded in the website logs). We may retain these email alerts for as long as we need the information they contain.

Please keep in mind that, since our web host, DreamHost®, owns the servers on which this website runs, they have full access to the site’s server and server error logs. (Our access to those logs is read-only, so we cannot redact or remove any of that log data without the aid of our web host’s technical support staff.) In general, DreamHost has access to any data or files on any server they own — except in cases where we have specially encrypted such file(s) or data — subject to the DreamHost Privacy Policy. We may also share additional data with them if we deem it appropriate for security and/or troubleshooting purposes.

Otherwise, we only disclose website log data as described in “Disclosure of Personally Identifying Information” below.

Security Scans

  • Categories of information gathered: IP addresses*; domain names*; user agent information*; visitor activity*; errors and suspicious activity; geolocation data (estimated from IP addresses and/or inferred from other data)*; URLs/websites*; special: visitor mobile phone types/models (determined from user agent information)*; metadata*; special: other technical details relevant for security purposes*
  • Purpose(s): Legal compliance or audit; security, troubleshooting, quality control, and technical improvement
  • Data retention: Varies; potentially indefinite.

We and our web host use a variety of security measures to protect this website, its related services, and their data, including, but not limited to, scanning the site, site-related files, and/or the site database for malware and/or signs of other malicious activity. Some of these scans are purely automated, but in some cases, we may initiate additional manual scans or request that our web host’s technical support staff conduct a more thorough active scan to help us root out a possible security threat or troubleshoot a technical problem.

Among the security measures we use on this website is the Sucuri Security plugin, provided by Media Temple, Inc. d/b/a Sucuri, a subsidiary of Go Daddy Operating Company (Sucuri), which includes activity monitoring, notifications, security auditing tools, 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.) Data gathered through this plugin and/or the scanning service — which may sometimes include personal information such as (without limitation) IP addresses that perform certain suspicious actions and/or information in comments or other published content — may be processed and/or stored by Sucuri as well as us and/or our web host and 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, Sucuri complies with the EU-US Privacy Shield framework, as does Cloudflare®, which serves certain plugin components.

We also use a variety of other anti-malware tools and security measures to protect our device(s), software, and data. A representative sampling of the providers of these tools and security measures is included among the examples of third-party service providers listed under “Disclosure of Personally Identifying Information” below. (Since the specific tools, devices, and security measures we use may change over time, this is not an exhaustive list.)

In addition, our web host also hosts the email servers for many of our email addresses and may scan incoming, outgoing, and/or stored messages for suspected spam and/or malware. Our Internet service provider(s) and/or mobile carrier(s) may also use their own security tools to scan for different types of suspicious activity involving our account(s) and/or connections. (For example, but without limitation, our mobile carrier sometimes flags certain incoming voice calls and/or text messages with warnings such as “scam likely.”)

By their nature, some anti-malware scanners and other security tools routinely access almost any file or data on the systems or devices they protect. Since modern security tools sometimes incorporate web- or cloud-based scanning features, and/or may transmit samples of suspicious files or code to such services for analysis, this means a certain amount of personal information (e.g., names, contact information, and/or other personal details contained in scanned email messages or electronic documents) could be disclosed to the scanning service and/or other third parties in the course of a scan or security analysis. The likelihood and possible extent of such disclosure is difficult to predict or quantify, but it cannot be completely avoided without greatly compromising the security of our system, devices, and data.

(Naturally, malware scanning services and other security tools may also provide us with additional security-related information, such as “signatures” of known malware types. Much of this information is of a technical nature and is not personally identifying, but it may sometimes include certain personal information; see the “Information We Receive from Third for Security Purposes” section below.)

Our retention of data related to security scans and/or other security measures varies depending the tools involved, whether they are operated by us or a third party, and the context. As noted in the “Website Server, Error, and Security Logs” section above, log data stored by Sucuri is normally retained for about 90 days while most other website security log data is typically retained for 30 days or less. Security data for our devices (e.g., malware scan results, system error logs, logs of traffic blocked by a firewall) may in some cases be retained for at least as long as we own that device and/or use the applicable security tool(s). We also typically retain indefinitely any correspondence regarding specific security threats or problems. The retention and use of security-related data by our web host, Internet service provider(s), mobile carrier(s), and/or other third-party service providers varies, and is generally outside of our control.

We may share information from security scans and/or other security measures with third parties, and/or post such information publicly, if we need additional technical assistance, consider such disclosure appropriate for our security and/or the security of others (e.g., to notify DreamHost technical support if we identify malware that might threaten the integrity of their web or email servers), and/or as otherwise described in “Disclosure of Personally Identifying Information” below.

Embedded Content

  • Categories of information gathered: IP addresses; user agent information; visitor activity; geolocation data (estimated from IP addresses and/or inferred from other data); special: login status for certain other websites/services (determined based on cookies)*, mobile phone types/models (determined from user agent information)*, and/or other browser settings/configuration details*
  • Purpose(s): Functionality; providing a service; fulfilling a contractual obligation [see below]; research and publishing; security, troubleshooting, quality control, and technical improvement
  • Data retention: Varies depending on the specific content provider; we do not have access to most such data and so its retention is normally beyond our control.

As explained in the “Definitions” section above, embedded content is content hosted on and served by some server or service other than our web host. If you access a portion of this website that contains embedded content, the embedded content provider can collect information about you.

At a minimum, the information gathered typically includes your IP address, your user agent information, and the fact that you accessed the embedded content from this website. Some embedded content may also place cookies on your device. In certain cases, embedded content providers can also detect the presence of other cookies (such as the ones placed on your device when you log into a specific third-party website or service); your browser’s settings; and/or whether your browser is using certain add-ons such as ad blockers. Such information is collected and processed by the applicable embedded content provider, not by us, and is subject to the provider’s terms of service/terms of use and privacy policy, which are outside of our control.

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 Checks” section above describes how these certificate checks work, although embedded content providers may use different certificate authorities than the one used by this website.)

In some cases, you may be able to hide or disable certain types of embedded content on this website (for example, by using options we may provide through the Privacy Tools, or through your web browser or browser add-ons). Disabling embedded content may prevent that content from functioning, but will generally 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, 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.

Special Note: The reason we include “fulfilling a contractual obligation” among the possible purposes lists above is that the terms of service or terms of use for most embedded content providers typically prohibit us from modifying their embedded content or interfering with the normal function of their servers, which prevents us from (for example, but without limitation) removing tracking features or attempting to block or “spoof” information their servers would otherwise collect.

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(s), 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 may be 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.
  • Certain icons (whether on the administrative dashboard, the public-facing portions of the site, or both) may be served by the Font Awesome content delivery networks, which record your IP address and user information as well as which specific icons your browser accesses or downloads. Font Awesome may use that data for service optimization, troubleshooting, and security purposes; to compile usage statistics; and in some cases to calculate fees for users of their paid accounts (which we are not), as described in their Privacy Policy.
  • 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. Special Note: You can now hide the payment button that appears in the “Support Ate Up With Motor” box (although 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 have access to the data embedded content providers gather about our visitors/users, nor do we usually have any control over those providers’ use and/or retention of that data. Some embedded content providers may use the information they collect about you through your access to or interaction with that content for a variety of commercial purposes, such as showing you advertising or providing information about your online habits to the provider’s clients and customers. The only way we could completely avoid the possibility of such commercial use would be to cease using or offering embedded content and the functionality it provides.

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 is hosted on our website server along with our other site content rather than being served by some external provider.

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 on advertising links or otherwise patronize our advertisers’ businesses, they may gather information about you as described in their respective privacy policies, which is outside of our control.

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

Information You Provide to Us

Through your interactions with this website and its related services, you may provide us with personal information in a number of different ways, described in the sections below.

For obvious reasons, we can’t provide certain services or functionality if you don’t provide us with at least a certain amount of accurate information — for example, we can’t respond to your inquiries if we don’t have a valid email address or other contact information for you. We typically also need your legal name and certain other personal information for financial transactions (see the “Financial Transactions Policy” section below), image use authorizations, and legal communications such as copyright inquiries.

Otherwise, you’re under no obligation to share personal information with us beyond what the site collects automatically.

Consents and Agreements

  • Categories of information gathered: IP addresses*; user agent information*; visitor activity; names*; email addresses*; geolocation data (estimated from IP addresses and/or inferred from other data)*; special: mobile phone types/models (determined from user agent information)*
  • Purpose(s): Legal compliance or audit; security, troubleshooting, quality control, and technical improvement
  • Data retention: Typically indefinite.

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 the “Cookies” section above). Certain site functions or content may not be available unless you indicate your consent to the Privacy Policy and/or other terms.

Some consents are stored only in cookies and are not associated with your name or other personal information. Other consents may be logged in the database in conjunction with other information we have gathered or that you submit to us (such as a comment or feedback form submission). Where we compile logs of user consents and/or privacy choices, 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, or, in some cases, if the consents were logged in conjunction with some plugin, service, or tool we no longer use (in which case the consent log may no longer be usable).

We may disclose saved consent data in connection with a site-related dispute or legal action, and/or as otherwise described in “Disclosure of Personally Identifying Information” below.

Financial Transactions Policy

  • Categories of information gathered: Visitor activity*; names; email addresses; email header information*; other contact information (e.g., phone numbers, postal mailing addresses, and/or other street addresses)*; geolocation data*; URLs/websites*; other personal information*; special: amounts and other transaction-specific details and/or other financial information such as transaction IDs, checks, and/or tax forms* (Please note that the applicable payment processor(s) and/or bank(s)/financial institution(s) may also collect other types of information not listed here.)
  • Purpose(s): Providing a service; completing a transaction; fulfilling a contractual obligation; legal compliance or audit; security, troubleshooting, quality control, and technical improvement; advertising and other commercial purposes
  • Data retention: Usually indefinite.

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) a unique transaction ID number, 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

  • Categories of information gathered: IP addresses; user agent information; visitor activity; names; email addresses; email header information*; other contact information (e.g., phone numbers, postal mailing addresses, and/or other street addresses)*; photos and/or other media (including metadata)*; other documents/materials (including metadata)*; geolocation data*; URLs/websites*; other personal information*; special: mobile phone types/models (determined from user agent information)*
  • Purpose(s): Functionality; providing a service; legal compliance or audit; research and publishing; security, troubleshooting, quality control, and technical improvement
  • Data retention: Typically indefinite, although we promptly delete spam/abuse, comments the submitter asks us to delete, or comments on or in reply to a comment or other content that has been deleted. IP address and user agent information of published comments may be redacted after publication.

Note: Although the comment function includes a box for your name, you are perfectly free to comment us using only a pseudonym. However, without a valid email address, we won’t be able to contact you with any questions about your comment and we may not be able to associate that comment with any other personal information about you (so, for example, it won’t be included if you use the data retrieval tools on the Privacy Tools page).

Comments you submit to Ate Up With Motor are usually moderated, meaning they are not published until we approve them. Any comment you submit may also be subjected to certain automated tests for security purposes. 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 we have obtained; 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 (“stripped”) prior to publication.

Each time a comment is submitted, the website automatically forwards that comment to us as an email notification so that we can review the comment and decide whether or not to approve and publish it. (As noted in “Security Scans” above, this means that any information in your comment may be scanned by various malware-detection and/or other security programs.)

By submitting a comment, we will assume that you are expressly authorizing us to publish and use the contents of that comment (including any images, other media files, and/or links the comment may contain) as described in the Comment Policy section of the Terms of Use. If your comment is approved and published, any information you entered in the “Name” and “Comment” fields (and/or the “Website” field, if we have enabled it) will become publicly visible. The email address you entered in the “Email” field will not be published, nor will your IP address, although any contact information you may have included in the “Comment” field will be, as will any images or other media files you include and the metadata of those files. (See the “Data in Submitted Images” section below.) If the site’s “Recent Comments” widgets are enabled, your name/pseudonym and a link to your comment may also 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 we have enabled the option that allows visitors to request email notifications of replies or follow-up comments, copies of your published comment may also be emailed to visitors who have requested such notifications. Once your comment is published, Ate Up With Motor cannot control and takes no responsibility for what third parties may do with any publicly visible personal information that comment contains!

As noted in “Cookies” above, when you submit a comment, you may have the option to save your name, email, and URL 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 also 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.

If you submit a valid email address with your comment, we may email you at that address prior to or instead of publishing the comment, particularly if we have questions or need to clarify some aspect of your comment. For example (but without limitation), if you have submitted two very similar comments, we might email you to ask which one you prefer us to publish, and if your comment contains what appears to be particularly sensitive information, we typically try to double-check that you wish to publish that information before approving it.

From time to time, we may gather additional personal information about you in connection with your submitted comment(s). For example (but without limitation), we might look up your name in a search engine to better understand who you are and the context of your comment. Naturally, if you offer corrections or clarifications of our articles or other content, we will also take steps to verify that information and, where appropriate, reflect it in the applicable text (and/or make a note of it for future articles/content).

Although the website automatically collects the IP address and user agent information of anyone who submits a comment (information we need for security and troubleshooting purposes and to distinguish human users from automated “bots”), we typically redact that information after a comment is published. We retain the email address along with the comment in case we need to contact the person who submitted it with any questions or issues related to the comment; email addresses are also our primary means of associating comments with the people who submitted them in the event we receive a request to retrieve, delete, or amend personal information.

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. (We may ask you 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 or if we need to take additional steps to verify your identity.)

The deletion of a comment (whether at your request or at our discretion) typically also deletes its associated information, although we may retain that information if we still need it for some specific purpose (e.g., for security or troubleshooting, for legal reasons, or because it contains information pertaining to our content or research), and copies of the comment and its associated information may remain for a time in backups or archives created by us and/or our web host. Keep in mind that even if a previously published comment is deleted, any publicly visible information in that comment (and/or any image(s) or other media it may have included) may have been accessed or used by third parties prior to its removal, which is beyond our control.

Obviously, if you’ve left multiple comments and/or communicated with us in other ways, we may still retain your email address and/or other information in connection with your other comments/messages even if certain of your individual comments are deleted.

We may disclose non-public information related to user comments as described in “Disclosure of Personally Identifying Information” below.

Contact and Image Authorization Forms

  • Categories of information gathered: IP addresses; user agent information; visitor activity; names; email addresses; email header information*; other contact information (e.g., phone numbers, postal mailing addresses, and/or other street addresses)*; photos and/or other media (including metadata)*; other documents/materials (including metadata)*; geolocation data*; URLs/websites*; other personal information*; special: details of legal agreements (where applicable)* and/or mobile phone types/models (determined from user agent information)*
  • Purpose(s): Functionality; providing a service; completing a transaction; legal compliance or audit; research and publishing; security, troubleshooting, quality control, and technical improvement; advertising and other commercial purposes
  • Data retention: Typically indefinite, although we promptly delete obvious spam/abuse, duplicates, blank or unreadable submissions, or any submission containing suspicious code and/or suspicious links.

This section applies to communications you send us via any of the feedback forms, such as the Contact Form or Advertise with Us form, or if you submit an Image Authorization Form or (if offered) a Do Not Sell My Personal Information Opt-Out Form. (The latter form is not currently available, but we may reactivate it in the future, in which case this policy will apply to your use of that form as well as any other feedback forms we may add.)

Special Note on Legal Names vs. Pseudonyms/Aliases: We need your legal name for Image Authorization Forms, requests that pertain to other legal matters (e.g., copyright inquiries), and certain privacy-related requests. For other inquiries, you are free to submit forms using a pseudonym, although if you want us to reply, we do need a valid email address or other contact information. (If you enter a valid email address, the website will also automatically email you a copy of your submission for your records.)

This website may perform certain automated tests on form submissions in order to filter out submissions made by automated bots and discourage spam and other malicious activity. 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. 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 suspicious code.

Because the website forwards new form submissions to us as email notifications, your submitted information may also be scanned by the security programs and/or services that monitor our email for malware and malicious activity, as described in the “Security Scans” section above.

When we receive your submission, we may gather additional personal information about you to help us better understand who you are and the context of your inquiry. For example (but without limitation), if your Contact Form submission contains a business offer or advertising inquiry, we might look up your company name and/or visit your website to learn more about the nature of your business.

Unlike comments, we do not generally publish your form submissions. However, there are certain exceptions:

  • If your inquiry provides significant assistance for our current or future content, we may acknowledge you by name in the “Acknowledgments” and/or “Notes on Sources” sections of the applicable content, as described in Acknowledgments of User Assistance and Information below, unless you indicate or we reasonably surmise that you prefer to remain anonymous.
  • If you ask a general question or report some functional or technical issue with the site, we may (unless you ask us not to) publish excerpts of your question or report on the Ate Up With Motor website and/or its associated social media accounts to respond to your inquiry and/or support other users with similar concerns. We will redact any information that appears to be personally identifying other than your name or pseudonym. If we have published your inquiry in this manner and you wish us to amend or further redact it (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.
  • In the event your message identifies a technical problem that we are unable to fix, we may publish or otherwise communicate the substance of your reported issue (but NOT your name or other personal information) on this website, on our associated social media accounts, in other public forums (e.g., the WordPress support forums), and/or to other third parties to help us determine how to address or repair the problem you identified.
  • If you ask us to publish some portion of your message, we may do so as we deem appropriate.

Otherwise, we may disclose information we receive through and/or in connection with form submissions as described in “Disclosure of Personally Identifying Information” below.

Other Inquiries, Messages, and Support Requests

  • Categories of information gathered: IP addresses*; user agent information*; visitor activity*; names; email addresses*; email header information*; other contact information (e.g., phone numbers, postal mailing addresses, and/or other street addresses)*; photos and/or other media (including metadata)*; other documents/materials (including metadata)*; geolocation data*; URLs/websites*; other personal information*; special: information on or provided by third-party services (as applicable)* and/or mobile phone types/models (determined from user agent information)*
  • Purpose(s): Functionality; providing a service; completing a transaction; legal compliance or audit; research and publishing; security, troubleshooting, quality control, and technical improvement; advertising and other commercial purposes
  • Data retention: Typically indefinite, although we promptly delete obvious spam/abuse, duplicates, blank or unreadable messages, or any message containing suspicious code and/or hyperlinks.

This section refers to messages we receive in connection with Ate Up With Motor that are NOT through comments or the feedback forms on this website. This may include messages you send to our ateupwithmotor.com email addresses, via our associated social media accounts/pages, via our Flickr account, through other third-party websites or services (e.g., our account on a photo hosting website or instant messaging service), by telephone or SMS/MMS text, or by some means not specified here.

Special Note: In general, you’re perfectly free to contact us using a pseudonym unless your message is a privacy request, a legal inquiry or agreement, or in connection with a specific financial transaction. Obviously, some modes of communication are better suited than others for anonymity.

The types of personal information we collect in connection with such messages can vary significantly depending on the specific mode of communication. For example (but without limitation), a text message is unlikely to include your IP address or user agent information, but will almost certainly reveal your phone number. Email messages typically include a variety of potentially identifying metadata in the email headers and any file attachments, such as images (see “Data in Submitted Images” below). If you contact us via a third-party website or service such as social media, the message will likely include your account name, profile picture, and potentially information in your public profile or that you otherwise make visible to us; the message itself might also be publicly visible.

As noted in the “Comments and Personal Information” and “Contact and Image Authorization Forms” sections above, when you contact us, we may sometimes gather additional information about you to help us better understand who you are and the context of your message. For example (but without limitation), if we receive a telephone call from an unfamiliar number, we might look up the number in a search engine or reverse telephone directory, and if you email us a business proposition, we might visit your website to learn more about your business before replying.

If we reply to your message, we will normally do so via the same means you used to contact us unless you indicate that you wish us to respond in some other way. However, if you have sent a site-related message to one of our non-Ate Up With Motor accounts or addresses, we typically prefer, to the extent possible, to forward the message to an appropriate Ate Up With Motor account or address and respond from there instead.

Keep in mind that messages exchanged via a third-party site or service are subject to the terms of service/terms of use and privacy policy of the applicable service, which are outside of our control. This includes messages sent to our personal Gmail or 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 trademark of Google LLC and is subject to the Google Privacy Policy. Yahoo! is now part of Verizon Media® and subject to the Verizon Media Privacy Policy. Until April 2018, Yahoo! 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 is presently owned by SmugMug, Inc.; has its own privacy policy; and is now based on an Amazon Web Services platform, messages we sent or received were previously subject to the privacy policies of Yahoo and later Oath (which have since been superseded by the Verizon Media policy). We initiated the closure of our Yahoo! account on November 11, 2019, although we retain our Flickr account and our personal Gmail account.)

As explained in the “Security Scans” section above, messages we send or receive via email or text may be scanned by various malware scanning services. This may include messages we receive through a third-party website or service if we have message notifications forwarded to us via email or text message. (With some services, notifications include only the fact that a new message was received from a particular sender; other services place the entire message text in the notification.)

Where we receive a message through some third-party website or service, we typically retain, to the extent possible, 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.

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 suspicious code). 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 any data we receive via text may be transferred to other records before the original text is deleted. (For example, 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 our periodic phone backups, which we may retain for a year or more.

We typically retain indefinitely most site-related emails, excepting duplicate messages, obvious spam, messages containing suspicious code, and certain automated notification and alert emails (which we may delete if they are no longer needed and/or relevant). 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 notifications) in addition to (or instead of) leaving them on the applicable third-party website/service. However, 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., if we believe the message/attachment came from a minor child, it appears to be corrupted in some way that creates technical or security problems, or we have agreed to delete it).

We may disclose information received from such messages or other communications in the same circumstances as the examples listed in the “Contact and Image Authorization Forms” section above, or as otherwise described in “Disclosure of Personally Identifying Information” below.

The data retention and data use policies of any third-party websites or services you use to contact us are generally outside of our control.

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 and/or your household. 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.

Data in Submitted Images

  • Categories of information gathered: Names*; email addresses*; other contact information*; photos and/or other media (including metadata); other documents/materials (including metadata)*; geolocation data (provided by the creator/rights holder/repository, determined from metadata, and/or inferred from other data)*; URLs/websites*; other personal information*; special: camera and/or mobile phone types/models (determined from metadata or inferred from other data) and/or potentially personally identifying information such as (without limitation) license plate and/or vehicle identification numbers*
  • Purpose(s): Functionality; providing a service; legal compliance or audit; research and publishing; security, troubleshooting, quality control, and technical improvement; advertising and other commercial purposes
  • Data retention: Typically indefinite, unless we have some specific reason to delete it.

Photographs and other images or media we collect for use on Ate Up With Motor and/or its related services (or for some related business purpose) — 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 voice in a video or audio recording or broadcast) is usually considered to be personal information about that individual. The image might also contain 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.

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 (e.g., file extensions) are necessary for an electronic file to function properly, 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 from an image or media file that 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.

We typically retain indefinitely offline copies and archival backups of the photos, images, and other media files we publish on the Ate Up With Motor website and/or its related services, including, where possible, the associated work files and editing stages, if any, for images or files we have modified. However, we may delete or destroy certain specific images or other media files if they are duplicates, if we deem them unusable (e.g., photos that are out of focus, badly cropped, or too dark to see), if the files are damaged or corrupt, if we have some legal reason to delete them (e.g., if we have agreed to delete all copies of a particular image), or if we elect to not use them (or to discontinue using them) for some other reason. If we have contact information and/or other relevant data pertaining to the creator(s) and/or subject(s) of a particular photograph, image, or other media file (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 file itself.

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.

Information We Receive from Other Sources

Transaction-Related Information We Receive from Third Parties

As noted in the “Financial Transactions Policy” section above, we may receive information about you from third parties in connection with your transactions with us (e.g., transaction reports). See that section for more details.

Information Provided by Social Media Services

  • Categories of information gathered: Visitor activity*; names*; email addresses*; other contact information (e.g., phone numbers, postal mailing addresses, and/or other street addresses)*; photos and/or other media (including metadata)*; URLs/websites*; other personal information*; special: social media service-specific information/insights (e.g., user names/account names, connections with other users, activity on that service)*
  • Purpose(s): Functionality; providing a service; research and publishing; security, troubleshooting, quality control, and technical improvement; advertising and other commercial purposes
  • Data retention: Frequently indefinite.

Social media services typically offer a variety of information and insights about the people who interact with you and/or the content you post on those services and/or with whose content you interact — for example, sending notifications when someone “likes” or comments on your content or providing insights such as summaries of how many people have viewed or otherwise interacted with a specific post. The information we may collect in this manner obviously varies depending on the specific service and context, but it may include (or at least make readily available to us) any information about the applicable person or entity that is publicly visible (e.g., their user name/account name, profile picture, and public profile information) and/or that the person or entity has otherwise made visible to us through their individual settings. Such information typically includes, but is not limited to, details about the individual or entity’s connections with other users of that social media service and/or about the individual or entity’s other activity on that service (e.g., other posts on which they have just commented), and may also reveal a variety of other personal information.

On some social media platforms, certain types of information, insights, and/or notifications can be muted or hidden, but cannot normally be deleted, and may still remain in the social media service’s files even if the applicable content and/or users have been removed. For this reason, most such information can normally be considered to be retained indefinitely, whether or not we separately retain it.

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

Information We Receive from Third Parties for Security Purposes

  • Categories of information gathered: IP addresses*; domain names*; user agent information*; email addresses*; other contact information (e.g., phone numbers, postal mailing addresses, and/or other street addresses)*; geolocation data (estimated based on IP address/domain name and/or inferred from other data)*; URLs/websites*; other personal information*; metadata*; special: other security-related technical details*
  • Purpose(s): Security, troubleshooting, quality control, and technical improvement
  • Data retention: Varies, but potentially indefinite.

Some of the security measures we use to secure this website, its associated services, their data, and/or our system and devices periodically supply us with ban lists/blacklists/block lists of IP addresses, domain names, email addresses, and/or user agents that may be associated with malicious activity such as spam. 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 Avast Software s.r.o and/or their subsidiary Piriform (CCleaner®), through Bitdefender®, via Malwarebytes, via Mozilla Firefox and/or other web browsers, via the NetGuard mobile firewall, through Safer-Networking Ltd.‘s Spybot® software, from the StevenBlack hosts file, via the TinyWall firewall, via the Google Safe Browsing service (which is used by Mozilla Firefox, various other web browsers, and some other online services, and which is subject to the Google Privacy Policy; Google Safe Browsing is a trademark of Google LLC), and/or through browser extensions such as (without limitation) EFF‘s Privacy Badger, InformAction‘s NoScript, and/or uBlock Origin. From time to time, we may also receive additional security-related information from our web host, Internet service provider, mobile carrier, bank, and/or other sources not specified above.

Naturally, our security software and/or services also maintain regularly updated lists of virus signatures and other detection data to identify and prevent malicious activity.

Such security-related information is not necessarily personally identifying (for example, the IP addresses included on spam block lists are typically for email servers rather than individual users), but certain information may be personally identifying or potentially personally identifying (e.g., email addresses associated with spam or telephone numbers used by telemarketers or as part of scams or other malicious activity).

In some cases, we may perform WHOIS or similar lookups on visitors’ IP addresses and/or domain names, especially if they have been used for suspicious or malicious activity directed at the website or at us. 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. (For example, but without limitation, the NetGuard firewall app retrieves such info via IPinfo to help us understand and control the Internet connections our mobile apps make or attempt to make.)

Our retention of such data varies. Much of the information we collect of this kind is managed automatically by our security tools, which regularly update the associated data, adding new information and sometimes changing or removing older data. Also, we periodically make manual changes to that information, such as (without limitation) when we whitelist an email address that was wrongly flagged for spam or blacklist an email address or domain that has sent us suspicious emails.

In many cases, such data is already publicly available (for instance, the HackRepair.com list is readily available at their website). We may also share or otherwise disclose such information if we need additional technical assistance and/or otherwise consider such disclosure appropriate for our security and/or the security of others. For example (but without limitation), we might submit to the maintainers of these lists or databases certain email addresses or domain names that have been used in malicious activity directed at us.

We may also disclose such information in connection with legal action involving malicious activity, and/or as otherwise described in “Disclosure of Personally Identifying Information” below.

Information We Gather Through Our Research or Receive from Other Third-Party Sources

  • Categories of information gathered: Names; email addresses*; other contact information*; photos and/or other media (including metadata)*; other documents/materials (including metadata)*; geolocation data (provided by sources and/or inferred from other data)*; URLs/websites*; other personal information*
  • Purpose(s): Functionality; providing a service; legal compliance or audit; research and publishing; security, troubleshooting, quality control, and technical improvement; advertising and other commercial purposes
  • Data retention: Typically indefinite

Running and creating/publishing content for this website and its related services requires significant amounts of ongoing research. That includes not only researching our historical subjects (or researching other content we’re writing and/or editing as part of our business) and obtaining or creating appropriate images, but also managing various technical and procedural challenges. Some of this research necessarily involves the collection of personal information, whether directly or incidentally.

The following are some representative examples of this information-gathering:

We routinely gather information about the subjects of our automotive articles or other content we write and/or edit in the course of our business, including people involved with and/or otherwise relevant to that content (such as auto industry executives or famous owners of particular models). 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 subjects of one or more of our automotive articles (whether working within the auto industry or studying/publicly commenting about it), and/or are a public figure, some of the information we gather may be about you, your work, and/or your career. In many cases, this information is drawn from sources that were already publicly available at the time of writing, but it may also include non-public information provided by you and/or obtained from third parties. The information we collect 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 certain publicly available information about you for the purposes of properly attributing that content and otherwise complying with the applicable license terms. (Where we deem it 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.

As noted in the “Data in Submitted Images” section above, when we gather photographs and other images or media intended for use on this website or for some related business purpose (whether those images were created by us or obtained from others), we typically look for additional information about the subjects of those images. This information, which may come from a variety of public and/or private sources, may sometimes include personal information (such as, without limitation, the name and/or contact information of a pictured car’s owner or the colorful history of a famous race car driver associated with a particular vehicle) and/or potentially personally identifying information (such as, again without limitation, the license plate number, vehicle identification number, other serial number(s), and/or registration dates) of a particular vehicle).

From time to time, site visitors or other personal or professional acquaintances may provide us with personal information about someone. For example (but without limitation), another visitor might provide us with your contact information so we could ask about your vintage car, send us a clipping of a newspaper interview with you, or submit photographs or other media in which you and/or your car are visible.

As noted in the “Comments and Personal Information”; “Contact and Image Authorization Forms”; and “Other Inquiries, Messages, and Support Requests” sections above, we may sometimes gather additional information about individuals who contact us in order to better understand who they are and the context of their inquiries.

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. If you’re a developer, we may collect or have collected information about you in such contexts.

(Again, the above scenarios are just some representative examples, not an exhaustive list. The disclosures in the “CCPA Information Collection and Sharing Notice” section below will give you a sense of what kinds of personal information we gather through our research.)

Our retention of such information varies depending on the nature of the information and the context in which we received it. We normally retain indefinitely our research notes and other information relevant to our past, current, or possible future articles or content, including image-related information and the suggestions, corrections, and/or references that site visitors provide to us. (Obviously, we don’t necessarily retain or remember every fact we see, read, or hear, but we do typically retain our notes.) Since software licenses typically prohibit redacting or altering any attribution information, we usually retain that information for at least as long as we continue using the applicable software.

Obviously, information we gather for our articles or other content may be published or disclosed in that context; non-public information we receive incidentally, such as email headers, generally will not be except as otherwise described in “Disclosure of Personally Identifying Information” below.

Additional Information about Data Retention

In addition to the data retention practices described in the various sections above, we typically retain indefinitely:

  • Information pertaining to our professional writing/editing work and/or other creative endeavors, including — except as otherwise stipulated by a specific client or employee agreement and/or other applicable legal requirement(s) — research notes, drafts, and/or other relevant data, which may sometimes include information about or in some way connected with visitors to this website and/or users of its related services.
  • Information pertaining to any financial transactions or legal agreements involving Ate Up With Motor, which includes records of purchases or payments we make in connection with the website, such as phone bills or the purchase of research materials. (Obviously, our financial and legal records often necessarily include some personal data.)
  • 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, historians, 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!).
  • Information pertaining to our licenses/authorizations for the use of intellectual property owned by others, including any relevant contact information. (We may discard this information if we discontinue using that intellectual property, e.g., if we uninstall a particular app or other software.)
  • Information pertaining to site-related technical or legal questions.
  • Any information pertaining to a site-related dispute or legal issue. Similarly, for compliance purposes, we must retain information pertaining to privacy-related requests to the extent required by applicable law and/or regulation.
  • 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 log data as of the dates they were created. If you have questions about the contents of these backups, please contact us.

Any other personal information we may collect in connection with this website and/or its related services that is not specified above or mentioned elsewhere in this Privacy Policy 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.

Even where it is our normal practice to retain personal 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 redacting portions of the data that we no longer need.

Acknowledgments of User Assistance and Information

If you provide us with significant personal assistance with Ate Up With Motor content (for example, if you supply images, suggest useful resources, or offer substantial factual corrections) or 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. 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.

Reports and Aggregated Statistics

From time to time, Ate Up With Motor may compile and publish aggregated, non-personally identifying statistical information about users of the website. For example, we may create reports 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, and/or the average time visitors spend on the site. However, such reports and statistics — which we may display publicly and/or otherwise share with third parties (including potential advertisers) — do not include personally identifying information about individual visitors to this website or users of its associated services.

Information Captured by Service/Software/App/Device Telemetry

Many modern electronic services, software programs, apps, and devices, from operating systems to office software and even printers/print drivers, now incorporate surveillance mechanisms (often called “telemetry”) that gather information about the use of that service/software/app/device and then transmit that data to the manufacturer/developer and/or other third parties. The information collected by these mechanisms can sometimes include personal information or potentially personally identifying information about us and/or other individuals.

Here are some examples of how this might occur:

  • If a service/app/software/device crashes while we are accessing a file or website containing personal information, details about that file or website and its contents might be captured and transmitted as part of a crash report.
  • Security features incorporated into our web browsers and/or devices might capture personal information contained in the filenames, metadata, and/or contents of documents or other files we download from or upload to the Internet.
  • Our antivirus software and/or other security services/software/apps might capture personal information in scanned email messages and/or other electronic files.
  • Our office software might record the filenames and/or other metadata of files we access, and/or capture any text on which we use the software’s spelling and/or translation features.
  • Mapping or navigation services/software/apps we use, particularly ones with access to our mobile phone’s location data, might record the geographical locations and/or addresses of people we meet or visit.
  • Services/apps/software/devices with access to device microphone(s) might overhear and/or record our calls or other conversations.
  • Certain services/apps/software/devices might record what we type while using that service/app/software/device.

Again, these examples are just a small sampling of the possible scenarios. The specifics of device and software telemetry vary widely, and manufacturers/developers are not always forthcoming about the details of their information-gathering.

Such surveillance can be difficult or impossible to escape. Certain services/software/apps/devices, like malware detection services, cannot adequately perform their intended functions without full access to device/system data. Some information-gathering features (like the telemetry incorporated into recent versions of the Microsoft® Windows® operating system) can’t be completely disabled without modifications that would violate the license agreement or terms of service. Even where it is theoretically possible to disable the telemetry features of a specific service/software/app/device, doing so may require advanced technical knowledge and/or special tools. Also, our work and research sometimes involves our using devices, software, and/or apps controlled by third parties — e.g., the computers offered to patrons of public libraries — that may incorporate telemetry or other surveillance mechanisms that we cannot disable or with which we are not familiar.

While we have made an effort to block and/or minimize such surveillance — for our privacy and security as well as yours — the bottom line is that some of the services/software/apps/devices we use retain at least the potential to collect and transmit personal information about us, the subjects of our research, and/or the people with whom we interact in the course of our business.

The examples of third-party vendors and service providers listed in the “Disclosure of Personally Identifying Information” section below include a representative sampling of 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/surveillance features. Please note that this is NOT an exhaustive list. We may sometimes use services, software, apps, and/or devices not listed (obviously, it’s not practical for us to list every service, device and/or piece of software we might conceivably use!); certain services/software/apps/devices that did not previously incorporate information-gathering/surveillance features might add them in subsequent updates; and certain services/software/apps/devices may incorporate surveillance features that are not readily apparent to us.

As we noted in the “Security Scans” section above, the likelihood and possible extent of any disclosure of personal information in such ways is difficult to predict or quantify, but it cannot be completely avoided without greatly compromising our security, the functionality of the tools and devices we use, and our ability to perform our work and provide our services.

Disclosure of Personally Identifying Information

We may share, release, or otherwise 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 privacy policies):

  • As part of journalistic or historical accounts we publish, perform, and/or otherwise disseminate (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 many 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 resources such as search engines, library catalogs, and vendors of published works like books or DVDs.
  • 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 collect for publication on Ate Up With Motor or elsewhere — 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 your submitted comments (including, as applicable, any images, other media files, and/or links they may contain), 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.
  • 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.
  • In the form of “Acknowledgments of User Assistance and Information,” as described in the applicable section above.
  • As part of a public response to an inquiry or support request, as described in the “Contact and Image Authorization Forms” and “Other Inquiries, Messages, and Support Requests” sections 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. If you want to modify or remove that information, please contact us!
  • To our independent contractors, employees, agents, and/or business partners (if any) that need to know the information in order to collaborate with us and/or 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. Some or all of these contractors, employees, agents, and/or partners 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. (As noted in the “Information Captured by Service/Software/App/Device Telemetry” section above, 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):
    • Social media services on which we have Ate Up With Motor accounts or pages, such as (without limitation) Facebook® (we initiated the deletion of our Facebook account on December 11, 2018, which deactivated the Ate Up With Motor page, but Facebook likely retains its data; our separate privacy policy for the Ate Up With Motor Facebook Page is archived here); Flickr (a photo-sharing service — owned until April 2018 by Yahoo!®/Oath (which has since become part of Verizon Media®), but now owned by SmugMug, Inc., which has moved the service to an Amazon Web Services platform (making Amazon Web Services a principal Flickr subprocessor) — 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); and/or Twitter.
    • Providers whose services we may use in operating this website, such as (without limitation) our web host, DreamHost® (which also hosts the mail servers for email addresses using this domain name); the Sectigo SSL/TLS Certificate Authority service described in the Certificate Authority Checks section above (and/or other certificate authorities we may use or access); Media Temple, Inc. d/b/a Sucuri, a subsidiary of Go Daddy Operating Company (Sucuri), which provides the Sucuri Security plugin described in the “Security Scans” section above, which is subject to the Sucuri Security Privacy Policy and the Data Processing Addendum to the Sucuri Security Terms of Service); the embedded content providers described in the “Embedded Content” section above; Font Awesome (which, in addition to any embedded content it may serve on this site, may also be used by some of our other vendors and/or service providers in connection with other services we use, such as (without limitation) our web host’s online control panel and web mail interfaces); 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); PayPal® (which serves the payment buttons that appear on the site and processes some payments for us); 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); 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); and/or WHOIS lookup providers (if we need to look up an IP address or a domain registration using tools such as ICANN‘s WHOIS Lookup).
    • Google (which provides the Google Analytics, Google Fonts, Google Hosted Libraries, Google Maps, Google Safe Browsing, Gmail, Feedburner, and Firebase Crashlytics services described elsewhere in this Privacy Policy; the Android operating system and the related Google Mobile Services applications and APIs (Android is a trademark of Google LLC); Google Play and its related services (Google Play is a trademark of Google LLC); their well-known search engine; and other apps, services; and/or tools we may use and/or offer (which are too numerous to list here), and which also owns YouTube, as noted in the “Embedded Content” section above).
    • 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).
    • Other providers whose services enable us to operate and secure our devices, such as (without limitation) 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; 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; Avast Software s.r.o and/or their subsidiary Piriform (CCleaner®) (whose security and maintenance tools we may use on some or all of our systems and devices; their Data Factsheet explains what data their products may gather); Bitdefender® (whose Bitdefender Mobile Security and Bitdefender Central apps and associated services we may use on some of our devices; these apps incorporate Google’s Firebase Crashlytics crash reporter service, which is subject to the Google Privacy Policy); Malwarebytes (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); providers of Internet firewall applications/services, such as (without limitation) TinyWall and the NetGuard mobile firewall and Internet traffic monitor (you can read the NetGuard privacy statement here; NetGuard may also connect to IDB LLC’s IPinfo service to obtain information about IP addresses and/or domains to which mobile apps attempt to connect); and/or encryption software and/or services such as (without limitation) the OpenKeychain open-source mobile encryption app, GnuPG for Windows (Gpg4win), and/or VeraCrypt.
    • Other providers we may use in accessing the Internet, such as (without limitation) our home 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)); ASUS (ASUSTeK Computer Inc.) and/or Netgear Inc. (the manufacturers of our wireless routers and their associated software/services); the open-source Simple DNSCrypt utility (which doesn’t have a privacy policy, although its source code is freely available for review); Cloudflare® (through our use of their recursive domain name system (DNS) resolver services Cloudflare 1.1.1.1 (which is a partnership between Cloudflare and APNIC subject to the Cloudflare Privacy Policy), the 1.1.1.1 App and/or its associated WARP mobile security/encryption service (which are subject to the Cloudflare Application Privacy Policy), and/or the Cloudflare Resolver for Firefox® (which has its own privacy policy); Cloudflare also provides the content delivery network (CDN) and distributed denial-of-service (DDoS) protection services used by some websites or online services we use/visit, also subject to the Cloudflare Privacy Policy); 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; 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); 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 CAD Team (maker of the Cookie AutoDelete browser extension, which does not appear to collect usage data; its source code is freely available for review); 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; InformAction, which currently asserts that it does not collect personal information through the use of its NoScript browser extension; Nodetics, which currently asserts that it does not collect data about the use of its Cookiebro – Cookie Manager browser extension; Thomas Rientjes, developer of the open-source Decentraleyes browser extension (whose Privacy Policy says the extension does not collect user data); and/or the developers of the uBlock Origin browser extension and its related lists.
    • Other providers of apps, tools, and/or services we may use in connection with this website, its related services, and/or the creation of our content, such as (without limitation) 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); Artifex Software, Inc. (which may gather certain information about our use of their SmartOffice® mobile app as described in their App Privacy Policy); the Audacity® open-source audio editing suite (which doesn’t appear to have a privacy policy, although its source code is freely available for review); Peter Batard’s open-source Rufus utility (whose source code is freely available for review); the calibre ebook management suite (which presently lacks a privacy policy, although its code is open-source and publicly available; Cannaverbe Limited (in connection with the use of their CDBurnerXP software); the open-source CDex audio utility; CompanionLink Software, Inc. and their associated subprocessors (whose CompanionLink®, DejaOffice®, and/or DejaDesktop products/services we may use to synchronize data on our mobile device(s); the CompanionLink Data Processing Agreement applies to data the service processes that may be subject to European Union data protection laws); the ComicRack comics reader; DataViz®, Inc. (which might gather information about the use of the Documents To Go app on the older of our BlackBerry® devices); the Document Foundation (through our use of their LibreOffice suite); the open-source FileZilla® FTP client (which doesn’t have a privacy policy, but whose source code is freely available from their downloads page); the open-source GNU Image Manipulation Program (which doesn’t appear to have a privacy policy, although the source code is freely available from their downloads page); Phil Harvey’s ExifTool utility and Bogdan Hrastnik’s related ExifToolGUI user interface for it; the open-source HashCheck Shell Extension; Florian Heidenreich’s Mp3tag utility; the ImgBurn freeware disc-burning utility; JoeJoe‘s Rename Master utility; Petr Lastovicka’s open-source Precise Calculator utility (which doesn’t have a privacy policy, although its source code is freely available for review); the open-source Librera Reader app (the F-Droid version, which according to the developer gathers no personal information and which we have granted no Internet access privileges; the technically inclined can always browse the source code to be sure); the open-source Media Player Classic – Black Edition (MPC-BE) (which doesn’t have a privacy policy, although its source code is freely available for review); the open-source MozBackup utility, (whose source code is freely available for review); the open-source editing tool Notepad++ (which doesn’t appear to have a privacy policy, although again its source code is freely available for review); the open-source Open Camera mobile app; Igor Pavlov’s 7-Zip utility (which doesn’t have a privacy policy, but whose source code is freely available for review); Dương Diệu Pháp’s open-source ImageGlass (which doesn’t have a privacy policy, but whose source code is freely available for review); the open-source PuTTY SSH/Telnet client utility (whose source code is freely available for review); SalSoft’s open-source SQLite Studio (whose source code is freely available for review); Ted Smith’s open-source QuickHash utility (which doesn’t have a privacy policy, although its source code is freely available for review); Tracker Software Products (Canada) Ltd. (in connection with our use of their PDF creation and editing software); and/or VideoLAN‘s open-source VLC media player (which doesn’t appear to have a privacy policy, although its source code is freely available for review).
    • Providers of other search engines and/or other research tools we may use, such as (without limitation) DuckDuckGo and/or StartPage.com (the search engines we most commonly use; we also use StartPage’s associated “Anonymous View” proxy service); Yahoo!®, whose search engine, webmail service, and/or other services and/or tools we may use (Yahoo! is now part of Verizon Media® and subject to the Verizon Media Privacy Policy); the International DOI Foundation, whose servers resolve the DOI® numbers (Digital Object Identifiers) used to identify certain academic papers and other online documents and redirect DOI requests to the appropriate online address(es); libraries, archives, and/or databases, public or otherwise, including but not limited to the Los Angeles Public Library and L.A. County Library (through our use of their computers, catalogs, databases, and/or other systems, and/or our communication with their librarians, archivists, and/or other staff); and/or bookstores and/or other retailers or vendors through which we may search for and/or purchase research materials and/or other site-related materials.
    • Services and/or service providers that help us promote and/or sell (or otherwise offer for commercial advantage) our content, writing/editing services, and/or other creative endeavors, such as (without limitation) literary or talent agents or agencies, publicists, promoters, public relations firms, advertising agencies, brokers, distributors, wholesalers/resellers, booksellers or other retailers, and/or publishers.
    • Other types of service providers, such as (without limitation) third-party 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; taxi and/or ride-share services (which we may use if we travel to meet with you via such means and/or arrange such transportation for you in the course of our business); 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; and/or 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).

    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 subject to the European General Data Protection Regulation (GDPR).

  • 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 the non-public information we collect from individual site visitors or users of the site’s related services. However, we do sometimes license our written content 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 professional writer/editor, so we regularly research, create, adapt, present, publish, and/or 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. (Also, as noted in “Information We Gather Through Our Research or Receive from Other Third-Party Sources” above, our research and writing process often involves discussing and sharing relevant information with third parties.) 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!)

Additionally, some of our service providers and/or vendors (including, though not necessarily limited to, providers of embedded content used on this website, as described in “Embedded Content” above) may use and/or disclose — potentially for advertising, marketing, and/or other commercial purposes — personal information they gather through our use of their content and/or services in ways that are beyond our control. (For example, but without limitation, we have no control over how YouTube uses information they collect about visitors who watch embedded videos we share, or how companies such as search engines or social media services use data they gather through the use of their services.)

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 malware scans, and appropriate password protection.

Your Rights (GDPR and State Laws)

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 (see “Your California Privacy Rights” below), applicable data protection laws may give you certain rights with respect to your personal data, subject to any exemptions provided by the law and/or associated regulations. For example, the rights provided by the GDPR include the rights to:

  • Request access to your personal data
  • Request rectification (correction) of your personal data
  • Request deletion of your personal data
  • Object to our use and processing of your personal data
  • Request that we limit our use and processing of your personal data; and
  • Request portability of your personal data.

Individuals within the European Economic Area subject to the GDPR 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 request 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.)

To 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 et seq. (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 this law, 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 data protection laws, including the California Consumer Privacy Act of 2018 (CCPA), give California residents additional rights with respect to their personal data, including rights similar to those provided by European General Data Protection Regulation (GDPR) rules. The rights the CCPA provides California residents include:

  1. The Right to Know and the Right to Access: You have the right to request access — free of charge, up to two times in a given 12-month period, and (where possible) in “a readily usable format” — to:

    1. The categories and/or specific pieces of personal information we have collected about you in the preceding 12 months, and
    2. The categories of business and/or commercial purposes for which we collected and used the information, and
    3. The categories of sources from which we collected that information, and
    4. The categories of personal information about you that we have shared with third parties for business or commercial purposes in the past 12 months, and
    5. The categories of third parties with whom personal information was shared.
  2. The Right to Delete: You have the right to request the deletion of your personal information.
  3. The Right to Opt Out of the sale of your personal information.
  4. The right to not be discriminated against or penalized for exercising these rights.
  5. The right to make a complaint to a state government supervisory authority.
  6. The right to take private legal action in the event of a data breach that exposes your personal information to theft or unauthorized access.

These rights are subject to certain exemptions, exceptions, and restrictions provided by the law and/or its associated regulations. You need not be physically present in California to exercise these rights provided that you have a current California residence. You may designate an authorized agent to act on your behalf in exercising these rights.

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.

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 law and/or regulations may stipulate the maximum time allowed for acknowledging and/or responding to your request. There is no charge for for making a request.

In order to better safeguard your privacy and the privacy of others, we may be required to verify your identity before processing certain requests pertaining to your personal information. We may be unable to fulfill your request if we cannot verify your identity to the degree of certainty applicable law and/or regulations require. Also, please note that in addition to any exceptions and exemptions applicable law and/or regulations may provide to the rights provided by the CCPA (particularly with regard to the deletion of your personal information), we may be unable to delete certain information (e.g., our web host’s server and error logs) for technical reasons.

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

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, or any of your other rights under the California Consumer Privacy Act (CCPA), such as the right to access or delete your personal information, please visit our Do Not Sell My Personal Information page.

CCPA Information Collection and Sharing Notice

The California Consumer Protection Act of 2018 (CCPA) also requires certain businesses to disclose the categories of information that the business has collected about individuals or households during the preceding 12 months; that the business disclosed for business purposes during the preceding 12 months; and that the business disclosed for commercial purposes during the preceding 12 months. These disclosures must be updated at least once a year.

As noted above, we believe we do not meet any of the CCPA’s applicability thresholds, but for the avoidance of doubt, we make the disclosures listed below.

Categories of Personal Information Collected

The following list summarizes the categories of personal information we have collected about individuals or households, both through or in connection with this website and its related services and in the larger context of our business as a professional writer/editor.

Please note that we do not necessarily collect all of these categories of personal information about every individual, or even most individuals. While we collect certain information from all site visitors (e.g., IP addresses, user agent information), the categories listed below also encompass the range of information we gather in connection with the articles and other content we create and/or edit, which is far more extensive than we customarily gather about site visitors. These categories include information (a) that certain people volunteer to us (e.g., in a comment or other communication), whether about themselves or someone else; (b) that we only collect from/about certain people for some specific reason(s); and/or (c) that we infer or surmise from other data (e.g., inferring an approximate geographical location based on an area code or email domain).

During the past 12 months, we have collected the following categories of personal information in the course of our business:

  • Identifiers, such as:
    • IP addresses
    • Names, pseudonyms/aliases, and/or user names/account names
    • Email addresses
    • Telephone numbers
    • Postal mailing addresses and/or street addresses
    • Social Security Numbers, taxpayer ID numbers, and/or other government-issued identification information
    • Device and/or other online identifiers
  • Commercial information, such as:
    • Records of financial transactions with us, including, where applicable, transaction ID numbers, tax-related information, and check/bank account information (we do NOT collect any bank account or credit card information in connection with PayPal® transactions)
    • Details about cars and/or other vehicles an individual has owned, rented, or otherwise driven, and/or that they have indicated that they want to buy, rent, or drive
    • Information about art, books, other publications, films, videos, and/or other media an individual or household has read, watched, or otherwise consumed (or desires/intends to consume)
    • Information about other property or services an individual or household owns or uses (e.g., Internet service providers, mobile carriers, mobile devices, and/or operating systems, which are often revealed in IP address and/or user agent information), has owned or used, and/or desires/intends to purchase or use
    • Property records (e.g., who owns or has owned a particular building or other real property)
    • Information about other financial transactions
    • Opinions, critical judgments, tastes, and/or preferences, expressed or implied, regarding cars and/or other vehicles; art, books, other publications, films, videos, and/or other media; and/or other products, goods, or services
  • Characteristics of protected classifications, such as:
    • Genders
    • Ages and/or dates of birth
    • Races or ethnicities
    • Religions or religious affiliations
    • Sexual orientations
    • Marital/relationship status and/or information about spouses/partners
    • Information about children, other family members, and/or family history/ancestry
    • Health status information (e.g., health conditions, treatments or therapies received)
  • Internet or other online activity information, such as:
    • Domain names and/or websites/URLs (e.g., personal blogs, social media pages/profiles/feeds)
    • User agent information
    • Web browsing activity and/or history
    • Search history
    • Cookies
    • Errors and/or suspicious activity on this website
    • Other information about an individual’s online interactions
  • Geolocation data (such as a location based on an IP address)
  • Audio, electronic, visual, or similar information, such as photographs, videos, audio recordings, and/or other media in which recognizable individuals or likenesses are visible and/or their voice(s) audible
  • Professional or employment-related information, such as:
    • Current and/or past employer(s)
    • Job title(s) or position(s)
    • Business ownership/registration information (e.g., whether an individual has some ownership interest in and/or is an officer of a corporation or other business entity)
    • Compensation
    • Military service information
    • Other group or organization membership and/or affiliation information
    • Publishing histories/bibliographies/discographies/filmographies/portfolios/CVs/development credits/patent records for writers, artists, designers, performers, developers, engineers, scientists, and other professionals
    • Authorship, other credits, and/or rights holder information for artwork, books, films, software, photographs, other media, other published works or designs, and/or other intellectual property such as trademarks and/or patents
  • Education information (e.g., schools attended, degrees and/or credentials earned)
  • Other financial information (e.g., whether someone has (or had) loans and/or has declared bankruptcy, or the net worth of a public figure)
  • Information about specific vehicles, such as:
    • License plate numbers, vehicle identification numbers, and/or related information (e.g., vehicle registration dates)
    • Other identifying details (e.g., year, make, model, body style, color, equipment, features, distinguishing markings)
  • Other types of personal information (including, but not limited to, additional categories of information defined in the California Customer Records statute, California Civil Code § 1798.80(e)), such as:
    • Signatures, physical and/or digital
    • Other physical characteristics or descriptions of individuals (e.g., height, weight, hair color)
    • Health insurance information (e.g., whether or not individuals are insured and with which insurance carrier(s) — we do NOT collect policy numbers or similar data, and most of the insurance-related data we do receive is in aggregated form)
    • Legal information (e.g., if an individual has been accused of or charged with a crime and/or involved in a civil lawsuit)
    • Political affiliations and/or activity
    • Information about other household members (e.g., roommates, pets)
    • Encryption public keys and similar security data
    • Other potentially identifying information in electronic files and/or associated metadata
    • Other data that could potentially be deemed personal information, but that does not easily fit into any of the above-listed categories
  • Inferences we make.

The fact that we collected and/or inferred certain information does not necessarily mean that we still retain it, or that we have any practical way to associate the different categories of information we may have collected about a given individual or household (e.g., to connect a visitor’s name with an IP address in the server logs and/or a face visible in the background of a photograph).

Keep in mind that if you have interacted with us via some third-party service, that service may have collected and/or shared — potentially for commercial purposes — personal information about you that is not reflected in the above list. The collection/sharing of personal information by third-party services is subject to the applicable service’s privacy policy and terms of use/terms of service, and is outside of our control. (The disclosures above DO include categories of personal information that third-party services have provided to us.)

Collection Sources

Personal information we collect about you or your household comes from one or more of the following categories of sources:

  • You, whether directly through your communications with us, through other public disclosures you’ve made (e.g., social media posts), or through your use of this website and/or its related services
  • Our employees, independent contractors, agents, and/or business partners (as applicable)
  • Our vendors and/or service providers
  • Other visitors/users, whether directly or indirectly
  • Published and/or publicly available sources (e.g., books, articles, films, videos television programs, radio programs, podcasts, other audio recordings, social media, online databases, public records)
  • Photographers, videographers, and/or illustrators
  • Subject matter experts (e.g., historians, biographers), archivists, librarians, observers, eyewitnesses, and/or other knowledgeable parties
  • Clients or employers for whom we provide (or have provided) writing/editing services.

Collection Purposes

Personal information we collect is for one or more of the following purposes:

  • Functionality
  • Providing a service
  • Completing a transaction
  • Fulfilling a contractual obligation
  • Legal compliance or audit
  • Research and publishing
  • Security, troubleshooting, quality control, and technical improvement
  • Advertising and other commercial purposes

These purposes are defined in the “Categories of Information and Purposes for Collection” section above and have the same meanings here as in other sections of this Privacy Policy.

Information Shared for Business or Commercial Purposes

The CCPA defines sharing information “for business purposes” as disclosing personal information about individuals or households to third parties such as service providers or independent contractors for any of the following purposes:

  1. Auditing interactions with consumers
  2. Security
  3. Debugging/repair
  4. Certain short-term uses
  5. Performing services
  6. Internal research for tech development
  7. Quality and safety maintenance and verification.

A disclosure of personal information is considered to be “for commercial purposes” if it serves to “advance a person’s commercial or economic interests, such as by inducing another person to buy, rent, lease, join, subscribe to, provide, or exchange products, goods, property, information, or services, or enabling or effecting, directly or indirectly, a commercial transaction,” with the exception of “engaging in speech that state or federal courts have recognized as noncommercial speech, including political speech and journalism.”

We may disclose personal information we collect through or in connection with Ate Up With Motor as described in the “Disclosure of Personally Identifying Information” section above. Also, as noted in that section, the proprietor of this website is a professional writer/editor, an occupation that routinely involves collecting and sharing personal information through and/or in connection with our writing/editing work and/or other creative endeavors. Therefore, we may share personal information we collect in the course of our business with any or all of the following:

  • Our employees, independent contractors, agents, and/or business partners, if any.
  • Service providers and/or vendors we use in connection with this website, our other professional activities, and/or the management of our business.
  • Any government agency, investigator, auditor, court, arbiter, or other official entity that requires or compels us to disclose personal information related to our business.
  • Any individual or entity with whom we communicate, consult, and/or collaborate in the course of researching and developing our content, writing/editing work, and/or other creative endeavors, and/or who communicates and/or consults with us regarding their content and/or other creative endeavors.
  • Editors, publishers, clients, employers, and/or other third parties for whom we provide writing/editing services and/or to whom we may license, sell, or otherwise offer our content and/or other creative work.
  • Individuals or entities who help us promote and/or sell (or otherwise offer for commercial advantage) our content, writing/editing services, and/or other creative endeavors.
  • The public, through the publication, performance, broadcast, other dissemination, and/or public discussion of our content and/or other creative work; our sharing, discussing, and/or otherwise disseminating information that is already publicly available (e.g., in news articles, published works, and/or public records); and/or, as applicable, our publication of your comments, any images and/or other media you submit to us, and/or your other communications with us.

The CCPA’s definitions are so expansive that almost any disclosure or transmission of virtually any piece of information about any individual or household — even information that was already publicly available — could potentially be considered sharing of personal information for business or commercial purposes if it takes place in any business-related context.

Much if not all of the personal information we collect or access in the course of our business may be processed by one or more third parties. For example (but without limitation):

  • For obvious reasons, it is impossible for us to call, text, email, or mail any individual or household without disclosing a certain amount of the recipient’s personal information to third parties. For example, making a phone call or sending a text message requires communicating the recipient’s telephone number to the applicable telephone companies or mobile carriers.
  • Our web host, DreamHost®, owns the web servers on which this website runs as well as the mail servers for our associated email addresses. Therefore, DreamHost has full administrative access to most files, messages, and data processed by or stored on those servers. (This is in addition to any information we deliberately share with DreamHost for purposes such as troubleshooting or security.)
  • If in the course of our business we access any website or online resource that is not encrypted (i.e., via an HTTP rather than HTTPS connection), any data we access on that site or resource is visible to our Internet service provider and potentially also other third parties. Even if a website or online resource IS encrypted, our Internet service provider and other third parties (such as our DNS (domain name system) server and the website or resource’s certificate authority and embedded content providers) can generally see that we have connected to that site or resource, as can that site/resource’s certificate authority and embedded content providers, if any. If we use a proxy server or VPN, the VPN or proxy server can also see our connections and any unencrypted data we access.
  • Most files and data on our systems and devices are routinely scanned by one or more malware detection and/or other security tools, some of which may incorporate cloud-based scanning or analysis features, as explained in the “Security Scans” section of this policy. (As noted in that section, some website security log data is also stored by Sucuri.)
  • Most payments we receive are processed by our bank(s) (or other applicable financial institution(s) and the applicable payment processor, if any (e.g., PayPal®). Those payments and any related tax documents must also be disclosed to several different tax agencies, and may be discussed with our tax preparer and/or other financial or legal professionals for administrative and compliance purposes.
  • Some information about our activities and/or data accessed on our systems and devices may have been captured by the telemetry and/or other surveillance features of the software, apps, services, and devices we use, as explained in the “Information Captured by Service/Software/App/Device Telemetry” section of this Privacy Policy.

Any or all of the above would likely be considered disclosures for business purposes by the CCPA’s definitions.

The collection of information on website visitors by the Google Analytics service, described in “Online Tracking” above, also constitutes sharing information for business purposes. (See that section to learn more about what information that may include and your options for opting out.)

Actions like the following could also be deemed sharing information “for business purposes” if we do so in some business-related context:

  • Looking up someone’s name in a search engine, library catalog, or other database.
  • Entering someone’s address into a mapping or navigation service to look up driving directions, or meeting with someone face to face while our phone’s geolocation services are turned on.
  • Using an automated translation service to translate text containing any names or other personal information.
  • Printing a document containing names or other personal information using a commercial print service or a printer controlled by a third party (e.g., printing a copy of a news article we read at the public library).
  • Performing a WHOIS lookup on an IP address from the website’s security or error logs, or allowing our firewall or other security software to perform such lookups.
  • Storing or transmitting any electronic file containing personal information using any cloud storage service or other online storage system.
  • Sharing links to a news article or online post that contains names or other personal information.
  • Describing an unusual or distinctive vehicle we saw on the street or in some other public setting.
  • Discussing the life and career of a well-known public figure with other writers, historians, enthusiasts, or subject matter experts, whether or not the information discussed is already publicly available.
  • Publishing or submitting for publication any content that contains any personal information such as names, photographs, videos, or biographical information. (Even publishing a bibliography with authors’ names might count.)

(These are just a few examples, not an exhaustive list.)

Because the proprietor of this website is a professional writer/editor and much (though not all) of the information we collect in connection with our business is intended for publication — whether on this website or elsewhere — a variety of activities we routinely undertake in connection with our work could potentially be deemed “commercial” as defined by the CCPA, even if our actual content is deemed “noncommercial speech.” (For writers, photographers, and other creative professionals, the distinction between “commercial” activity and engaging in “noncommercial speech” as an integral part of one’s business is a complicated, muddy legal question mark.) Examples could include:

  • Licensing, selling, or otherwise offering our articles or other content for money or other valuable consideration (including offering the content on this website, which is supported by advertising and user contributions) if that content incorporates any names or other personal information about individuals or households.
  • Advertising, promoting, or marketing our content, or published works incorporating our content, if that content contains any names or personal information or if such information is referenced in the promotion or marketing.
  • Proposing or pitching articles, books, or any other content containing names or other personal information to editors, agents, or publishers.
  • Sharing, exchanging, or discussing with clients, coauthors, or collaborators any personal information pertaining to articles, books, or other content we are creating and/or editing for commercial advantage.
  • Arranging for people featured and/or quoted in our content to receive complimentary copies of our published work or be notified of its publication or commercial availability.

Even if disclosures like these are NOT deemed to be “for commercial purposes” by the CCPA’s definitions, they are certainly “for business purposes.”

From time to time, we may also facilitate other types of commercial transactions, whether directly or indirectly, such as:

  • By putting into contact (with their mutual consent) parties who have expressed interest in some transaction with one another. For example:
    • If a visitor asks about licensing a photo or other content on Ate Up With Motor that is owned by someone else, we might ask the applicable rights holder if they’re comfortable with our putting them in touch with the interested party.
    • If a site visitor expresses interest in purchasing an item another visitor has indicated a desire to sell, we might assist the two parties in contacting one another.
  • By recommending that a professional contact or acquaintance be hired for a job, assignment, or commission, or chosen as a vendor or service provider.
  • By endorsing (explicitly or by implication) some author, artist, service provider, or vendor, and/or their products or services.

By the CCPA’s definitions, disclosing any personal information in such circumstances might be deemed sharing information “for commercial purposes” whether or not any transaction is actually completed, whether or not we are a party to that transaction, and whether or not we receive any compensation or consideration in connection with it.

As noted in “Ads on Ate Up With Motor” above, we do not allow our advertisers to gather information about you while you are on the Ate Up With Motor website. However, if you click on advertising links or otherwise patronize our advertisers’ businesses, they may gather information about you as described in their respective privacy policies, which is outside of our control. This could conceivably be deemed to constitute sharing information “for commercial purposes” as the CCPA defines it, even if we do not directly provide any information about you to those advertisers.

Additionally, some of our embedded content providers (described the “Embedded Content” section above) and/or other service providers might use information collected about our visitors (and/or otherwise obtained from us) for commercial purposes. For example (but without limitation), if you accessed a YouTube video we shared, particularly if you were logged into a Google Account at the time, YouTube may have shown you advertisements and likely added your viewing history to the repository of data Google (which owns YouTube) has compiled about you, much of which is used for commercial purposes. Although we typically have no control over such use (other than completely discontinuing the use of embedded content or third-party services), this too could be deemed sharing information “for commercial purposes” as defined by the CCPA.

Put simply, by the law’s extremely broad definitions, any or all of the categories of personal information we collect in the course of our business could be deemed to be shared for business and/or commercial purposes, whether or not we “sell” personal information in the way most people understand that term.

You can learn more about the circumstances under which we may share or otherwise disclose personal information we collect through and/or in connection with this website and/or its related services in the “Disclosure of Personally Identifying Information” section above.

If you have general questions about our data-sharing practices (i.e., questions about our typical practices rather than about the personal data of any specific individual or household), feel free to contact us using one of the methods shown under “Controllers, Questions, and How to Reach Us” below. If you are a California resident and would like to exercise your rights under the California Consumer Privacy Act (CCPA), such as the right to access or delete your personal information or 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 by using the Contact Form. If you are a California resident and wish to exercise your rights under the California Consumer Privacy Act (CCPA), please contact us via 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:

  • January 26, 2020: Updated and clarified the Information Provided by Social Media Services in an effort to better describe the scope of information social media services may make available. In Definitions, corrected the spelling of “referer” [sic] and clarified that it is (mis)spelled that way on purpose. Fixed a link error.
  • January 24, 2020: In CCPA Information Collection and Sharing Notice, further updated the Information Shared for Business or Commercial Purposes subsection to change the bullet point that read “Any individual or entity with whom we communicate and/or collaborate in the process of researching and developing our content, writing/editing work, and/or other creative endeavors” to “Any individual or entity with whom we communicate, consult, and/or collaborate in the course of researching and developing our content, writing/editing work, and/or other creative endeavors, and/or who communicates and/or consults with us regarding their content and/or other creative endeavors.” In Disclosure of Personally Identifying Information, added “taxi and/or ride-share services” to the examples of third-party service providers. In that list, separated Microsoft into its own bullet point and fixed a typographical error. Updated Controllers, Questions, and How to Reach Us to change the phrase “please contact us using one of the contact methods …” to “please contact us via one of the contact methods …”
  • January 23, 2020: In Information We Receive from Third Parties for Security Purposes, changed “via the Mozilla Firefox browser” to “via Mozilla Firefox and/or other web browsers” and also added Google Safe Browsing (which is used by Mozilla Firefox, various other web browsers, and some other online services) to the examples of information sources. Fixed a typo in that list. Added InformAction’s NoScript extension to that section and to the examples of third-party service providers listed under Disclosure of Personally Identifying Information. Also added the CAD Team (maker of the Cookie AutoDelete browser extension), Nodetics (maker of the Cookiebro – Cookie Manager extension), and Thomas Rientjes’ Decentraleyes to the latter list.
  • January 22, 2020: In CCPA Information Collection and Sharing Notice, further updated the Information Shared for Business or Commercial Purposes subsection to change “… sharing and/or discussion of information that is already publicly available” to “… sharing, discussing, and/or otherwise disseminating information that is already publicly available.” Added Font Awesome to the examples of Embedded Content providers and third-party service providers in Disclosure of Personally Identifying Information.
  • January 21, 2020: In CCPA Information Collection and Sharing Notice, updated the Categories of Personal Information Collected subsection’s examples of commercial information collected to include information about art, books, other publications, films, videos, and/or other media an individual or household has read, watched, or otherwise consumed (or desires/intends to consume) and opinions, critical judgments, tastes, and/or preferences, expressed or implied, regarding cars and/or other vehicles; art, books, other publications, films, videos, and/or other media; and/or other products, goods, or services. Also updated the item beginning “Information about other property or services …” to append “and/or desires/intends to purchase or use,” slightly rearranging the wording to better accommodate the additional clause. Updated the item under professional or employment-related information regarding authorship and rights holder information to change “for books, films, software, photographs, other published works or designs, and/or for other intellectual property …” to “for artwork, books, films, software, photographs, other media, other published works or designs, and/or other intellectual property …” Updated the Information Shared for Business or Commercial Purposes subsection to reiterate that we may also share and/or discuss information that is already publicly available (e.g., in news articles, published works, and/or public records). Also changed “the general public” to just “the public.”
  • January 20, 2020: In CCPA Information Collection and Sharing Notice, updated the Collection Sources list to also include employees, independent contractors, agents, business partners, photographers, videographers, illustrators, observers, eyewitnesses, and clients or employers for whom we provide (or have provided) writing/editing services. Made some minor adjustments to the wording and punctuation of other items on that list. Updated the Information Shared for Business or Commercial Purposes subsection to change “Editors, publishers, clients, and/or other third parties …” to “Editors, publishers, clients, employers, and/or other third parties …”
  • January 18, 2020: Updated the examples of third-party service providers in Disclosure of Personally Identifying Information and revised the Information Shared for Business or Commercial Purposes subsection of the CCPA Information Collection and Sharing Notice to include service providers and other entities who help us promote and/or sell (or otherwise offer for commercial advantage) our content, other creative endeavors, and/or services (e.g., literary or talent agents or agencies, publicists, promoters, public relations firms, ad agencies, brokers, and the like).
  • January 17, 2020: In Disclosure of Personally Identifying Information, updated the examples of third-party service providers to include DataViz®, Inc. (in connection with the Documents to Go BlackBerry® app), Tracker Software Products (in connection with their PDF creation and editing software), and a variety of open-source and freeware programs/apps. Fixed some inconsistent punctuation in that section and changed “and bookstores …” to “and/or bookstores …” Fixed a typo in this list.
  • January 16, 2020: In Disclosure of Personally Identifying Information, updated the examples of third-party service providers to include Librera Reader and Notepad++. Rearranged several items in that bullet point to put them in alphabetical order and made some minor text edits for consistency of presentation.
  • January 15, 2020: Updated California Privacy and Data Protection Rights to note that, except as otherwise required by law, privacy-related requests pertaining to children under 18 should be submitted by a parent, legal guardian, or other authorized adult representative and change “You may authorize an agent …” to “You may designate an authorized agent …”
  • January 14, 2020: Updated Information We Receive from Third Parties for Security Purposes to include some additional information sources.
  • January 13, 2020: In California Privacy and Data Protection Rights: Categories of Personal Information Collected, changed “photographs, videos, audio recordings, and other media …” to “photographs, videos, audio recordings, and/or other media …” In Comments and Personal Information, clarified some of the language about data retention and the deletion of comments and fixed some clunky grammar in the language about the information that becomes publicly visible when a comment is published. Rearranged some text in that section for better flow.li>
  • January 12, 2020: In California Privacy and Data Protection Rights, changed “The purposes for which we shared or disclosed the information” to “The categories of business and/or commercial purposes for which we collected and used the information”; changed “The categories of such third parties” to “The categories of third parties with whom personal information was shared”; rearranged the order of those bullet points; and struck the word “unredacted” from the phrase “… that exposes your unredacted personal information …”
  • January 10, 2020: In Disclosure of Personally Identifying Information, amended the language about embedded content providers’ possible use or disclosure of information to also include other service providers and/or vendors. Updated Website Server, Error, and Security Logs to clarify that the logs typically include dates and times in addition to the other types of information described.
  • January 8, 2020: Further clarified some language in CCPA Information Collection and Sharing Notice. Fixed some inconsistent punctuation and an improperly configured anchor link. In Disclosure of Personally Identifying Information, updated the link to the privacy policy for the Artifex SmartOffice app. In Definitions, further adjusted the entry for “personal information.”
  • January 7, 2020: Made some minor adjustments to Categories of Information and Purposes for Collection, fixing a grammatical error and changing a parenthetical aside about “associated services” to “related services.” Added “advertising and other commercial purposes” to the list of potential purposes under Financial Transactions Policy; Contact and Image Authorization Forms; Other Inquiries, Messages, and Support Requests; Data in Submitted Images; Information Provided by Social Media Services; and Information We Gather Through Our Research or Receive from Other Third-Party Sources.
  • January 6, 2020: Updated Cookies to note that while the cookie descriptions include the cookies typically used on this website, embedded content providers may sometimes change or add cookies, and the descriptions may not include cookies set by certain administrative dashboard components.
  • January 5, 2020: Further updated CCPA Information Collection and Sharing Notice to include a more emphatic statement about how by the law’s broad definitions, any or all of the categories of personal information we collect in the course of our business could be deemed to be shared for business and/or commercial purposes, even if we do not “sell” personal information in the way most people understand that term. Also, in the lists of categories of personal information, moved “signatures” from “Identifiers” to “Other types of personal information” (also changing “written and/or digital” to “physical and/or digital”) and moved “domain names and/or websites/URLs” to “Internet or other online activity information.” Removed an inadvertent duplication of “identifiers.” Renamed “Information about an individual or household’s financial status” to “Other financial information” and made it a separate category. Reordered several of the items under “Other types of personal information.” Added “Other information about an individual’s online interactions” to “Internet or other online activity information” and changed “Errors and/or suspicious activity” to “Errors and/or suspicious activity on this website.”
  • January 4, 2020: In CCPA Information Collection and Sharing Notice, noted that the collection of information by the Google Analytics service also counts as sharing personal information for business purposes. Also updated the examples of commercial information collected, changing “personal property or services” to “property or services” and adding a separate item about property records.
  • January 3, 2020: In Information We Receive from Third Parties for Security Purposes, added the StevenBlack hosts file to the list of examples of sources. In Definitions, in the item on “personal information,” changed “(which for the purposes of this policy we treat synonymously)” to “(terms this policy uses synonymously).” Updated Legal Bases for Collecting and Using Information to reword the first sentence (fixing the grammar and making clear that it applies to people in areas subject to European data protection laws); reorder several items; and change “to better understand how (and how many) people access our content, and to appropriately respond …” to “to better understand how (and how many) people access our content, and/or to appropriately respond …” in the last bullet point. Added the calibre ebook management suite to the examples of third-party service providers under Disclosure of Personally Identifying Information. Updated Website Server, Error, and Security Logs to add “special: other technical details*” to the types of information gathered. Fixed a typo in Information We Receive from Third Parties for Security Purposes. In Additional Information about Data Retention, updated the item about information related to the use of intellectual property owned by others to note that we may delete such information if we discontinue using that intellectual property for some reason (e.g., if we uninstall and delete some app or software) and change “it is our customary practice to retain …” to “we typically retain …”
  • January 2, 2020: In the Information Shared for Business or Commercial Purposes section, amended that section’s second list (the one prefaced with the sentence “We may disclose personal information we collect …”) to refer back to the Disclosure of Personally Identifying Information section, revised some wording (striking the phrase “for commercial advantage”; changing “publication, performance, broadcast, and/or other dissemination” to “publication, performance, broadcast, other dissemination, and/or public discussion”; and adding “and/or, as applicable, our publication of your comments, any images and/or other media you submit to us, and/or your other communications with us” to the item about disclosures to the general public), reordered some items, and adjusted the punctuation. Later in that section, added some additional language about advertising disclosures. Clarified some language in Ads on Ate Up With Motor. In the Additional Information about Data Retention, Disclosure of Personally Identifying Information, and CCPA Information Collection and Sharing Notice sections, changed the word “freelance” to “professional” (because not all of our professional writing/editing work is necessarily in a freelance capacity). In Disclosure of Personally Identifying Information, amended the paragraph following the bullet-pointed list to reiterate (as already explained in Information We Gather Through Our Research or Receive from Other Third-Party Sources) that our research and writing process process often involves discussing or sharing relevant information with third parties. Fixed a link formatting error in Embedded Content. In Data in Submitted Images, updated the list at the beginning to note that geolocation data may be “provided by provided by the creator/rights holder/repository, determined from metadata, and/or inferred from other data.” In Definitions, in the definition of “IP address,” changed “Each device that can access the Internet has its own IP address; if you use several different Internet-capable devices, their individual IP addresses are usually all different” to “If you use several different Internet-capable devices, their individual IP addresses are typically all different (although if you have several devices connected to the same router or tethered together, they might share the same IP address so long as they remain connected or tethered).”
  • January 1, 2020: Added the International DOI Foundation to the examples of third-party service providers under Disclosure of Personally Identifying Information. In the first sentence of that section, changed “may release or disclose …” to “may share, release, or otherwise disclose …” Also in that section, made some adjustments to the wording of the first bullet point (beginning “As part of journalistic or historical accounts …”), including emphasizing that such accounts may be published. In the paragraph immediately following that section’s large bullet-pointed list, corrected a duplication of the word “perform.” Under California Privacy and Data Protection Rights, simplified the language about verifying your identity before processing certain privacy requests. Under Categories of Personal Information Collected, added compensation to the examples of professional or employment-related information collected and changed “Current or past employer(s)” to “Current and/or past employer(s).” Under Definitions, changed the boldface heading “Personal information” to “Personal information/personally identifying information,” since this policy treats those terms synonymously. Under Your Rights (GDPR and State Laws), clarified the wording of the first paragraph and the list of rights provided by the GDPR.
  • December 31, 2019: In Disclosure of Personally Identifying Information, updated the description of Piriform (CCleaner) to include a link to their Data factsheet and clarify that their products include security and maintenance tools (rather than just security tools). Renamed the CCPA Information Collection and Disclosure Notice section “CCPA Information Collection and Sharing Notice” and adjusted other references to that section accordingly. Reordered and clarified some of the categories of personal information listed in that section (taking some cues from the latest update of Automattic’s Privacy Policy). In Definitions, changed “personal identifiers” to just “identifiers,” clarified that that term can also include device identifiers, and updated the item about IP addresses to note that the IP address typically also reveals the Internet service provider or mobile carrier you are using.
  • December 30, 2019: In the Disclosure of Personally Identifying Information bullet point regarding independent contractors, employees, agents, and business partners, struck the parenthetical phrase “(e.g., on our content, our other writing/editing work, and/or other creative endeavors)” after “collaborate with us.”
  • December 29, 2019: Extensive revamp, adding a table of contents, definitions, several new sections (including one on the possibility of personal data being captured by software/device telemetry), and additional information and disclosures related to the California Consumer Privacy Act (CCPA); reorganizing and/or renaming some sections (including integrating most of the data retention info into the applicable sections); reorganizing/updating the third-party service provider examples (including restoring some items that had been inadvertently deleted and adding others); making many minor corrections; and revising substantial portions of the text to better explain how and why we collect personal information. Moved older entries in this Recent Revisions list to a separate page. Assorted stylistic adjustments.
  • December 28, 2019: In Disclosure of Personally Identifying Information, updated the description of Bitdefender to include both the Bitdefender Mobile Security and Bitdefender Central apps and note that they use Google’s Firebase Crashlytics crash reporting service. Updated Information We Receive from Other Sources to provide an example of how the NetGuard firewall app provides information about the IP addresses or domains to which our mobile apps connect or try to connect. Added this to the description of Netguard under Disclosure of Personally Identifying Information.
  • December 26, 2019: In California Privacy and Data Protection Rights, updated the description of the proposed verification requirements to include the verification standards that may be required for data deletion requests.
  • December 25, 2019: In Data Retention, updated the bullet point about our customary retention of photos and other images to change “it is our customary practice to indefinitely retain” to “we typically retain indefinitely” and note that we may also delete specific images if they are duplicates, if we deem them unusable, if they are damaged or corrupted, if we have some legal reason to delete them, or if we elect to not use them (or to discontinue using them) for some other reason. Changed the phrase “including our associated work files and editing stages” to “including, where possible, our associated work files and editing stages.” Added Yahoo!® to the list of examples of third-party service providers under Disclosure of Personally Identifying Information. In that same section’s description of Google, added their well-known search engine to the listed examples of their services. In Online Tracking, changed the phrase to “how often specific Google search keywords lead visitors to this website” to “what specific search keywords lead visitors to this website” (because these analytics results aren’t necessarily limited to Google search results) and struck the word “necessarily …” in the phrase “such as (though not necessarily limited to) …” in the description of the information the analytics service may collect.
  • December 24, 2019: In Disclosure of Personally Identifying Information, updated the description of Startpage.com to note that we also use Startpage’s associated proxy service. Updated the reference to libraries and archives to add links to the privacy policies of two local public libraries we use. Following the bullet-pointed list, changed the sentence “In general, we do not sell or rent information about individual site visitors (or users of the site’s related services)” to “In general, we do not sell or rent the non-public information we collect from individual site visitors or users of the site’s related services.” In GDPR and State Law, struck the parenthetical phrase “(starting in 2020, California residents may request this up to twice per year)” after “Request portability of your personal data” (to avoid contradicting the Your California Privacy Rights section). Further updated the text of the California Privacy and Data Protection Rights section.
  • December 22, 2019: In Controllers, Questions, and How to Reach Us, changed “… and wish to submit a privacy-related request under the CCPA, please use one of the contact methods …” to “… and wish to exercise your rights under the California Consumer Privacy Act (CCPA), please contact us using one of the contact methods …” Further adjusted the description of rights under California Privacy and Data Protection Rights and Do Not Sell My Personal Information. Under Disclosure of Personally Identifying Information, changed the phrase “Photos we use on Ate Up With Motor” to “Photos we collect for publication on Ate Up With Motor or elsewhere.”
  • December 21, 2019: In Disclosure of Personally Identifying Information, updated the description of Cloudflare to note that websites and online services we visit/use may use Cloudflare’s CDN and/or DDoS protection services. Also fixed a typographical error in that language and corrected the links to the Cloudflare privacy policies that apply to each service. Made some clarifications and updates to the list of rights under California Privacy and Data Protection Rights.
  • December 19, 2019: In Other Inquiries, Messages, and Support Requests and Disclosure of Personally Identifying Information, updated the description of Flickr to clarify the wording and indicate that the service is now on an Amazon Web Services platform (making Amazon Web Services a principal Flickr subprocessor).
  • 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 types/models 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.

For space reasons, we have moved the older entries in this revision list to a separate Older Privacy Policy Revisions page.

Updated: January 26, 2020 — 11:54 pm