Skip to content

Legal

Cookies

Two analytics cookies, two strictly necessary ones, and no advertising. Here is what each holds, and how to refuse the ones that are optional.

Effective

The short version

This site sets no advertising cookies and no cross-site tracking cookies. It does set a pair of analytics cookies, through Google Analytics, so that we can tell how many people read a page and which of our own pages sent them there. That is the whole of it, and the rest of this page says exactly what it holds and how to refuse it.

What this site uses

Three things. The first two are strictly necessary; the third is the analytics pair, and it is not.

  • Our hosting provider may set a cookie needed to serve and secure the site: routing a request correctly, or absorbing an attack. It carries no profile and is not used to recognize you across sites.
  • The anti-spam challenge on the inquiry form is served by Cloudflare and may set a strictly necessary cookie in order to run and validate the challenge. It exists to tell a person from a script and is not used for advertising or tracking.
  • Google Analytics sets two first-party cookies, _ga and _ga_4JW6T4PQWW. They hold a random identifier and session state so that three page views in one sitting are counted as one visit and a return next week is counted as a returning reader. They expire after two years, they carry nothing you typed, and because they are set on computingamerica.com, moving between the four sections of the site counts as one visit and not four.

The analytics cookies, and how to refuse them

Google Analytics: which pages you viewed and in what order, how long you stayed, which site or search linked you here, the country and approximate city your visit came from, your device, browser and screen size, and whether you sent the contact form, recorded as one count with the section of the site you sent it from and never with anything you wrote in it, and whether you pressed our published email address or telephone number, recorded as which of the two and the part of the page it was in, and nothing else. On our packages pages we also count each step as a named event. select_item is pressing a package’s link, recorded with the package, the plan and the part of the page it was in. view_item is seeing a package’s payment form, recorded with the package, the plan and the monthly price. begin_checkout is starting to pay, and purchase is completing a payment. Both are recorded with the package and plan, the amount, whether billing is monthly or yearly, and whether the add-on and a promotion code were chosen, as yes or no. When you pay for a package, our server tells Google Analytics what was bought and the amount, under your browser’s analytics id and the number of that visit, or a random id if there is none, with no name or email. A payment made in our test mode is sent as purchase_test instead, with the same details and no amount, so it never counts as revenue. Pressing a link to our contact page on those pages is recorded the same way, as form and the part of the page it was in. On our free check of whether someone can send email as you, check_domain is one run of the check, recorded with its result only, such as protected or DMARC missing, or the kind of error. generate_lead is sending the follow-up form after the check, recorded as coming from the check. None of these events carries the domain you checked, your name, your email address, your telephone number, the text of a promotion code, anything else you typed, or your card. Google receives your IP address in order to derive that location and to protect the service, and does not store it. We have not enabled Google Signals, ad personalization or any advertising integration on the property, so nothing collected here is used to target advertising or joined to your Google account.

Refusing them costs you nothing here. Every page on this site works identically with them blocked, and nothing is gated behind it. Your browser can block or delete cookies for this domain; Google publishes a browser add-on that switches Google Analytics off everywhere at tools.google.com/dlpage/gaoptout; and browsers that block third-party or cross-site tracking by default already restrict how long ours survives.

We are a United States company writing to United States law, and these cookies are set without asking you first. If you are reading from the EU or the UK, where an analytics cookie needs your consent before it is set rather than after, tell us and we will delete what we hold for you; the address is in the privacy notice.

If that ever changes

The categories a cookie can fall into, so that you can see where the ones above sit and what would have to happen before we added another:

  • Essential: required for the site to function or to stay secure. No consent required.
  • Analytics: to understand how the site is used. That is the Google Analytics pair described above, and they are the only non-essential cookies this site sets.
  • Functional: to remember a preference you set. Consent required. This site sets no such cookie: the one preference you can set here, the theme, is kept in your browser's own storage, is never sent to us, and is cleared by clearing site data.
  • Advertising: to target or measure advertising. We set none, and adding one would mean a consent banner and a rewrite of this page, not a quiet edit.

Managing cookies

Every browser lets you see, block and delete cookies, and blocking them on this site will not stop you reading it. Blocking the anti-spam challenge may stop the inquiry form from submitting; if that happens, email us directly instead.

We honor Global Privacy Control. Since we do not sell or share personal data for advertising, there is nothing for it to switch off, but we respect it regardless.

Contact

Questions about this policy: info@computingamerica.com.