Read and manage the cookie notice
The public Cookie Notice route and banner explain cookie choices available in the POS browser. Open Cookie Notice from login or the banner, review the described cookie categories, and use the available banner choice. Use the current published notice and collect only the customer information needed for the stated operational purpose.
Before you start
- No sign-in is required to read the published cookie notice.
- Use the same browser profile whose cookie choice needs review.
Read the Cookie Notice
- Open /legal/cookie-notice.
- Read the current published document and version without signing in.
Respond to the cookie banner
- Read the choices presented by the banner.
- Select the intended available choice once.
- Verify the banner or cookie control shows the saved choice before selecting it again.
Expected result
The public notice explains the available categories and the selected banner choice persists for that browser. Use the published document currently displayed and collect only the customer information required for the stated purpose.
Permissions
- Public read access. The browser user can choose among the cookie options actually offered by the banner.
Troubleshooting
The workflow stops while staff open Cookie Notice from login or the banner, before they can review the described cookie categories.
First confirm the following access and record state: No sign-in is required to read the published cookie notice. Use the same browser profile whose cookie choice needs review. Return to /legal/cookie-notice without changing user, branch, or record. Try the blocked step once; if it remains unavailable, stop and provide Support the document title, public URL, version, or consent control; omit credentials and customer data. Keep evidence of the result when staff open Cookie Notice from login or the banner.
The published version or explicit consent state is missing or unclear after the final checkpoint: Reopen the notice when policy details are needed.
Check the public URL, published title/version, connection, and any explicit cookie or customer-consent choice. Refresh the public document once after connectivity returns; do not repeat a consent change until its state is clear. If those records still disagree, stop and send Support the document title, public URL, version, or consent control; omit credentials and customer data. Before another attempt, establish whether staff could reopen the notice when policy details are needed.
Related articles
The POS privacy route and in-app notice explain current data handling; customer collection should be limited to the operational purpose and applicable consent.Read the POS terms of service
The public Terms route displays the currently published terms returned by the legal content service.
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback