Required cookies
Needed for secure sessions, CSRF protection, form handling, login state, consent storage, abuse prevention, and basic page delivery.
AWRA OpsHub
Loading workspace...
Cookie Preferences
Required cookies keep sessions and forms secure. Optional categories help remember preferences, measure website performance, and manage demo engagement. You can review or update your choices below.
Needed for secure sessions, CSRF protection, form handling, login state, consent storage, abuse prevention, and basic page delivery.
Remember public-page preferences, helper prompt state, convenience settings, and non-essential display behavior.
Measure aggregated site usage, product interest, public-page performance, and conversion patterns to improve the website.
Support demo prompts, campaign attribution, and public engagement flows where enabled and permitted.
How preferences apply
Your choices mainly apply to AWRA public website experiences such as feature pages, pricing, blogs, help center, request demo, and legal resources.
Dashboard, vendor portal, payment, security, and form workflows still rely on required cookies to operate safely.
You can also block or delete cookies through your browser. Some browser choices may override or erase saved AWRA preferences.
The consent manager stores your choice so AWRA can remember it. If storage is blocked, the choice may only apply temporarily.
Need more detail?
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
Exact cookie names and expiry can change as the platform, analytics configuration, security tooling, and public website evolve. This table explains the practical categories.
Using the manager
Use the button on this page or the Cookie Preferences link in the public footer.
Read the purpose of each category and decide which optional categories fit your preference.
Save preferences, accept all, or choose necessary only. Required cookies remain active.
Return to this page or the footer link to update preferences when your choice changes.
Browser controls
Most browsers allow you to delete cookies or block third-party cookies. This may also remove saved AWRA choices.
Private windows may forget preferences when closed, so the banner or manager may appear again.
Some browsers or extensions send privacy preference signals. AWRA also provides explicit cookie controls for the public site.
Strict blockers can prevent analytics or engagement scripts from loading and may also block preference storage.
Cookie preference questions
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.
They mainly affect optional public website behavior. Authenticated app sessions, payment, vendor portal, and security workflows still need required cookies.
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.
Your browser may have cleared storage, blocked preference persistence, opened a private window, or used a different browser or device.
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
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.
Demo booking
Share a few details so we can send the confirmation email and route your request to the right AWRA team.
Privacy choices
We use necessary cookies for secure sessions. With your permission, we also use cookies and browser storage for preferences, analytics, and demo engagement. Privacy Policy
AWRA OpsHub
Cookie settings
Necessary cookies stay on for login, CSRF protection, and security. You can choose the optional categories below.
Overview
AWRA uses cookies and browser storage to keep public pages secure, remember selected preferences, measure website performance, and manage demo engagement prompts.
You can choose whether functional and marketing engagement storage apply. Analytics measurement is always active in this AWRA setup.
These settings apply to AWRA public website experiences such as the homepage, feature pages, pricing calculator, blog, help center, and request-demo page. Authenticated dashboard and vendor portal sessions still rely on required security cookies.
For more context on privacy handling, open the Privacy Policy.
Required Cookies
Required cookies and storage support basic website delivery, secure sessions, request protection, and remembering the consent choice itself.
These cannot be switched off from this manager because disabling them would break login/session behavior, form protection, or the ability to remember the privacy choice you save.
Functional Cookies
Functional storage improves the public website experience by remembering interface choices, helper states, dismissed notices, and short-lived interaction preferences.
Turning this off does not stop secure required cookies or analytics. It only limits optional convenience memory.
If disabled, AWRA may show some helper prompts again or forget non-essential display choices. Core public pages, contact forms, and request-demo forms still work.
Analytics Cookies
Analytics helps AWRA understand public page performance, traffic patterns, and content usefulness so we can improve the marketing website.
This category does not by itself enable demo popups, exit-intent prompts, or advertising pixels. Those are controlled by Marketing & engagement.
In this AWRA setup, Google Analytics and Google Tag Manager measurement are treated as mandatory website measurement and remain active.
Marketing & engagement
Marketing and engagement storage supports demo prompts, exit-intent prompts, campaign attribution, and future advertising pixels.
When disabled, AWRA will not auto-open demo or exit-intent popups. CTA buttons can still open a form because that is a direct visitor action.
When enabled, AWRA can remember that a visitor already saw, dismissed, or submitted a demo prompt so the same popup is not repeated aggressively.
Public assistant
Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.