The **SAFE Launcher** will act as your gateway to the SAFE Network, you can use it to access data stored on the **SAFE Network** and to authorise apps to fetch, upload, modify and delete data on your behalf. [block:image] { "images": [ { "image": [ "https://files.readme.io/201f1b2-Screen_Shot_2016-08-01_at_10.43.35_PM.png", "Screen Shot 2016-08-01 at 10.43.35 PM.png", 1500, 1100, "#eaebeb" ] } ] } [/block] [block:api-header] { "type": "basic", "title": "Why do we need a gateway?" } [/block] An application's direct access to the SAFE Network on behalf of the user is an issue with high security concerns. Without Launcher, every app would ask for user credentials to log into the SAFE Network. This means that sensitive information, for example a user's session packet data could be compromised and potentially misused. Launcher will prevent this from happening as, with regard to credentials, apps only interface with the SAFE Network indirectly via Launcher. ** What will SAFE Launcher do for you?** * SAFE Launcher will allow you to create an account and log into the SAFE Network. * SAFE Launcher will ask you to manually authorize apps that want to access the SAFE Network on your behalf. * SAFE Launcher will manage any metadata related to apps, to provide uniformity in the SAFE app experience when moving from one device to another. For example, if app A is installed on device one then when the user logs into device two using their SAFE Network account (via the Launcher), they will be presented with a unified view of all the apps that were installed on all the devices they use to access the SAFE Network. * SAFE Launcher must not allow apps to mutate each other's configs. * SAFE Launcher makes it easy to revoke an app's ability to read and mutate the SAFE Network on behalf of a user. [block:callout] { "type": "info", "title": "Give it a go", "body": "[Install SAFE Launcher](doc:install-launcher)" } [/block]