PolkTX
POLK COUNTY, TEXAS
NOT THE POLK COUNTY GOVERNMENT · LOOKING FOR THE COUNTY? POLKTX.GOV

What we collect

Short version: Google Analytics and Cloudflare Web Analytics tell us how many people read PolkTX and roughly where from; the Meta Pixel tells Facebook which pages were visited (and when someone signs up from our ad page) so we can measure and target PolkTX's own Facebook ads; our own counters tell local businesses how their listings did. We do not sell data and we run no ad networks on the site.

Google Analytics

PolkTX uses Google Analytics 4, a service from Google LLC, to measure readership: how many people visit, which pages they read, what kind of device they use, roughly what area they are in (city or region level, worked out by Google from the connection — never a precise location), and whether they arrived from a search, Facebook, or a link we posted.

Google Analytics sets first-party cookies (named _ga and _ga_…) so a returning reader is counted once rather than every time. We use the numbers in aggregate — for example, "4,200 people read PolkTX last month, most of them in Polk County" — to run the site and to show local businesses what advertising here reaches. We have not turned on Google's advertising features, so this data is not used to show you ads.

To stop it: Google's opt-out browser add-on, a content blocker, or your browser's cookie settings all work, and PolkTX works exactly the same without it. Google's handling is described in its privacy policy and in how Google uses information from sites that use its services.

Meta Pixel

PolkTX uses the Meta Pixel, a tool from Meta Platforms, Inc. (Facebook and Instagram). When you open a page, it tells Meta that the page was viewed. We use it for two events only: a page view, and a sign-up when someone joins the newsletter from our ad page (/join/), so we can tell whether PolkTX's own Facebook ads bring in readers. Your email address is never sent to Meta. Meta may connect that visit to a Facebook or Instagram account you are logged into. That lets PolkTX measure its own Facebook ads and show them to people who have already read the site. PolkTX sees only totals in Meta's tools, never who you are.

Meta's cookie is named _fbp. To stop it: use your Facebook ad settings to turn off ads based on activity from other sites, use a content blocker, or block cookies in your browser. PolkTX works exactly the same without it. Meta's privacy policy applies.

Cloudflare Web Analytics

PolkTX is served through Cloudflare, Inc., which also provides Cloudflare Web Analytics: visit and page-view counts by country, with no cookies and no cross-site tracking. Cloudflare's privacy policy applies.

Our own counters

Alongside those, PolkTX keeps simple counters of its own, because they keep working when an ad blocker stops the services above. They look like this:

p:2026-10:burn-ban:view                   412
n:2026-10:casa-della-tire:call             18
a:2026-10:sponsor--events:view            960
s:2026-10:fb-lne                          133

A page, a business or an ad placement, a month, a kind of action, and a number. The last line counts readers who arrived on a link PolkTX itself posted — we add a short tag like ?s=fb-lne to our own links and remove it from the address bar as the page opens. These counters store no cookie, no identifier, no IP address and nothing about you; one person opening a page four times counts four. Businesses with a paid listing or placement receive their own counts monthly.

What we do not do

No advertising networks run on PolkTX pages, and nobody else's ads follow you from here. The only retargeting is PolkTX's own Facebook ads, described above. We do not sell, rent or trade information about readers to anybody. Advertisers receive totals — never anything about an individual reader.

When you write to us

Forms on this site send what you typed to PolkTX by email. We use it to answer you and to check the record you are telling us about. We do not sell it, we do not add you to a mailing list, and we never publish an email address or phone number given on a form.

Messages sent from a business page go to that business, with your email as the reply address so they can answer you directly. PolkTX is copied on those messages — not to read your business, but so a message that bounces is not silently lost, and so that if one of our forms is ever used to send a local business abuse, we can see it and stop it.

The newsletter list is kept at Resend and used for the newsletter. Every issue has a one-click unsubscribe, and leaving removes you from the count.

Right after you subscribe we ask a few optional questions (your area, whether you own or rent, any plans to move, and what you want more of); we use the answers to choose what goes in the update and which sponsors fit it, and we never sell or share anyone's individual answers.

Text alerts

If you sign up for PolkTX text alerts, we store your mobile number, the topics you picked, and a record of your consent (the date, time and exact wording you agreed to). We use the number only to send the alerts you asked for. Texts are delivered through Twilio, which handles the number only to deliver the messages.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent will not be shared with any third parties.

Reply STOP to any text to opt out. Your number is then marked as stopped and receives nothing further. To have it deleted entirely, email info@polktx.com.

When you pay for a placement

Payments for listings, sponsorships and promotions are processed by Stripe. Stripe collects your card details and we never see or store your full card number. We receive your name, email, phone, billing details and the answers you give at checkout, and use them to set up the placement, send receipts and keep the records the law requires. Stripe's privacy policy applies to what it handles.

Check it yourself

  • src/layouts/Base.astro — everything every page loads, including Google Analytics
  • scripts/stamp-meta-pixel.mjs — adds the Meta Pixel to every page at build time
  • functions/api/tap.js — our counters, and the list of what they accept
  • functions/api/forms.js — where a form submission goes

Something here wrong, or something you would rather we did not do? Tell us.