> For the complete documentation index, see [llms.txt](https://docs.playnance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playnance.com/how-g-coin-works/connection-and-accounts.md).

# Connection & Accounts

***

### Account Access in Playnance

Playnance supports flexible connection methods designed to fit both Web2 and Web3 users.\
Users can access the ecosystem instantly without technical setup, while all activity remains securely executed on-chain.

There is no concept of a traditional centralized “account.”\
Instead, each user is connected to a blockchain-based identity through a non-custodial wallet.

***

### Supported Connection Methods

#### **Web3 Wallet Connection**

Users may connect using an existing self-custody wallet, such as:

* MetaMask
* Coinbase Wallet

This method allows direct interaction with the ecosystem using a personal wallet, without creating new credentials or sharing personal data.

***

#### **Social Login**

Users may connect using:

* Google
* Apple

When a user signs in via social login, Playnance automatically creates a non-custodial on-chain wallet linked to that identity.\
No wallet setup, seed phrase handling, or blockchain knowledge is required.

***

#### **Email Login**

Users may also connect using an email address.\
Upon first login, a non-custodial wallet is automatically generated and associated with the user.

This option is designed for users transitioning from Web2 into on-chain environments.

***

#### Non-Custodial Wallet Model

Regardless of how a user connects, Playnance operates on a non-custodial model.

Key principles:

* Wallets are created on-chain
* Private keys are owned by the user
* Playnance does not store or control user funds
* Assets can be withdrawn or managed at any time

This ensures full ownership without sacrificing usability.

***

#### One Identity Across the Ecosystem

Each user maintains a single on-chain identity **per login method** that:

* Persists across sessions
* Works across platforms powered by Playnance
* Records activity, rewards, and progress transparently

Users can later connect or migrate to a traditional Web3 wallet without losing access to assets or history.

***

#### ‏Login Methods & Wallet Identity

‏Each login method is treated as a separate identity and creates its own wallet the first time it is used.

‏If a user signs in with Google, the same wallet is reused every time Google is used.\
‏If the user later signs in using email, Apple, or another method, a different wallet is created.

**‏To access the same wallet and balance, users must always use the same login method they originally chose.**

{% hint style="info" %}
**‏Tip: Always use the same login method to access the same wallet and account.**
{% endhint %}

***

#### Security & Transparency

All connection flows are designed to:

* Prevent custody risk
* Eliminate centralized fund control
* Ensure on-chain verification of activity
* Maintain privacy and user autonomy

***

#### What to Read Next

To understand how economic activity works after connecting, continue with:

* **How G Coin Works**
* **Token Movement Basics**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.playnance.com/how-g-coin-works/connection-and-accounts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.