Data Portability Application Guidelines

To ensure a successful submission to the Data Portability API Application, it is important that your requested data scopes are clearly necessary for your use case. You must also communicate this to users.

Before users log in with their TikTok credentials, they should be informed about what data will be used and how often data will be requested, if applicable.

After a user completes a request for data transfer, they should be able to access their data at any time and easily stop ongoing requests for data. TikTok recommends including transfer dates and a log of the received data content.

Your use case must follow the listed guidelines:

1. Give users clear choice and control
1. Outline the purpose of the data transfer request, requested scope, and frequency thereof.
2. Explain how the user's TikTok data will be used.
3. Give users the ability to disconnect, or stop data transfers at any time.
2. Explain to users how you will protect their data and comply with local laws or regulations
1. Provide links to your data retention policies or security practices.
2. Outline relevant information for compliance with local laws or regulations, including links to related tooling, such as how to make data subject access requests.
3. Make data portability request history available for users.

Example use cases

The following examples represent mockups that illustrate a clear connection between a user's in-app experience and the requested data scope. You must attach similar mockups to your application.

Back-up and sync

Data scope: portability.all.ongoing

Use case: Enable users to receive continuous and ongoing backup services.

Sync a user's profile across multiple platforms

Data scope: portability.postsandprofile.single

Use case: Enable users to achieve a one-time share of their profile information across platforms.