This policy explains what Fireporter does with data when you use the Figma plugin,
the Roblox Studio plugin, and optional online features such as Live Mode.
Overview
Fireporter is a tool for converting UI layouts from Figma into Roblox GUI instances.
We aim to collect only what is needed for the features you use, and to avoid selling
or monetizing your design data.
We do not sell personal data. We do not use advertising trackers
or analytics SDKs inside the plugins.
How Fireporter works
Fireporter has two main components:
Figma plugin — reads the layer(s) you select in Figma
(position, size, fills, effects, text, and related properties) and builds an export
(JSON and, when needed, image assets).
Roblox Studio plugin — builds matching UI instances in your open place
from export data (pasted JSON or Live Mode delivery).
Network activity
Default / paste export can be used without signing in. In that flow,
processing stays on your machine until you copy JSON yourself.
Live Mode and related online features (when you choose to use them)
communicate with Fireporter's backend and, when you connect a Roblox account,
with Roblox's APIs. Typical purposes include:
Roblox OAuth sign-in and token refresh
Delivering an export so Studio can import it
Uploading image assets to Roblox on your behalf when Live Mode / Auto Mode requires it
Enforcing temporary safety lockouts after certain moderation failures
Design payloads and images you export in these modes are sent only as needed to provide
that functionality. They are not used for advertising.
Data storage
On your device — the Figma plugin may store small preferences in
Figma clientStorage (for example session hints, lockout timers, or optional
"My Assets" images you upload for local reuse). That data stays in your Figma client
storage quota.
On our backend — when you use online features, we may temporarily store
export payloads, session/token metadata needed for Roblox OAuth, and short-lived
lockout records. Export staging data is time-limited and not kept as a permanent archive
of your designs.
Roblox — images uploaded through Live/Auto Mode are subject to Roblox's
own storage, moderation, and policies.
Accounts & tokens
Optional Roblox login uses Roblox OAuth. Access and refresh tokens are stored so Live Mode
can act on your behalf (for example uploading assets). You can log out from the plugin;
logging out clears the local session association used by Fireporter.
Fireporter does not ask for your Figma password. It uses the normal Figma plugin APIs
available inside the editor.
Images & moderation
When images are uploaded to Roblox, they are reviewed under Roblox's rules. If content is
rejected or an account is restricted for upload-related reasons, Fireporter may show an
error and may apply a temporary lockout so the feature cannot be abused.
You are responsible for ensuring that designs and assets you export are appropriate and
that you have the rights to use them.
Support tickets
The Support tab lets you open a support ticket instead of messaging on
Discord. Submitting a ticket sends the following to the developer by email, for the sole
purpose of responding to your request:
The category and subject you selected
The message you wrote
The email address you provide, so we can reply
Any files you choose to attach (screenshots, video, or Figma/Roblox files) — attachments are optional and only sent if you add them
Ticket content is delivered directly by email through our email-delivery provider and is
not stored in Fireporter's own database. Attachment size and file type are limited on the
client before anything is sent.
Third-party services
Depending on the features you use, Fireporter may rely on:
Figma — plugin host and client storage
Roblox — OAuth, asset upload, and Studio
Hosting providers — for the Fireporter backend (e.g. deployment and short-lived data stores)
Email delivery provider — used only to send support tickets you submit to the developer's inbox
Those providers process data under their own terms and privacy policies when you use the
related platforms.
Contact
Questions about this policy can be raised through the Fireporter Discord community or other
support channels listed in the plugin (Socials / Support tabs).
We may update this page when the product changes. The "Last updated" date at the top will
change when we do.