> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c167/q557.md).

# How do I get a refund for my subscription?

Refunds are provided on a discretionary basis. However, we understand that the service may not be what you are looking for.

If you subscribed from an iPhone or iPad, you can request a [refund directly from Apple](https://support.apple.com/en-au/118223).

If you subscribed from an Android device, please [email us](/manual/faq/c169/q575.md) from the email address that made the purchase and include the receipt number (it will start with "GPA," followed by a series of numbers).

If you subscribed from our web portal, please contact us from the email address that made the purchase.

{% hint style="info" %}
We can only search for your purchase with the email address or receipt number.
{% endhint %}

## Related

* [FAQ: What steps should I take if I can’t log in to the app to access the premium features?](/manual/faq/c160/c165/q542.md)
* [FAQ: How do I download invoices or receipts for my subscription payments?](/manual/faq/c167/q564.md)
* [FAQ: How do I cancel my subscription?](/manual/faq/c167/q555.md) 
* [FAQ: How do I contact support?](/manual/faq/c169/q575.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.reportandrun.com/manual/faq/c167/q557.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.