> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/fr/gestion-du-compte/billing/refund-policy.md).

# Politique de remboursement

Sesami inclut une période d’essai afin que vous puissiez évaluer le produit avant d’être facturé.

## Essai

Lorsque vous installez Sesami pour la première fois et choisissez un forfait, vous recevez un **essai gratuit de 10 jours**.

## Scénario de remboursement / sans frais

Si vous désinstallez Sesami pendant la période d’essai (dans les 10 jours), l’abonnement ne vous sera pas facturé, car vous n’avez pas sélectionné de forfait payant dans Sesami et Sesami ne peut pas encore vous facturer via la facturation Shopify !

{% hint style="info" %}
Si vous avez des questions sur votre situation de facturation spécifique (par exemple, le moment d’émission de la facture Shopify), contactez l’assistance Sesami avec l’URL de votre boutique Shopify et la date de la facture.
{% 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://help.sesami.co/fr/gestion-du-compte/billing/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.