> 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/operation/service-termination.md).
# Terminate the service
In Apps in Toss, the mini app service ends upon a partner company's voluntary request or in the event of a violation of laws or policies. Please review and strictly comply with the process, notice obligations, refund handling method, and post-termination screen handling by termination type below.
***
### 1. Service termination types
Service termination is classified into the following types.
| Type | Description | Advance notice obligation | Refund and account deletion handling |
| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ------------------------------------ |
| **Termination by partner company request** | When the partner company directly requests service termination | 30-day advance notice (Partner company → user) | Handled by partner company |
| **Termination due to policy/legal violation** | Immediate termination due to violation of policies and laws (including termination for failure to make improvements) | Notice for 30 days after termination (Partner company → user) | Handled by partner company |
| **Termination due to business closure** | Immediate termination due to business closure | Notice for 30 days after termination (Partner company → user) | Handled by partner company |
***
### 2. Process by termination type
#### 2-1.**Process for voluntary termination requests by partner company**
1. Apps in Toss [Channel Talk](https://apps-in-toss.channel.io/workflows/787658)Please let us know your intention to terminate the service through
2. The partner company must **send an in-mini-app advance notice and a functional message about service termination 30 days before termination**is required.
* The screen and functional message to be notified must include the scheduled service termination date and customer center contact information.
* After reflecting the relevant details, please contact us via Channel Talk.
{% hint style="info" %}
**Please be sure to check**
If you do not use Toss Login, you cannot send functional messages. Please make sure to provide a mandatory notice within the mini app so that users can see the termination notice when they access the service.
{% endhint %}
3. The partner company must promptly carry out refund requests for in-app purchases (or Toss Pay) and promptly comply with a user's deletion request.
* If a user requests account deletion and deletion of related information, it must be destroyed without delay.
* In-app purchase and Toss Pay refund requests must be processed without delay.
4. Please submit the termination request via Channel Talk on the service termination date.
5. Afterwards, the terms and conditions consent withdrawal related to the Apps in Toss console will be processed.
#### 2-2. **Termination for failure to make improvements due to policy/legal violation**
1. We will inform the partner company of the improvement period and service termination according to the violated policy.
2. If not carried out within the improvement period, a post-termination notice and functional message will be sent after service termination.
* The screen and functional message to be notified include **the service termination date, service termination reason, and customer center contact information**will be notified.
3. The partner company must promptly carry out refund requests for in-app purchases (or Toss Pay) and promptly comply with a user's deletion request.
* If a user requests service deletion and deletion of related information, it will be destroyed without delay.
* In-app purchase and Toss Pay refund requests will be processed without delay.
4. Afterwards, the terms and conditions consent withdrawal related to the Apps in Toss console will be processed.
#### 2-3. **Immediate termination due to violation of laws and regulations**
{% hint style="info" %}
**Please note**
In cases of serious violations such as violations of laws and regulations or infringement of intellectual property rights, the service will be taken down immediately without a grace period.
{% endhint %}
1. Upon confirmation of the violation, a post-termination notice and functional message will be sent immediately after service termination. (For 30 days after termination)
* The screen and functional message to be notified include **the service termination date, service termination reason, and customer center contact information**will be notified.
2. The partner company will be notified that the service has been terminated due to violation of relevant laws, and it can also be checked in the console.
3. The partner company must promptly carry out refund requests for in-app purchases (or Toss Pay) and promptly comply with a user's deletion request.
* If a user requests service deletion and deletion of related information, it will be destroyed without delay.
4. Afterwards, the terms and conditions consent withdrawal related to the Apps in Toss console will be processed.
#### 2-4. **Termination due to business closure**
1. If the business is closed, it becomes a non-business entity, so monetization features and Toss Login cannot be used.
2. Accordingly, if the timing of closure is confirmed, the mini app currently in operation will be automatically terminated.
3. If the service is terminated, the partner company must promptly carry out refund requests for in-app purchases (or Toss Pay) and promptly comply with a user's deletion request.
* If a user requests service deletion and deletion of related information, it will be destroyed without delay.
4. If you wish to launch the service as a non-business entity, please create a new workspace, register the mini app again, and then launch it.
***
### 3. Toss Pay and in-app purchase refund processing
#### 3-1. **Refund responsibility principle**
The refund obligations and responsibilities for Toss Pay and in-app purchases are **with the partner company**. In principle, Apps in Toss does not directly involve itself in refund processing.
* When notifying of service termination, clearly inform the partner company of its refund obligations.
* If a refund complaint arises, Apps in Toss may contact the partner company individually and request refund processing.
#### 3-2. **Google Play Store refund processing**
{% hint style="info" %}
**Please note**
Since whether a refund is possible (whether goods/services have been fully used) cannot be directly confirmed by Apps in Toss, please have the partner company handle it directly.
{% endhint %}
* Within **48 hours** case: A refund may be processed at Google Play Store's discretion.
* Within **After 48 hours** case: The partner company must directly approve or reject the refund in the Apps in Toss console.
#### **3-3. Apple App Store refund processing**
Refunds may be processed at Apple's App Store at its discretion without a separate deadline.
***
### 4. Toss Login
#### 4-1. **Toss Login handling**
* When accessing the service, show a screen that guides users to the account deletion channel. If a user requests service deletion and deletion of related information, destroy it without delay.
* Responsibility for related communications and issues with users lies with **with the partner company**the partner company.
***
### 5. Withdrawal of consent for Apps in Toss related terms
#### 5-1. **Withdrawal of consent**
* After service termination, **withdraw consent for feature-specific terms and service partnerships within the console**and operate accordingly.
* Since consent for terms is managed in the console by feature, such as Toss Login and in-app purchases, it will be withdrawn sequentially after termination.
***
### 6. User information handling guide when mini app service ends
After the mini app service ends, this guide explains the criteria for handling users' personal information provided by Toss and transaction information generated or collected independently by the partner.
This guide explains general processing principles. Please separately review the specific retention items and periods according to the partner's legal obligations and internal management plan.
#### 6-1. Toss identifier handling
The following identifiers received from Toss during mini app operation must be destroyed after the mini app service ends.
* `userKey`
* `anonKey`
* `deviceId`
If you need to continue identifying the user for transaction record retention, replace the value with the partner company's own user identification key.
After replacement is complete, delete the following information.
* Original identifier received from Toss
* Mapping information between the original identifier and the internal identifier key
* Information that can restore or re-link the original identifier
The internal identifier key must be generated independently of Toss identifiers and must not be reversible to a Toss identifier.
#### 6-2. Retention of name, phone number, and transaction information
Information of users whose transactions such as reservations and payments occurred may be retained only to the extent necessary if there is a retention obligation under relevant laws or other legitimate processing grounds such as separate consent for collection and use of the partner company's valuable personal information, terms of service, etc.
* Please separate and retain only the information necessary for transaction evidence.
* Please reflect the retained items and periods in the partner company's terms of use, consent form, privacy policy, and internal retention policy.
* Please destroy it without delay once the legal retention period has elapsed.
* User information for which no transaction occurred or for which there is no separate retention basis should be deleted after the service ends.
The retention period is not extended merely because the name and phone number were provided through Toss Login. \
The partner company must confirm whether there is a legitimate processing basis, such as an obligation under relevant laws or separate consent.
#### 6-3. Customer inquiries and transaction history management
After the mini app service ends, even if the partner company provides its converted internal identifier key to Toss, it will be difficult for Toss to look up or identify that user's transaction history.
Therefore, please prepare so that the following tasks can be handled independently by the partner company.
* View reservation and payment history
* Cancellation and refund handling
* User inquiries and complaint handling
* Submission of transaction records in accordance with legal obligations
It is recommended that necessary transaction information be managed based on the partner company's order number, reservation number, or internal user identification key rather than the Toss identifier.
#### 6-4. Processing procedure
1. Check the list of user information collected and generated in the mini app.
2. Classify personal information that must be retained under relevant laws (such as transaction records) and information to be deleted.
3. Replace the Toss identifier of records that need to be retained with the internal identifier key.
4. Delete the Toss original identifier and mapping information.
5. Delete personal information and operating logs that have no separate retention basis.
6. Personal information that must be retained under relevant laws should be separated from other information and access permissions should be restricted.
7. Record the destruction result and processing date in internal records.
#### 6-5. Final checklist
* `userKey`, `anonKey`, `deviceId`Have you replaced it with the internal identifier key?
* Did you delete the Toss original identifier and mapping information?
* Did you confirm the retention basis and period for transaction information?
* Did you delete user information with no transactions?
* Can you handle reservation, payment, and refund inquiries internally?
* Do you have a process in place to destroy information whose retention period has ended?
---
# 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/operation/service-termination.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.
