Help & security

Frequently asked questions

Quick answers about quota, privacy, account access, and common generation problems.

Common questions

Clear answers for the decisions that affect privacy, usage, and security.

No. A new image stays private in your account. It appears in the community gallery only after you publish it.

Web quota limits daily generations from the site. API quota is a separate lifetime allowance for authenticated API requests.

Check whether another request is still pending, your daily quota is exhausted, or your email needs verification. The Created images page shows pending work and remaining usage.

No. Edit image creates a new child result using the original prompt and image as references. The original remains unchanged.

API quota is charged only after generation succeeds. Invalid input, rejected content, exhausted quota, and provider failures are not charged.

Open the failed image to read its safe error message, then retry. Adjust the prompt or reference image if validation or content review rejected the request.

Verify your email, use a unique password or passkey, enable two-factor authentication, and store recovery codes offline.

The old token stops working immediately. Your quota, request statistics, and logs remain attached to the same key record.

Still need help?

Open the relevant image or request log first. Its current status and safe error message usually identify the next step.

Ready for the next step?

Put the guide into practice, or continue with the next topic when you need a deeper workflow.