> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/guide/en/authentication/user-info.md).
# Connect User Information
Even if the user doesn’t enter it directly, you can safely fetch the necessary information from Toss. For example, when sending a package, you can retrieve the name, mobile number, and address stored in Toss after obtaining consent, without the user having to enter them one by one.
{% hint style="info" %}
**Please be sure to check**
* Retrieving user information **is a separate feature from Toss Login**You can use it even without Toss Login.
* To the user **Consent to provide personal information to third parties**Information is delivered only after receiving.
* You can register up to **5**items.
* It can be used without a separate server, and the SDK **v2.7.0** and later.
{% endhint %}
***
### 1. Access Retrieving User Information
Please go to the Retrieving User Information menu in the console.
* **How to access:** App in Toss Console → Select workspace → Select mini app → Left menu **'Retrieve user information'**
When you first access it, a blank screen with no registered information is displayed. `Register` button to start setting it up.
***
### 2. Set the consent notice display timing
Set the timing at which you request consent from the user to provide information. Please write the title according to the situation where user information is needed within the service.
**Consent screen title**
This is the title displayed on the consent screen. After the text you enter, **"when do you want to fetch the information needed?"** is automatically appended. For example, `to send a package`If you enter **"when sending a package, should we fetch the information needed?"** is displayed to the user.
**User information to retrieve**
Please select the user information to retrieve at that timing. The available items are as follows. User information is retrieved from the information in the Toss app → Settings → My Info · Address Management.
| Item | Description | Notes |
| --------------------------- | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Name | User name | |
| Gender | User gender | |
| Korean national / Foreigner | Whether the user is Korean or foreigner | |
| Date of birth | User date of birth | |
| Mobile number | User mobile number | |
| Address | User home address | Because it is not required when signing up for Toss, there may be no value, and in that case it is delivered as null. |
| Email address | User email address | Because it is not required when signing up for Toss, there may be no value, and in that case it is delivered as null. |
**Add display timing**
If there are multiple points in the service where user information is needed, `Add display timing` you can add timings with the button. Up to **5**can be registered. You can set different user information to retrieve for each timing. For example, when sending a package you can request name, mobile number, and address, and when verifying identity you can request only name and date of birth.
***
### 3. Check the consent notice content
The consent notice shown to the user is **Consent to provide personal information to third parties** automatically generated in the format. The consent notice content is automatically composed according to the selected user information items. `View` You can preview the full consent notice by pressing the button.
***
### 4. Set up callback (optional)
If the user withdraws from the mini app, the withdrawal event is sent to the registered callback URL. After receiving the event, please destroy that user's information.
{% hint style="info" %}
Callback is optional. To use a callback, set the toggle to **ON**.
{% endhint %}
**Callback URL**
Enter the URL that will receive the withdrawal event.
**HTTP method**
Select the HTTP method to use when calling the callback: **GET** or **POST** .
**Basic Auth header**
This is the authentication information included in the HTTP header when making the callback request. `Authorization: Basic {entered value}` format.
**Callback test**
Before saving the settings, `Test` button to check whether the callback works properly. You can save only after the test succeeds.
***
### 5. Registration complete and copy code
Once registration is complete, for each display timing `cud_`unique code starting with (`consentedUserDataKey`) is generated. This code is used when retrieving user information in the SDK. Please copy the code by pressing the copy icon.
After registration, you can see the display timing, user information to retrieve, and code at a glance on the consent notice information screen. `Edit` You can change the settings with the button.
***
### 6. Withdraw
Consented consent notices can be withdrawn via the path below. Individual withdrawal is possible.
* **How to withdraw:** Toss app → Settings → Terms and privacy policy consent → Mini app name
***
### Integrate development
> User information >
>
> You can retrieve user information through the SDK.
---
# 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://developers-apps-in-toss.toss.im/guide/en/authentication/user-info.md?ask=&goal=
```
`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.