Is Figma safe?
Figma embeds an OAuth client secret and uses it when refreshing tokens with api.figma.com.
After login, the extension reads a stored refresh token and sends it to api.figma.com/v1/oauth/refresh with a Basic Authorization header built from an embedded client ID and client secret. It stores the returned access token locally and uses bearer tokens for Figma API requests such as recent files, search, file metadata, file creation, and account details.
Who publishes itFigma, Inc. - no other listings under this identity, 1 shared hostname
Figma, Inc. - no other listings under this identity, 1 shared hostname
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
What Figma can do
Permissions this extension asks for, as declared in version 1.3.8. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to. The current listed version is 1.3.27, which we have not unpacked yet.
Read and change your data on t-boweisvde9h9.us-west-2.experiments.sagemaker.aws
*://t-boweisvde9h9.us-west-2.experiments.sagemaker.aws/*
Store data in your browser
storage
Sign you in with your Google account
identity
See the address and title of every tab you have open
tabs
Run its own code inside the pages you visit
scripting
Figma version history
1.3.8
Mar 4, 2026
1.3.24
Jul 17, 2026
1.3.25
Sep 22, 2026
1.3.27
Oct 14, 2026
Where Figma sends data
- api.figma.com
Found in its code · only this extension
Chrome Web Store listing
- Versions
- 1.3.27 latest of 4 seen since March 4, 2026
- Store rating
- 4.2 from 85 ratings
- Last updated
- July 15, 2026
- Size
- 3.73 MiB
- Privacy policy
- www.figma.com
