Last updated: February 9, 2026


Overview

LayerSweep is designed to process style information locally in your Figma environment. This policy explains what data the plugin accesses, what it stores, and what it does not do.

Data LayerSweep Accesses

When you run LayerSweep, the plugin may access information from the currently open Figma file, including:

This access is required to scan results accurately, perform swaps, and support layer navigation.

How Processing Works

LayerSweep processes scan and swap operations inside the Figma plugin runtime.

Data Stored by the Plugin

LayerSweep stores minimal preference/state data:

  1. In Figma clientStorage:
    1. Theme preference (auto, light, dark)
    2. Onboarding dismissal state
    3. Product tour progress
  2. Fallback in document shared plugin data:
    1. Product tour progress (only if client storage is unavailable)
  3. In UI local browser storage:
    1. Product tour progress cache used to keep UI state synchronized

LayerSweep does not automatically persist full scan results or full design content between sessions.

Exported Files

If you choose Export current scan, LayerSweep generates a JSON export on your side. That export is user-initiated and stored where you choose.

Third Parties and Tracking

LayerSweep does not:

If you contact support by email, any information you send is handled through your email provider.

Your controls

You can:

You can also remove local plugin state by clearing relevant Figma/client and browser storage for LayerSweep.

Changes to This Policy

This policy may be updated as LayerSweep evolves. The “Last updated” date reflects the latest revision.

Contact

Questions about privacy:

📧 [email protected]

About LayerSweep

How to Use

Privacy Policy

Changelog

Feedback