# Welcome! This is a draft document, finalized doc will be released at Nov with SafuGear service ## Glossary * **Client**: you, owner or developer of a web3 project, you build according to this doc and purchase our service. * **User**: users or customers of your product. * **Key**: private key of blockchain account/address ## Welcome to Safugear Our services allows client create and manage wallet for their users without domain knowledge about MPC, public key cryptography and difference transaction implementation between blockchains. ### Keyless login To make best experience for users, our services authenticate user's wallet operation on their one key login or social login credentials. ### Custodial service We will manage the storage of keys for clients and their users with proper segregation and service availability guarantee. Clients interact with this service with HTTPs APIs, and you have the responsibility on customizing all user experience about login/logout user flow. Clients also could put access limit (ban signing for) over the specific keys via our API. ### Semi-custodial service Note: This service is under construction and on our roadmap. We will manage only one key share of every private key for clients. With our app (Android, iOS, Web) SDK, you can participant in key generation procedure with our servers and get one key share to store on app side or on your storage services. This ensures **neither Safugear nor our client** will have user's full private key. Thus enhanced the trusty of your product. You could also provide "export key" functionality (via our app SDK) on your product and give user full ownership of the private key on emergency event. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.safulet.io/welcome.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.