Required cookies
Needed for secure sessions, CSRF protection, form handling, login state, consent storage, abuse prevention, and basic page delivery.
Cookie Preferences
The cookie and storage categories used on AWRA’s public pages, which are required and which are optional, and how to change your choice.
Last updated October 8, 2026
Functional cookies
Remember public-page preferences, helper prompt state, convenience settings, and non-essential display behavior.
Analytics cookies
Measure aggregated site usage, product interest, public-page performance, and conversion patterns to improve the website.
Marketing and engagement
Support demo prompts, campaign attribution, and public engagement flows where enabled and permitted.
How preferences apply
Consent choices are practical controls, not a replacement for required security cookies.
Public pages
Your choices mainly apply to AWRA public website experiences such as feature pages, pricing, blogs, help center, request demo, and legal resources.
Authenticated app
Dashboard, vendor portal, payment, security, and form workflows still rely on required cookies to operate safely.
Browser controls
You can also block or delete cookies through your browser. Some browser choices may override or erase saved AWRA preferences.
Preference storage
The consent manager stores your choice so AWRA can remember it. If storage is blocked, the choice may only apply temporarily.
Need more detail?
Cookie preference controls connect to the wider privacy program.
Review the Cookie Policy for detailed categories, the Privacy Policy for data-use context, and Your Privacy Choices for access, deletion, correction, restriction, and opt-out pathways.
Cookie inventory
Representative cookies and storage AWRA may use.
Exact cookie names and expiry can change as the platform, analytics configuration, security tooling, and public website evolve. This table explains the practical categories.
Name or group Category Purpose Typical retention
app_session Required Maintains secure web session state for visitors and authenticated users. Session (about 120 minutes of inactivity)
XSRF-TOKEN Required Helps protect forms and authenticated actions from cross-site request forgery. Session or short-lived
awra_cookie_preferences Required Stores your cookie preference choice so AWRA can honor it on public pages. Also mirrored in local storage as awra.cookieConsent.preferences.v1. Up to 6 months
awra.publicEngagement.* Functional or engagement Controls public prompts, demo engagement state, and convenience memory where enabled. Varies by setting
Google Analytics identifiers Analytics Measures aggregate public website traffic, page performance, and product interest signals. Provider-defined expiry
Campaign or attribution storage Marketing and engagement Helps connect a public website visit to a demo request or campaign source where enabled. Varies by configuration
Using the manager
Cookie controls should be easy to revisit, not a one-time trap.
01
Open the manager
Use the button on this page or the Cookie Preferences link in the public footer.
02
Review categories
Read the purpose of each category and decide which optional categories fit your preference.
03
Save your choice
Save preferences, accept all, or choose necessary only. Required cookies remain active.
04
Revisit anytime
Return to this page or the footer link to update preferences when your choice changes.
Browser controls
Your browser can add another layer of control.
Block or clear cookies
Most browsers allow you to delete cookies or block third-party cookies. This may also remove saved AWRA choices.
Private browsing
Private windows may forget preferences when closed, so the banner or manager may appear again.
Global Privacy Control
Some browsers or extensions send privacy preference signals. AWRA also provides explicit cookie controls for the public site.
Script blockers
Strict blockers can prevent analytics or engagement scripts from loading and may also block preference storage.
Cookie preference questions
Common questions before changing settings.
Why are required cookies always active?
They keep sessions secure, protect forms, remember the consent choice, support login behavior, and prevent abuse. Disabling them would break core website or app behavior.
Do cookie choices affect the dashboard?
They mainly affect optional public website behavior. Authenticated app sessions, payment, vendor portal, and security workflows still need required cookies.
Can I reject analytics?
Use the Cookie Manager and browser controls to manage optional categories where available. Some aggregate operational telemetry may still be required for security or service reliability.
Why did the cookie banner return?
Your browser may have cleared storage, blocked preference persistence, opened a private window, or used a different browser or device.
Do you use cookies to sell personal data?
AWRA does not sell personal data. See the Privacy Policy and Your Privacy Choices page for more detail about data use and opt-out paths.
Help Center
Need a quick answer while you read?
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.
