> For the complete documentation index, see [llms.txt](https://doc.appflow.ai/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.appflow.ai/docs/get-started/faq.md). # FAQ Here you will find the most often questions *** **How much does Appflow\.ai cost?** It depends on which monthly subscription plan you decide to take. We have three set plans which range from $3.88 per 1K revenue to $6.88 per 1K revenue. We also have a more flexible subscription plan for those who require a more customized solution. Please contact us for more details regarding this type of plan. **Why is your pricing based on my revenue?** This is our way of keeping things fair. We want to make sure that all our customers are able to afford our product. If you use Appflow\.ai less in one month (and make less revenue), why should we expect you to pay the same as a boom month? Essentially, it’s a way to justify our pricing. **How safe is my data?** We’re committed to keeping your data safe, so never ever would we sell it, or do anything strange with it. That’s a guarantee. Your privacy is important and we really care about protecting it. AWS (Amazon Web Services) is our preferred choice for web hosting, so please rest assured that your data is in good hands. We also use SSL encryption and a lot more to prevent your data from leaking out to the world. --- # 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://doc.appflow.ai/docs/get-started/faq.md?ask=&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.