How we measure the board.

We use first-party, aggregate analytics to understand which directory views and events are useful. We count directory and suggestion-page visits, view changes, event opens, flyer enlargements, registration/announcement/map clicks, filter categories, and active viewing time. Time only accumulates while the page is visible, focused, and recently used.

A random token in session storage groups visits in the same browser tab. We record a coarse device class and referral category. We do not collect names, emails, IP addresses, precise locations, raw search terms, full referrer URLs, keystrokes, screenshots, or session recordings for these analytics. We do not sell analytics or send them to a third-party analytics vendor.

Traffic and technical aggregates are available only to administrators. Records older than 90 days are removed during routine traffic cleanup; cleanup resumes on the next visit if the site has been idle. Manual backups may retain snapshots longer. Technical server response/error counts remain active to operate the site. Admin visits are excluded from visitor analytics. Browser blockers, opting out, and bots can affect counts; sessions are not individual people.

Event attendance

Attendance does not require an account. When you first save a response, we set a secure, first-party attendance cookie that can last up to one year. We store a hash of its random browser token and your event choices in the database. This functional cookie is separate from analytics and is used to remember and change your responses. Only totals are displayed publicly; browser tokens and individual response records are not listed.

You can change or clear a response in event details. Clearing cookies, private browsing, and different devices can create separate responses, so these are informal browser-based counts, not verified unique people. Existing counts remain if the cookie is lost. Manual backups include attendance records. Optional profiles and attendance history may be added later.

Event suggestions

Suggesting an event does not require an account. Cloudflare Turnstile checks the browser before enabling submissions, location searches, and flyer uploads. A secure, first-party suggestion cookie remembers a random browser identifier for up to 30 days; verification lasts one hour. This identifier links your uploads to your suggestion and enforces submission limits. Clearing cookies can prevent you from attaching earlier unpublished uploads.

Turnstile processes information needed to detect bots under Cloudflare’s privacy policies. We do not send your event draft or flyer to Turnstile. For abuse limits, we retain a daily keyed digest of the network address in expiring counters, rather than the address itself. Submitted event information and flyers are retained for administrator review and included in encrypted backups.

Do Not Track and Global Privacy Control disable browser analytics automatically. You can also opt out on this device:

The public directory does not require analytics. This preference applies to this browser. Event suggestions and sign-in use separate information needed to provide those features.