Is there any algorithm where user can prove to server that the encrypted data sent by the server has been re-encrypted/destroyed by user after reading it?
Lets assume there is a server and user. The server wants the proof that data sent to user has been re-encrypted/destroyed after it has been read. Assuming user didn't create multiple copies of data.
Though there is one option to encrypt with the servers public and sent the data back to server so that server can verify. But in this case I dont want the server to read actual data. So this scenario is ruled out.
This can be applied to the scenario where the customer stores the data in the third party servers and after the contract is finished he wants to make sure that the data has been destroyed by the 3rd party servers and proof is provided to the customer.
Assumptions : There are no multiple copies of data, Third party servers can access the data before deletion.
To the doubts raised by community member. Lets assume the server will give access to some other resource on providing information that data has been encrypted. Second one: I gave the example of public key encryption so that server can use his private key to decrypt , but I dont want server to read the data. I need something similar to that. I dont need 100% reliable solution. I just need a close one.