|
| 1 | +--- |
| 2 | +title: Terms of Service — FeatureDrop |
| 3 | +description: Terms of service for FeatureDrop, the open-source product adoption toolkit by GLINR STUDIOS. |
| 4 | +--- |
| 5 | + |
| 6 | +# Terms of Service |
| 7 | + |
| 8 | +**Last updated:** February 28, 2026 |
| 9 | + |
| 10 | +These terms govern your use of the FeatureDrop open-source library, documentation site (featuredrop.dev), and related services provided by **GLINR STUDIOS** ("we", "us", "our"). |
| 11 | + |
| 12 | +--- |
| 13 | + |
| 14 | +## 1. The Library (MIT License) |
| 15 | + |
| 16 | +The `featuredrop` npm package is released under the [MIT License](https://github.com/GLINCKER/featuredrop/blob/main/LICENSE). In summary: |
| 17 | + |
| 18 | +- You **can** use it in personal and commercial projects |
| 19 | +- You **can** modify, distribute, and sublicense it |
| 20 | +- You **can** use it without attribution in your product (though attribution is appreciated) |
| 21 | +- You **must** include the original copyright notice and license in copies |
| 22 | +- The software is provided **"as is"** without warranty of any kind |
| 23 | + |
| 24 | +The full license text is available at [github.com/GLINCKER/featuredrop/blob/main/LICENSE](https://github.com/GLINCKER/featuredrop/blob/main/LICENSE). |
| 25 | + |
| 26 | +--- |
| 27 | + |
| 28 | +## 2. Documentation Site (featuredrop.dev) |
| 29 | + |
| 30 | +### Acceptable Use |
| 31 | + |
| 32 | +You may use featuredrop.dev to: |
| 33 | +- Read documentation and guides |
| 34 | +- Access code examples and API references |
| 35 | +- Use the interactive playground and component gallery |
| 36 | +- Link to our docs from your own projects |
| 37 | + |
| 38 | +You may **not**: |
| 39 | +- Scrape the site for commercial redistribution |
| 40 | +- Use the site to conduct denial-of-service attacks |
| 41 | +- Misrepresent FeatureDrop or GLINR STUDIOS in your use of our content |
| 42 | + |
| 43 | +### Content License |
| 44 | + |
| 45 | +Documentation content (text, code examples, diagrams) on featuredrop.dev is licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). You may share and adapt it with attribution. |
| 46 | + |
| 47 | +Code examples in the documentation may be used freely in your projects without attribution (they are effectively MIT-licensed). |
| 48 | + |
| 49 | +--- |
| 50 | + |
| 51 | +## 3. Claude Code Plugin |
| 52 | + |
| 53 | +The FeatureDrop Claude Code plugin and skill files are distributed as part of the MIT-licensed npm package. The same MIT license terms apply. |
| 54 | + |
| 55 | +--- |
| 56 | + |
| 57 | +## 4. Contributions |
| 58 | + |
| 59 | +By submitting a pull request, issue, or other contribution to the FeatureDrop repository, you agree that: |
| 60 | + |
| 61 | +- Your contribution is your original work (or you have the right to submit it) |
| 62 | +- You grant us a perpetual, worldwide, non-exclusive, royalty-free license to use, modify, and distribute your contribution under the MIT License |
| 63 | +- You understand your contribution will be publicly available |
| 64 | + |
| 65 | +We follow the [Contributor Covenant Code of Conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/). |
| 66 | + |
| 67 | +--- |
| 68 | + |
| 69 | +## 5. Trademarks |
| 70 | + |
| 71 | +"FeatureDrop" and the FeatureDrop logo are trademarks of GLINR STUDIOS. You may: |
| 72 | + |
| 73 | +- Use the name "FeatureDrop" to refer to the project in blog posts, tutorials, and documentation |
| 74 | +- Use the logo in articles, presentations, and comparison pages with proper attribution |
| 75 | + |
| 76 | +You may **not**: |
| 77 | +- Use our name or logo to imply official endorsement of your product |
| 78 | +- Create derivative logos that could be confused with ours |
| 79 | +- Use our marks in your product name (e.g., "SuperFeatureDrop" or "FeatureDrop Pro") |
| 80 | + |
| 81 | +--- |
| 82 | + |
| 83 | +## 6. Disclaimer of Warranties |
| 84 | + |
| 85 | +THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. WE DO NOT WARRANT THAT THE SOFTWARE WILL BE ERROR-FREE, SECURE, OR UNINTERRUPTED. |
| 86 | + |
| 87 | +--- |
| 88 | + |
| 89 | +## 7. Limitation of Liability |
| 90 | + |
| 91 | +IN NO EVENT SHALL GLINR STUDIOS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES ARISING FROM YOUR USE OF FEATUREDROP, WHETHER BASED ON WARRANTY, CONTRACT, TORT, OR ANY OTHER LEGAL THEORY. |
| 92 | + |
| 93 | +--- |
| 94 | + |
| 95 | +## 8. Changes to These Terms |
| 96 | + |
| 97 | +We may update these terms as the project evolves. Material changes will be communicated through the repository changelog. Continued use of FeatureDrop after changes constitutes acceptance. |
| 98 | + |
| 99 | +--- |
| 100 | + |
| 101 | +## 9. Governing Law |
| 102 | + |
| 103 | +These terms are governed by the laws of the jurisdiction in which GLINR STUDIOS operates, without regard to conflict of law provisions. |
| 104 | + |
| 105 | +--- |
| 106 | + |
| 107 | +## 10. Contact |
| 108 | + |
| 109 | +Questions about these terms? Open an issue on [GitHub](https://github.com/GLINCKER/featuredrop/issues) or email [hello@glincker.com](mailto:hello@glincker.com). |
| 110 | + |
| 111 | +--- |
| 112 | + |
| 113 | +GLINR STUDIOS |
| 114 | +[glincker.com](https://glincker.com) |
0 commit comments