[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-05。"],[],[],null,["# Client-side encryption keys\n\nThis page discusses *client-side encryption* , which is any data encryption you\nperform prior to sending your data to Cloud Storage. For other encryption options,\nsee [Data Encryption Options](/storage/docs/encryption).\n\nWhen you perform client-side encryption, you must create and manage your own\nencryption keys, and you must use your own tools to encrypt data prior to\nsending it to Cloud Storage. Data that you encrypt on the client side arrives\nat Cloud Storage in an encrypted state, and Cloud Storage has no knowledge\nof the keys you used to encrypt the data.\n\nWhen Cloud Storage receives your data, it is encrypted a second time. This\nsecond encryption is called *server-side encryption*, which Cloud Storage\nmanages. When you retrieve your data, Cloud Storage removes the server-side\nlayer of encryption, but you must decrypt the client-side layer yourself.\n\nYou can use the open source cryptographic SDK, Tink, to perform client-side\nencryption, then protect your keys with Cloud Key Management Service. For more\ndetails, see [Client-side encryption with Tink and Cloud Key Management Service](/kms/docs/client-side-encryption).\n| **Warning:** Cloud Storage doesn't know if your data has already been encrypted on the client side and has no knowledge of your client-side encryption keys. You must securely manage your client-side keys and ensure that they are not lost. If you lose your keys, you are no longer able to read your data, and you continue to be charged for storage of your objects until you delete them."]]
