# IPFS encryption IPFS encryption safeguards the source files of every parent asset registered through the Interoperable Asset Store. When a studio or creator uploads a gaming asset, the files are encrypted locally before being stored on IPFS. This ensures that raw asset files, such as textures, meshes, animations, or models, cannot be accessed by unauthorized parties. The encrypted files are referenced in the parent asset’s metadata, creating a secure connection between the tokenized asset and its stored files. Only the owner of the parent asset can approve reuse proposals. Once reuse is approved, the protocol grants the integrating studio permission to decrypt the asset files through wallet-based access. A child asset does not contain its own file set. Instead, it maintains a parent-child link to the original parent asset, and the integrating studio uses the decrypted files to adapt the asset for their game. IPFS encryption ensures that creators retain control over their intellectual property while enabling secure and permission-based integration of assets across multiple games. --- # Agent Instructions: 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://infinity-games.gitbook.io/infinity-games-docs/interoperable-asset-store/key-concepts/ipfs-encryption.md?ask= ``` 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.