Terms of Service
Last updated: July 28, 2026
This page is maintained by the Obsidian team to outline the rules, responsibilities, and limitations that apply when you use the Obsidian website, firmware, software, documentation, and community spaces.
1. Acceptance of Terms
By accessing or using Obsidian resources, you agree to be bound by these Terms of Service. If you do not agree, please do not use the site, downloads, or community channels.
2. Open-Source Software and Firmware
Obsidian projects are made available under the open-source licenses referenced in each repository. Unless otherwise stated, you may use, modify, and distribute the software in accordance with the applicable license. All code is provided "as is" without warranty of any kind.
3. Supported Devices
Official support is limited to the devices explicitly listed on the site, currently the Lilygo T-Embed and Flipper Zero. Use with other hardware is at your own risk and is not guaranteed or supported.
4. Community Conduct
When participating in community spaces, including Discord, forums, or GitHub, you agree to be respectful, avoid harassment, and stay on topic. We reserve the right to remove content or suspend access for behavior that violates these standards.
5. Intellectual Property
The Obsidian name, logo, and branding are the property of the Obsidian team. Third-party trademarks, device names, and logos referenced on the site belong to their respective owners.
6. Limitation of Liability
In no event shall the Obsidian team be liable for any damages arising out of or related to the use or inability to use the software, firmware, documentation, or community resources, including but not limited to data loss, device damage, or business interruption.
7. Changes to These Terms
We may update these Terms of Service from time to time. Changes will be posted on this page with an updated "Last updated" date. Your continued use of the site after changes are posted constitutes acceptance of the revised terms.
8. Contact
For questions about these Terms of Service, please reach out through the community Discord or open an issue in the relevant GitHub repository.