Skip to content

Cookie Notice

Last Updated: August 23, 2026

This Cookie Notice explains how Arizona Talks Foundation ("we," "our," or "us") uses cookies and similar tracking technologies on our website at arizonatalks.org (the "Service").

1. What Are Cookies?

Cookies are small text files that are placed on your device (computer, tablet, or mobile phone) when you visit a website. Cookies allow websites to recognize your device and store information about your preferences or past actions.

2. How We Use Cookies

We use cookies and similar technologies for the following purposes:

  • Essential Cookies: Required for the Service to function properly
  • Functionality Cookies: Remember your preferences and settings
  • Analytics Cookies: Help us understand how visitors interact with our Service
  • Security Cookies: Protect against fraud and ensure security

3. Types of Cookies We Use

3.1 Essential Cookies

These cookies are necessary for the Service to function and cannot be disabled. They include:

  • Session Cookies: Maintain your session while using the Service (e.g., authentication, form submissions)
  • Security Cookies: Used for spam prevention and security
  • CSRF Protection: Protect against cross-site request forgery attacks

3.2 Functionality Cookies

These cookies remember your preferences and enhance your experience:

  • Cookie Consent: Remembers your cookie preferences (stored in localStorage)
  • User Preferences: Stores settings and customization choices

3.3 Analytics

We use three analytics tools. Analytics are on by default — see Section 5.1 for what that means and how to turn them off. If your browser sends a Do Not Track signal, none of them start.

Our own tracker. First-party and self-hosted, running on Cloudflare. It records the pages you view, the full page address including any query parameters, the page you came from, and campaign parameters (UTM tags). If analytics are allowed, it stores a random identifier in your browser's localStorage so your visits can be connected over time. If that identifier is unavailable, the server derives a temporary one from your IP address and browser type using a salt we rotate daily, which cannot be linked across days.

It sets one cookie. If you arrive from a personalized link in one of our emails, we store a cookie named at_attr on your device for 90 days. It records which link brought you here, first and most recent, so we can tell which email or campaign worked. It contains no name or email address. It is cleared if you select "Reject All."

Rybbit. Analytics software we run on our own server, reached through our own domain. It sets no cookies. It records page addresses and titles, query parameters, the page you came from, campaign parameters, session information, your browser and its version, operating system, device type, screen size, and approximate location (country, region, and city) derived from your IP address. Your IP address itself is not stored.

PostHog. A third-party product-analytics service. It stores an anonymous identifier in cookies and in localStorage. It records pageviews, masked session replays, and goals you complete. A session replay is a video-like recording of your visit showing scrolling, mouse movement, and clicks; all text and anything you type is hidden in your browser before the recording is sent. When you donate, join, renew, or register for an event, our servers also send PostHog the amount, the membership plan or event involved, and whether payment succeeded. See PostHog's privacy policy.

All three run on infrastructure operated by other companies — Cloudflare for our own tracker and for reaching Rybbit, and Rybbit's own hosting provider. Those providers process the requests on our behalf.

3.4 Connecting Analytics to Your Contact Record

If you complete something that identifies you — a newsletter signup, an event registration, a donation, or a membership purchase — we connect that website activity to your contact record, so we can understand what leads people to get involved.

This includes pages you viewed before we knew who you were. When the connection is made, activity already recorded in that browser is linked to your contact record. From then on, activity in that browser is connected to you as it happens.

The connection is per browser, not per person. Activity in another browser, on another computer, or in a private window is not connected until you identify yourself there too.

All three tools do this. In each of them we store an internal contact number, never your name or email address. That number identifies you in our contact database, so staff with access to that database can see which pages a named person viewed. We use a number so that a copy of the activity data on its own is not a list of names — not because the two are held apart.

Simply clicking a link in one of our emails records which link you clicked, but does not by itself identify you.

We do not use any of this to set what we charge you, to target advertising, or to estimate what you might give. We do not sell it or share it for advertising.

What we delete, and what we do not. If you ask us to delete your data, we remove your contact record, the connection between your browser and you, your profile on our analytics server, and the individual pageviews recorded on browsers only you used. On a browser you share with someone else who also has a record with us, we remove the events attributed to you and keep theirs. Aggregate daily counts, which cannot be traced to a person, remain.

4. Third-Party Cookies

Some third-party services we use may set their own cookies:

4.1 Service Providers

Cloudflare: Our hosting and security provider sets cookies for load balancing, performance optimization, security and DDoS protection, and performance monitoring. See Cloudflare's Cookie Policy.

Stripe: Our payment processor sets cookies for payment processing and fraud prevention. See Stripe's Cookie Policy.

4.2 Third-Party Services

YouTube: We embed YouTube videos on our Service. YouTube sets cookies when you interact with embedded videos (if you consent to marketing cookies). See Google's Cookie Policy.

5. Managing Cookies

5.1 Cookie Consent

Analytics are on by default. On your first visit the analytics tools described in Section 3.3 start running immediately, and the cookie banner appears asking what you want. Until you answer, we treat that as permission to continue. We do not wait for you to select "Accept All."

  • Accept All: analytics keep running.
  • Reject All: our own tracker and PostHog stop collecting, the identifiers in your browser are deleted, and the at_attr cookie is cleared. Rybbit stops on your next page load. Anything recorded before you chose stays in our systems unless you ask us to delete it.

If your browser sends a Do Not Track signal, none of it starts in the first place. That is the only control here that takes effect before anything is collected.

Your choice is stored in your browser's localStorage and remembered for future visits.

5.2 Browser Settings

You can control cookies through your browser settings. Most browsers allow you to view and delete cookies, block cookies from specific websites, block all cookies, or receive notifications when cookies are set. However, blocking cookies may affect the functionality of our Service.

5.3 Changing Your Consent

Select Cookie preferences in the footer of any page to reopen the banner and change your answer.

Choosing "Reject All" stops all three tools. We delete the identifiers stored in your browser, ask our server to clear the at_attr cookie, stop PostHog including any session recording in progress, and then reload the page — a reload is the only way to be certain nothing already running keeps collecting. Anything recorded before you chose stays in our systems unless you ask us to delete it.

Changing your choice stops future collection. It does not delete what we already hold. To have that deleted, contact us — see Section 9.

6. Cookie Duration and Data Retention

Cookies may be either "session" cookies, which expire when you close your browser, or "persistent" cookies, which remain for a set period.

  • at_attr (our own tracker): 90 days from your most recent click on a personalized link.
  • PostHog's identifier: set and managed by PostHog under their policy.
  • Your cookie choice and our tracker's visitor identifier are stored in localStorage until you clear them.

How long we keep the activity itself:

  • Our own tracker: individual pageview records are deleted after 90 days. Daily aggregate counts, which cannot be traced to an individual, are kept indefinitely.
  • The link between a browser and a contact record: kept for as long as the contact record exists, unless you ask us to delete it.
  • Rybbit: raw event records are configured to expire after 14 months, and bot-traffic records after 3 months. Session replay is switched off for this website, so no replays are recorded by Rybbit.
  • PostHog: retained according to PostHog's configuration for our account, under their policy.

7. Do Not Track Signals

Some browsers can send a "Do Not Track" (DNT) signal. There is no uniform standard for responding to it, but we do respond: if your browser sends the signal, none of the analytics tools in Section 3.3 start, and no connection is made between your activity and your contact record.

8. Updates to This Cookie Notice

We may update this Cookie Notice from time to time to reflect changes in our practices or for legal, operational, or regulatory reasons. We will notify you of material changes by posting the updated notice on this page with a revised "Last Updated" date.

9. Your Rights

Depending on your location, you may have certain rights regarding cookies under applicable privacy laws (e.g., GDPR, CPRA/CCPA):

  • Right to know what cookies are being used
  • Right to consent or withdraw consent to non-essential cookies
  • Right to access information about cookies used
  • Right to delete cookies from your device

For more information about your privacy rights, see our Privacy Policy.

10. Contact Us

If you have questions about our use of cookies, please contact us: