Terms and Conditions
1. Introduction
These Terms and Conditions ("Terms", "Terms and Conditions", or "Agreement") govern access to and use of DevClub UI (the "Library", "Service", "Software", or "Product"), including its source code, compiled packages, components, templates, styles, design assets, documentation, examples, utilities, plugins, APIs, websites, package registries, repositories, and related services.
The Library is provided by DevClub ("Provider", "we", "us", or "our").
By downloading, installing, accessing, copying, modifying, integrating, distributing, or otherwise using the Library, you acknowledge that you have read, understood, and agree to be bound by these Terms.
If you do not agree to these Terms, you must not use, install, copy, distribute, or otherwise access the Library.
If you are using the Library on behalf of an organization, company, educational institution, or other legal entity, you represent and warrant that you have authority to bind that entity to these Terms. In that case, "you" includes both you and the entity you represent.
2. Definitions
"Library" means the software component library made available by the Provider, including all versions, releases, packages, source code, compiled distributions, components, utilities, styles, assets, documentation, examples, and associated materials.
A "Component" means any reusable software component, UI component, module, hook, function, utility, stylesheet, token, configuration, asset, or other software element included in the Library.
"Documentation" means guides, references, API documentation, examples, installation instructions, tutorials, changelogs, migration guides, README files, and other explanatory materials provided by the Provider.
"User", "you", or "your" means any individual or legal entity accessing or using the Library.
"Project" means any software application, website, mobile application, desktop application, service, product, internal system, client project, commercial product, open-source project, or other work that incorporates or uses the Library.
"Third-Party Material" means software, libraries, packages, fonts, icons, images, APIs, services, dependencies, frameworks, or other material created or supplied by parties other than the Provider.
"License" means the license terms that apply to the specific version, package, component, or asset of the Library. Where a separate open-source license, commercial license, or asset-specific license accompanies a portion of the Library, that license controls the relevant portion to the extent stated in that license.
3. Acceptance of Terms
By using the Library, you confirm that you have legal capacity to enter into this Agreement and will comply with applicable laws and regulations.
- You will comply with all applicable license terms.
- You will not use the Library for unlawful purposes.
- You will not intentionally interfere with the Library or its infrastructure.
- You will respect the intellectual property rights of the Provider and third parties.
- You will comply with restrictions applicable to third-party dependencies and assets.
- You will review these Terms periodically for changes.
4. Scope of These Terms
These Terms apply to all supported forms of access to the Library, including package manager installations, source-code downloads, git repositories, binary distributions, CDN distributions, hosted documentation, component previews, design resources, example projects, templates, plugins and integrations, APIs made available with the Library, developer tooling, command-line tooling, development environments, commercial and non-commercial projects, internal organizational projects, client projects, educational projects, and open-source projects.
Additional terms may apply to specific products, packages, services, or features. If a separate written agreement expressly conflicts with these Terms, the separate agreement controls only for the subject matter covered by that agreement.
5. Eligibility
You may use the Library only if you are legally capable of entering into a binding agreement, your use is permitted under applicable law, you are not prohibited from receiving software under applicable sanctions or export restrictions, and you comply with the applicable license for the Library.
If you are under the age required by applicable law to enter into this Agreement independently, you must use the Library only with appropriate permission and supervision from a parent, guardian, educational institution, or other legally authorized person.
6. License and Right to Use
Your rights to use the Library are determined by the applicable license. Unless expressly stated otherwise in a separate license, these Terms do not automatically grant ownership of the Library or its intellectual property.
Depending on the applicable license, you may be permitted to install the Library, use the Library in personal projects, use the Library in commercial projects, modify source code, create derivative works, distribute applications incorporating the Library, include the Library in client projects, use the Library internally, and use the Library in open-source projects.
You must comply with all applicable license conditions, including attribution, notice, redistribution, source availability, trademark, or other requirements where applicable.
7. Open-Source Components
Some portions of the Library may be distributed under open-source licenses. Open-source components remain subject to their respective licenses.
Where applicable, the Provider will identify relevant third-party or open-source licenses through LICENSE files, NOTICE files, package metadata, documentation, repository directories, dependency manifests, or license information included with distributions.
You are responsible for reviewing and complying with applicable open-source licenses. If an open-source license grants rights that cannot legally be restricted by these Terms, those rights remain unaffected.
8. Commercial Use
Unless prohibited by the applicable license, the Library may be used in commercial Projects, including SaaS products, websites, mobile applications, desktop applications, enterprise applications, internal business software, client work, freelance projects, agency projects, paid applications, subscription products, e-commerce systems, educational products, startup products, and government or institutional software.
If a specific package or asset is subject to a commercial license, commercial use is permitted only in accordance with that license.
9. Personal and Educational Use
Subject to the applicable license, the Library may be used for personal learning, academic assignments, university projects, research projects, prototypes, demonstrations, hackathons, educational applications, and portfolio projects.
Educational use does not automatically override license restrictions or third-party intellectual property requirements.
10. Modification
Where permitted by the applicable license, you may modify the Library for your Projects, including changing component behavior, changing styles, adding functionality, removing functionality, refactoring code, changing configuration, adapting components to a different framework, integrating additional dependencies, and creating custom variants.
You are responsible for maintaining your modifications and ensuring that they remain compatible with your Project. Unless separately agreed, the Provider has no obligation to support modified versions.
11. Distribution
If the applicable license permits redistribution, you may distribute the Library or software incorporating the Library subject to all applicable license requirements across source repositories, package registries, application installers, production deployments, container images, client deliverables, internal distributions, and public downloads.
You must not remove legally required notices, license information, copyright statements, or attribution requirements. You must not represent the Library as independently created by you where such representation would be misleading.
12. Prohibited Uses
You must not use the Library to violate applicable laws, infringe intellectual property rights, circumvent security controls, distribute malware, facilitate unauthorized access, conduct fraudulent activities, conduct phishing or credential theft, create ransomware or destructive software, intentionally damage systems or networks, interfere with infrastructure supporting the Library, attempt to gain unauthorized access to Provider systems, abuse APIs or hosted services, circumvent technical usage limits, reverse engineer portions where prohibited by law, remove required copyright or licensing notices, misrepresent authorship, or attack, scan, exploit, or compromise systems without authorization.
Nothing in this section is intended to prohibit activities expressly permitted by applicable law or the applicable open-source license.
13. Security
You are responsible for implementing appropriate security controls in your Project. The Library may contain software components that interact with user input, authentication systems, databases, APIs, browsers, servers, local storage, network services, and third-party services.
You must independently evaluate the security requirements of your Project and should not assume that use of the Library makes an application secure.
You are responsible for input validation, authentication, authorization, access control, secret management, dependency management, secure configuration, logging, monitoring, encryption where appropriate, secure deployment, and vulnerability management.
14. Security Vulnerabilities
If you discover a security vulnerability affecting the Library, please report it through the Provider's designated security contact: security@devclub.co.
Security reports should include a description of the vulnerability, affected versions, reproduction steps, proof of concept where appropriate, potential impact, and suggested mitigation if known.
You should avoid publicly disclosing sensitive vulnerability details before the Provider has had a reasonable opportunity to investigate and address the issue.
15. Dependencies
The Library may depend on third-party packages, frameworks, libraries, or services including React, Node.js, TypeScript, CSS frameworks, GSAP, Radix UI, OGL, build tools, package managers, browser APIs, cloud services, and authentication providers.
Third-party dependencies are subject to their own terms and licenses. The Provider does not necessarily control third-party dependencies and is not responsible for changes made by third-party maintainers. You are responsible for reviewing dependency licenses and security advisories relevant to your Project.
16. Third-Party Services
The Library may optionally integrate with third-party services such as hosting providers, authentication providers, analytics services, payment providers, cloud platforms, AI services, databases, package registries, and content delivery networks.
Your use of third-party services is governed by the relevant provider's terms and privacy policies. The Provider does not guarantee the availability, security, accuracy, or continued operation of third-party services.
17. APIs
Where APIs are provided, you agree to use them only for lawful and authorized purposes. You must not abuse API endpoints, circumvent rate limits, attempt unauthorized access, extract data in violation of applicable terms, conduct denial-of-service attacks, use automated access beyond permitted limits, or share credentials improperly.
API availability, quotas, rate limits, and functionality may change over time.
18. Package Registry and Distribution Channels
The Library may be distributed through package registries or other platforms such as npm, GitHub, GitLab, jsDelivr, unpkg, or custom registry endpoints.
Third-party distribution platforms may impose additional terms. The Provider does not control third-party platform availability or policies.
A package may become temporarily unavailable because of registry outages, security incidents, platform policy changes, network failures, maintenance, version removal, or account/infrastructure issues.
19. Versioning
The Provider may release new versions of the Library containing new features, bug fixes, security patches, performance improvements, documentation updates, breaking changes, dependency changes, API changes, or deprecated functionality.
You are responsible for evaluating upgrades before deploying them to production. The Provider does not guarantee backward compatibility between all versions unless expressly stated.
20. Deprecation
The Provider may deprecate features, components, APIs, or packages. A deprecated feature may remain available for a period of time but may eventually be removed.
Where reasonably practical, the Provider will communicate significant deprecations through release notes, changelogs, documentation, repository notices, and migration guides. You are responsible for migrating away from deprecated functionality when appropriate.
21. Breaking Changes
Breaking changes may occur between major or other releases, affecting component APIs, props, events, hooks, CSS classes, tokens, build configuration, package exports, dependencies, browser compatibility, or framework compatibility.
You should review release notes and migration instructions before upgrading.
22. Compatibility
The Provider documents supported operating systems, browsers, framework versions, runtime versions, package manager versions, Node.js versions, and build tools.
Unsupported environments may still work, but the Provider makes no guarantee of compatibility unless expressly stated.
23. Documentation
Documentation is provided for informational and implementation purposes. The Provider may update, correct, remove, or reorganize documentation without notice.
Examples and sample code may require modification before production use. Documentation does not constitute professional legal, financial, security, medical, or other regulated advice.
24. Examples and Sample Code
Example code is provided to demonstrate possible implementations. Unless explicitly stated otherwise, examples are not guaranteed to be production-ready, secure for all use cases, accessible for all users, optimized for performance, or compatible with every environment.
You are responsible for adapting examples to your own product requirements.
25. Accessibility
Where the Library includes user-interface components, the Provider attempts to support accessibility standards such as WCAG and WAI-ARIA authoring practices.
However, final accessibility depends on component configuration, user-provided content, application structure, browser behavior, assistive technologies, styling, and custom modifications.
You remain responsible for testing your final Project for accessibility and complying with applicable accessibility legal requirements.
26. Browser and Platform Differences
Different browsers, devices, operating systems, screen sizes, rendering engines, and assistive technologies may produce different behavior or visual appearance.
The Provider does not guarantee identical rendering or behavior across every environment. You are responsible for testing your Project on the environments relevant to your end users.
27. Performance
Performance depends on factors including application architecture, bundle size, network conditions, browser environment, device hardware, rendering strategy, third-party dependencies, data volume, and server configuration.
The Provider does not guarantee specific performance results unless expressly stated in a written agreement.
28. Intellectual Property
The Library and its original materials may be protected by copyright, trademark rights, database rights, design rights, trade secrets, and other intellectual property rights.
Except for rights expressly granted under the applicable license, all rights are reserved by their respective owners. Nothing in these Terms transfers ownership of intellectual property to you.
29. Ownership of Your Project
Subject to third-party rights and applicable licenses, you retain ownership of the original intellectual property that you create in your Project.
Using the Library does not automatically transfer ownership of your independent Project to the Provider. However, your rights may be subject to the licenses governing the Library and its dependencies.
30. Contributions
If the Library accepts community contributions, contributions are subject to contribution guidelines. By submitting a contribution, you represent that you have the necessary rights and permissions to submit it.
Unless a separate contribution agreement states otherwise, contributions are licensed under the terms specified by the Provider's repository. You must not submit confidential information, proprietary code belonging to another party without license, malicious code, credentials, or personal data.
31. Pull Requests and Community Contributions
The Provider may review, reject, modify, or accept contributions at its discretion. Acceptance of a contribution does not guarantee inclusion in a particular release, continued maintenance, backward compatibility, or attribution beyond what the applicable contribution terms require.
32. Feedback
If you provide suggestions, ideas, feature requests, bug reports, or other feedback, you grant the Provider permission, to the extent legally permitted, to use that feedback without restriction or compensation, unless otherwise agreed in writing.
You should not submit confidential information as feedback.
33. Trademarks
Names, logos, product names, service names, and other branding associated with the Provider constitute trademarks. Use of Provider trademarks must comply with applicable trademark law and published brand guidelines.
You must not imply sponsorship, partnership, certification, endorsement, employment, or official affiliation unless such relationship actually exists in writing.
34. Attribution
Where attribution is required by the applicable license, you must provide it in the required manner across source distributions, binary distributions, documentation, product interfaces, about pages, license files, or notices.
Failure to provide required attribution may constitute a license violation.
35. Privacy
The Library itself runs client-side and does not harvest personal data. If the Library includes hosted services, telemetry, analytics, authentication, or crash reporting, applicable privacy terms are provided separately.
You are responsible for ensuring that your Project complies with applicable privacy and data protection laws including GDPR, UK GDPR, CCPA/CPRA, and other relevant regional frameworks.
36. Personal Data
If your Project processes personal data using the Library, you are responsible for determining what data is collected, why it is collected, the legal basis for processing, storage, security, retention, international transfers, and user rights.
You must not assume that the Library provides compliance with privacy laws by itself.
37. Cookies and Tracking
If your Project uses cookies, pixels, analytics, local storage, fingerprinting, or similar technologies, you are responsible for providing legally required notices and obtaining consent where applicable.
The Library does not automatically make a Project compliant with cookie or tracking regulations.
38. Data Security
You are responsible for protecting data processed through your Project using reasonable security practices including encryption, secure authentication, least-privilege access, secret management, dependency updates, security monitoring, backups, and incident response procedures.
39. Data Retention
Unless otherwise expressly stated, the Provider does not determine how long you retain data in your own Project. You are responsible for establishing appropriate retention and deletion policies.
40. User Content
If your Project allows end users to upload, create, publish, or transmit content, you are responsible for establishing appropriate rules governing that content and ensuring that your Project does not facilitate unlawful activities.
41. AI-Related Features
If the Library includes or integrates with artificial intelligence functionality or code generators, AI-generated output may be inaccurate, incomplete, outdated, or biased.
AI output should be reviewed before being relied upon for consequential decisions. The Provider does not guarantee that AI-generated output is accurate, original, lawful, or suitable for a particular purpose.
42. Sensitive and High-Risk Uses
Unless expressly authorized, you should not rely solely on the Library or its output for decisions involving significant risks to individuals, including medical decisions, emergency response, legal determinations, financial decisions, credit decisions, employment decisions, safety-critical systems, or critical infrastructure.
43. User Responsibility
You are responsible for your use of the Library, your Project, your users, your deployment, your security, your data, your compliance obligations, your third-party integrations, your modifications, and your distribution practices.
The Provider is not responsible for problems caused solely by your implementation or configuration.
44. No Warranty
To the maximum extent permitted by applicable law, the Library is provided on an "AS IS" and "AS AVAILABLE" basis.
The Provider does not guarantee that the Library will be error-free, uninterrupted, meet every requirement, remain available indefinitely, be compatible with every environment, be secure against every vulnerability, produce particular results, remain unchanged, or be free of third-party defects.
45. Disclaimer of Implied Warranties
To the maximum extent permitted by law, the Provider disclaims implied warranties, including warranties of merchantability, fitness for a particular purpose, non-infringement, quiet enjoyment, accuracy, and availability.
46. Limitation of Liability
To the maximum extent permitted by applicable law, the Provider and its affiliates, officers, employees, contributors, licensors, and service providers will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages arising from or related to use of the Library.
Such damages include loss of profits, revenue, data, business opportunities, goodwill, business interruption, security incidents, or replacement costs.
Maximum aggregate liability is capped as permitted by applicable law.
47. Indemnification
To the extent permitted by applicable law, you agree to defend, indemnify, and hold harmless the Provider and its affiliates, officers, employees, contributors, and agents from claims arising from your unlawful use of the Library, violation of these Terms, violation of third-party rights, your Project, your modifications, your distribution of the Library, or your misuse of third-party services.
48. Availability
The Provider may modify, suspend, or discontinue any hosted aspect of the Library due to maintenance, security incidents, infrastructure changes, business decisions, legal requirements, or platform failures.
No specific availability or uptime commitment is made unless separately agreed in writing.
49. Maintenance
The Provider may maintain the Library through bug fixes, security patches, feature releases, refactoring, documentation updates, and dependency updates. Maintenance schedules are not guaranteed unless separately stated.
50. Backups
You are responsible for maintaining backups of your Project, configuration, modifications, deployments, and data. Do not rely on the Library or its public repositories as your sole backup mechanism.
51. Service Changes
The Provider may change APIs, components, documentation, distribution methods, package names, features, hosting infrastructure, URLs, or release schedules. Where reasonably practical, advance notice may be provided.
52. Suspension and Termination
The Provider may suspend access to hosted services if reasonably necessary to protect infrastructure, prevent abuse, address security incidents, comply with legal requirements, or prevent unauthorized access.
Termination of hosted services does not terminate rights granted under an irrevocable open-source license.
53. Effect of Termination
Upon termination of rights granted under a license that is legally terminable, you must stop activities that are no longer authorized.
However, rights granted under an irrevocable open-source license remain governed by that license, and previously distributed copies remain subject to the applicable license terms.
54. Survival
Provisions that by their nature should survive termination will survive, including intellectual property, disclaimers, limitation of liability, indemnification, governing law, dispute resolution, and license obligations.
55. Confidentiality
Unless separately agreed, the Library and its public documentation are not confidential. You should not submit confidential or sensitive proprietary information through public repositories, issue trackers, discussions, or contribution channels.
56. Export Controls and Sanctions
You are responsible for complying with applicable export control, sanctions, and trade laws. You must not use or distribute the Library in violation of applicable international restrictions.
57. Government Use
Government or public-sector users are responsible for determining whether their use complies with procurement, security, data protection, accessibility, export, and other applicable regulatory requirements.
58. Educational Institutions
Educational institutions may use the Library subject to applicable license terms. Institutions are responsible for ensuring that student and staff personal data is handled in accordance with applicable laws and policies.
59. Client and Agency Projects
If you use the Library to create Projects for clients, you are responsible for ensuring that your client agreements properly address intellectual property, third-party software, open-source licenses, attribution, security, maintenance, and support. The Provider is not a party to your client agreements.
60. Resale and Redistribution
You may not claim ownership of the Library itself merely because you include it in a Project. Any resale, sublicensing, white-labeling, redistribution, or bundling must comply with the applicable license.
61. White-Label Use
White-label use is permitted only where allowed by the applicable license. Where attribution is mandatory under an open-source license, white-labeling does not remove that attribution requirement.
62. Forks
Where permitted by the applicable open-source license, you may fork the Library. A fork may use a modified name, different branding, and independent maintenance, but must comply with the original license and must not falsely imply that it is an official Provider release.
63. Security of Secrets
You must not commit or distribute API keys, passwords, private keys, access tokens, database credentials, or signing keys. If credentials are accidentally exposed, revoke or rotate them immediately.
64. Malicious or Unauthorized Modifications
You must not knowingly distribute modified versions containing malicious code while representing them as official Provider releases, nor impersonate official repositories, packages, maintainers, or distribution channels.
65. Reporting Abuse
Abuse reports may be sent to abuse@devclub.co with sufficient information to investigate the alleged abuse. The Provider may take appropriate action where permitted by law.
66. Copyright Complaints
Copyright or intellectual property complaints should be submitted to legal@devclub.co, including identification of the claimant, protected work, infringing material location, contact info, and rights statement.
67. DMCA or Similar Procedures
Where applicable, the Provider maintains procedures for responding to legally valid copyright notices under the Digital Millennium Copyright Act (DMCA) or equivalent international legislation.
68. Dispute Resolution
Before initiating formal proceedings, the parties agree to attempt in good faith to resolve disputes through informal written communication.
69. Governing Law
These Terms are governed by the laws of the State of Delaware, United States, without regard to conflict-of-law principles, except where mandatory consumer law provides otherwise.
70. Jurisdiction
Subject to applicable law, any disputes arising under these Terms shall be resolved in the competent courts located in Delaware, United States.
71. Changes to These Terms
The Provider may update these Terms from time to time to reflect product changes, legal requirements, or new features. The Last Updated date indicates when revisions took effect.
72. Material Changes
For material changes, the Provider may provide additional notice through reasonable means such as website banners, repository notices, release notes, or package documentation.
73. Severability
If any provision of these Terms is found to be invalid or unenforceable, that provision will be modified only to the extent necessary, and the remaining provisions will continue in full effect.
74. Waiver
Failure to enforce any provision does not constitute a permanent waiver of that provision or any other right under these Terms.
75. Assignment
You may not assign your rights or obligations under these Terms without prior written consent. The Provider may assign these Terms in connection with a merger, acquisition, corporate restructuring, or sale of assets.
76. Entire Agreement
These Terms, together with applicable licenses and published policies, constitute the entire agreement concerning the Library and supersede prior agreements on the same subject matter.
77. No Partnership
Nothing in these Terms creates a partnership, joint venture, employment, agency, franchise, or fiduciary relationship between you and the Provider.
78. Force Majeure
The Provider is not responsible for delays or failures caused by circumstances beyond reasonable control, including natural disasters, war, government action, internet outages, cloud outages, or cyberattacks.
79. Notices
Legal notices should be sent via email to legal@devclub.co. Notices to users may be delivered through electronic postings or repository announcements.
80. Support
Unless separately agreed in an enterprise agreement, the Provider does not guarantee individualized technical support. Community support is available via GitHub issues and documentation.
81. Bug Reports
Bug reports are welcome through our official GitHub issue tracker. Reports should include library version, runtime, OS, browser, reproduction steps, expected behavior, and minimal repro code.
82. Feature Requests
Feature requests may be submitted through supported community channels. Submission of a request does not guarantee implementation or timeline.
83. Documentation and Content Accuracy
While reasonable efforts are made to keep documentation accurate, errors may occur. You should verify critical implementation details before deploying to production.
84. Open-Source Notice
This document does not replace the actual open-source license (such as MIT) included with the Library. Upstream license texts remain authoritative.
85. License Priority
If there is a conflict between these Terms and an applicable open-source license concerning rights granted by that license, the open-source license controls to the extent required by law.
86. Fonts, Icons, Images, and Design Assets
The Library may contain or reference visual assets (fonts, icons, svgs, images) which may be subject to separate licenses. Before redistributing assets, verify that redistribution is permitted.
87. User-Provided Assets
If you provide assets for use with the Library, you represent that you have the necessary rights to use those assets and remain responsible for any claims arising from them.
88. Accessibility of Documentation
The Provider attempts to make documentation accessible. If you identify an accessibility barrier, please notify accessibility@devclub.co.
89. International Users
The Library is accessible globally. You are responsible for determining whether use of the Library complies with local laws in your jurisdiction.
90. Consumer Rights
Nothing in these Terms is intended to remove or restrict mandatory statutory rights that consumers enjoy under applicable law.
91. Professional Advice
The Library and documentation do not constitute legal, tax, financial, medical, or cybersecurity certification advice. Seek professional counsel for regulated applications.
92. Compliance
You are responsible for evaluating and meeting all compliance obligations applicable to your Project (privacy, accessibility, security, consumer protection, and industry regulations).
93. Enterprise Use
Enterprise users requiring custom SLAs, vendor security reviews, data processing agreements, or tailored licensing should contact enterprise@devclub.co.
94. Service-Level Agreements
No service-level agreement applies to public community releases unless expressly executed in a separate written agreement.
95. Beta Features
Experimental or beta features may change without notice, contain bugs, lack documentation, or be removed. Use of beta functionality is at your own risk.
96. Experimental Components
Components tagged as experimental may alter APIs and behavior without adhering to semantic versioning guarantees.
97. Archived Versions
Older versions may be archived or unsupported. The Provider does not guarantee ongoing security patches or fixes for deprecated versions.
98. End-of-Life
When components reach end-of-life status, official distribution and updates cease. Migration guidance will be provided where reasonably practical.
99. Responsible Disclosure
Security researchers are encouraged to report vulnerabilities privately to security@devclub.co before public disclosure.
100. No Guarantee of Error-Free Software
Software inherently may contain defects. Despite rigorous automated testing, the Library may contain bugs. Maintain appropriate testing and rollback controls.
101. Production Deployment
Before deploying to production, pin dependency versions, run automated test suites, perform security scans, test target browsers, and verify accessibility compliance.
102. Recommended Development Practices
You are encouraged to use git version control, review dependency updates, conduct security scanning, use automated testing, protect credentials, and document modifications.
103. No Automatic Security Certification
Use of the Library does not mean your Project is automatically SOC 2, ISO, GDPR, HIPAA, or PCI DSS compliant. Such compliance depends on your total system controls.
104. Third-Party Claims
The Provider is not responsible for claims arising solely from third-party products, dependencies, or external assets that you choose to integrate.
105. Conflicts Between Policies
If separate policies exist (Privacy Policy, License, Code of Conduct), each applies to its specific stated subject matter.
106. Code of Conduct
Users participating in DevClub community platforms (issue trackers, discussions, forums) must adhere to respectful and collaborative standards of conduct.
107. Community Platforms
Community discussions hosted on third-party services (such as GitHub or Discord) are governed additionally by the terms and policies of those respective platforms.
108. Repository Availability
Public repositories may experience temporary downtime due to maintenance, upstream provider outages, or network interruptions. Maintain local git mirrors of essential code.
109. Package Integrity
Users are encouraged to verify package integrity using package-lock checksums, cryptographic signatures, and provenance metadata.
110. Automated Systems
Automated systems interacting with DevClub infrastructure must respect rate limits and technical quotas, and must not degrade service availability for other users.
111. Scraping and Data Extraction
You must not extract data from Provider infrastructure in a manner that violates applicable law, technical rate limits, intellectual property, or server stability.
112. Reverse Engineering
Nothing in these Terms prohibits activity expressly permitted by applicable open-source licenses or governing law.
113. Interoperability
Where applicable law provides rights for interoperability, those rights remain unaffected. Interoperability must not be used as a pretense for unauthorized access or security exploits.
114. User Accounts
If accounts are offered in the future, you are responsible for maintaining credential confidentiality and promptly notifying the Provider of unauthorized access.
115. Account Termination
The Provider may suspend accounts for abuse, fraud, security violations, or terms violations, without terminating irrevocable rights granted under open-source licenses.
116. Payments
If commercial tiers or paid support packages are offered, additional pricing, billing, and tax terms will be specified in the relevant order form.
117. Taxes
Users are responsible for any applicable sales, value-added, or withholding taxes associated with their commercial purchases or usage.
118. Refunds
Refund eligibility for commercial products is governed by the specific commercial agreement, preserving all non-waivable statutory consumer protections.
119. Free and Paid Versions
If distinct versions exist, each may provide differing features, support tiers, and distribution terms as set out in their respective documentation.
120. License Compliance
You are responsible for retaining license texts, copyright notices, and dependency attribution required to demonstrate software license compliance.
121. Audit Rights
These Terms do not grant the Provider automatic audit access to your systems unless explicitly executed in a separate commercial enterprise agreement.
122. Security Audits
Independent security reviews conducted on the Library do not certify the security of your overall integrated application.
123. Incident Response
If an incident affects your application, you are responsible for containment, investigation, customer notification, and regulatory reporting.
124. Vulnerability Scanning
Automated vulnerability scanners may produce false positives. Evaluate dependencies in the context of your specific deployment environment.
125. Data Processing Agreements
If the Provider processes personal data on your behalf through hosted services, a Data Processing Agreement (DPA) will be executed as required by law.
126. International Data Transfers
Where personal data crosses borders, the parties will implement legally recognized safeguards such as Standard Contractual Clauses.
127. Children
The Library is not directed at children under the age of 13. Projects directed at minors must independently comply with COPPA and relevant regional protections.
128. Accessibility Compliance
Where legal accessibility mandates apply to your Project (e.g. ADA Title III, European Accessibility Act), you must independently test and ensure compliance.
129. Localization
Translations of documentation or UI text are provided for convenience; the English version remains legally authoritative in the event of ambiguity.
130. Language
These Terms are executed in the English language, which controls all aspects of interpretation and dispute resolution.
131. Interpretation
Section titles and numbering are for convenience and reference only and do not affect the legal interpretation of these Terms.
132. Electronic Acceptance
Downloading, installing, cloning, copying component code, or accessing the registry constitutes valid electronic execution and agreement to these Terms.
133. Contact Information
For general support: support@devclub.co. For legal notices: legal@devclub.co. For security disclosures: security@devclub.co. For privacy: privacy@devclub.co.
134. Additional Policies
These Terms may be supplemented by our Privacy Policy, Cookie Policy, Security Policy, MIT License, Contribution Guidelines, and Code of Conduct.
135. Final User Responsibilities
Before production deployment, verify the applicable license, dependencies, accessibility compliance, runtime compatibility, and attribution obligations.
136. Acknowledgment
By using the Library, you acknowledge that you have reviewed the license, understand that software may contain defects, and accept these Terms.
137. Recommended Project-Level License Notice
Include the following notice in projects utilizing DevClub UI: "This project uses DevClub UI components under the terms of the MIT License. See LICENSE for details."
138. Recommended Third-Party Notices
Ensure third-party dependency licenses (GSAP, Radix UI, OGL, Motion, Tailwind CSS) are preserved in your distributions as required.
139. Recommended Security Contact
For responsible security disclosures: security@devclub.co. Follow responsible disclosure timelines before making findings public.
140. Recommended Legal Contact
Legal inquiries should be directed to DevClub via legal@devclub.co.
141. Version History
Version 1.0 — Published 23 September 2026. Initial comprehensive publication.
142. Customization Checklist
Ensure all organization-specific variables, licensing models, and jurisdictional parameters are reviewed and verified before commercial distribution.
143. Final Notice
This document establishes a complete framework for using DevClub UI. It does not replace independent legal counsel. Open-source licenses remain authoritative.