Support and complaints · prototype

Support categories without exposing private account data.

The production support flow is not connected yet. This page defines the categories and safe information boundary for account, payment, generation, and deletion help.

Account and login

Support should handle sign-in cancellation, failure, account-link attention, disconnect requests, and deletion questions without asking for OAuth codes, tokens, or passwords.

Payment and subscription

Cases should use internal order or subscription references when available. Users should never be asked to send card numbers, CVV, full webhook payloads, or sensitive payment data.

Generation and results

Support can investigate failed, rejected, timed-out, or undelivered jobs using job references and error classes rather than storing prompt text or photos in the support case.

Complaints and refunds

Refund, duplicate charge, cancellation, dispute, and policy complaints require a real intake channel and status tracking before launch.

Support intake prototype

Choose a category and use an internal reference where available. The form backend is intentionally not connected.