> For the complete documentation index, see [llms.txt](https://docs.finceptor.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finceptor.app/about/features/capital-protection.md). # Capital Protection ### Refund Policies for IDOs Investors can ask 100% refund following the TGE unconditionally and on an individual basis. Investors have the flexibility to request a full refund within a specified timeframe. However, at any time, if they claim the purchased tokens, there’ll be no refund option. Unclaimed tokens after the refund period will be regarded as claims. * **24-hour Unconditional Refund** * **48-hour Unconditional Refund** ### Refund Policies for Liquidity Vaults As LVs are locked and liquidity-only financing tools, any break in the LV deal terms, such as timely token launch and malicious behaviors on top of the previous clauses, will result in investor refunds to protect capital deployers from inefficient use of capital. * **When the deadline for TGE has passed:** Investors can ask for a refund up to 30 days after the deadline for the TGE date passes. After the first 30 days, all the funds generated in the LV will be used as liquidity. * **Malicious Acts:** Finceptor retains the right to initiate a refund process at any given moment before the TGE should there be a harmful or gravely problematic incident related to a project, particularly in instances of liquidity financing policy violations. If a protocol fails to meet these stringent conditions, eligible users are welcome to submit a refund request. It should be noted that Finceptor reserves the right to modify this policy at any point to better protect our investors and to adapt to the ever-evolving market environment. --- # 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.finceptor.app/about/features/capital-protection.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.