Skip to content

Commit 7e06e9d

Browse files
committed
fix: enhance clarity on iApp's secure processing and its significance
1 parent 2b806e7 commit 7e06e9d

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

src/build-iapp/what-is-iapp.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,11 @@ description: Privacy-first applications that run on decentralized infrastructure
66
# 🚀 What Is an iApp?
77

88
An iExec Application (iApp) is your regular application code (Python script, AI
9-
model, data processor) that can securely process sensitive data inside a
10-
privacy-safe environment called a Trusted Execution Environment (TEE).
9+
model, data processor) that can securely process protected data (created by
10+
DataProtector) inside a privacy-safe environment called TEE (a Trusted Execution
11+
Environment).
1112

12-
## Why Would You Want This?
13+
## Why iApps Matter?
1314

1415
Simple: **to process sensitive data that users won't normally share.**
1516

@@ -25,12 +26,13 @@ they will.**
2526

2627
## How It Works
2728

28-
Your code runs in a **trusted execution environment** (TEE) - think of it as a
29-
"privacy bubble" that even iExec workers can't peek into.
29+
Your code runs in a Trusted Execution Environment (TEE) a secure area inside
30+
specific processors (Intel SGX/TDX chipset). Everything that happens there stays
31+
private and protected, even from the operating system.
3032

31-
Users run your iApp when they want to **use** their Protected Data for
32-
something. Your code gets access to their protected data, performs actions with
33-
it - all without you ever seeing the raw data.
33+
An authorized user can trigger an iApp that processes someone’s protected data
34+
inside this private environment. The data is used, but never exposed, not even
35+
to the person running the app.
3436

3537
## iApp Generator: Your Development Tool
3638

0 commit comments

Comments
 (0)