> 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/help-center-live-nl/accountbeheer/billing/refund-policy.md).

# Restitutiebeleid

Sesami bevat een proefperiode zodat je het product kunt evalueren voordat er kosten in rekening worden gebracht.

## Proefperiode

Wanneer je Sesami voor het eerst installeert en een abonnement kiest, ontvang je een **10-daagse gratis proefperiode**.

## Terugbetaling / geen kosten-scenario

Als je Sesami binnen de proefperiode verwijdert (binnen 10 dagen), worden er geen kosten voor het abonnement in rekening gebracht, omdat je in Sesami nog geen betaald abonnement hebt geselecteerd en Sesami je nog niet via de facturering van Shopify kan belasten!

{% hint style="info" %}
Als je vragen hebt over je specifieke facturatiesituatie (bijvoorbeeld de timing van de Shopify-factuur), neem dan contact op met de support van Sesami met de URL van je Shopify-winkel en de factuurdatum.
{% 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/help-center-live-nl/accountbeheer/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.