Data Portability - Frequently Asked Questions

Below are answers to some frequently asked questions. If you have a query not answered by the available resources or FAQs below, please reach out to the team directly at dataportability@meta.com.

Can the same application support multiple data types?

Yes, it can. Please use the drop down during onboarding to select the data types which your destination supports.

Will Meta have access to any data about my business or users?

No.

What should I do if I’m stuck while onboarding?

Reach out directly to the Meta data portability team (dataportability@meta.com) who will gladly assist.

I onboarded a couple of weeks ago but there are still no transfers coming from Meta. How can I find out what’s going on?

Reach out directly to the Meta data portability team (dataportability@meta.com) who will be able to check whether this is due to a lack of users wishing to make transfers or technical issues.

I received a message saying my request to onboard the Data transfer app has been rejected. I do not understand the reason for rejection. Could you please explain more?

Reach out directly to the Meta data portability team (dataportability@meta.com) who will be able to provide further details.

I created the data adapters and submitted a Pull Request (PR) with the open source master branch. How long does it take to merge my adapter code to open source?

This process typically takes 10 days.

How do I validate the data transfers to my destination before rolling it out to the public?

We suggest internal employee dogfooding of the service. Recruit your colleagues to create transfers and ensure the experience works. The key things to check for are: (1) data received matches request sent (e.g., data types, date range, data consistency, etc.), (2) requests are completed in a timely manner (e.g., there is no bottleneck anywhere) and (3) failure rates are minimal (e.g., less than 1%).

I do not have an API on my platform to create my data entities. How do I proceed?

Depending on which web technologies you use, there are many libraries and frameworks you can use to build out an API. When building an API we encourage the use of OAuth 2.0 to keep your endpoints secure. Whilst we cannot recommend particular technologies, there are many open source and commercial options available.

APIs on my platform, which allows creation of data entities, are not open to the public. Can I still use it for data transfer?

Yes.

What are the most common reasons why applications to onboard are denied?

• Inaccurate, incomplete or missing information from the application.
• Third party privacy policy does not include provisions on how users can exercise their data subject rights.
• Lack of a security reporting function for users.
• Third party privacy policy is not publicly available on applicant's site/app.
• Links provided in application do not work.