Cookies policy
Lightweight browser storage helps distinguish whether informational notices received acknowledgement. Categories below summarize what may load alongside static HTML describing outdoor facilitation workshops headquartered in Oklahoma City references.
Technically routed storage
Fonts, stylesheet libraries, mapping embeds, and HTTPS assets fetched from CDNs attach session identifiers bounded to those networks. Coordinators neither purchase cross-site trackers nor incentivize intrusive retargeting.
Preference remembrance
Selecting “Allow notice storage” records a benign localStorage key named openfield_consent_signal_v1 that stores literal strings “accepted” or “declined” so the banner stops repeating unnecessarily. Selecting decline prevents writing any marketing pixel beyond unavoidable CDN diagnostics.
Clearing browser data removes those keys silently without contacting our servers.
Diagnostic snippets
Minimal server-side metrics capture HTTP statuses, referrer domains, coarse geography at state resolution, and request timestamps aggregated into weekly spreadsheets for uptime monitoring—not micro-segment audiences.
Controls you retain
- Browser settings commonly include global cookie blocking—we respect those signals whenever technically feasible.
- Contact staff if embedded mapping fails after strict blocking; coordinators can summarize directions without interactive maps upon request.
- Questions cascade to the documented inbox with subject line referencing “cookies.”