Lizaro Privacy Policy

This page explains how privacy works around your Lizaro account, payments, support, and verification checks.

Your safest reference is the current privacy policy on the site, plus what your account screens show in Payments and KYC.

Below you’ll see what data is typically involved, why it is used, and what rights you can exercise.

If you want a change, export, or deletion, you will also find a practical request routine.

Where to Find the Current Privacy Policy

The current policy is the version you should rely on. Always check the “last updated” line and make sure you are reading the right language/locale version for your account.

Use this table to confirm you are looking at the right source.

For legal definitions that interact with privacy, review terms and conditions alongside this policy.

What Data Lizaro Collects

Privacy policies typically cover several data categories. Some are required to run your account, while others support security, payments, and troubleshooting.

This overview helps you understand what category a piece of information belongs to.

• Never post your account email and references publicly online.
• Never share full ID photos or documents in open chats.
• Never share 2FA codes, passwords, or recovery details with anyone.
• Keep screenshots private and remove unrelated personal information first.
• Use official support channels for anything involving documents.

Why Lizaro Uses Your Data

Data is generally used to provide the service, keep accounts secure, process payments, deliver support, and meet compliance requirements. What matters is what purpose applies to what data.

Use this map to connect purposes with what you can verify in your account.

Cookies and Similar Technologies

Cookies help sites remember sessions and preferences. Some cookies are functional, while others can be analytics or marketing-related (if used). Your controls depend on the consent banner, browser settings, and sometimes in-account settings.

Use this table to understand typical cookie categories and what you can control.

Payments Data: What’s Stored and What You Should Save

Payments data is important because it ties directly to deposits, withdrawals, and support investigations. You should keep your own clean records too, so you can prove what happened without guessing.

• Save deposit and withdrawal timestamps for any disputed case.
• Save transaction references or IDs shown in Payments history.
• Save crypto transaction hashes and the network label used.
• Save screenshots of the status line when something looks wrong.
• Save the method name you used for deposit and withdrawal.

For payout-related data, use withdrawal history to capture references and status lines.

If a payment record is missing, check payment methods and your cashier context first.

Verification (KYC) Data and Document Handling

Verification can involve sensitive documents. The safest approach is to upload only what is requested, use clear files, and never share documents outside official channels.

If your request involves documents, follow verification steps and upload only what is asked.

1. Open your Verification/KYC screen and read the request carefully.
2. Prepare clean, readable files that match the requested document type.
3. Upload only requested pages and avoid unnecessary extra information.
4. Confirm submission status in the KYC screen after upload.
5. Keep screenshots of the request text and submission confirmation.

Support Messages and Attachments: What Happens to Them

When you contact support, your messages and attachments become part of the support record. That record is used to solve issues, confirm timelines, and explain outcomes.

Only send evidence that is relevant, and avoid sending additional personal documents unless support requested them through KYC channels.

Marketing Preferences and Communication Controls

You may be able to manage marketing preferences through account settings or within messages. If you do not want marketing messages, use opt-out controls where they are provided.

• Check account settings for communication preferences and switches.
• Use opt-out links in messages if they are provided.
• Keep transactional emails enabled for security and payments.
• Do not disable essential cookies if login becomes unstable.
• Confirm changes by checking whether you still receive promotions.

Data Sharing: Processors, Partners, and Legal Requests

Privacy policies typically explain that data may be shared with service providers (processors) needed to run the platform, handle payments, provide analytics, or deliver customer support.

They can also describe situations where disclosure is required by law or legitimate requests. Always rely on the policy wording for the specific scope.

Data Retention and Deletion Basics

Retention rules define how long certain data is kept. The privacy policy may describe retention in principle, while exact durations can depend on legal and operational requirements.

If you want deletion or closure, the correct approach is to submit a formal request through support.

Your Rights: Access, Correction, Deletion, Objection

You may have rights such as requesting access to your data, correcting details, requesting deletion/closure, or opting out of marketing communications. Use a clear request and include the details support needs to identify your account.

Use this practical map to prepare a clean rights request.

To submit a privacy request or correction, contact support with your account email and details.

Security: What Lizaro Does vs What You Should Do

Security is shared responsibility: the platform uses security controls, while you protect your own login and devices. The easiest wins come from clean account habits.

• Use a unique password and never reuse it across sites.
• Do not share account access with friends or third parties.
• Log out on shared devices and avoid saving passwords publicly.
• Take screenshots carefully and store them in a private folder.
• Watch for suspicious login prompts and react immediately.

For safer-account controls and limits, use responsible gambling tools in your profile.

Problems and Solutions

Request a Copy of My Data (Access Request)

If you want a copy of your data, send a clear access request and be ready to prove account ownership. Keep the request short and specific.

• Write a subject like “Data access request” in your message.
• Include your account email and the date you created it if known.
• Specify what you need: full export or specific category data.
• Wait for identity confirmation steps if support requires it.
• Keep all replies in the same ticket for clean tracking.

Send support your email, request scope, and any case references.

Correct My Personal Details (Email / Profile Data)

If your profile details are wrong, request a correction with evidence. Some details may be locked if they are tied to compliance checks.

• Describe what field is wrong and what it should become.
• Attach a screenshot of the profile field if visible.
• Include timestamps of when you noticed the issue.
• Be ready for identity checks if the change is sensitive.
• Do not create a second account to “fix” a profile issue.

Send support your email, screenshots, and the corrected data text.

Delete or Close My Account (Deletion Request)

Account deletion or closure requests should be made formally and clearly. Support may explain constraints if there are open transactions or compliance retention rules.

• Write a clear request: “Please close my account and delete data.”
• Include your account email and confirm you are the owner.
• Check your Payments history for pending items before requesting.
• Save screenshots of the request confirmation in the ticket.
• Follow any identity confirmation steps sent by support.

Send support your email, confirmation of ownership, and any pending status info.

KYC Document Privacy Concern (What to Upload and When)

If you are concerned about KYC privacy, the safest move is to upload only what is requested and only through the official KYC screen. Avoid sending documents through chat unless the platform explicitly directs it.

• Read the request carefully and upload only requested document types.
• Use clear, readable images and avoid unnecessary extra pages.
• Never send full ID photos in social channels or email threads.
• Keep the request text screenshot for your own record.
• Ask support to confirm the correct upload channel if unsure.

Send support your email, screenshot of the KYC request, and your concern text.

Suspicious Login or Activity (Security + Evidence)

If you notice suspicious activity, act quickly. Secure your account first, then report it with a clean timeline and screenshots.

• Change your password and log out of other devices if possible.
• Stop playing or depositing until you confirm account safety.
• Capture screenshots of unusual prompts or history entries.
• Write a timeline: what happened, when, and what you saw.
• Contact support with evidence and avoid repeated logins.

Send support your email, timeline, and screenshots of suspicious activity.

Cookie Banner Choices Broke Login or Payments Pages

If cookies are disabled too aggressively, login sessions and payment pages can break. Restore functional cookies and reload the site.

• Enable functional cookies or reset your cookie consent choices.
• Try a private window to avoid old cookie conflicts.
• Clear site cookies and cache, then log in again cleanly.
• Disable heavy blockers temporarily to test page behavior.
• Re-check whether Payments pages load after cookie reset.

Send support your browser details, screenshots, and the time it happened.

FAQ

Where can I find the latest Lizaro privacy policy?

Open the Privacy Policy page on the official site and check the “last updated” line.

What data does Lizaro collect about my account?

Typical categories include account details, device/session data, payments history, support messages, and verification data.

Does Lizaro collect payment and transaction information?

Yes, payments history and references are typically stored to process deposits, withdrawals, and disputes.

Why might verification documents be requested?

Verification can be required for security and compliance checks, especially during withdrawals.

How are support messages and attachments handled?

They become part of your support record and are used to resolve issues and confirm timelines.

What cookies are used and can I disable them?

Functional cookies keep sessions working, while analytics/marketing cookies may be optional. Controls depend on consent and browser settings.

Will disabling cookies break login or payments pages?

It can. If functional cookies are blocked, login and Payments pages may not work properly.

How do I opt out of marketing messages?

Use account preference controls or opt-out links in messages when available, while keeping security emails enabled.

Can I request a copy of my data?

Yes, submit an access request through support with your account email and request scope.

How do I correct my personal information?

Ask support for a correction and provide what is wrong, what it should be, and screenshots if possible.

Can I request deletion of my account data?

You can request deletion/closure through support, but retention constraints may apply for legal reasons.

What should I include in a privacy request to support?

Include your account email, a clear request type, timestamps, and any relevant screenshots or references.