> 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/storage-and-caching.md).

# Storage & Caching

## Overview

Amondo stores and caches content from supported third-party platforms in accordance with each platform's developer and API terms. This ensures that any data or media accessed via Amondo's integrations is handled lawfully, securely and within the limits of the rights granted by the originating platform.

Where a platform does not permit storage or caching, Amondo displays content using the platform’s official embed player or other approved integration.

## Storage

Amondo uses trusted cloud-based services for secure storage and delivery of media and data:

* **Cloudinary** for image and video management and delivery.
* **Amazon Web Services (AWS)** (RDS, Ireland) for textual and metadata storage.

All data is encrypted and hosted within the European Economic Area (EEA), unless otherwise permitted by GDPR-compliant transfer mechanisms.

## Compliance with platform terms

Amondo stores or caches content only where permitted under the applicable platform’s API and developer terms. The following outlines general compliance by platform:

| Platform             | Storage/Caching Allowed | Method of Display                                                                                    | Reference                                                                                                                                    |
| -------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **X (Twitter)**      | Allowed                 | Cached and displayed with attribution                                                                | [Developer Agreement, Section B2](https://developer.twitter.com/en/developer-terms/agreement-and-policy.html)                                |
| **Facebook (Meta)**  | Allowed                 | Cached and displayed with attribution                                                                | [Meta Platform Terms, Section 3](https://developers.facebook.com/terms)                                                                      |
| **Instagram (Meta)** | Allowed                 | Cached and displayed with attribution                                                                | [Instagram Platform Policy, Section A](https://help.instagram.com/325135857663734)                                                           |
| **YouTube**          | Not allowed             | Displayed via the [YouTube Embedded Player](https://developers.google.com/youtube/player_parameters) | [YouTube Developer Policies, Section E](https://developers.google.com/youtube/terms/developer-policies#e.-handling-youtube-data-and-content) |
| **TikTok**           | Not allowed             | Displayed via the [TikTok Embedded Player](https://developers.tiktok.com/doc/Embed)                  | [TikTok Developer Terms of Service, Section II](https://www.tiktok.com/legal/tik-tok-developer-terms-of-service?lang=en)                     |

## Why Amondo stores rather than embeds

For platforms that permit caching, storing content rather than embedding provides several advantages:

* **Compliance:** Most supported platforms explicitly allow caching within their developer terms when content is accessed via their APIs.
* **Consistency:** Embeds differ visually and functionally between platforms, preventing a cohesive display experience.
* **Performance:** Caching improves page rendering speed and reduces unnecessary network calls.
* **Reliability:** Embeds are dependent on platform-side UI changes, which can break or degrade display performance.
* **Accessibility:** Cached content ensures users see consistent layouts and performance across devices.

## Content removal and expiry

Amondo’s systems automatically remove or refresh cached content in accordance with platform requirements. When a post is deleted or restricted on the source platform, it is also removed from Amondo. This ensures continued compliance with platform policies and user rights.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.amondo.com/trust-and-compliance/usage-rights/storage-and-caching.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.