Real product screenshots and brand assets may be uploaded to third-party image services
Source references: 2The workflow calls for real product screenshots, while the prompting guide recommends uploading product screenshots, brand assets, or style references to services such as Flux. Screenshots can expose customer records, internal features, test accounts, access tokens, or unreleased designs; brand files may also be confidential.
Without redaction, this material leaves the local environment and becomes subject to the provider’s retention, training, logging, and access policies, potentially exposing business or personal data.
There is a conditional data-disclosure risk: the skill recommends capturing real product screenshots, while its referenced guide explicitly recommends uploading product screenshots, brand assets, or style references to Flux. If that multi-reference workflow is used, those assets are processed by a third party. The source gives no instruction to inspect or redact customer data, tokens, internal features, or unreleased designs first. Users can ask for pre-upload review/redaction and an option limited to local or approved services.
1. **Capture real screenshots** of your product at 2x resolution2. **Frame in device mockups** — use browser frame, laptop, or phone templates3. **Add context** — callout arrows, feature labels, before/after comparisons4. **Annotate with code** — Hyperframes or HTML/CSS for programmatic overlaysShow 1 other places
- **Multi-image reference** is the killer feature — upload product screenshots, brand assets, or style references- Best for **brand consistency** across a set of images- Use Flux Pro for final assets, Flux Dev for rapid iteration- Flux Klein for high-volume batch generation (cheapest)- Style transfer via reference images > style keywords in prompt- Prompts can be shorter than other models — the references do heavy lifting