DeepsyqStudio

TECHNICAL PRIVACY NOTICE

How AI media is handled

This page describes the current Deepsyq implementation on this feature branch. It is not a substitute for the final legal Privacy Policy or Terms that must be reviewed before public launch.

Before you press Generate

Selecting images or preparing a prompt does not by itself trigger AI generation. Check the model, references, and pricing in Studio before giving consent and pressing Generate.

When you generate

Studio sends the prompt and supported reference images to the AI service used by your selected model only after you check the consent box and accept the final confirmation. That confirmation shows the selected model and current credit estimate before a job starts. Deepsyq validates reference MIME type, file signature, base64 format, size and model-specific reference count on the server.

Provider API credentials stay on the server and are not sent to the browser.

What Deepsyq stores

Generation History stores job metadata such as your prompt, provider/model, status, timestamps, settings, credit information and recorded costs. Raw reference images are not written into the generation-job record.

Generated output is stored in configured S3-compatible object storage when that production storage is enabled. In the current gated fallback/pilot path, result bytes may instead be stored in PostgreSQL. Deepsyq does not rely on a temporary provider URL as permanent storage.

Deletion and retention

You can delete a completed result from Studio History when it is not still processing and does not have an unresolved credit reservation. Deleting a result removes Deepsyq's stored result data according to the active storage backend; copies you already downloaded are not affected.

No automatic server-side retention period is promised yet. A final retention schedule must be approved and configured before public commercial launch.

External AI providers

AI generation may send the prompt and approved references to the provider selected for that model, such as Google or BytePlus when those integrations are enabled. Final public Terms/Privacy must identify the providers actually launched and describe their processing and retention terms accurately.

Not collected by this workflow

Studio does not request unrestricted access to files on the device. Deepsyq receives only user-selected references submitted through supported generation workflows after Studio consent.