> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mythos.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Support policy

> How Mythos support works — the three ways to reach us, what support covers vs. what it does not, and the line between the platform and your code.

This page explains how to get help with Mythos and where the line sits between what the platform
supports and what it does not. The short version: Mythos supports **the platform** — building,
billing, publishing, and the workspace. It does not debug the external infrastructure you connect or
the code you take elsewhere.

<Note>**Reaching us is the same for everyone.** Three channels — **email**, **Telegram**, and the
**in-app support form** — all land in the same queue, and we reply within one business day. Pro adds
*priority* Telegram support and Ultra adds a *dedicated* Telegram channel plus a priority generation
queue, but access to support is not gated by pack. See [Credits & pricing](/introduction/credits-and-usage).</Note>

## How to reach us

There are three ways to get in touch — pick whichever fits, they all reach the same queue:

* **Email** — `support@mythos.new`. Best for billing questions, refunds, and anything that needs a
  paper trail.
* **Telegram** — [@mythos\_support](https://t.me/mythos_support). Fastest for bugs and quick questions.
* **In-app support form** — the **Help** page inside Mythos. Pick a topic (bug, billing, feature, other),
  write your message, and the reply lands in your account email.

We reply within **one business day** on every channel.

## How to get help

<Steps>
  <Step title="Check the docs first">
    Most issues — a refunded build, a blank preview, a form that does not save, stale published content,
    running low on credits — have a fix on the [Troubleshooting](/reference/troubleshooting) page.
  </Step>

  <Step title="Re-prompt for build failures">
    If a generation failed, you were refunded in full. Re-prompting often resolves a transient failure
    at no extra cost. See [Troubleshooting](/reference/troubleshooting).
  </Step>

  <Step title="Reach out if the docs don't cover it">
    Email, Telegram, or the in-app form — whichever fits. When reporting a bug, include what happened,
    what you expected, and any project IDs or URLs that help us reproduce it.
  </Step>
</Steps>

## What support covers

Support helps with the Mythos platform itself:

* **Billing and credits** — payments, the credit balance, refunds, and referrals.
* **Account and access** — sign-in, your dashboard, and account settings.
* **The build pipeline** — a generation that fails, refunds, or behaves unexpectedly.
* **Publishing** — getting a project live on its published URL.
* **The workspace** — the chat, the preview, and the built-in IDE.

## What support does not cover

Mythos supports the platform, not the external infrastructure you connect to it or the code you take
elsewhere. Out of scope:

* **Your connected Supabase project.** Apps are frontend-only by default and use
  **bring-your-own Supabase**. Debugging your own Supabase database, its data, its policies, or its
  migrations after you have connected it is your responsibility, not the platform's.
* **Your exported code.** Once you connect a GitHub account and export a project's code to your own
  repo, then run or change it outside Mythos, support does not debug that external setup.
* **Third-party services you wire in.** Anything you connect that is not part of Mythos is owned by you.
* **General coding help.** Support is for the platform, not for teaching or reviewing application code
  in the abstract.

<Note>The build agent will still **write** integration code for you inside Mythos — for example, wiring
a form to your connected Supabase. That is part of building. The boundary is about **debugging external
infrastructure after the fact**, not about whether the agent can generate the code in the first place.</Note>

## Plan & cost note

Support scope is not a feature tier — Mythos has no subscription tiers, and Pro and Ultra are the same
product at different volumes and per-credit rates. Everyone can reach support on all three channels.
The pack differences are **priority**, not access: **Pro** adds *priority* Telegram support; **Ultra**
adds a *dedicated* Telegram channel plus a **priority generation queue**. See
[Credits & pricing](/introduction/credits-and-usage).

## Refunds

Unused credits can be refunded in **USDT within 30 days of purchase** — reach out on Telegram
[@mythos\_support](https://t.me/mythos_support). Note this is separate from the automatic refund for a
*failed build*, which goes back to your balance immediately with no action needed.

## FAQ

<AccordionGroup>
  <Accordion title="How do I reach support?">
    Email `support@mythos.new`, message [@mythos\_support](https://t.me/mythos_support) on Telegram, or
    use the in-app support form on the **Help** page. All three land in the same queue and we reply
    within one business day.
  </Accordion>

  <Accordion title="Is support better on Pro or Ultra?">
    The channels are the same for everyone. Pro adds *priority* Telegram support; Ultra adds a
    *dedicated* Telegram channel and a priority generation queue. Access to support itself is not gated
    by pack.
  </Accordion>

  <Accordion title="Can I get a refund?">
    Unused credits can be refunded in USDT within 30 days of purchase — reach out on Telegram
    [@mythos\_support](https://t.me/mythos_support). A *failed build* is refunded automatically, with no
    request needed.
  </Accordion>

  <Accordion title="Will support fix my Supabase database?">
    No. Your connected Supabase project is your own infrastructure. Support covers the Mythos platform,
    not the data, policies, or migrations in a database you brought and connected.
  </Accordion>

  <Accordion title="Will support debug my code after I export it?">
    No. Once you connect a GitHub account and export a project to your own repo, then run or change it
    elsewhere, that external setup is yours to maintain. Support covers issues inside the platform.
  </Accordion>

  <Accordion title="My build failed — is that a support issue?">
    Usually not. A failed build is refunded in full automatically; re-prompting often fixes it. If
    builds fail repeatedly and re-prompting does not help, that is worth raising with support.
  </Accordion>
</AccordionGroup>

## Related

* [Troubleshooting](/reference/troubleshooting) — fixes for the most common issues.
* [Credits & pricing](/introduction/credits-and-usage) — pack comparison and support priority by pack.
* [Plan mode](/features/plan-mode) — shape a project for free before spending credits.