> For the complete documentation index, see [llms.txt](https://privy-labs.gitbook.io/privy-labs-protocol-whitepaper-v-1.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://privy-labs.gitbook.io/privy-labs-protocol-whitepaper-v-1.0/the-core-technology/systems-overview/content-certificate-and-tracking-system/storage.md).

# Storage

Before a piece of content exfiltrates a Privy application with encrypted intention, it’s EXIF data is first sanitized prior to being split into uniform chunks. Each individual chunk is then encrypted per the encryption schema above and archived. The archive is then uploaded to [IPFS](https://ipfs.tech/), a distributed P2P storage network. Each upload yields a unique CID (content ID) from IPFS:

`bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi`

This CID is then publicly registered on CCTS as a pointer to an encrypted resource.

<br>