Privacy policy

How we handle your data

What we collect when you visit Texas Police Salaries, what we do with it, and the third-party tools that touch your traffic. Written in plain English — and short on purpose.

01
May 2026
Last updated
02
HTTPS · TX
Encrypted in transit
03
9 sections
~4 minute read
04
No sale
We never sell your data
The short version

Browsing salary data is anonymous. If you fill in a form or use the chatbot, we keep only what's needed to reply or improve answers — and we don't sell any of it.

We do
  • +Use Google Analytics & Microsoft Clarity for anonymous usage stats
  • +Store contact-form replies and chatbot conversations to improve the site
  • +Serve everything over HTTPS, encrypted in transit
  • +Honor access, correction, and deletion requests
We don't
  • Sell or rent your personal information to anyone
  • Require an account to browse salary data
  • Knowingly collect info from anyone under 13
  • Tie chatbot conversations to your name, email, or IP
01

Information we collect

Texas Police Salaries ("we," "our," or "us") is committed to protecting your privacy. We collect only what's needed to run the site and reply to inquiries. Specifically, we may collect:

  • Contact form
    Your name, email, and department affiliation — only when you voluntarily submit a form.
  • Analytics
    Anonymized page views, device type, browser, approximate geographic location, and referring URLs — collected by Google Analytics.
  • Behavioral
    Anonymized session recordings and heatmaps showing clicks, scrolls, and mouse movement — collected by Microsoft Clarity, which masks input fields and sensitive content by default.
  • Salary data
    Public salary information stored in Firebase/Firestore. This is publicly available data and contains no personal user information.
  • Chatbot
    Messages you send to the on-site chatbot and the bot's replies, stored alongside a per-session identifier. We use this to improve answer quality and identify topics that need better coverage. We don't collect your name, email, or IP through the chatbot, and we don't share these conversations with third parties beyond what's described in Section 3 — please avoid entering personal or sensitive information.
  • Account data
    If you sign in with Google, we store your email, display name, and profile photo to identify your account. If you complete your profile, we also store the values you choose: country, state, sworn-officer status, department, years of service, favorited departments, personal notes you write about departments, and your email-alert preferences. Account data is held in Firebase / Firestore and is treated as personal to you — notes you write about a department are visible only to you when signed in. You can review, edit, or permanently delete everything tied to your account at any time from My Profile.
02

How we use it

We use the information we collect for four things:

  • Respond to inquiries — we use contact-form submissions to reply to questions, feedback, and requests for information.
  • Improve the site — analytics data helps us understand how visitors use the site so we can improve content, navigation, and experience.
  • Keep salary data accurate — information submitted through our contact and update forms helps us keep department salary data current.
  • Run your account — your saved favorites, personal notes, and alert preferences let you pick up where you left off and receive only the email alerts you've opted into.
03

Third-party services

SVC—01
Google AnalyticsTraffic analytics
Analyzes website traffic and usage patterns. Uses cookies to collect anonymized data.
Privacy policy
SVC—02
Microsoft ClarityHeatmaps · replay
Collects interaction data (clicks, scroll depth, mouse movement) for heatmaps and session replay. To opt out globally, install a tracker-blocking extension; Microsoft does not provide a per-site opt-out URL.
Privacy policy
SVC—03
Firebase / FirestoreAccounts · data storage
Stores public salary data, chatbot conversation logs, and account data (profile, favorited departments, personal notes, alert preferences). Firebase Authentication handles sign-in via Google. May collect IP addresses and device identifiers for security and performance.
Privacy policy
SVC—04
Anthropic ClaudeChatbot replies
Powers the on-site chatbot. Messages you send are transmitted to Anthropic to generate replies.
Privacy policy
SVC—05
EmailJSForm delivery
Processes contact-form submissions. Your name, email, and message are transmitted through EmailJS to reach our inbox.
Privacy policy
SVC—06
Gmail APIAccount email alerts
Sends the email alerts you've opted into — salary updates, new departments, monthly digest, and department nudges — from our Gmail mailbox to your inbox. We use the Gmail API only to send mail from our own account; your email address appears in the recipient field. Unsubscribe at any time from any alert email or from Alert Settings in your profile.
Privacy policy
04

Cookies

You can control or disable cookies through your browser settings. Disabling them may affect some site functionality.

05

Data security

We take reasonable measures to protect the information we collect from unauthorized access, alteration, disclosure, or destruction. Our site is served over HTTPS to encrypt data in transit.

That said, no method of transmission over the internet or electronic storage is 100% secure, and we cannot guarantee absolute security.

06

Your rights

Access

Request a copy

Ask for a copy of any personal information we hold about you, and we'll put it together.

Correction

Fix what's wrong

Request that we correct anything inaccurate or incomplete in our records about you.

Deletion

Erase it

Request that we delete your personal information from our records, and we will.

To exercise any of these rights, reach out via our Contact page. We'll get back within a few business days.

07

Children's privacy

Our website is not directed at children under the age of 13, and we do not knowingly collect personal information from them. If we become aware that we have inadvertently collected information from a child under 13, we'll delete it as soon as possible.

If you believe a child under 13 has provided us with personal information, please contact us immediately.

08

Changes to this policy

We may update this Privacy Policy from time to time to reflect changes in our practices or for operational, legal, or regulatory reasons. Any changes will be posted on this page with an updated "Last Updated" date.

We encourage you to review this policy periodically to stay informed about how we protect your information.

09

Contact us

If you have any questions or concerns about this Privacy Policy or our data practices, reach out through our Contact page. We read every message.

Questions about your data? Drop us a note and we'll walk through what we have, change, or delete it — whichever you need.
Contact us Terms of service