Privacy by architecture
The plugin cannot send your design to the internet.
It reads the layers you select, converts them inside Figma, and returns code to you. There is no upload step, plugin backend, or external service in between.
Published manifest
The privacy claim is machine-enforced.
Figma uses the plugin manifest to control capabilities. This project declares an empty permissions array and setsnetworkAccess.allowedDomains to none.
{
"permissions": [],
"networkAccess": {
"allowedDomains": ["none"]
}
}The complete data flow
Your selection goes in. Code comes back.
The entire conversion is a short, closed loop inside Figma. No account is created and no design data is handed to another company.
01 · Read
You choose the layers
The plugin reads only the Figma selection needed to generate the requested output.
02 · Convert
Generation stays in Figma
Public TypeScript rules transform layout and style metadata inside the plugin runtime.
03 · Return
The result comes back to you
Preview, copy, or download the generated code and its local assets from the plugin interface.
Enterprise-friendly by design
There is no server to trust.
Figma enforces the published network boundary. If plugin code tries to call an API, upload data, or fetch an external resource, Figma blocks the request because no domains are allowed.
A smaller security review
- No upload endpoint
- No account or API token
- No telemetry or cloud storage
- Public manifest and source
Your organization's normal plugin approval policy still applies. The difference is that the privacy boundary is inspectable and enforced, not merely promised.
Read Figma's network rulesEnterprise and privacy FAQ
What security teams usually ask.
Direct answers for teams evaluating whether selected design data can leave Figma.
Source-backed trust
No policy page can replace inspectable architecture.
Review the manifest and generator, then try it on a selection.