Cookies and browser storage
Essential sign-in and security storage is needed for the website to work. Optional AnuAssure custom event analytics stays off unless you choose to allow it.
What the application stores
- Essential authentication/session cookies: first-party sign-in, session, security and short-lived navigation behavior. These are needed for the requested account and portal features and are not controlled by the optional analytics choice.
- Trial-request form security:
aa_access_formis a signed, first-party security cookie lasting up to one hour. It protects the request and invitation forms and contains no applicant details or invitation code. - Cookie preference: a versioned first-party preference cookie remembers whether optional analytics was accepted or rejected.
- Optional analytics, only after acceptance: a short-lived receipt cookie may carry a fixed, allow-listed event for delivery; session storage may remember delivered event IDs for this browser session to avoid duplicates. No care-note, person-name, email, account or location values are included in these custom events.
Rejecting or withdrawing the optional choice does not sign you out or disable essential authentication. The website removes pending event receipts and does not load its custom-event script unless the current versioned preference is accepted.
Separate platform setting: the hosting platform can have its own publishing analytics separate from application code. Its status and consent behavior are not visible here. The owner must verify that setting and disable it or ensure its own appropriate consent control before public release. The controls above govern AnuAssure’s application-level custom events.
There is no website cookie banner or browser-cookie choice in the native app. Native device permissions, including location, are managed separately in the operating system and in the app’s staff duty controls.