> For the complete documentation index, see [llms.txt](https://docs.goproxies.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goproxies.com/proxies/faq/billing-and-pricing/subscription-cancellation-refund-billing-cycles-and-quotas.md).
# Subscription Cancellation, Refund, Billing Cycles and Quotas
FAQ article explaining subcription cancellation, refund billing cycle and quotas processes
### Intro
This article explains how subscription cancellations work in GoProxies, outlines refund eligibility, and provides details on billing cycles and traffic quota management.
### Subscription cancellation
GoProxies handles subscriptions manually. If you wish to cancel your subscription, please contact our support or sales team via email, and our team will process your request promptly.
### Refunds
Refunds are generally applicable only if the client has not used the proxy service prior to requesting a refund. Requests for refunds after usage are evaluated on a case-by-case basis at GoProxies’ discretion.
### Billing Cycles
GoProxies subscriptions operate on a monthly billing cycle. Clients are billed monthly for their subscription, and renewal is automatic unless the subscription is canceled.
### Quotas
Each client’s subscription comes with a traffic quota:
**Monthly subscriptions:** Quotas reset at the start of each billing cycle. If a client exhausts their quota before the end of the month, they can top up to continue using the service. The self-service dashboard page includes an upgrade/top up button, which directs clients to contact support or sales to complete the process.
**Pay-as-you-go subscriptions:** Quotas are valid for 182.5 days from the time of purchase. Once the quota is used or the period expires, clients will need to top up to continue using the service.
\
---
# 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.goproxies.com/proxies/faq/billing-and-pricing/subscription-cancellation-refund-billing-cycles-and-quotas.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.
