> For the complete documentation index, see [llms.txt](https://help.flycode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flycode.com/subscription-compliance.md).

# Subscription Compliance

Subscription compliance for recurring billing: the FTC Click-to-Cancel rule and its status, ROSCA and state auto-renewal laws, dark patterns, a quick cancellation-flow test, consent records and monito

Regulators in the US, EU and UK have tightened the rules on how subscriptions are sold, renewed and cancelled. Getting it wrong means complaints, chargebacks and enforcement; getting it right also reduces voluntary churn, because a clean cancellation flow is one customers trust to come back to. This collection summarizes the rules and the records you need to keep. It is general information, not legal advice; confirm specifics with counsel.

{% hint style="info" %}
**Quick answer:** cancelling must be as easy as signing up, renewal terms and pricing must be disclosed clearly before consent, and you should store proof of that consent (timestamp, IP and the exact language shown). Dark patterns that delay or discourage cancellation are the main enforcement target.
{% endhint %}

## In this section

* [Regulatory Rules](https://help.flycode.com/subscription-compliance/regulatory-rules): the FTC Click-to-Cancel rule and its status, existing subscriptions, dark patterns, and a fast compliance test.
* [Legal & Tracking Requirements](https://help.flycode.com/subscription-compliance/legal-and-tracking-requirements): storing proof of consent and monitoring friction in the cancel flow.

## Related

* [What kind of legal terms should we have to enable backup payment methods?](https://help.flycode.com/backup-payment-methods/product-overview)
* [Is FlyCode outreach compliant with privacy and email laws?](https://help.flycode.com/failed-payment-outreach/delivery-strategy)
* [Card network retry rules for failed payments](https://docs.flycode.com/docs/read-more/card-network-retry-rules-for-failed-payments-visa-and-mastercard)
* [Failed payment recovery glossary](https://docs.flycode.com/docs/read-more/failed-payment-recovery-glossary)


---

# 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.flycode.com/subscription-compliance.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.