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

# Usage Rights

## Overview

This section explains how Amondo sources, displays and manages content from third-party platforms in line with copyright law, platform terms and creator permissions. It covers how content can be lawfully displayed, what rights are required, how stored media complies with platform terms and the relevant developer policies that govern this.

Amondo respects the intellectual property and privacy rights of creators and partners. All content displayed through the platform is obtained through approved APIs or direct submissions and is handled within the limits of the permissions granted by the originating platform or content owner.

## Why usage rights matter

Amondo enables brands and organisations to publish authentic creator and user-generated content (UGC) across digital and physical environments. To do this responsibly, Amondo ensures:

* All content access complies with the platform’s API and developer terms
* Creator attribution is preserved where required
* Content is stored or cached only when permitted by platform policies
* Any content can be removed quickly if requested by the creator or rights holder

Usage Rights are therefore central to how Amondo operates, balancing campaign flexibility with legal and ethical compliance.

The following pages explain how Amondo lawfully accesses, uses and manages content from third-party platforms, covering display permissions, creator rights, storage practices and platform policies.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-sparkles">:sparkles:</i></td><td><strong>Why Amondo can display content</strong></td><td>Explains how Amondo lawfully displays public content obtained through approved platform APIs.</td><td><a href="/pages/AlXWCZhnUFEygOdF4WnR">/pages/AlXWCZhnUFEygOdF4WnR</a></td></tr><tr><td><i class="fa-shield">:shield:</i></td><td><strong>Permissions &#x26; Rights</strong></td><td>Outlines how permission is obtained to use creator and user-generated content across different channels.</td><td><a href="/pages/QNcjSIOxKSfAHQVqzGjt">/pages/QNcjSIOxKSfAHQVqzGjt</a></td></tr><tr><td><i class="fa-cabinet-filing">:cabinet-filing:</i></td><td><strong>Storage &#x26; Caching</strong></td><td>Describes how stored or cached media complies with platform terms and developer policies.</td><td><a href="/pages/oK5P5B75zrrtOwW99Z8L">/pages/oK5P5B75zrrtOwW99Z8L</a></td></tr><tr><td><i class="fa-books">:books:</i></td><td><strong>Platform Policies</strong></td><td>Summarises the key developer and content policies for supported platforms.</td><td><a href="/pages/EbjvwG3Nm1UARnd2YbxQ">/pages/EbjvwG3Nm1UARnd2YbxQ</a></td></tr></tbody></table>