Contact and Support
Use this page to report product issues, request integration support, or submit policy/privacy questions. For faster resolution, include task-level context so support can reproduce and diagnose the issue accurately.
Who this is for
Users who need technical support, integration help, or privacy/policy routing.
Support channels
- General support: [email protected]
- Privacy requests: [email protected]
- Abuse/policy reports: [email protected]
If these addresses are updated, this page is the source of truth.
How to submit a support request (step-by-step)
- Pick the correct channel: support, privacy, or policy.
- Include at least one task_id and a timestamp (UTC preferred).
- Describe expected vs actual behavior and what you tried.
- Attach screenshots only when they help explain the issue.
Issue categories
| Category | Examples | Priority | Recommended data to include |
|---|---|---|---|
| Pipeline failure | Task stuck, failed status, missing output | High | task_id, timestamp, prompt version, expected output path |
| Quality issue | Identity drift, artifacts, inconsistent style | Medium | task_id, reference usage, comparison screenshots, acceptance criteria |
| Integration support | Workflow setup, automation, batch usage | Medium | use case summary, expected throughput, environment details |
| Privacy/legal request | Deletion request, data-handling question, rights complaint | High | request type, account/project context, relevant task IDs, date range |
Required support request format
Requests without reproducible context are slower to resolve. Use this minimum format for all technical tickets.
| Field | Why it matters |
|---|---|
| task_id | Lets support inspect one exact pipeline execution |
| Timestamp (UTC preferred) | Correlates logs and event windows |
| Expected vs actual behavior | Clarifies success criteria and defect scope |
| Prompt summary (or version ID) | Enables controlled reproduction without exposing excess data |
| Reference image usage (yes/no) | Narrows root-cause analysis path |
Response timeline (target SLA)
| Request type | First response target | Status update cadence |
|---|---|---|
| Critical pipeline outage | Within 4 business hours | Every 4 hours until mitigated |
| Standard technical issue | Within 1 business day | Every 1 to 2 business days |
| Privacy request | Within 3 business days | Per legal/process requirement |
| General inquiry | Within 3 business days | As needed |
Before contacting support
- Check status panel and confirm task state and download readiness.
- Retry with one controlled prompt change if issue is quality-related.
- Gather task IDs and timestamps for at least one failed and one successful run.
- Attach only required files and avoid sharing unnecessary sensitive data.
Security and privacy note
Do not send raw personal data or sensitive media through unsecured channels. For deletion or privacy requests, use the dedicated privacy contact and include only the minimum required identifiers.
Common pitfalls
| Pitfall | What happens | Fix |
|---|---|---|
| Changing multiple things at once | Root cause becomes unclear | Change one variable per run |
| Overloaded prompts | Unstable style and artifacts | Use structured prompt blocks |
| Weak reference quality | Identity drift increases | Use clean, well-lit references |
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
What is the safest way to iterate?
Change one variable per run and keep a baseline prompt for comparison.
How do I improve consistency?
Use structured prompts and stable reference inputs when identity continuity matters.