@@ -9,12 +9,9 @@ description:
9
9
** Want to keep your data private while still using it in confidential
10
10
applications?**
11
11
12
- Here's how DataProtector works: first you encrypt your data, then manage your
13
- orders to control exactly who can access it, how many times, and at what price.
14
-
15
- Once data is protected, it's only accessible inside secure enclaves (TEEs) by
16
- the specific users and iApps (iExec application running in TEE) you authorize
17
- through the orders you create. No exceptions.
12
+ DataProtector lets you encrypt data and control access through orders -
13
+ specifying who can use it, how many times, and at what price.Protected data is
14
+ only accessible in secure enclaves (TEEs) by authorized users and iApps.
18
15
19
16
## Installation
20
17
@@ -68,12 +65,11 @@ console.log('Protected data address:', protectedData.address);
68
65
** Data** : Any kind of data you want to keep private and make available for
69
66
computations by authorized users and iApps.
70
67
71
- ** Supported types** : Strings, numbers, booleans, nested objects, files (convert
72
- to ArrayBuffer first), and arrays (convert to Record format), you can find the
73
- full list [ here] ( /manage-data/dataProtector/types )
68
+ ** Supported types** : Common data types like text, numbers, true/false values,
69
+ and files. See the [ full list here] ( /manage-data/dataProtector/types ) .
74
70
75
- ** Limits ** : File size depends on your storage choice ( IPFS or Arweave) . For
76
- large datasets, consider using another IPFS node.
71
+ ** Storage ** : Store your data on IPFS or Arweave. For larger files, you can use
72
+ your own IPFS node.
77
73
78
74
::: tip
79
75
@@ -106,12 +102,15 @@ const protectedData = await dataProtectorCore.protectData({
106
102
107
103
## Grant Access
108
104
109
- ** Here's the key:** The protocol blocks all access to your protected data by
110
- default. You must explicitly grant permission for each app and user combination.
111
- By doing this, you publish signed orders that ensure your protected data stays
112
- private while controlling access to it.
105
+ By default, your protected data is private. To let others use it, you need to
106
+ grant access to both:
107
+
108
+ - An authorized user (who can trigger the processing)
109
+ - An authorized iApp (the application that will process the data in the private
110
+ environment)
113
111
114
- Once you own protected data, here's how to share access:
112
+ This ensures that only specific users can use specific applications to process
113
+ your data. Here's how to set it up:
115
114
116
115
``` ts twoslash
117
116
import { IExecDataProtectorCore , getWeb3Provider } from ' @iexec/dataprotector' ;
0 commit comments