Security Model
Design data is customer data. Tokens are secrets.
Beam keeps credentials local by default, avoids writing secrets to project files, makes cloud sync explicit, and leaves enterprise controls for paid deployment boundaries.
Local credentials live in the user Beam directory and must never be committed. Tokens should not appear in logs, error messages, project config, debug bundles, or MCP responses.
Design data, rendered exports, assets, implementation briefs, and compare results are customer data. Beam Free keeps them local unless a future paid sync feature is explicitly enabled.
Enterprise controls are future product capabilities, not hidden defaults in the Free product. The local open-source workflow must remain transparent and cloud-optional.
Run Sequence
- Store Figma credentials only in the user Beam directory.
- Write project artifacts only under local
.beam/paths unless the user chooses another output directory. - Redact secrets from terminal output, logs, debug bundles, JSON responses, and MCP responses.
- Make cloud sync explicit when paid features exist.
- Use enterprise controls for organization policy, not hidden behavior in Free.
Expected Output
Security-sensitive commands should report what they changed without printing tokens. Debug and support outputs should identify redaction status and any customer-data opt-ins.
Files And Artifacts
- ~/.beam/credentials.json
- .beam/cache/
- .beam/debug/
- Agent MCP settings file
Next Step
Before sharing any debug bundle or snapshot, review whether it contains customer design data.
Recovery Paths
- If a token is printed or committed, rotate it immediately in Figma.
- If a debug bundle includes raw payloads accidentally, delete it and regenerate without raw data.
- If cloud sync is enabled later, provide deletion, retention, and export controls.
