When you import a Figma prototype into Useberry for the first time, Figma presents an authorization screen:
Why does Useberry request this data?
This is due to the current design of the Figma API, which unfortunately does not allow granular permission scopes. As a result, the list of requested access may appear broader than what is actually used.
What access does Useberry have to my data?
Here’s a breakdown of what each permission means and how Useberry uses (or doesn’t use) the data:
- Read files you can access. Useberry only accesses the specific Figma file you explicitly import. We retrieve metadata such as top-level frame names and images necessary to enable testing. We do not fetch data from other files in your account.
- Read and modify comments for files you can access. This is a default scope provided by Figma. Useberry does not read, write, or interact with comments in any way.
- Read projects you can access. While this permission is requested by the API, Useberry does not access or process project-level data.
- Read components and styles you can access. While this permission is requested by the API, Useberry does not access or process components and styles.
- Read your name, email, and profile image. Same with the above, Useberry does not access or process your name, email, and profile image.
While the scopes requested may seem broad due to Figma’s API limitations, Useberry strictly accesses only what is needed from the file you import.
For transparency, here are the specific Figma REST API endpoints Useberry interacts with during file import:
Disconnect Useberry from Figma
If you ever wish to revoke Useberry’s access to your Figma account, you can easily do so through the Connected Apps section in your Figma settings. For more details, refer to the Figma documentation.
Comments
0 comments
Article is closed for comments.