Storage that belongs to your account, not to the app
Your files should belong to your account, independently of the app that created them. An app can use a folder you approve without getting access to everything else you store.
A recipe app can keep your recipes in its own folder. If it wants access to your photos, it has to ask. You can connect another app to the same folder and remove the old app’s access.
The goal is that people can change apps without moving their data to another service. Shared storage makes that possible; apps still need to support the formats they read and write.
-
Your Seige account
-
recipes
- Recipe appApproved
- Another recipe appApproved
-
photos
- Recipe appHas to ask
-
recipes
How apps use your account
-
Sign in with Seige Use one Seige account for mail, storage, Ada and connected apps. Apps receive a verified identity without handling your Seige password.
-
Give each app its own folder A connected app gets a dedicated folder. Access to other folders requires your approval, and the folder belongs to your account rather than to the app.
-
Remove access in settings An approved app can keep working while Seige is closed. Disconnecting it blocks further requests and protects future changes with new keys. It cannot erase data or keys the app already copied.
Formats another app can read
Files and SQLite databases give apps formats that other tools can read. Developers should document their schemas and migrations so users can choose a compatible replacement.
An authorized client can decrypt and save its approved data locally. Compatibility depends on the file format and schema; access to a folder alone does not make every app understand its contents.
An assistant that works with what you allow
Ada can find and summarize information in your files and mail, organize messages and draft replies. You review and send drafts yourself in Mail.
Ada runs while you have it open in your browser. Your chats and Ada’s saved notes about you are encrypted in storage, and you can edit or delete those notes. To answer you, Ada sends selected context in readable form through Seige’s AI service for model processing.
Our direction is to let apps ask Ada for help, with each request limited to data the user authorized. That interface is not available yet; apps currently integrate through the sign-in and storage SDK.
What encryption does and does not cover
Your device encrypts files, notes and app data before uploading them. Seige stores the encrypted result without the keys needed to read it, and an approved app receives keys only for the folders you share with it.
Encryption does not hide every detail. Seige still handles public identity information and can see details such as timing and data sizes. Ordinary internet mail is readable by the systems that deliver it, and Ada needs readable context to answer you.
If you lose your password, another enrolled passkey may still let you sign in. If you lose every way to unlock your account, Seige cannot recover your encrypted contents.
Encryption and data protection covers each of these in detail.
Build an app that keeps its data with its users
Use sign-in, files, a database and AI from one browser SDK. Ask for the folders your app needs and leave your users’ data in their own accounts.