Legal

Privacy Policy

Last updated November 22, 2026

This policy explains what information Council Fire collects through councilfire.org, why we collect it, who helps us handle it, how long we keep it and the choices you have. We wrote it to describe what the site actually does. If anything here is unclear, email us at info@councilfire.org.

Who we are

Council Fire is a sustainability strategy consultancy based in Annapolis, Maryland. Our legal name is Council Fire, Benefit LLC. CF Labs is Council Fire's software studio. In this policy, "Council Fire," "we," "us" and "our" mean Council Fire. Our mailing address is 125 Chester Ave, Annapolis, MD 21403.

What this policy covers

This policy covers councilfire.org, including the CF Labs pages, our free tools and calculators, the Trovance AI visibility check and the Aptation tour. It does not cover:

  • the Aptation and Trovance applications themselves, including text messages you send to Trovance, which have their own terms and privacy policies;
  • information we handle for clients under a contract, which that contract governs;
  • other websites we link to, which have their own policies.

Information you give us

We collect what you choose to send us:

  • Contact and inquiry forms: your name, email address, organization, role, type of organization, state, your message, how you found us if you choose to say and, on CF Labs forms, the starting point you're interested in and your timing.
  • Newsletter: your email address and, where a form asks, your first name. Every form on the site that asks for your email address also adds it to our newsletter, and says so beside the email field.
  • Tools that email you a result: your email address plus what the tool needs to produce the result, such as the county for a climate risk brief, the jurisdiction for a hazard mitigation plan timeline, the program for funding deadlines, the spending and measures for an ESG savings estimate, your answers to a scorecard or checker, your answers to the CF Labs project estimator, or the website address you enter in the AI visibility check.
  • Follow-up notes: if you tick the box for them on one of our tools (a CF Labs estimate, an AI visibility check, the Aptation tour, a plan timeline or the funding deadlines), three short emails over the next two weeks, scheduled when you submit. Each has a link to stop the rest, and writing to us through the site cancels any still waiting.
  • Downloads: your email address when you request a white paper or template.
  • Scheduling: if you book a call, the booking service collects your name, email address and any notes you add, and tells us about the booking (see Cal.com below).
  • Email: anything you write to us directly.

When you run the AI visibility check, our server visits the public website you enter, reads its public pages and files (such as robots.txt and its sitemap), and shows you the result. If you ask us to email the report, we keep the website address and the score with your request.

Information collected automatically

When you browse councilfire.org, a first-party cookie named cf_j records the first page you landed on, the site that sent you (the referrer), any campaign tags in the link (UTM parameters), the last twelve pages you viewed on our site, how many visits you've made and the date of your first visit. If you come back later through another site or a campaign link, it also records that most recent arrival: its date, the page you landed on, the referring site and the campaign tags. It also keeps the site's guess at what you're interested in and where the site used it (see How the site tailors itself). It records pages on our site only, not your name or anything you type. It stays in your browser for 90 days. Your browser sends it to our site with each request, but we only use it when you send us a form, so we can see which pages led to your message and route it to the right person. If you book a call, a short version of the same record (nothing you typed) is passed to our scheduling service with the booking, for the same reason.

If you ask for follow-up notes, a second first-party cookie, cf_n, holds your email address and references to the notes scheduled for you, signed so it can't be altered. It lasts 30 days and lets us cancel the notes still waiting if you write to us.

Other browser storage

The site stores a few small items in your browser:

  • when it last showed you an offer or a pop-up and whether you closed it, so it doesn't show you the same one too often;
  • for 30 minutes after you click one of our offers, which offer it was, so we can count whether an offer led to an inquiry;
  • for the length of your visit, the approximate location described below, so the site doesn't look it up on every page;
  • whether your browser is in the group that sees the standard site, and whether you've turned personalization off (see below).

You can clear these at any time through your browser's settings.

Approximate location

Our hosting provider, Vercel, tells our site the country, state and nearest city it estimates from your IP address. We use it to suggest the climate risk brief for your county, for example. We don't store it.

How the site tailors itself

The site adjusts a few things to what you seem to be interested in. The home page may show a short section about our work for your kind of organization, such as local governments or foundations, or for a subject you've been reading about. The end of some guides may suggest a next step that fits the subject. Our case studies page may list the most relevant ones first.

To choose, the site looks at the pages you've read here, the website that sent you (a .gov or .edu address, for example) and any campaign tags in the link you followed, all from the cf_j cookie above. It works this out in your browser. It doesn't use your name, your email address, anything you type or the visitor identification described below.

The cf_j cookie keeps the site's guess and where it was used, so if you send us a form, our record of your inquiry shows how the site was tailored for you. One browser in ten sees the standard site instead, so we can tell whether tailoring helps, and your browser remembers which group it's in.

Analytics

  • Google Analytics: we use Google Analytics 4 to understand how people use the site, such as which pages are visited, which of our offers are shown and clicked, which buttons are clicked and which forms are submitted. It uses cookies (such as _ga). We don't send it your name, email address or what you type into our forms. You can opt out with Google's browser add-on.
  • Fathom Analytics: Fathom counts visits without cookies and reports them to us in aggregate.
  • Trovance Pixel: Trovance, a CF Labs product, measures visits to our site, including visits referred by AI assistants. It doesn't use cookies. It records the page, the referring site and any campaign tags in the link. To count visits, Trovance's server turns your IP address and browser type into a code that changes every day. It doesn't store your IP address or browser type, and the code can't connect your visits on different days.

Visitor identification

We use RB2B, a service that may identify some visitors in the United States, and the companies they work for, by matching information about the visit with information RB2B holds. RB2B may then tell us the visitor's name, job title, company and professional profile, which we may use to follow up with people who show an interest in our work.

When you visit or log in to our website, cookies and similar technologies may be used by our online data partners or vendors to associate these activities with other personal information they or others have about you, including by association with your email. We (or service providers on our behalf) may then send communications and marketing to these email addresses. You may opt out of receiving this advertising by visiting https://app.retention.com/optout.

Some pages include videos from YouTube. A video doesn't load from YouTube until you press play; once it does, YouTube may set cookies under Google's privacy policy. Booking a call opens Cal.com, and downloading our white paper opens Google Drive. Each of those services handles your information under its own policy.

Server logs

Like most websites, our hosting provider records technical information about each request, such as IP address, browser type, the page requested and the time. These logs are used to run and secure the site. To stop automated abuse of our forms, we also keep the IP address and email address of recent submissions in memory for up to an hour. If our forms receive an unusually large number of submissions in a short time, we may keep a submission in these logs instead of emailing it, so we can follow up by hand.

How we use information

We use the information described above to:

  • answer your inquiry, arrange a call and send what you asked for (a report, estimate, brief, download or newsletter);
  • route your inquiry to the right person and decide how quickly to follow up, based on what you tell us and the pages you read before you wrote. This is our own prioritization, and no decision with legal or similar effects is made about you automatically;
  • keep a record of inquiries, requests and bookings, alert our team to new ones and, once a member of our team approves it, add the person and organization to our customer relationship system;
  • tailor what the site shows you, as described in How the site tailors itself;
  • send our newsletter to the email addresses given to us through the site, and the follow-up notes you ask for. Every email includes a way to unsubscribe;
  • follow up with organizations that show an interest in our work, including those identified by RB2B;
  • understand how the site is used and improve it;
  • keep the site and our forms secure, and prevent spam and abuse;
  • meet our legal obligations.

How we share information

We don't sell your personal information for money. We share it with the service providers that help us run the site and respond to you, only as needed for those purposes:

Provider What it does for us
Vercel Hosts the website, records server logs and estimates approximate location from IP addresses
Resend Delivers the emails our forms send, both to you and to our team
Beehiiv Runs our newsletter and keeps our subscriber list, with any details you give at sign-up (such as first name, scorecard results and which page you signed up on)
Google Google Analytics; YouTube, when you play a video; Google Drive, for downloads
Fathom Analytics Cookieless visit counts
RB2B Visitor identification, as described above
Cal.com Scheduling, when you book a call, with the record of which pages and campaign led to the booking
Supabase Stores a copy of each inquiry, request and booking sent through the site, for our team to review
Slack Internal notices of new inquiries and bookings, and a weekday summary of other requests
Attio Our customer relationship system, where our team keeps the people and organizations we're working with
Trovance (CF Labs) Our own visit measurement, as described above

We may also disclose information if the law requires it, to protect the rights, safety or property of Council Fire or others, or as part of a merger, acquisition or sale of all or part of our business.

Some state privacy laws define "selling" or "sharing" personal information broadly enough to cover letting analytics or visitor-identification services such as Google Analytics and RB2B collect information through a website. You can opt out of both: RB2B through app.retention.com/optout and Google Analytics through Google's opt-out add-on. You can also email us and we'll help.

Your choices

  • Email: unsubscribe through the link at the bottom of any newsletter, or email us.
  • Cookies and browser storage: you can block or delete cookies and site data in your browser's settings. The site still works without them; we just can't connect your visit to your inquiry.
  • Google Analytics: use Google's opt-out add-on.
  • RB2B: use app.retention.com/optout.
  • Personalization: turn it off for your browser with the switch in How the site tailors itself.
  • Do Not Track and Global Privacy Control: our site doesn't currently respond to Do Not Track or Global Privacy Control signals. The opt-outs above work whatever your browser sends.

How long we keep information

  • Your messages, requests and bookings stay in our email, our customer database, Slack and Attio for as long as we need them to work with you and to keep business records.
  • Newsletter subscriptions last until you unsubscribe.
  • Follow-up notes go out within two weeks of your request; the cf_n cookie expires after 30 days.
  • The cf_j cookie, with the site's guess at your interests, expires after 90 days. Offer and pop-up settings, your browser's personalization group and the off switch stay in your browser until you clear them; the approximate-location result is cleared when you close the tab.
  • Form-abuse checks (IP and email address) last up to an hour.
  • Google Analytics data tied to cookies or identifiers is kept for 2 months for events and 14 months for user-level data; aggregated reports are kept longer.
  • Other providers keep information according to their own retention policies.

Your rights

Depending on where you live, you may have the right to:

  • know what personal information we hold about you and get a copy;
  • correct it;
  • delete it;
  • opt out of the "sale" or "sharing" of your personal information, of targeted advertising and of profiling;
  • not be treated differently for using these rights.

To make a request, email info@councilfire.org with "Privacy request" in the subject line. We may need to confirm your identity before we act on it. You can use an authorized agent; we may ask for proof that they act for you.

We'll respond within the time the law that applies to you allows. If we decline your request, you can appeal by replying to our answer, and we'll review the decision. If you're still not satisfied, you can contact your state's attorney general.

Children

Our site is for professionals and isn't directed to children under 16. We don't knowingly collect personal information from them. If you believe a child has sent us information, email us and we'll delete it.

Security

The site is served over HTTPS, access to the information we hold is limited to the people who need it, and our forms are protected against automated abuse. No method of sending or storing information is completely secure, so we can't guarantee absolute security.

Visitors outside the United States

We're based in the United States, and our service providers process information in the United States and elsewhere. If you visit from another country, your information will be transferred to and processed in the United States, where data protection laws may differ from those where you live.

Changes to this policy

We'll update this policy when our practices change and revise the "last updated" date at the top. For significant changes, we'll also note them on this page.

Contact us

Questions or requests about privacy: info@councilfire.org

Council Fire, 125 Chester Ave, Annapolis, MD 21403