Component Release QA Privacy Policy

Effective date: November 5, 2026.

Publisher and contact

Component Release QA is provided by the Figma Community creator kwjnn. Contact exportpreflightsupport@gmail.com, with “Component Release QA — Privacy” in the subject, for privacy questions.

Data processed in the plugin

When you select a local Component Set and run the plugin, it reads that set and its direct child Components. It processes their names, node IDs, variant axes, values, description availability, and the required combinations and quality settings you provide. Processing occurs locally within the Figma plugin environment. It does not scan the whole file or retrieve remote libraries.

Descriptions are reduced to present, missing, or unavailable indicators for checks; their full text is not stored in profiles or included in report messages. Node IDs are used for current reports and navigation. The plugin does not depend on a file ID as a persistent identifier and does not write plugin data into design nodes.

Profiles and retention

If you choose to save a profile, the plugin stores its schema version, generated profile ID, name, axis names, required combinations, and creation/update timestamps in Figma clientStorage. This is local storage associated with this Plugin ID on the device; the plugin provides no cloud backup, team sharing, or cross-device sync. Profiles do not include a persistent Figma file or node ID, optional Quality Rules, or complete QA reports.

Profiles remain until you delete them through Saved Profiles or the local Figma storage is cleared. Use Delete profile and confirm for each valid profile you want removed. Invalid or unsupported entries are excluded from use and kept in the original stored data to avoid destructive recovery. If such records prevent removal, contact support for help. The plugin enforces bounded profile storage. Changing Plugin ID may make older profiles inaccessible.

Unsaved requirements, current reports, and session settings are held in plugin memory. They are not uploaded by this plugin. Close the plugin to end the session; explicitly saved profiles remain.

CSV exports

When you request a permitted export, the UI generates a local CSV download containing inspection time, set name and node ID, result state, combinations, target node IDs, severity, messages, and rule IDs. The plugin does not upload that CSV. You control its save location, retention, deletion, and any later sharing. Exports can contain confidential design names and IDs, so review them before sharing.

Payments

The plugin uses Figma’s official Payments API to check purchase status and to open checkout only after you request it. Purchase-status flags from the UI are not accepted as proof of payment. The plugin does not receive or store your card number, bank information, or Stripe credentials and does not run a separate license or payment server. Figma and its payment providers process transactions according to their own terms and privacy policies.

Network access and third parties

The plugin’s manifest disables its own network access. It has no publisher-operated server, analytics SDK, telemetry, advertising, or external AI API, and it does not transmit design data to such services. This describes the plugin, not Figma’s host application or its official checkout, which may use their own network services and storage.

If you contact support, the email provider processes the information you voluntarily send. Do not include passwords, card information, or unnecessary confidential designs. Support correspondence is separate from in-plugin processing and may be retained as needed to handle your request and applicable obligations; contact us about access or deletion. The support mailbox uses Gmail.

The documentation pages have no analytics or tracking scripts added by this project. These documentation pages are hosted on Cloudflare Pages. Cloudflare receives ordinary web-request data under its own Privacy Policy; this is separate from plugin data.

Changes and requests

We will update this policy when the plugin’s data practices change. Contact the address above to ask about this plugin’s processing or support correspondence. Local profile and CSV deletion remain under your control as explained above.