Account + creditsSign-in, balance, and generation records
Tell us whether the issue happened before sign-in, during the return to the editor, at generation, or after a result was saved. If credits appear incorrect, include the project and approximate time. A successful edit uses 3 credits; failed, timed-out, blocked, and duplicate requests should use 0.
BillingPurchases and payment status
Include the account email and payment date. Never send full card details. We may ask for a payment reference that does not expose the card number. Real purchases are not part of routine product testing and require the account holder's authorization.
Privacy + deletionData questions and account requests
State whether the request concerns a specific upload, generated result, project, or the entire account. We may need to verify account ownership before changing or deleting private records. See the Privacy Policy for the current handling terms.
Product feedbackResults that need a clearer workflow
Describe the task, source type, prompt, and the detail that changed unexpectedly. If you can share an image safely, remove confidential information first. Feedback about edges, text, identity, product geometry, or marked refinement helps us improve the instructions and interface.