FAQ

Q: Will being local-first affect syncing across my devices?

A: No, it won’t. Easchi’s sync mechanism is deeply optimized for a massive number of files, allowing you to sync data as smoothly as with traditional cloud software. What sets it apart is that your data is encrypted locally before it ever leaves your device. During transmission, data exists only in the form of encrypted fragments, which nobody (including us) can inspect; it is only securely decrypted when you log in and authenticate on another one of your own devices.

Q: Can I recover data using only my password?

A: No, you cannot. To mitigate the security risks of weak passwords, Easchi generates a large amount of random data in the startup configuration file (startup.json). The system needs to combine this random data with your password to compute the correct decryption key. Therefore, you must properly back up your configuration files, including startup.json and config.bin. When recovering data on a new device, you must first place the backed-up configuration files into the new device’s configuration directory, and then launch Easchi to decrypt successfully.

Q: Is it fully compatible with the Markdown syntax of note-taking apps like Obsidian?

A: It is not 100% fully compatible at the moment. Easchi is making every effort to be compatible with mainstream syntax, but because many Markdown editors use a large amount of custom extended syntax and handle file reference paths differently, completely seamless compatibility still presents certain challenges. For detailed technical specifications on note formats, please refer to Note Formats.

Q: Why is there a separate Solo edition?

A: Because different countries or jurisdictions have significant differences in laws, regulations, and discretionary powers regarding “data encryption” and “end-to-end encryption,” some regions require the operator to have decryption capabilities or even to surrender decryption keys. To avoid legal charges and potential criminal liability, Easchi has introduced the Solo edition for specific regions. For details on whether your region is subject to such restrictions, please refer to the clauses on Feature Editions in the Terms of Service and End User License Agreement.

Q: Can I use custom sync methods?

A: Yes, you can. Easchi stores data directly in original file formats without any proprietary format conversion, and the data generated at runtime is also stored in plaintext. This design inherently provides great flexibility; you can use version control tools like Git for multi-version management, or sync directly through simple methods like object storage. For specific operation details, please see the chapter on Custom in the Sync Guide.

Q: If I cannot log in, can I request a refund?

A: Yes, you can. Easchi is committed to protecting the legitimate rights and interests of users. To request a refund, please have your original proof of payment ready and submit your application through Easchi’s official customer service channels. For specific refund policies and procedures, please see the Refund Policy.

Q: Is a plugin system supported?

A: At present, Easchi’s underlying code has already implemented a plugin-based architecture. However, because we plan to carry out a deep refactoring (involving the rich-text editor and responsive framework), the API currently provided to external developers is not yet fully stable. Therefore, external plugin functionality has not been opened at this stage. Thank you for your understanding and anticipation.