> For the complete documentation index, see [llms.txt](https://guide.finceptor.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.finceptor.app/refund-policies/secured-refund-policy.md).

# Secured Refund Policy

With the Secured Refund, claiming the TGE release does not mean the user has to claim the sale's vestings as well. Users can claim the TGE amounts and still refund the post-TGE vestings of the tokens. 

Typically, with the unconditional refund policy, claiming expires the refund option. However, with this secured refund policy, users can claim the TGE and refund the rest of the tokens, and get their USDTs back. 

{% hint style="success" %}
Say the X token has a 30% TGE unlock with 7-month vestings, and say user A deposited $1k into the IDO pool. 

* **Claim TGE, claim vesting**: The user must claim the TGE allocation within the refund period. Then, the user must not manually request a refund. Hence, no additional action is required if the user wants to claim the post-TGE vesting. 
* **Claim TGE, refund vesting:** The user must claim the TGE allocation and then request a refund within the refund period. The user must complete two actions: 1) Claim and 2) Refund, sequentially. 
* **Refund: If the user requests a refund, the user is not eligible for any token claims.** 
  {% endhint %}

{% hint style="danger" %}
Note that refunding the TGE release implies an automatic refund of the vestings.
{% endhint %}


---

# 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://guide.finceptor.app/refund-policies/secured-refund-policy.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.