Mobile / Casino
This policy sets out exactly what account and session data decklucky collects, why we collect it, and what controls you hold over it. We wrote it to be read — not archived — so if a section raises a question, the contact route at the end of this page is where you take it.
When you create an account on decklucky, we collect the information you enter during registration — your name, contact details, and the payment method you choose to fund your wallet, whether that is GCash, Coins. ph, or Bank Transfer. We also collect session-level data: the pages you visit, the time you spend on them, and the device and browser type used to access the platform. This operational data helps us keep account sessions stable and detect unusual access patterns that could affect your account security. We do not sell your personal data to third parties. Where we share information — for example, with a payment processor handling a GCash or Bank Transfer transaction — the sharing is limited to what that processor needs to complete the transaction. Any third-party service operating in connection with our platform has its own privacy terms, and those terms govern data they independently collect. Availability of our services depends on local law and eligible regions. This policy applies to all sessions conducted through decklucky, regardless of the device used.
Transaction records tied to GCash top-ups are held for the period required to support account queries and comply with applicable obligations in your region.
Coins. ph transfer records are stored within your account wallet history and are accessible to you from your account dashboard after login.
Bank Transfer deposit references are logged against your account and available for your review through the transaction history section of your account.
Not every data interaction you have on decklucky falls under this single document. Understanding the boundary helps you know where to direct a question — to us, or to the third-party service involved. The four areas below outline what is in scope, what is handled separately, and where the line sits for your account activity.
Registration details, login credentials, session tokens and account settings are fully within this policy. We control and are responsible for how this data is stored and who may access it.
The payment step itself — processing a GCash, Maya or Bank Transfer deposit — passes through a payment processor. Their own privacy terms govern data collected at that processing stage, not ours.
Browsing behaviour, cookie preferences and analytics collected while you navigate decklucky are covered here. You can review and adjust cookie settings through your browser at any time.
Links from our site to external services — including payment apps or verification partners — take you outside our policy boundary. We have no control over data those services collect independently.
You are not a passive holder of an account here. This policy gives you concrete actions you can take over your personal data, and we have built the account interface to support those actions directly. Reviewing what we hold, correcting an error, or raising a concern each follow a clear path. Start with your account dashboard after login — most record queries and contact-detail corrections can be resolved there without needing to contact support. For data requests that go beyond what the dashboard covers, the policy contact route described in the support section below is the right channel. We aim to acknowledge data requests within a reasonable period and will tell you clearly if a request falls outside what we can act on under current applicable rules in your region.
Your transaction history, session log and stored contact details are accessible from your account dashboard. Log in and navigate to the account settings page to see what is currently held.
Name, contact number or email errors can be updated through the account settings section. Where a correction requires identity verification, the dashboard will display the steps needed.
If a section of this policy is unclear or you believe data has been handled incorrectly, contact us through the privacy support route listed in the support section of this page.
For requests involving data deletion or portability, reach out through the dedicated policy contact path. We will confirm receipt and outline the process and timeframe that applies in your case.
Three contact paths are available for privacy-related questions. Choose the one that suits the urgency of your query. For most account-level record questions, the dashboard is the fastest starting point — the options described below are for queries that need a direct response from our team.
Send your data request or policy question to our designated privacy address. Include your registered account email so we can locate your record without delay.
For time-sensitive account concerns — including unexpected data activity on your account — live chat connects you to a support agent who can flag the issue for the right team.
Log in and open the Help section. The in-account contact form routes your message with your account details already attached, which reduces back-and-forth for data-specific queries.
Account security and data handling are not separate concerns here — they are managed together. Every account session uses encrypted connections, and access to stored account data is restricted to the team members who need it to resolve a specific account matter. We do not retain data indefinitely; records are kept for the period required to support your account and meet applicable obligations in your region, after which they are removed from active systems. Cookie data collected during your session is used for platform function and session continuity, not for advertising profiles sold to third parties. You can clear or restrict cookies through your browser settings at any time without affecting your account login. When policy terms change, we post the updated version at decklucky/privacy-policy/ and note the revision at the top of the document so you can identify what has changed without reading the full text again.
Every account session — including GCash and Bank Transfer wallet activity — runs over an encrypted connection. This applies to mobile and desktop access equally, with no difference in protection based on device.
Cookies we set serve session continuity and platform function. You can review which cookies are active through your browser settings. Removing functional cookies may affect how pages load during your session.
We keep account records for the period that supports active account use and meets regional obligations. When the retention period ends, records are removed from live systems. Your dashboard shows the data currently held.
When this policy is revised, the updated version is posted at decklucky/privacy-policy/ with a revision note at the top. Continuing to use your account after a revision means you have seen the updated terms.
The questions below cover what we hear most often about account data, cookie handling, payment record access and how to reach us when something needs clarifying. If your question is not here, the policy contact route in the support section is where to take it.
We collect the details you enter during registration — name, contact email, phone number and the payment method you link to your wallet, such as GCash or Bank Transfer. We also log session data like device type and pages visited to keep your account session stable and secure.
Yes. Log in and open your account dashboard — transaction history, stored contact details and session records are displayed there. For data that does not appear in the dashboard, contact us through the privacy email route and we will locate the relevant records for you.
We share data only where it is needed to complete a service — for example, passing transaction details to the processor handling your GCash or Bank Transfer deposit. We do not sell your data. Any processor we work with is limited to data needed for that specific operation.
Retention periods are set by the type of data and the obligations that apply in your region. Active account records are kept for as long as your account is open. After account closure, records are held for the period required under applicable rules and then removed from live systems.
Open your account settings page after login and update the field with the error. If a correction requires identity verification — for example, a name change — the dashboard will show the steps to follow. For corrections the dashboard cannot process, use the privacy email contact route.
We set functional cookies that keep your session active and remember your account state between pages. We do not build advertising profiles from this data or share cookie information with ad networks. You can clear or limit cookies in your browser settings; this will not affect your account login credentials.