Reference

Privacy Policy for Your Account

This page explains how kr739 handles account details, device data, session logs and payment records, and when cookies are used to keep your language and login settings in…

Account dataCookiesRecordsLocal law
kr739 Privacy Policy for Your Account
CONTACT PATHS

How to Reach Our Privacy Team

For privacy requests, we keep the contact paths simple so you can reach the right team without repeated handoffs.

Privacy email Write to our privacy inbox if you want a copy of the data we…
In-app chat Use chat for quick questions about cookies, consent choices, or how long a record…
Contact form If you need a formal request in writing, send it through our contact form…
SAFE HANDLING

How We Handle Your Records

We keep this area practical: collect only what the account needs, store it for a defined reason, and let you ask for access or correction through the same account you use.

Data minimisation

We collect only what is needed to open and run your account, confirm payments, answer support, and meet legal duties. We avoid extra fields unless a specific step asks for them.

Cookie control

Cookies remember your login state, language and session settings. You can clear them in your browser, though some pages may ask you to sign in again or reset preferences.

Account security

We expect you to keep your password and one-time codes private. On our side, we watch for unusual sign-ins, lock risky sessions, and ask for extra checks before sensitive changes.

Storage period

We keep records only as long as needed for account support, dispute handling, fraud checks and legal duties. When the retention window ends, we remove or archive the data under our process.

Change requests

If your phone number, email or other details change, contact us from the account or through support and ask for a correction. We will update what we can and tell you if a rule blocks the change.

Access requests

You can ask what we store, why we store it and who can see it. We respond through the contact path tied to your account, and we may ask for checks before sharing sensitive records.

Privacy Questions You May Ask

These questions cover the parts you are most likely to check before opening an account or sending a request. We answer from the records we keep, the access rules that apply to your location, and the steps we use to protect sensitive data. If a request depends on local law, we will say so plainly and tell you what we can do next.

We usually collect the details you enter on the account form, your contact details, device and browser data, session logs, payment references and support messages. If a local rule asks for extra checks, we may collect those too.

Cookies help us keep you signed in, remember language settings and reduce repeated checks during the same session. You can block or delete them in your browser, but some pages may then ask for fresh sign-in.

Send the request from the email or mobile number linked to your account, or contact support and choose the privacy subject. We may ask for a verification step before making changes to protect your record.

You can ask for deletion or closure where local law permits and where we do not need to keep the record for fraud checks, disputes or legal duties. If we must retain part of it, we will say why.

Access is limited to staff and service partners who need it to run the account, process payments, handle support or meet legal duties. We do not open your record for casual use.

We compare the request with the contact details and account history we already hold, and we may ask for a code or other proof before acting. That helps stop anyone else from changing your record.

We keep data only for the period needed for account support, dispute handling, fraud checks and legal duties. When that period ends, we delete or archive records under our retention process.