---
metadata:
  - name: generator
    content: Diplodoc Platform v5.52.0
alternate:
  - https://yandex.com/dev/games/doc/en/sdk/construct-3/authorization-and-data.md
  - https://yandex.com/dev/games/doc/hi/sdk/construct-3/authorization-and-data.md
  - https://yandex.com/dev/games/doc/ko/sdk/construct-3/authorization-and-data.md
  - https://yandex.com/dev/games/doc/ru/sdk/construct-3/authorization-and-data.md
  - https://yandex.com/dev/games/doc/tr/sdk/construct-3/authorization-and-data.md
  - https://yandex.com/dev/games/doc/vi/sdk/construct-3/authorization-and-data.md
  - https://yandex.com/dev/games/doc/zh/sdk/construct-3/authorization-and-data.md
  - href: en/sdk/construct-3/authorization-and-data.md
    type: text/markdown
    title: Markdown version
  - href: ../../llms.txt
    type: text/markdown
    title: llms.txt
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com/dev/games/doc/en/llms.txt

# Authorization and player data

<!-- source: en/_includes/script-common.md -->
<!-- source: en/_includes/script/index-js.md -->

<!-- endsource: en/_includes/script/index-js.md -->

<!-- source: en/_includes/script/requirements-js.md -->

<!-- endsource: en/_includes/script/requirements-js.md -->

<!-- source: en/_includes/script/image-modal-js.md -->

<!-- endsource: en/_includes/script/image-modal-js.md -->
<!-- endsource: en/_includes/script-common.md -->

You can save game state data (completed levels, experience, in-app purchases, etc.) on the Yandex server or send it to your own server. You can also personalize the game using some data from the user's Yandex profile, such as their name.



## Player information {#player-info}

To start working with player data, use the **Fetch player info** action together with the trigger conditions **Player info is successfully fetched** and **Failure to fetch player info**.

To get player data use:

- **Player is authorized** condition: Checks if the player is authorized in Yandex.
- **Player personal info access granted** condition: Checks if the player's personal data has been obtained.
- **Player signature** expression: A `string` containing user data from the Yandex profile and a signature. Consists of two strings encoded in `Base64` format.
- **Player avatar** expression: A `string`, link to the player's avatar.
- **Player name** expression: A `string`, the player's name.
- **Player paying status** expression: A `string`, the user's payment activity status on the platform.
- **Player unique id** expression: A `string`, the player's unique identifier.

![Player Authorization Example](../../_images/construct-3/authorization-and-data/fetch-player-info.webp)



## In-game data {#ingame-data}

To work with the user's in-game data, use these actions:

- **Get player data** — requests the user's in-game data and writes it to a JSON object.
- **Set player data** — sends the user's in-game data from a JSON object to Yandex Games.
- **Get player stats** — requests the user's numerical data and writes it to a JSON object.
- **Set player stats** — sends the user's numerical data from a JSON object to Yandex Games.
- **Increment player stats** — increases the user's numerical data by the specified value.

![](../../_images/construct-3/authorization-and-data/player-data.webp)

{% note warning %}

All these actions are asynchronous and their execution takes some time. Remember to use the **Wait for previous actions** action to avoid errors.

{% endnote %}


---


<!-- source: en/_includes/button-git.md -->
<a href="https://github.com/yandex-games-plugins/construct3">
  <span class="button">Repository</span>
</a>
<!-- endsource: en/_includes/button-git.md -->