Core Concepts

Encryption

Arcsec employs end-to-end encryption to ensure data privacy. All sensitive information is encrypted before being stored, ensuring that even if the storage is compromised, the data remains secure. IPFS is in nature a public storage, but Arcsec encrypts the data before it is stored, so that the data is private to the user, even if the CID is public.

Decentralized Storage

We leverage IPFS for decentralized storage of encrypted data. This approach provides several benefits:

• Increased data availability and redundancy
• Resistance to single points of failure
• Enhanced data integrity

How we store your data

Arsec only keeps the most crucial data required to interact with your databases on IPFS. This includes your wallet address, the CIDs of your encrypted databases and internal Arcsec data. All of your data is still yours, and you have full control over it. You can even remove your databases from Arcsec at any time.

IPFS Database Structure

Our databses mimick SQLite databases, but instead of being stored on a singular server, they are stored on IPFS. This means that your databases are decentralized and resistant to single points of failure. The files still maintain the same structure, but are encrypted before being stored on IPFS. You can export your databases from Arcsec and import them into any other SQLite compatible database. Keeping the files in SQLite foramt allows for seamless communication and SQL querying.

Authentication

We currently only support EVM wallet-based authentication. This is to allow for on-chain ownership and control of your data, and potential fuutre web3 based features. A social sign in is in the works, but currently not available.

API-First Approach

Our database solution is designed with an API-first approach, making it easy to integrate with various front-end frameworks and backend services, but all your databases are still browsable and editable in the dashboard.