Policy · Effective October 19, 2026
Privacy
The site has no accounts. It measures traffic with Google Analytics, described below. Personal data reaches us in two ways, by email and through the question form, and this page says what we do with each. It also lists every outside service a page on this site makes your browser contact, and what the site stores in the browser itself.
What the site itself collects
The site has no user accounts, no comment system, no newsletter and no advertising script on the date above. It measures how many people read which pages, using Google Analytics, described in its own section below. Reading a page sends nothing you type to us. The pages have three things to type into: the question form, which sends us what you write only when you press its button and is described in its own section below; the weather check described below; and the calculators, which run in your browser and send nothing to us.
What we receive when you email us
The one way personal data reaches us is email to research@beestsprayfoam.com. When you write, we receive your email address, your name and anything else in your signature, the subject and body of the message, and any attachments or links you include. The prefilled "write to the research desk" link on product pages adds the product name and page URL to the subject so we can find the record you mean; it adds nothing about you.
We use that correspondence to read the document you sent against the record, to reply to you, and to keep the record of what was submitted and what changed, because each correction is dated and the message is the evidence behind the date. We do not add senders to any mailing list, we do not sell or share the correspondence, and we do not publish your email address, your name or your contact details. What can be published from a submission is the document itself, its title, date and revision, and short quotations from it, as the submissions page describes; a public link to a file on your own site is what we prefer to cite.
Correspondence is kept for as long as the record it supports exists, so that a dated correction can be traced to the document that caused it. The schedule is this: correspondence that led to a published correction or a document on file is kept for as long as that record is published and for two years after it is withdrawn; correspondence that led to no record is deleted twelve months after the last message in the thread; and the sender’s name, address and any personal details are deleted on request at any time unless a published correction depends on them, in which case the record keeps the document and drops the person. To ask what we hold about you, to have it corrected, or to have it deleted where no published correction depends on it, write to the same address with "Privacy request" in the subject line.
Email to that address is received through Hostinger, the mailbox provider for the domain, which processes the message in order to deliver and store it under its own privacy policy.
What we receive through the question form
The question pages and the comparisons carry a form headed "Ask the research desk". When you press its button we receive what you typed into it: the question, the product or project if you named one, and a reply address if you gave one, together with the address of the page you sent it from and whether that page was the English or the Spanish edition. Your IP address, your location and anything about your browser are not put in the message, and the form itself sets no cookie. To slow automated sending, the site counts attempts from each network for one minute under a one-way code made from the address, so that more than five a minute are refused; the address itself is not stored.
The form sends the question as an email from the desk’s own mailbox to the desk’s own address, through the Hostinger Mail API, so it arrives in the same Hostinger mailbox as any other email to us; nothing is stored on the website itself. We use a question to decide whether the records can answer it. A question we answer becomes a question page, written in our own words, with a note giving the date it was asked; the page never carries your name or your address. A reply address is used only to reply to you, is never published, and is never added to a list.
A question is correspondence and is kept on the schedule above: it is deleted twelve months after the last message in its thread, unless it became a question page, in which case the question text is kept for as long as the page is published. The reply address is deleted with the question, and on request at any time. To ask what we hold or to have it deleted, write to research@beestsprayfoam.com with "Privacy request" in the subject line, giving the page and the date you sent it.
Outside services your browser contacts
Pages on this site are built as plain files, but some of them make your browser request things from other companies. These are the ones we know of on the date above. Each request goes from your browser straight to that service and is governed by that service's privacy policy; none of it passes through us and we receive none of it.
- Video thumbnails and videos. Product pages that carry a maker's video show a preview image loaded from YouTube's image servers (i.ytimg.com) as soon as that part of the page comes into view, which tells Google that a browser at your IP address loaded that page. Nothing plays until you press the play button; when you do, the page loads the video from youtube-nocookie.com, YouTube's privacy-enhanced embed. "Privacy-enhanced" means YouTube says it does not store viewing history on that domain before you play; it does not mean no data reaches Google. Google's privacy policy applies to both requests.
- Product photos. Some product images are loaded from Amazon's image servers (m.media-amazon.com), so opening those pages sends a request to Amazon for the picture. Amazon's privacy notice applies to that request.
- The weather check. The spray-today weather check has a text box. Type a ZIP code and it goes to Zippopotam.us, which returns a place name and coordinates. Type a place name instead and it goes to the Open-Meteo geocoding service, which returns coordinates the same way. The coordinates then go to Open-Meteo to fetch the temperature and humidity forecast. If you press the button that uses your device location, your browser asks your permission first, and the coordinates it returns go to Open-Meteo in the same way. Nothing is sent until you act, and we keep none of it.
- The spam check on the question form. The form is protected by Cloudflare Turnstile. Its script loads from challenges.cloudflare.com only when you start using the form, not when a page opens. It then runs a check in your browser and sends Cloudflare signals about the browser and the request, so that it can tell a person from an automated script. We receive only its verdict on that one check. Cloudflare's Turnstile privacy addendum applies to it.
- Email address protection. Where an email address is printed on a page, the host may rewrite it in the served page and add a small script from Cloudflare that restores it for readers, so that address-harvesting bots do not get it. That script comes from Cloudflare and is covered by the host's policy below.
The remaining calculators on this site work entirely in your browser and contact no outside service.
What the site stores in your browser
When you follow a glossary link from a page, the site writes the page you came from (its address and title, and the time) into your browser's session storage, so that the glossary can show you a way back to that exact page. That value never leaves your browser, is not sent to us or to anyone else, and your browser discards it when the tab is closed. We set no cookies of our own. The only cookies on this site are the ones the Google Analytics tag sets, described below.
What Google Analytics measures
Every page on this site loads Google Analytics 4, property G-811TXHYCJQ. The tag runs in your browser and reports to Google the address you opened, the address that sent you here, your browser and device type, an approximate location worked out from your IP address, and the interactions the tag counts as events. Google processes that data and we read the reports. We use it for one thing: to see which pages get read and which do not.
The tag stores identifiers in your browser, cookies named _ga and _ga_ followed by the property code, so that a second visit counts as the same browser rather than a new person. These are the only cookies on the site. You can stop them: block cookies for this site, use a content blocker, or install Google's own opt-out add-on. Nothing here stops working if you do; the calculators, the glossary and every page read the same way.
We upload nothing to that property ourselves, and we do not join it to your email, to a document you send us, or to anything you type into a calculator. Google's own handling is described in how Google uses information from sites that use its services, and how long the event data is kept is a setting on the property rather than something the page controls. If this property is ever connected to advertising or to another Google product, this page says so before it happens.
For an Adsterra-tagged visit, a short-lived record in this tab's session storage keeps validated numeric campaign, placement and creative IDs and controlled campaign labels. It expires after 30 minutes of inactivity. We attach those fields to product-view and outbound-link events to compare advertising sources. This record contains no advertising click ID, cost, calculator answers or contact information. A product-view event requires at least half of a product card to be visible for one second; opening a page is not itself a product view. These custom events stop when your browser exposes Do Not Track or Global Privacy Control; the base Google tag has its own controls described above.
What the host collects
The site is served by Cloudflare Pages. Like any web host, Cloudflare processes the request data a browser sends, such as an IP address, a user agent and the page requested, and keeps it in its logs for as long as its own policy says; its handling of that is governed by Cloudflare's privacy policy rather than by us. We have not enabled Cloudflare's analytics on this site, and we do not build reader profiles from anything the platform makes available.
Outbound links
When you follow a link to Amazon, Walmart, a brand store or any other site, that site's privacy policy applies. Links to Amazon product pages carry our Amazon Associates tracking ID, which tells Amazon that the visit came from this site so a qualifying purchase can be credited to it; Amazon's cookie and privacy practices then apply to that visit. We do not receive your name, your address or anything else that identifies you; Amazon's reports to an Associate list the products bought and how many, not who bought them. Walmart, brand-store and document links carry no identifier of ours. The ownership page says what the fee is and what it cannot change.
Children
The site is not directed at children, and we do not knowingly keep correspondence from anyone under 13. If you believe a child has written to us, write to the same address and we will delete it.
Changes
The effective date at the top of the page is the record. When a new outside service, script or storage use is added to the site, this page is updated before it goes live.