Our sso77 privacy introduction

sso77 Privacy Policy for Mobile Account Data Protection

This page describes what we collect when you use sso77 and how we keep that data protected when you open our mobile login, review a sportsbook market, enter a live-dealer table, or contact our support team.

We handle newer mobile signals differently from older desktop records because phone access often includes device details, notification settings, browser storage, and payment app references. Our policy explains that difference in plain English, with special attention to Android access, iOS browser use, KYC document handling, account recovery, and payment review.

We provide our services only where local law permits. Our users are responsible for checking that access and use comply with their own jurisdiction's law before they open or continue an account on sso77.

Our sso77 data collection and mobile use details

We collect account data that you give us directly, including your name, email, phone number, login credentials, support messages, and verification documents. We collect payment-related references when you use DANA, e-wallet, mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, online payment, or e-wallet, but we do not ask you to send unnecessary information outside the official account or support flow.

We collect technical data from mobile and desktop sessions, such as device type, browser version, approximate location signal, IP address, language preference, and security logs. We use these records to help detect account takeover risk, support login recovery, review disputed activity, and improve the way our pages load on smaller screens.

We use your data to operate sso77 account access, sportsbook coverage, live-dealer tables, slot game sessions, esports markets, wallet review, and customer support. We may also use the same records to confirm whether a request about Liga 1 markets, a live baccarat round, or a Mobile Legends esports market came from your verified account session.

Note: We may ask for additional verification when payment records, device signals, or KYC documents do not clearly match the account profile.

Our sso77 case example for verification review

We can illustrate our privacy handling with a neutral account review. Our user logs in from a phone in Jakartachanges a payment route, and later asks support about a withdrawal status. We compare the verified identity record, the payment ownership reference, recent device access, and the support message before we decide whether more documents are needed.

We do not use this review to create a public profile. Our purpose is limited to account security, payment accuracy, dispute handling, and service support. When our team asks for a clearer document image, we use it only for the related verification process unless a longer retention period is needed for legal, audit, or dispute reasons.

Our sso77 use of processors and cookies

We work with service processors that help us host pages, maintain security logs, deliver messages, process payments, review KYC documents, and provide support tools. Our processors may handle data outside your jurisdiction, and our contracts or operating controls require them to use the data only for the service task assigned to them.

We use cookies and similar storage for login continuity, language preference, session protection, fraud checks, and basic performance measurement. We also use mobile browser storage so iOS access can stay practical without a separate installed package, while Android users can manage app-related storage and notification permissions through their device settings.

We use essential cookies to keep account sessions stable and secure.
We use preference records to remember language, display, and device choices.
We use security logs to review unusual login, payment, or account recovery activity.
We use support history to answer follow-up questions with proper context.

Our sso77 privacy rights, retention, and contact policy

We give you the right to ask about the personal data we hold, request correction of inaccurate details, and ask for deletion where our legal, payment, and dispute duties allow it. We may keep some records when we need them for KYC review, payment reconciliation, account protection, or unresolved support questions.

We protect account data with standard security practices, access controls, staff handling rules, and review procedures. We do not promise standard security practices or standard security practices, because no online service can honestly make that claim. We focus on reasonable safeguards, careful document handling, and clear support records.

We may send account messages about login activity, payment status, document requests, or support replies. We may also send service notices related to sso77 mobile access, push-notification settings, or browser compatibility. You can manage some notification choices on your phone, and you can contact support if an account message looks incorrect.

We recognise local context when reviewing payment and support records. Our team may see references to DANA e-walletSurabaya, Bandung, Medan, Idul Fitri, Idul Adha, Imlek, Piala Indonesia, or Piala AFF as part of a normal account history, but we use those references only for operational review and support context.

Our contact channel can receive privacy, KYC, payment, and account recovery questions.
Our response windows depend on document quality, queue conditions, and processor review.
Our policy may change when our services, security practice, or legal duties change.

We write this privacy policy so you can understand how we handle data across sso77 mobile access, desktop access, payments, games, support, and jurisdiction review. If any privacy point is unclear, we encourage you to contact our support team before sharing additional information.