Starvegas account security and identity checks

These are related safeguards, but they answer different questions. Account security concerns access to an account and the handling of information; identity verification checks who the account holder is and whether the account can be used under the stated requirements.

That distinction matters because a completed identity check is not the same as protection against unauthorised access. Nor does a security measure such as encrypted data transmission, by itself, confirm a player’s identity.

In the Starvegas casino account context, the recorded requirements point to three separate layers: verification, information protection and safer-play controls. Their practical effects differ, even when all contribute to a more controlled account environment.

Starvegas separates account protection from identity checks

Identity verification is a customer and account-control process. Full account use requires KYC within 30 days of registration, verification is required before withdrawal, and the stated pre-verification deposit cap is CHF 1,000 over 30 days. Accepted evidence includes a passport, ID card, driving licence or specified residence permits, alongside proof that a deposit or payment account is in the player’s name.

Account security is broader than that document check. The supplied details identify SSL encryption and PCI DSS as payment security measures, while the data controller is Casino Interlaken AG. Cookie consent is required for Strictly Necessary, Performance, Functional and Marketing Cookies. These measures relate to information handling and payment protection, not to proving that a person is the account holder.

• Identity verification establishes the account holder’s identity and supports account-use and withdrawal requirements.
• SSL encryption protects information as it is transmitted; it does not establish who is entering account credentials.
• PCI DSS relates to payment-card security rather than account identity.
• Safer-play controls set boundaries around gambling activity, rather than serving as login or identity checks.

The distinction also sets a limit on what can be inferred: the available account details do not specify two-factor authentication or another particular login-verification method. A player should therefore avoid treating KYC completion as proof that every possible account-access safeguard is present.

Verification has operational consequences

The verification deadlines and withdrawal condition make KYC consequential, not merely an optional privacy step. The 30-day period is tied to registration and full account use, while the separate before-withdrawal requirement means verification can matter again when a player seeks to receive funds. The permitted evidence also includes proof of payment accounts in the player’s own name, connecting identity review with the ownership of account-related payment methods.

That is distinct from data-protection rights. A person seeking to exercise data-subject rights can use email, phone or postal mail; the listed contact email is dataprotection@starvegas.ch. Verification asks for evidence about the player, whereas data-protection channels concern requests about personal information. Neither should be confused with a technical login control.

Safer play changes the conditions of participation

Safer-play tools operate on a different axis: they can limit or pause gambling activity without replacing identity checks or protecting login credentials. Available options include deposit and loss limits, gambling-activity statistics, a reality check and temporary withdrawal from play. A time-out may last from 24 hours up to six months; voluntary self-exclusion lasts at least three months and may be unlimited.

Once self-exclusion is active, account access is blocked, deposits and game participation are refused, and marketing material is not sent during the exclusion period. These consequences show the relationship between account controls and safer play: identity checks establish who is using the service, while participation controls determine whether play is permitted under a chosen restriction. They complement account security, but they are not interchangeable with it.