Trust and policy
Cookies Policy
Explain essential cookies, session cookies, analytics choices, and how website users can understand cookie use on ESAAP.
Trust context
Cookies Policy supports approval confidence
Cookie use should be understandable
Visitors should be able to distinguish essential session behavior from any measurement or analytics use.
Demo login may need sessions
Session behavior can support login, protected ESAAP workspace areas, forms, and security-related website behavior.
Control stays with the user
Cookie guidance should explain browser controls and where to ask privacy questions.
Evidence to keep ready
Cookies Policy: evidence your team should ask for
Essential behavior
Sessions, form behavior, protected ERP preview access, and security functions that may require cookies.
Measurement clarity
Any analytics or performance measurement should be described in plain language before launch.
User choice
Browser controls and privacy contact routes should be easy for institutional visitors to understand.
Essential cookies
Session and security cookies keep demo login and protected app areas working correctly.
Measurement choices
Describe analytics or measurement cookies clearly if enabled for website performance review.
User control
Provide clear contact or browser guidance for users who want to manage cookies or ask privacy questions.
Review checklist
Cookies Policy: what your institution should clarify
Essential use
Clarify which cookies keep demo login, session state, security, or form behavior working.
Measurement use
Explain any website performance measurement in plain language for institutional reviewers.
Browser control
Guide users to browser-level choices for cookie management where relevant.
Policy owner
Keep cookie wording aligned with privacy review and website behavior.
Trust next step
Move from cookies policy review into a focused ESAAP discussion
Your team can continue with security, support, demo, pricing, or implementation planning after reviewing cookies policy.
Book ESAAP Demo