You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: enhance iApp documentation with new trust benefits section
- Added a new section detailing the trust benefits for users and builders, emphasizing control over data and the advantages of privacy-preserving features.
- Improved the presentation of key concepts with clearer formatting and visual elements for better user understanding.
<p class="m-0"><strong>Zero Trust Architecture:</strong> Users don't need to trust you with their data. The protocol guarantees privacy.</p>
63
61
</div>
64
62
</div>
65
63
66
-
## The Trust Model
67
-
68
-
Here's why users will actually use your iApp with their private data:
69
-
70
-
### What Users See
71
-
72
-
- ✅ "This code runs in a secure enclave, not on the developer's servers"
73
-
- ✅ "My data gets used privately for actions I want"
74
-
- ✅ "Even iExec workers can't see my data during execution"
75
-
- ✅ "I can revoke access anytime"
76
-
77
-
### What You Get
78
-
79
-
- ✅ Users willing to use your services with their sensitive data
80
-
- ✅ New business models around privacy-preserving analytics
81
-
- ✅ Competitive advantage through privacy guarantees
82
-
83
64
## How It Works
84
65
85
66
Your code runs in a Trusted Execution Environment (TEE) a secure area inside
86
67
specific processors (Intel SGX/TDX chipset). Everything that happens there stays
87
68
private and protected, even from the operating system.
88
69
89
-
An authorized user can trigger an iApp that processes someone's protected data inside this private environment. The data is used, but never exposed, not even to the person running the app.
70
+
An authorized user can trigger an iApp that processes someone's protected data
71
+
inside this private environment. The data is used, but never exposed, not even
0 commit comments