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-190: No subject

Browse source
This commit is contained in:
Charlotte Chiang 2023-02-21 14:39:13 +00:00 • committed by gitbook-bot
parent 7a8b3946d2
commit a8eeee234a
No known key found for this signature in database
GPG key ID: 07D2180C7B12D0FF
15 changed files with 20 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

2
faqs/can-pages-be-nested-one-to-another.md
View file

@ -21,4 +21,4 @@ All Anytype structures are based on links between objects. Links are directional
All objects connections will soon look like an interconnected network:
![Some objects have links from completely different context](<../.gitbook/assets/Screenshot 2021-11-09 at 12.54.59.png>)
![Some objects have links from completely different context](<../.gitbook/assets/Screenshot 2021-11-09 at 12.54.59 (1).png>)

6
faqs/privacy-and-security.md
View file

@ -22,12 +22,12 @@ Anytype stores data in a non-encrypted way locally. We have a prerequisite that
### Tech details
There are some technical details on encryption and data storage:
Here 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.&#x20;
* Every object’s change has 2 encryption layers with different keys.
* The First layer is used to connect changes within an object (for example, all this encrypted data belongs to the object with id \<abc>)
* 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
* Anytype backup nodes HAVE NO access to the second layer key, so it can’t read the actual changes to the data

2
faqs/syncing-and-p2p.md
View file

@ -1,6 +1,6 @@
# Syncing & P2P
All your data primarily syncs to the encrypted backup node in the current alpha. Therefore, all data storage is at **no cost** to you. The application is always connected to the backup node and cannot be disconnected.
All your data primarily syncs to the encrypted backup node in the current alpha. For alpha testers, the application is always connected to the backup node and cannot be disconnected.
#### Local backups