anyproto/docs
1
0
Fork 0
mirror of https://github.com/anyproto/docs.git synced 2025-06-08 05:47:05 +09:00
Code Activity

GitBook: [#166] No subject

Browse source
This commit is contained in:
Vladimir Ermolaev 2022-05-05 15:54:20 +00:00 • committed by gitbook-bot
parent c9fb597c6b
commit 547a03566a
No known key found for this signature in database
GPG key ID: 07D2180C7B12D0FF
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
features/privacy-and-security.md
View file

@ -25,9 +25,9 @@ Anytype stores data in a non-encrypted way locally. We have a prerequisite that
There are some technical details on encryption and data storage:
* Anytype stores changes for each object you’ve created
* Every object’s change has 2 encryption layers with different keys
* Every object’s change has 2 encryption layers with different keys. 
* the First layer is used to connect changes within an object (e.g. all this encrypted data belongs to the object with id \<abc>)
* Second layer is used to encrypt the actual data
* Second layer is used to encrypt the actual data. We using AES with stream **encryption** with CFB mode
* When you create a new change for an object, we periodically send it to our backup node(with only the first-layer key). More info about sync [here](syncing-and-p2p.md).
* Anytype backup nodes have access to the first layer key, so it can group changes for the object and send them in one pack when you want to restore your data
* Anytype backup nodes HAVE NO access to the second layer key, so it can’t read the actual changes data