Privacy notice

This notice explains what this website collects about you, why, who can see it, how long it is kept, and what you can do about it. It covers the public pages of this site and the committee portal at /portal, where committee members sign in. It does not cover other websites, including the four fire districts’ own sites.

Who runs this site

This site is published by the Enfield Fire Districts Consolidation Committee. The committee was formed by the Hazardville Fire District No. 13, the North Thompsonville Fire District #10, the Shaker Pines Fire District and the Thompsonville Fire District #2. A web company builds and runs the site for the committee under a written agreement. It may use what the site collects only to run the site, and it does not sell it or use it for anything else.

The short version

You can read every page without giving us anything about yourself. We use no advertising, no social media plug-ins and no outside tracking companies. We count visits ourselves, and we do not count yours at all if your browser sends Do Not Track or Global Privacy Control. We never sell what you give us. What you send to the committee may be a public record under Connecticut law.

When you read pages

Like every website, this one cannot send you a page without your device’s network address (IP address). Cloudflare, the company that hosts the site, handles every request and sees that address and the type of browser you use, as any host does. Reading pages does not put your name, email or network address into the site’s records.

How visits are counted

The site counts visits itself, with no cookies. For each page you open, it records the page’s address (without anything after a question mark), the name of the website that sent you there if any, a campaign tag if the link had one, and whether you seem to be on a phone or a computer, judged by the width of your screen. It also records where on a page clicks land, as positions on the page, to show which parts of a page people use. To count how many different people visited in a day, it makes a scrambled code from your network address and browser type. The key for that code changes every day and is then deleted, so the codes cannot be linked from one day to the next or traced back to you once the day is over. If your browser sends Do Not Track or Global Privacy Control, none of this happens: your visit and your clicks are not counted at all.

Cookies and browser storage

The public pages set no cookies. They read one display setting from your browser’s storage, if one is there, to choose how the page looks; they do not save anything there themselves. The committee portal uses cookies only to keep a member signed in and to recognize a browser that has signed in before. Pages with a form also load a check from Cloudflare, described below, which follows Cloudflare’s own privacy terms.

Your fire tax

When you type an address into Your fire tax, it is used once, for that lookup, and is never stored or logged by this site. Suggestions appear as you type: what you have typed so far is sent to the site and matched against a copy of the Town of Enfield’s and the State of Connecticut’s public property records. That copy holds each property’s address, parcel number, fire district and assessed value. It holds no owners’ names. If your address is not in that copy, the site sends the address you typed to the US Census Bureau’s address service to find where it is on a map. It then checks that point against the Town of Enfield’s public map of the fire districts, which is hosted by the map company Esri. Esri receives only the map point, not the address. Both requests come from the site’s server, so the Census Bureau and Esri see the site, not your device. You can also skip the address and choose a district and type an assessed value by hand. That value is used for the calculation and is not stored. To stop misuse, the site counts how many lookups come from each network address, and uses that count only to limit tries within an hour.

Questions you send the committee

The question form asks for a topic and your question. Your name, your email address and your fire district are optional. The site also notes which page the form was on, and a campaign tag if the link you followed had one. It does not store your network address with your question. Your question is saved in the committee’s records and emailed to the committee’s inbox. If you gave an email address, the committee’s email shows it, so a member can reply to you, and the site sends you an automatic reply with answers that may help. Committee members who answer questions read them in the portal and may answer you by email. The committee may also post a question it gets often, with its answer, on the questions and answers page. It writes the question in its own words and does not post your name or email address. Please do not put private information in a question that you would not want shared.

Email updates

If you sign up for email updates, the site keeps your email address, the list or lists you chose, the page you signed up on, and when you signed up, confirmed or left. Ticking the box for members and firefighters adds you to that list too, and the site keeps that choice. Until you confirm, the site sends you only the email with the link to confirm, and at most three of those in a day. If you do not confirm within 7 days, the link stops working, and an address that is never confirmed is deleted after 30 days. Every update has an unsubscribe link that works with one click. When you unsubscribe, your address is marked so that it is never emailed again. If you would like it removed altogether, ask us as described below.

Committee members who sign in

For each person with a portal account, the portal keeps their name, email address, role and display choices. A member may sign in with a code sent by email or with a password. A password is never stored, only a scrambled form of it made with a slow, salted method that cannot be turned back into the password. Sign-in codes are stored the same way and work once, for 5 minutes. The portal keeps a list of signed-in browsers, with the browser’s description of itself, so a member can sign out of other devices. A sign-in ends after 14 days without use. The portal also keeps an activity log of what each member does in it: who, what, when, what was changed from what to what, and the network address it came from. That log is part of the committee’s records. To stop guessing, the portal counts failed sign-ins and code requests by the email address typed and by network address, and clears those counts after a day.

How email is sent

The site’s email, including confirmations, automatic replies, answers and updates, is sent through Cloudflare’s email service. The site keeps a record of each email it sends for 30 days, so a failed one can be sent again. The text of a sign-in code is never kept. Cloudflare also keeps its own short-term records of the email it sends.

The security check on forms

The question form and the email sign-up use Cloudflare Turnstile to tell people from automated programs. Turnstile runs in your browser and looks at signals from your browser and device. When you send a form, the site asks Cloudflare whether the check passed and includes your network address in that request. Cloudflare’s privacy terms for Turnstile are on Cloudflare’s website.

Who we share information with

We share what the site collects only with the services needed to run it: Cloudflare, which hosts the site, its database, its files and backups, and sends its email; the US Census Bureau and Esri, only as described under Your fire tax; and the company that runs the site for the committee. Questions also reach the committee’s email inbox. We do not sell, rent or trade any information, and we do not use it for advertising. We may also share information when the law requires it, for example in answer to a public records request or a court order.

Public records

The committee is made up of public bodies in Connecticut. Under the Connecticut Freedom of Information Act, records a public body keeps, including messages sent to it and lists of email addresses, may be public records. If someone asks for them, they may have to be released, unless a law allows them to be withheld. Connecticut’s Freedom of Information Commission has ordered a town to release its list of people signed up for its emails. So although we do not share your email address ourselves, we may be required to release it. Please keep this in mind when you write to us.

How long information is kept

Typed tax addresses are not kept. Visit counts are trimmed by the site automatically and never hold your name, email or network address. Unconfirmed email sign-ups are deleted after 30 days. Copies of sent email are kept 30 days. Questions, the email list, the portal’s activity log and the committee’s other records are kept as Connecticut’s rules for public records require. The committee has not yet set a shorter period for any of them. When the committee removes a question from its list, the portal keeps a copy with its records. The site’s database is backed up every night, and the 14 most recent backups are kept. The database also keeps its own history of changes for 30 days. So something deleted from the site is gone from the site’s copies within about 30 days. Copies of questions in the committee’s email inbox are kept there separately.

How it is protected

The site is sent over an encrypted connection. Only committee members with a portal account can see questions and the email list, and each member sees only what their role needs. The company that runs the site can see the records because it keeps the site working. Passwords and sign-in codes are stored only in scrambled form. Repeated failed sign-ins are blocked, forms are limited and checked for automated programs, and every action in the portal is logged. No system is perfectly secure. If we learn that someone got into personal information held by the site, we will tell the people affected as the law requires.

Children

This site is not directed to children under 13, and we do not knowingly collect information from them. If you believe a child has sent us their information, tell us and we will remove it, as far as the public records rules allow.

Your choices

You do not have to give your name or email to ask a question, and you can use Your fire tax without an address. You can turn on Global Privacy Control or Do Not Track in your browser to stop your visits being counted. You can unsubscribe from email updates at any time. You can ask to see what the site holds about you, to correct it, or to remove it. We will do so unless Connecticut’s public records rules require us to keep it, and if we cannot, we will tell you why.

How to ask

Send your request through the question form and choose “Something else” as the topic. Say what you would like and include the email address you used, so we can find your records. We may need to confirm the address is yours before we change or remove anything.

Links to other websites

This site links to other websites, such as the Town of Enfield and the fire districts. Their privacy practices are their own.

Changes to this notice

If what the site collects changes, we will update this notice and the date below.

Last updated November 14, 2026.