> For the complete documentation index, see [llms.txt](https://docs.trendswap.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trendswap.app/trust/privacy-and-retention.md). # privacy and retention User trust and data minimization are core architectural principles at TrendSwap. We treat user portraits and likeness data with the highest standards of confidentiality. *** ## Ephemeral Storage & 30-Day Auto-Purge * **Temporary Processing Only**: Uploaded portraits and synthesized video MP4 files are stored in private Cloudflare R2 object storage buckets exclusively to allow user review and download. * **Automatic 30-Day Purge**: All uploaded photos and completed video files are subject to an automated lifecycle deletion rule. Thirty (30) days after creation, assets are permanently and irrecoverably erased from our storage infrastructure. * **On-Demand Immediate Deletion**: Users can manually delete any generated video or uploaded photo at any time from their **My Creations** library, triggering immediate permanent deletion. *** ## Model Training Guarantee **TrendSwap NEVER trains foundation AI models on user photos.** * Uploaded portraits are utilized exclusively as inference inputs for your specific requested video take. * User data is never fed into public training corpora, fine-tuning datasets, or open-source image checkpoints. --- # 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://docs.trendswap.app/trust/privacy-and-retention.md?ask=&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.