How can we help?

For questions about your AppWispr account, subscription, saved research, discovery runs, or generated mockups, sign in and use the support control available inside the workspace. Starting from the workspace keeps your request connected to the correct account and gives the support flow the context needed to investigate without asking you to publish private product research.

When reporting a problem, include what you were trying to do, the step where the result differed from what you expected, the approximate time, and any non-sensitive error message. Do not include your password, OAuth token, API key, full payment-card details, or confidential source material in a support message.

For setup, OAuth, supported coding assistants, tool behavior, or MCP troubleshooting, begin with the public MCP documentation. It includes connection commands, configuration examples, the authorization flow, tool descriptions, example prompts, and common recovery steps for Claude Code, Codex, Cursor, VS Code, and Windsurf.

If setup still fails, identify the client and version you are using, the exact setup stage that failed, and the non-sensitive portion of the response. Never paste access tokens or authorization codes into chat, a public issue, or a support request.

For access, correction, deletion, or another privacy request, review the Privacy Policy first and then use the signed-in support path so AppWispr can verify the account connected to the request. Subscription status, cancellation, invoices, and payment-method changes are managed through the billing controls shown in the product.

The public Privacy Policy and Terms of Service explain how AppWispr handles data, subscriptions, acceptable use, product outputs, and service limitations. Those pages are the best starting point for policy questions that do not require account-specific information.