From 7b1b4b0efaf12fe5de3fdc9fa64b5b96c230f06e Mon Sep 17 00:00:00 2001 From: huangliling Date: Fri, 26 Jun 2026 10:05:08 +0800 Subject: [PATCH] docs: refund doc --- .../current.json | 4 + .../current/sdk/announcements/_category_.json | 5 + .../sdk/announcements/sunset-announcement.mdx | 50 ++++++++++ .../sdk/announcements/sunset-export.mdx | 99 +++++++++++++++++++ .../sdk/announcements/sunset-refund.mdx | 54 ++++++++++ 5 files changed, 212 insertions(+) create mode 100644 i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/_category_.json create mode 100644 i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-announcement.mdx create mode 100644 i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-export.mdx create mode 100644 i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-refund.mdx diff --git a/i18n/en/docusaurus-plugin-content-docs/current.json b/i18n/en/docusaurus-plugin-content-docs/current.json index d05e6f4..9bc5c7b 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current.json +++ b/i18n/en/docusaurus-plugin-content-docs/current.json @@ -49,6 +49,10 @@ "message": "Billboard", "description": "The label for category 公告系统 in sidebar sdk" }, + "sidebar.sdk.category.公告": { + "message": "Announcements", + "description": "The label for category 公告 in sidebar sdk" + }, "sidebar.sdk.category.排行榜": { "message": "Leaderboard", "description": "The label for category 排行榜 in sidebar sdk" diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/_category_.json new file mode 100644 index 0000000..96e4d19 --- /dev/null +++ b/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/_category_.json @@ -0,0 +1,5 @@ +{ + "label": "Announcements", + "collapsed": false, + "position": 0 +} diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-announcement.mdx b/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-announcement.mdx new file mode 100644 index 0000000..03450ae --- /dev/null +++ b/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-announcement.mdx @@ -0,0 +1,50 @@ +--- +title: Notice on the Discontinuation of LeanCloud Services +sidebar_label: Discontinuation Notice +sidebar_position: 0 +--- + +Dear LeanCloud users, + +Thank you for your trust and support of LeanCloud over the years. Since the platform launched, we have accompanied and witnessed the growth and innovation of countless developers, and we feel deeply honored to have shared these past ten-plus years with all of you. + +So that our team can focus on building better products, we have, after careful consideration, decided to gradually discontinue LeanCloud's services. + +To ensure a smooth transition for your business, we have established a one-year follow-up service and wind-down plan. The specific arrangements are as follows: + +### Feature Freeze + +Starting **January 12, 2026**: + +* New user registration will be suspended +* Creation of new applications (Apps) will be suspended + +Existing applications can continue to operate normally until services are officially discontinued. + +### Official Service Discontinuation Timeline + +Official service discontinuation date: one year from the date this notice is published, i.e., **January 12, 2027**. + +At that time, the platform will officially shut down all public-facing services, including application access, data read/write, API calls, and console usage. + +:::tip +In accordance with the Personal Information Protection Law and related laws and regulations, after services are discontinued we will, as required by law, permanently destroy or anonymize all user data retained on the platform. Once destroyed, the data cannot be recovered. +::: + +### Data Export and Migration + +To safeguard your data and ensure a smooth business transition, we have prepared a [Data Export and Migration Guide](/sdk/announcements/sunset-export). Please plan ahead according to your business needs and begin exporting and migrating your data as early as possible. + +### Balance Refunds + +If your account still has a remaining balance, you can apply for a refund yourself after completing the migration. Please refer to the [Refund Guide](/sdk/announcements/sunset-refund). + +### Acknowledgements + +Every step of LeanCloud's growth has been inseparable from your trust, your choice, and your companionship. Over the past ten-plus years, we thank every developer and enterprise user for using, giving feedback on, and co-creating with us. + +If you have any questions during the migration, please feel free to contact us at any time. + +Once again, our sincere thanks for your understanding and support! + +The LeanCloud Team diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-export.mdx b/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-export.mdx new file mode 100644 index 0000000..f49b7cc --- /dev/null +++ b/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-export.mdx @@ -0,0 +1,99 @@ +--- +title: Data Export and Migration Guide +sidebar_label: Data Export and Migration +sidebar_position: 1 +--- + +import { Conditional } from "/src/docComponents/conditional"; + +LeanCloud services will be discontinued and taken offline on January 12, 2027. To help you complete your data migration smoothly, we have prepared this guide to exporting and migrating your data. + +## Data Export + +### Data Storage + +Structured data storage offers several export mechanisms. In the console, go to "Data Storage" > "Import/Export," where you can perform "Data Export" and "Backup Export" separately. Specifically: + +* Data Export supports filtering by time range and provides an export file in JSON format; +* Backup Export provides a BSON-format file from that day's early-morning database backup, which can be imported directly into a MongoDB database with mongorestore. + + +
+ storage - export +
+ +In addition, you can export for migration via the REST API. We recommend using the Scan interface for traversal export. Please refer to the documentation [Iterating Over a +Class](/sdk/storage/guide/rest/#遍历-class). + +### Files + +File storage mainly consists of file metadata and file content. The file metadata is stored within structured data as the `_File` table, which you can export by referring to the [Data Storage](#data-storage) section above. + +After obtaining the file metadata, you can iterate over it to construct URLs in the form of the file domain `+ key`, and then download the file content. + +### Built-in Accounts + +Built-in accounts are stored within structured data as the `_User` table. They are exported in the same way as structured data storage; please refer to the section above. + +Note that the `password` field in the exported data is stored encrypted. For the encryption algorithm, please refer to the documentation [Encryption Algorithm for Exported User Data](/sdk/start/dashboard/#导出用户数据的加密算法). + +### Push Notifications + +Push notifications mainly consist of device information and push records. The device information is stored within structured data as the `_Installation` table, which you can export by referring to the [Data Storage](#data-storage) section above. + +Push records are retained only for the last 7 days and can be exported via the REST API. Please refer to [Querying Push Records](/sdk/push/guide/rest/#推送记录查询). + +### Instant Messaging + +Instant messaging mainly consists of conversation data and historical messages. The conversation data is stored within structured data as the `_Conversation` table, which you can export by referring to the [Data Storage](#data-storage) section above. + +Historical messages must be exported via the REST API. You can export [all historical messages in the app](/sdk/im/guide/rest/#查询应用内所有历史消息), or export the [historical messages of a specific conversation](/sdk/im/guide/rest/#查询历史消息-1). + + +### Cloud Engine + +Cloud Engine builds images using standard container technology, so you can rebuild and deploy your application on another container cloud platform. + +### LeanDB Hosted Database + +In the instance panel of the console, click the "..." button to export and download a database backup. + +### SMS + +You will need to re-register your signatures and templates with another SMS service provider. + +### Leaderboards + +Leaderboard rankings can be archived through the console, after which you can download the archived CSV to export them. + +If you need a leaderboard's hot data, you can perform a traversal export via the REST API. Please refer to [Querying a Leaderboard](/sdk/leaderboard/guide/rest/#查询排行榜). + +## Technical Support + +If you encounter any problems during data export and migration, you can contact us via a support ticket. + +## Recommended Alternatives + + + + +We recommend Tencent Cloud CloudBase as an alternative to LeanCloud. CloudBase offers capabilities similar to LeanCloud, including a database, cloud functions, cloud storage, and authentication, and it comes with a complete migration guide and intelligent migration scripts that support automatic data format conversion. For migration details, please refer to the +[Complete Guide to Migrating from LeanCloud to CloudBase](https://docs.cloudbase.net/quick-start/migration/leancloud). + +Migrating users can use an exclusive promo code to claim free cloud resources, [click to claim](https://buy.cloud.tencent.com/lowcode?buyType=tcb). + +For issues with redeeming the code or technical questions, you can join the group for assistance: +cloudbase-group + + + + + +We recommend [Google Firebase](https://firebase.google.com/) as your preferred alternative. If you prefer a self-hosted open-source solution to reduce costs, we recommend building and deploying [Parse Platform](https://github.com/parse-community/parse-server) yourself. + + + + +--- + +**Thank you again for your support of LeanCloud.** diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-refund.mdx b/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-refund.mdx new file mode 100644 index 0000000..6af02f9 --- /dev/null +++ b/i18n/en/docusaurus-plugin-content-docs/current/sdk/announcements/sunset-refund.mdx @@ -0,0 +1,54 @@ +--- +title: Refund Guide +sidebar_label: Refund Guide +sidebar_position: 2 +--- + +import { Conditional } from "/src/docComponents/conditional"; + +Once you have completed migrating and exporting your data and will no longer incur new charges, you can apply for a balance refund yourself. During this process, we will delete and reclaim all resources. After that, the data can no longer be recovered. + +### Refund Process + +Go to the console, click your avatar in the top-right corner, select "Account Settings," and choose "Service Discontinuation Refund" in the sidebar. + +* Before proceeding to the next step, please make sure you have completed migrating and exporting your data; +* Then click "Discontinue Service." **We will delete all applications and resources under your account** to avoid incurring further unnecessary charges; +* Because some billing items are delayed, you will need to wait 3 business days for all items to be settled; +* Click "Apply for Refund" and fill in the relevant refund bank information; +* Wait for the finance team's review. Once approved, the refund amount will arrive within 3 business days. + +### Balance Refund Principles + +* The order in which the balance is consumed follows the "first recharged, first consumed" principle, meaning the system uses the earliest received recharge amount first; refunds apply only to the most recently received recharge record in the current account that has not yet been fully consumed. +* Complimentary balances such as vouchers are not eligible for refunds. + +### Refund Methods + +:::tip +Because Alipay does not support refunds for historical recharges, refunds will be made uniformly to a bank account. +::: + +* For bank recharges, we will follow the principle of refunding along the original payment route. +* For recharges made via Alipay only: if recharged through a company account, the refund will be made to a bank account under the same company name; if recharged through a personal account, the refund will be made to a bank account under the same individual's name. +* If recharged via Stripe, please provide the Stripe paymentId of your most recent recharge and the account email for the refund. + + + +If the balance was recharged in an individual's name but needs to be refunded to a company account, you must provide a written refund statement ([download template](http://lc-OMMmeGjC.cn-n1.lcfile.com/xybvnxQsbtAdbMKpfyltUr0nGfMhihh7/%E9%80%80%E6%AC%BE%E8%AF%B4%E6%98%8E.docx)). The company receiving the refund must be the real-name-verified company of the account. + + + +### Invoice-Related Requirements + +If an invoice has already been issued for the recharge corresponding to the balance to be refunded, a red-letter (credit) invoice must be issued. In this case, the finance team will issue the red-letter invoice through the tax system. In the refund application form, the system will flag that invoice reversal confirmation is required and will provide the company entity of the invoice. Your company's finance team will need to confirm this online through the tax system. After confirming, click "Confirm" in the refund application form to notify us. The normal refund process can then proceed. + + + +**Cross-Border Recharge Refunds** + +If your company is a domestic (China-based) customer and previously paid service fees to our overseas entity through a domestic account, the relevant refund will be remitted by our overseas entity back to your company's domestic account along the original route. + +In accordance with the relevant national foreign exchange regulations, after receiving this cross-border refund, your company must promptly complete the foreign-related income declaration procedures through your bank. For the specific declaration process and required materials, please consult the account manager at your account-opening bank and proceed as instructed. + +