Read the POS privacy notice
The POS privacy route and in-app notice explain current data handling; customer collection should be limited to the operational purpose and applicable consent. Open Privacy from login or the notice, read the current published text, and use the customer consent controls when collecting personal data. 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 privacy notice.
- Identify whether the question concerns POS use, customer data, consent, or a privacy request.
Steps
- Open Privacy from login or the notice.
- Read the current published text.
- Use the customer consent controls when collecting personal data.
- Contact support for a privacy request.
Expected result
The current published privacy version is readable and any customer consent choice uses the dedicated consent workflow. Use the published document currently displayed and collect only the customer information required for the stated purpose.
Permissions
- Public read access; recording or withdrawing customer consent requires the assigned customer permission.
Troubleshooting
The public Privacy page does not load or no current document version is shown.
Check the `/legal/privacy` URL and connection; sign-in is not required. Refresh once. If the legal service still fails, retain the public URL and time and contact Support without sending credentials or customer data.
A customer consent choice is unclear after it was submitted.
Open the dedicated customer consent control and inspect its displayed state. Do not repeat or infer consent from the legal page. If the state remains unclear, preserve the customer reference and ask an authorized privacy user to review it.
Related articles
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