What the service processes
Diagnostic or security processing may temporarily include limited request parameters or upstream response fragments. Avoid submitting data that the task does not require.
Synchronous and asynchronous data
A synchronous request carries its content while the upstream model is processing it and returns the result on the same connection. An asynchronous request must persist enough task data to execute after the submitting connection ends. After completion, the result is associated with the task so the authenticated account can retrieve it. Move completed media to storage you control instead of treating the task API as permanent object storage.Retention periods are not fixed in this documentation
The current public policy does not promise one fixed number of days for prompts, source images, generated results, service metadata, diagnostic logs, or asynchronous task records. Retention depends on operational, billing, security, dispute, backup, and legal needs. A task execution timeout is not the same thing as a record or result retention period. If a procurement or compliance decision requires a contractual retention schedule, data residency, deletion deadline, or processor list, contact API support before sending production data.Reduce the data you expose
- Remove secrets, credentials, personal data, and confidential text that the generation does not need.
- Keep API keys on the server and separate development from production credentials.
- Do not write full Base64 content or Authorization headers to ordinary logs.
- Store the returned image in your own controlled system and keep only identifiers needed for support.
- Review the selected upstream provider’s current policies for the model and account type you use.
Secure API keys
Keep credentials out of browser-delivered code, logs, and screenshots.
Understand task storage
Persist your own task ID and copy completed output to controlled storage.