When you bring a new tool into your team's workflow, someone always asks the same question: "Where does our data go?"

With UX ContentHub, the answer is simple: it stays in Figma.

Everything lives in Figma Variables

UX ContentHub stores all your content — every string, every translation — directly inside Figma's native Variables system. That's Figma's own infrastructure, with Figma's own access controls and security policies.

Nothing leaves your Figma file. No content is processed outside of it.

This is a deliberate design choice — and like any architectural decision, it comes with its own constraints. For instance, the plugin can only access variables from the current file and its connected libraries. Variables from other files aren't visible. Rather than working around Figma's boundaries, UX ContentHub is built to make the most of them.

Your existing permissions already cover it

Because your content lives in Figma, it inherits the same access rules as your files. Your team's existing Figma permissions apply — no extra configuration, no additional layer to manage.

No separate compliance check needed

This is probably the most practical point for leads and stakeholders: if your organization has already approved Figma, UX ContentHub is already covered. There's no new vendor to evaluate, no data processing agreement to review, no additional security assessment to run.

If you're allowed to use Figma, you're allowed to use the plugin.