> For the complete documentation index, see [llms.txt](https://docs.marketingtool.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marketingtool.pro/billing/subscriptions.md).

# Subscriptions

How subscriptions work on each platform

## Plans

Three plans — **Starter** ($29/mo), **Pro** ($59/mo), and **Growth** ($99/mo) — plus annual billing at a steep discount and a **$3 = 100 generations** top-up. Full details: [Plans & credits](/getting-started/plans-and-credits.md).

## On the web

Manage your plan from the [dashboard](https://app.marketingtool.pro/dashboard) — upgrades apply immediately.

## On iOS

Subscriptions are **in-app purchases handled by Apple**. Manage or cancel in **Settings → your name → Subscriptions** on your device. Apple bills you directly.

## On Android

Subscriptions are handled by **Google Play**. Manage or cancel in **Play Store → Profile → Payments & subscriptions**.

## One plan everywhere

Whichever platform you subscribe on, your plan applies to your whole account — web and both apps.

Subscribed on mobile but the app doesn't show it? Make sure you're signed in with the same account you subscribed with, then see [Troubleshooting](/product/troubleshooting.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.marketingtool.pro/billing/subscriptions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.