All Collections
Communications
Disclaimers for Affiliate Program content
Disclaimers for Affiliate Program content
n
Written by nick graveline
Updated over a week ago

To ensure CEX.IO Affiliates remain sources of accurate information for potential participants, we ask program members to include our product disclaimers in all posted content.

As trusted guides, it’s our responsibility to equip users with all the tools they need to make informed choices along their crypto journey. These quick reminders can help new users make clear-eyed decisions about their first transaction.

Going forward, please include the following disclaimers where appropriate for all Affiliate Program content:

General disclaimer for blog posts and product reviews:

The availability of the products, features, and services on the CEX.IO platform is subject to jurisdictional limitations. CEX.IO may not offer certain products, features, and services on the CEX.IO platform in certain jurisdictions due to potential or actual regulatory restrictions. For more information, see our Licenses and Registrations.

Promotional content:

Don’t invest unless you’re prepared to lose all the money you invest. This is a high-risk investment and you should not expect to be protected if something goes wrong. Take 2 mins to learn more.

Social media posts and comments:

For information purposes only. Not investment or financial advice. Seek professional advice. Digital assets involve risk. Do your own research.

Exchange Plus:

Exchange Plus is currently not available in the U.S. Check the list of supported jurisdictions here.

CEX.IO Staking:

CEX.IO Staking is currently not available in the U.S. Check the list of supported jurisdictions here.

CEX.IO Savings:

CEX.IO Savings is currently not available in the U.S. Check the list of supported jurisdictions here.

We appreciate your help educating our growing community about the potential risks that arise in the crypto space. If you have any questions about our disclaimer policy, please contact affiliates@cex.io.

Did this answer your question?