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-261: change request with no subject merged in GitBook

Browse source
This commit is contained in:
Charlotte Chiang 2023-07-24 10:44:50 +00:00 • committed by gitbook-bot
parent 2cdb27b13e
commit 1d21a43d10
No known key found for this signature in database
GPG key ID: 07D2180C7B12D0FF
2 changed files with 1 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
data-and-security/data-storage-and-deletion.md
View file

@ -32,5 +32,3 @@ At the moment you can delete only the [Fundamentals](https://app.gitbook.com/o/S
#### Media <a href="#media-1" id="media-1"></a>
Objects like Media and those with Anytype (Types, Relations) might be deleted in further releases. You can delete all the content via the clear cache option in iOS and Android. This will remove all the data altogether and force the app to sync once again entirely. Since the media download works on-premise, you will remove all cached media and clear some storage.
### Root Folder <a href="#root-folder" id="root-folder"></a>

2
data-and-security/how-we-keep-your-data-safe.md
View file

@ -22,6 +22,6 @@ Here are some technical details on encryption and data storage:
* 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>".
* The second layer is used to encrypt the actual data. We use 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](https://app.gitbook.com/o/Ssa9i5QAuI6HhV4jXCLv/s/JbcKxgThRdSa4vZyLbvH/faqs/syncing-and-p2p).
* 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](https://tech.anytype.io/any-sync/overview).
* 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 to the data.