Optional analytics.
Before you allow analytics, we do not create a stable analytics identifier. Your choice is stored in a first-party preference cookie for 90 days. If you allow, a random session cookie helps count a consented landing and approved outbound clicks, and a separate random visitor cookie measures returns across days. The session expires after 30 minutes of inactivity; the visitor and preference cookies last 90 days from use.
Stored visit data is limited to the day, landing path and broad referrer class: direct or unknown, search, AI referral or other referral. Return measurement stores a one-way hash of the random visitor identifier, its first observed day and days of activity. Raw referrer URLs, question text, IP addresses and gambling histories are not saved in this analytics database. Query strings are excluded.
Visitor activity and session records are kept for 90 days; inactive visitor identifiers are removed with that history. Use Analytics preferences in the footer to decline later. Declining deletes the current visitor identifier and its activity days, clears its cookies and removes the current session association. Existing accounting click references may remain without the visit link. Clearing cookies can prevent us identifying an older association.
Sending a question to AI.
The adviser is optional. You must confirm that you are 18 or over and agree to send the question to Z.ai. This permission is separate from analytics. The question, selected product category and public source records are sent to Z.ai’s standard API using GLM-5.3. We do not send an analytics identifier, IP address or gambling account history in that request.
Wager Standard does not store chat questions or conversation history. Each question is processed separately. Avoid personal data: names, account numbers, identification documents, financial details and contact information. The app rejects common email and long-number patterns, but that is not a complete personal-data detector.
Z.ai processes the request under its API service terms and applicable data-processing arrangements. Do not assume that a consumer-chat privacy setting or a no-retention promise applies to the API.
Operational data.
The application uses short-lived in-memory request counters to limit abuse. It hashes the connection address with a process-specific random salt and does not persist the raw address. The site runs on Microsoft Azure in the EU (North Europe region). Hosting and network providers may process connection logs; our application logs are kept for 30 days.
Self-hosted fonts and brand artwork avoid third-party font requests. We do not embed advertising pixels, social tracking widgets or a third-party chat script.
Commercial records and your choices.
If an approved affiliate agreement is activated, a random click reference may be shared with that operator under the agreed attribution format and your analytics choice. Partner reports can contain qualification, commission, adjustment and cash events. They should contain no player names, email addresses, betting history or account credentials.
Analytics and the adviser run only with your consent, which you can withdraw at any time through Analytics preferences in the footer. To ask what is stored about you, or to have it deleted, write to the contact address below. You can also complain to a data protection authority; for our publisher that is the Office of the Data Protection Ombudsman in Finland.
