363 login Privacy Policy: How We Handle Your information
When you open an account with 363 login, you share personal details with us — and this policy explains exactly what we collect, why we collect it, and what choices you have. Availability of our service depends on local law and applies only to eligible regions where access is permitted.
This policy applies to all personal information collected when you register an account, log in, make a deposit through GCash, Maya or Coins. ph, or contact our support team. The data we collect falls into three broad categories: identity details you supply at registration (such as your name and contact number), transaction records associated with your wallet activity, and device or session data generated when you browse our pages. We collect this information to operate your account, process wallet deposits and withdrawals, verify account access, and respond to support requests. We do not sell your personal information to third parties for their own marketing purposes. Where we share data with payment processors — for example, to route a GCash or Maya transaction — we share only what is necessary to complete that specific action. Data is retained for as long as your account remains active and for the period required under applicable regulations in the regions where we operate. When you close your account, we follow a structured retention schedule before permanent deletion. The current status of any data held on your account is visible after login in your account dashboard. If you have questions about what is stored, the contact path in this policy is the right place to start.
GCash
Transaction records linked to GCash deposits or withdrawals are processed by the payment provider and referenced in your account history.
Maya
Maya wallet activity appears in your transaction log. We pass only the data required to complete the transfer to Maya's processing system.
Coins. ph
Coins. ph transfers follow the same data-minimisation approach — only the fields needed for the transaction are shared with the payment network.
INSIDE VS OUTSIDE
Where This Policy Applies and Where It Does Not
Not every digital touchpoint connected to your account falls under this policy in the same way. Understanding the boundary helps you know where to direct questions about your data and where to look at a third party's own terms instead.
Account access and login
Everything tied to your 363 login account — registration fields, login sessions, password resets and identity verification steps — is covered fully by this policy. We are the data controller for these records.
Wallet transactions
When you deposit or withdraw using GCash, Maya or Coins. ph, the transaction passes through the payment provider's own systems. We hold the account-side record; the provider holds the wallet-side record under their own privacy terms.
Site content and game sessions
Session data generated while you play — game history, bet records, session duration — is stored in your account and covered by this policy. Game content is supplied by studios; we do not share individual session data with them in identifiable form.
Third-party links and services
Links from our pages to external sites or apps are outside our policy scope. Once you leave 363 login, the destination site's own privacy terms apply. We have no control over how those services handle your data.
YOUR ACCOUNT CHOICES
Practical Steps You Can Take Under This Policy
You have concrete options for managing the personal information we hold on your account. These are not abstract rights — each one has a specific action path you can follow right now. To review the data associated with your account, log in and open the account dashboard. Your registered details, transaction history and linked wallet records are displayed there without needing to contact us first. If any detail is incorrect — a wrong contact number or a misspelled name — you can update it directly in the account settings fields shown on that page. If you want to raise a question about how your data is used, or if you believe a record is inaccurate and cannot correct it yourself, send a message through the support contact path listed in this policy. We will confirm receipt and respond within a reasonable period. For requests to close an account and initiate the data retention schedule, contact support directly rather than deleting the app — a formal account-closure request ensures the correct process is followed and that your wallet balance is handled before the account is deactivated.
Review your records
Log in and go to your account dashboard. Your registered details, transaction history and wallet records are visible there without a support request.
Correct account details
Update a wrong contact number, name or linked wallet reference directly in account settings. Fields are editable; instructions are shown on the settings page.
Raise a data question
Use the support contact path in this policy to ask about a specific record. Confirm the account email when you write so we can locate the right record quickly.
Request account closure
A formal closure request through support starts the retention schedule and ensures your wallet balance is settled before the account is deactivated. Do not simply uninstall the app as a substitute for this step.
PRIVACY CONTACT PATHS
How to Reach Us About This Policy
Privacy questions deserve a direct answer. The contact options below are the right channels for anything related to this policy — data access requests, correction queries, account-closure requests or questions about how a GCash or Maya transaction record is stored.
Live chat support
Open the chat widget from any page after login. Describe your data or privacy question and a support agent will pick it up. Have your registered account email ready to speed up verification.
Email support
Send your privacy-related question to the support email address shown in your account dashboard under Contact Us. Include your account reference number and a clear description of the record in question.
Account dashboard
Many data queries can be resolved without contacting us. Log in, open the dashboard, and check your transaction history, registered details and wallet records. The current state of your account data is shown there after login.
HOW WE MANAGE DATA
Data Handling, Cookies, Retention and Account Security
We keep this policy current and apply it consistently across account types. The four areas below cover the practices most relevant to your account and the data it holds.
Cookies and session data
We use cookies to keep your session active while you navigate the lobby and to remember your login state between visits. No cookie on 363 login tracks your activity across unrelated third-party websites. You can manage cookie preferences through your browser settings; some account functions require session cookies to operate correctly.
Account security practices
Account access is protected by your login credentials, and we apply standard encryption to data in transit. We never ask for your full password by chat or email. If you receive a message asking for this, do not respond — report it through the live chat support channel immediately.
Data retention schedule
Active accounts retain data for as long as the account is open. After a formal closure request, data is held for the period required under applicable regulations in eligible regions, then deleted on schedule. The retention period cannot be shortened on request where legal obligations apply.
Policy updates
When this policy changes in a material way, we post the updated version on this page and note the revision date. Continuing to use your account after a posted update means you have had the opportunity to review the change. Check this page periodically to stay current.
POLICY QUESTIONS ANSWERED
Frequently Asked Privacy Policy Questions
These are the questions we hear most often about how 363 login handles account data, wallet records and your rights under this policy.
What personal information does 363 login collect when I register?
At registration we collect the details you enter in the sign-up fields — typically your name, contact number and email address. If you connect a payment method like GCash or Maya, the account-side reference for that wallet is also stored. We do not store full wallet credentials or payment provider passwords.
Is my GCash or Maya transaction data stored on 363 login's systems?
We store the account-side transaction record — the amount, date and outcome visible in your account history. The wallet-side record sits with GCash or Maya under their own privacy terms. We share only the data needed to process the transfer and do not retain full wallet account numbers on our systems.
How do I see what data 363 login holds on my account?
Log in and open your account dashboard. Your registered details, linked payment references and transaction history are displayed there. If a record looks incorrect or you need information that is not shown on the dashboard, contact support through live chat or the email address shown under Contact Us.
Can I ask 363 login to correct or delete my personal data?
Yes. Errors in your registered details can be corrected directly in account settings after login. For deletion requests, contact support to initiate a formal account closure. Data is then held for the legally required retention period before deletion. We cannot delete records that are subject to active regulatory obligations.
Does 363 login share my data with game studios or third parties?
Game session data is not shared with studios in a form that identifies you personally. Payment data is passed to the relevant payment processor — GCash, Maya or Coins. ph — only to complete a specific transaction. We do not sell personal information to any third party for marketing purposes.
What should I do if I think my account data has been accessed without my permission?
Contact support immediately through live chat. Have your registered email address ready. Change your login password as soon as you can access the account settings page. We will review the account access log and respond to your report. Do not share your credentials with anyone claiming to be from support.