> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/faq/pricing/what-happens-when-a-site-reaches-its-cap.md).

# What happens when a site reaches its cap?

The alerts at 80% and 100%, the three rules to choose in advance, the default rule and what is invoiced.

Only the **Starter** (25,000 loads per month) and **Pro** (250,000 loads per month) plans have a cap. Essentials and Business have none.

## You are alerted at 80%, then at 100%

Sirdata sends you an email when a site reaches 80%, then 100% of its cap. The 80% email reminds you of the three possible rules, and of the one that applies without a choice from you: you have time to check yours in your account.

## At the cap, the rule you chose applies until the end of the month

You choose this rule **in advance**. When the cap is reached, it applies to the site until the end of the calendar month (UTC).

| Rule                                      | What happens until the end of the month                                                                                                                                                                 | What you pay for that month                                                                                                              |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| **Move to the higher plan**               | The site moves up one plan only: from Starter to Pro, or from Pro to Business. Its choice interface stays without the consent requests of Sirdata and its partners. A valid payment method is required. | The price of the plan subscribed to for the whole month, plus the price difference with the higher plan, pro rata to the remaining days. |
| **Move to Essentials** (default rule)     | The site moves to the Essentials plan: its choice interface stays displayed, records choices, and again presents the consent requests of Sirdata and its partners.                                      | The price of the plan subscribed to, for the whole month.                                                                                |
| **Suspend the service** (not recommended) | On that site, the tag no longer displays the choice interface and no longer records any choice.                                                                                                         | The price of the plan subscribed to, for the whole month.                                                                                |

**The following month, the site returns to the plan subscribed to**, whatever rule was applied.

{% hint style="warning" %}
**Without a choice from you, it is Essentials.** If you have chosen no rule, or if you chose the higher plan but your account has no valid payment method, the site moves to the Essentials plan until the end of the month. Your visitors then see the consent requests of Sirdata and its partners.
{% endhint %}

{% hint style="danger" %}
**Suspending means removing the choice interface from your site.** During the suspension, your site no longer collects its visitors' consent: if it uses trackers that require consent, it is no longer compliant. You remain solely responsible for the compliance of your sites.
{% endhint %}

## Example: moving to the higher plan

A Starter site reaches its cap with 10 days left in a 30-day month. The rule chosen is "Move to the higher plan". The site moves to Pro until the end of the month, and that month costs:

€9 + (€25 − €9) × 10/30 = €9.00 + €5.33 = **€14.33 excl. tax**.

On the 1st of the following month, the site returns to Starter.

For a Pro site that moves to Business, the price difference is also invoiced pro rata to the remaining days. As Business has no cap, the site has none until the end of the month.

## Choosing or changing your rule

* **When you sign up** for a Starter or Pro plan, choosing the rule is required, and no rule is ticked in advance.
* **Then, at any time**, in your Sirdata account: page [Sirdata products](https://account.sirdata.io/sirdata-products), block **Your ABconsent plan**, field **At the load cap**. Choose the rule, then click **Save the rules**.

The rule applies to your account: it applies to each of its sites that reaches its cap. The rule saved when the cap is reached is the one that applies.

If a site reaches its cap every month, you can also change its plan: see [Can I change plans?](/en/faq/pricing/can-i-change-plans.md)

Another setting, **On an unpaid invoice**, decides what happens when a payment fails: see [Invoicing and payment](/en/faq/pricing/invoicing-and-payment.md).

{% hint style="info" %}
**Account opened before 1 November 2026:** the plan applies to the whole account. The cap then covers the loads of all its sites, and the rule applies to the whole account.
{% 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://cmp.docs.sirdata.net/en/faq/pricing/what-happens-when-a-site-reaches-its-cap.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.
