mirror of
https://github.com/anyproto/docs.git
synced 2025-06-08 13:57:11 +09:00
GITBOOK-315: Clean up the Data & Security group
This commit is contained in:
parent
d17c49a892
commit
fb5634d1b4
4 changed files with 32 additions and 27 deletions
|
@ -61,11 +61,11 @@
|
||||||
|
|
||||||
## 🔐 Data & Security
|
## 🔐 Data & Security
|
||||||
|
|
||||||
* [Delete or Reset Your Account](data-and-security/delete-or-reset-your-account.md)
|
|
||||||
* [How we keep your data safe](data-and-security/how-we-keep-your-data-safe.md)
|
|
||||||
* [What is a Recovery Phrase?](data-and-security/what-is-a-recovery-phrase.md)
|
* [What is a Recovery Phrase?](data-and-security/what-is-a-recovery-phrase.md)
|
||||||
* [Data Storage & Deletion](data-and-security/data-storage-and-deletion.md)
|
* [Privacy & Encryption](data-and-security/how-we-keep-your-data-safe.md)
|
||||||
* [Backup and self-hosting](data-and-security/self-hosting.md)
|
* [Storage & Deletion](data-and-security/data-storage-and-deletion/README.md)
|
||||||
|
* [Backup & Self-Hosting](data-and-security/data-storage-and-deletion/self-hosting.md)
|
||||||
|
* [Delete or Reset Your Account](data-and-security/delete-or-reset-your-account.md)
|
||||||
* [Analytics & Tracking](data-and-security/analytics-and-tracking.md)
|
* [Analytics & Tracking](data-and-security/analytics-and-tracking.md)
|
||||||
|
|
||||||
## 🚵 MIgration
|
## 🚵 MIgration
|
||||||
|
|
|
@ -1,12 +1,20 @@
|
||||||
# Data Storage & Deletion
|
# Storage & Deletion
|
||||||
|
|
||||||
### Storage <a href="#storage" id="storage"></a>
|
### Storage <a href="#storage" id="storage"></a>
|
||||||
|
|
||||||
Anytype is offline first; hence, all data you create will be stored locally first. After that, the data is synced to the backup node and your devices for redundancy. We use a private [IPFS](https://docs.ipfs.tech/concepts/what-is-ipfs/) network to handle storage. It is a Peer-To-Peer file system that facilitates decentralized data storage across devices. Furthermore, we use the deduplication feature to reduce storage. For example, if the same picture is uploaded three times, there is only one image copy stored to reduce storage consumption.
|
Anytype is offline first; hence, all data you create will be stored locally first. After that, the data is synced to the backup node and your devices for redundancy. We use a private [IPFS](https://docs.ipfs.tech/concepts/what-is-ipfs/) network to handle storage. It is a Peer-To-Peer file system that facilitates decentralized data storage across devices.
|
||||||
|
|
||||||
#### Media <a href="#media" id="media"></a>
|
#### Media <a href="#media" id="media"></a>
|
||||||
|
|
||||||
Media files are not directly downloaded in overall syncing to save bandwidth. Instead, when that file is requested, it is streamed to your device from the backup node or your devices on the network. For example, if you have a 4K Video, it will be streamed from the backup node or P2P devices to your device. So when you open an object with an image, it downloads. When you press play on video & audio, it begins to download. After that, this file will be stored in the application cache.
|
Media files are not directly downloaded in overall syncing to save bandwidth. Instead, when that file is requested, it is streamed to your device from the backup node or your devices on the network. For example, if you have a 4K Video, it will be streamed from the backup node or P2P devices to your device. So when you open an object with an image, it downloads. When you press play on video & audio, it begins to download. After that, this file will be stored in the application cache. 
|
||||||
|
|
||||||
|
Furthermore, we use the deduplication feature to reduce storage. For example, if the same picture is uploaded three times, there is only one image copy stored to reduce storage consumption.
|
||||||
|
|
||||||
|
#### Custom storage location
|
||||||
|
|
||||||
|
{% hint style="warning" %}
|
||||||
|
Currently, you can not change the directory of your local data storage. We have it in [plans for Q3 2023](https://github.com/orgs/anyproto/projects/1/views/1). You might consider using a [workaround from our user](https://community.anytype.io/t/custom-storage-location/994) as a temporary solution for Windows and MacOS.
|
||||||
|
{% endhint %}
|
||||||
|
|
||||||
### Deletion <a href="#deletion" id="deletion"></a>
|
### Deletion <a href="#deletion" id="deletion"></a>
|
||||||
|
|
||||||
|
@ -14,6 +22,8 @@ Media files are not directly downloaded in overall syncing to save bandwidth. In
|
||||||
|
|
||||||
At the moment you can delete only the Objects that you've created inside Anytype. At first, you can move them to a bin that will remove them from navigation. Secondly, you can remove them completely from all devices. All your devices will also delete them when getting online. This action is irreversible, so please be careful.
|
At the moment you can delete only the Objects that you've created inside Anytype. At first, you can move them to a bin that will remove them from navigation. Secondly, you can remove them completely from all devices. All your devices will also delete them when getting online. This action is irreversible, so please be careful.
|
||||||
|
|
||||||
#### Media <a href="#media-1" id="media-1"></a>
|
#### Undeletable objects <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.
|
Objects like Media and those created by Anytype (Types, Relations) can't be deleted at the moment, but might be deletable in future releases. 
|
||||||
|
|
||||||
|
You can remove all the media 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.
|
|
@ -1,28 +1,23 @@
|
||||||
# Backup and self-hosting
|
# Backup & Self-Hosting
|
||||||
|
|
||||||
#### Backup node
|
## Backup node
|
||||||
|
|
||||||
Every Anytype user has access to a remote backup node provided by Anytype. Its capacity is currently limited to 1 Gb. These nodes are located in Switzerland.
|
Every Anytype user has access to a remote backup node provided by Anytype. Its capacity is currently limited to 1 Gb. If you go over the limit, a warning will appear, and you'll be able to ask for more storage.
|
||||||
|
|
||||||
|
Our backup nodes are located in Switzerland.
|
||||||
|
|
||||||
|
#### Disable the Anytype backup node
|
||||||
|
|
||||||
**How to remove Anytype backup node**\
|
This is currently not possible, but it's planned to be [implemented soon](https://github.com/anyproto/roadmap/issues/34) (**2023Q3**).
|
||||||
|
|
||||||
|
{% hint style="info" %}
|
||||||
It's also possible to use p2p sync between your devices, you can [block Anytype network traffic](https://community.anytype.io/t/is-there-a-way-to-limit-storage-of-data-only-local/6982) (Anytype & Anytype Helper) via your firewall.
|
It's also possible to use p2p sync between your devices, you can [block Anytype network traffic](https://community.anytype.io/t/is-there-a-way-to-limit-storage-of-data-only-local/6982) (Anytype & Anytype Helper) via your firewall.
|
||||||
|
{% endhint %}
|
||||||
|
|
||||||
|
## **How to self-host Anytype**
|
||||||
|
|
||||||
**How to self-host Anytype**
|
|
||||||
|
|
||||||
If you don’t want to use Anytype backup node, you can self-host your own using [this guide](https://tech.anytype.io/how-to/self-hosting). It is our first step in this direction, so it requires some technical skills from users and depends on several external solutions.
|
If you don’t want to use Anytype backup node, you can self-host your own using [this guide](https://tech.anytype.io/how-to/self-hosting). It is our first step in this direction, so it requires some technical skills from users and depends on several external solutions.
|
||||||
|
|
||||||
Our contributors are already working on creating a Docker image to simplify the setup of self-hosted infrastructure. You can join by following this [discussion](https://github.com/orgs/anyproto/discussions/17) on our GitHub page.
|
Our contributors are already working on creating a Docker image to simplify the setup of self-hosted infrastructure. You can join by following this [discussion](https://github.com/orgs/anyproto/discussions/17) on our GitHub page.
|
||||||
|
|
||||||
Internally, we're already working on adding network configuration ability into the apps. This will make the process of rebuilding clients optional and greatly simplify the self-hosting flow. We expect to deliver this feature in upcoming releases.
|
Internally, we're already working on adding network configuration ability into the apps. This will make the process of rebuilding clients optional and greatly simplify the self-hosting flow. We expect to deliver this feature in upcoming releases.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Custom storage location**
|
|
||||||
|
|
||||||
{% hint style="warning" %}
|
|
||||||
Currently, you can not change the directory of your local data storage. We have it in [plans for Q3 2023](https://github.com/orgs/anyproto/projects/1/views/1). You might consider using a [workaround from our user](https://community.anytype.io/t/custom-storage-location/994) as a temporary solution for Windows and MacOS.
|
|
||||||
{% endhint %}
|
|
|
@ -1,10 +1,10 @@
|
||||||
# How we keep your data safe
|
# Privacy & Encryption
|
||||||
|
|
||||||
#### Privacy <a href="#privacy" id="privacy"></a>
|
### Privacy <a href="#privacy" id="privacy"></a>
|
||||||
|
|
||||||
All of your data is private in Anytype. Only you have the encryption keys. No one at Anytype can decrypt your data. So if you lose your phrase, we can’t restore access. Likewise, no one in Anytype or anyone else can read the content of your Anytype.
|
All of your data is private in Anytype. Only you have the encryption keys. No one at Anytype can decrypt your data. So if you lose your phrase, we can’t restore access. Likewise, no one in Anytype or anyone else can read the content of your Anytype.
|
||||||
|
|
||||||
#### Data encryption logic <a href="#keychain" id="keychain"></a>
|
### Encryption <a href="#keychain" id="keychain"></a>
|
||||||
|
|
||||||
* Your objects are stored both locally and on nodes in an encrypted format, which can only be decoded using encryption keys. They are different for each document, and we have a certain hierarchy of keys.
|
* Your objects are stored both locally and on nodes in an encrypted format, which can only be decoded using encryption keys. They are different for each document, and we have a certain hierarchy of keys.
|
||||||
* To be able to search through the documents efficiently, we create indexes of your data locally on the basis of the encrypted objects. Think of that as two different storages: one for data, the other for indexes. We decrypt these encrypted objects on the fly with your keys, perform some logic and then save the results (i.e. indexes) locally. These indexes are not encrypted, but here we assume that only you have access to your local data, i.e. the access to your local computer is not compromised.
|
* To be able to search through the documents efficiently, we create indexes of your data locally on the basis of the encrypted objects. Think of that as two different storages: one for data, the other for indexes. We decrypt these encrypted objects on the fly with your keys, perform some logic and then save the results (i.e. indexes) locally. These indexes are not encrypted, but here we assume that only you have access to your local data, i.e. the access to your local computer is not compromised.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue