Privacy Policy (Operational Summary)
This page explains how AI Identity Seed Studio handles prompts, reference images, task metadata, and generated outputs. It is written as an operational summary to help users understand practical data handling boundaries.
Who this is for
Users who upload prompts or reference images and want to understand retention, access controls, and deletion requests.
Policy scope
This summary focuses on product-level handling principles. If a separate master legal policy applies in your organization, that document remains authoritative for binding terms.
How to submit a privacy request (step-by-step)
- Email [email protected] with your request type (deletion, access, clarification).
- Include relevant task_id values and timestamps to help locate data quickly.
- Do not include unnecessary sensitive data in the email body.
- Wait for identity/authorization verification before actions are taken.
Data categories we process
| Category | Examples | Why we process it |
|---|---|---|
| User inputs | Prompt text, optional reference images | To execute generation tasks requested by users |
| Task metadata | task_id, timestamps, status, output paths | To track pipeline execution and provide task lifecycle visibility |
| Generated outputs | Result image files and access URLs | To deliver requested generation results |
| Operational logs | Service events, error traces, access metadata | To operate, secure, and troubleshoot the platform |
Data use principles
- Use data only for requested task execution, service operations, and security.
- Collect the minimum needed for those purposes.
- Limit access to authorized roles with operational need.
- Apply retention and cleanup policies to reduce long-term exposure.
Retention and deletion principles
Retention should be time-bounded and purpose-limited. Data should not be stored indefinitely without operational or legal need.
| Data type | Retention principle | Deletion trigger |
|---|---|---|
| Reference uploads | Keep only for processing/review window | Window expiry or valid deletion request |
| Generated outputs | Keep per product and user expectations | Policy expiry or valid deletion request |
| Task metadata/logs | Keep minimal records needed for support/security | Log lifecycle policy expiry |
Access and security controls
- Scoped and time-limited signed URLs for media object upload/download.
- Role-based access for operational systems.
- Operational logging for incident review and audit support.
- Periodic review of privileged access paths.
User rights and requests
Users can request clarification, correction, or deletion handling based on applicable policy scope. To submit a request, contact [email protected] and include task IDs and timestamps where possible.
Requests are validated before action to protect account security and prevent unauthorized data operations.
Cross-border and third-party processing note
Service infrastructure may involve cloud providers and operational services. Where third-party infrastructure is used, handling follows contractual and security controls consistent with service operations.
Policy updates
We may update this summary as product behavior, legal requirements, or operational controls change. Material updates are reflected by revising the date on this page.
Common pitfalls
| Pitfall | What happens | Fix |
|---|---|---|
| Sharing signed URLs broadly | Uncontrolled access to media | Treat signed links as private; use short-lived access only |
| Uploading unnecessary sensitive content | Higher exposure and compliance risk | Upload only what is needed for the requested task |
| Missing task IDs in requests | Slower deletion/correction handling | Include relevant task_id values and timestamps |
When not to use this approach
Do not use this workflow for biometric verification, deceptive impersonation, or any use that violates rights, consent, or local law.
FAQ
How do I request deletion?
Email [email protected] and include task IDs and timestamps where possible.
Who should I contact for privacy questions?
Use [email protected]. For general support, use [email protected].
Are reference images sensitive?
Yes. Treat reference images and outputs as controlled content and share them only through approved channels.