1. What cookies are used for
Cookies and browser storage help WebRiskOps keep sessions active, protect forms, remember preferences, operate public pages and understand product usage.
- Sessions and security
- Preferences
- Product usage measurement
Cookie policy
WebRiskOps Cookie Policy
This policy explains how WebRiskOps uses cookies and browser storage for public pages, app sessions, preferences, security and limited product analytics.
Plain cookie policy for WebRiskOps public pages and app preferences.
This page is limited to cookie and browser-storage terms. It does not add marketing claims or legal advice.
Cookie settings boundary: This policy is not legal advice; changing browser settings may affect sign-in, security, preferences and product workflows.
2. Essential cookies
Essential cookies support sign-in, CSRF protection, account workflows, checkout routing, support forms and other required product functions.
- Authentication and sessions
- Security controls
- Workflow state
3. Preference storage
WebRiskOps may store theme preference, dismissed notices and similar settings in browser storage so the interface remains consistent.
- Theme preference
- Cookie notice dismissal
- Interface settings
4. Analytics and measurement
Analytics may be used to understand public page performance and product usage. Analytics should not decide legal status, scan results or eligibility by itself.
- Public page measurement
- Product usage signals
- No legal-status decision
5. Changing cookie settings
Users can change cookie and storage settings in their browser. Blocking or deleting cookies may affect sign-in, security controls, saved preferences and app workflows.
- Use browser controls
- Deleting storage resets preferences
- Some workflows may require cookies