Terms of use
A product demonstration, clearly bounded.
These terms explain the permitted use of the Gritnox concept, the limits of its illustrative data and why no catalog, RFQ or supplier record creates a commercial offer.
01 · Agreement
Acceptance of these terms
By accessing the Gritnox application, you agree to use it in accordance with these terms and applicable law. If you do not agree, do not use the application. These terms are a product-policy draft for an independent concept and are not legal advice.
02 · Status
Demo status and no commercial offer
No offer, contract or supplier relationship
Catalog records, prices, stock states, lead times, suppliers, fitment evidence and RFQ confirmations are illustrative. They do not constitute an offer to sell, a binding quote, an acceptance of an order, a warranty or evidence of availability.- A demo RFQ is recorded in the application but is not transmitted to a supplier.
- No order, reservation, payment obligation or fulfillment commitment is created by an RFQ.
- Checkout remains a separate commerce flow and does not validate Gritnox catalog data.
- Manufacturers, suppliers, certifications and partnerships shown in the demo are not represented as real relationships.
03 · Conduct
Acceptable use
- Use the application for evaluation, demonstration, research and portfolio review.
- Do not attempt to gain unauthorized access, bypass rate limits, disrupt the service or probe protected APIs.
- Do not submit malicious code, credentials, payment data, confidential drawings or another person's private information.
- Do not scrape or republish illustrative supplier data as if it were verified market intelligence.
- Do not remove demo disclosures or use the Gritnox name to misrepresent an affiliation.
04 · Access
Accounts and workspace access
Buyer, seller and administrator workspaces are role-scoped. Seller applications require a verified email and administrator review; storefront release is a separate administrator decision. You are responsible for keeping account credentials confidential and for activity performed through your account. API-side authorization remains the source of truth; client-side route protection is not a security boundary.
05 · Input
RFQ and contact submissions
You retain ownership of the information you submit. By submitting an RFQ or contact inquiry, you permit the operator to validate, store and process it for the demonstrated workflow, abuse prevention and record correction. Do not submit information you are not authorized to share.
Submitted content must not be unlawful, deceptive, malicious or infringing. The operator may remove demo records or restrict access to protect the application.
06 · IP
Intellectual property
The original Gritnox product concept, interface design, documentation and application code are presented as the portfolio work of Zisanur Haque unless a file states otherwise. Third-party software, fonts, icons and marks remain the property of their respective owners.
Component references and manufacturer names used as illustrative data do not grant a license or imply endorsement. No right to use another party's trademark is granted by these terms.
07 · Risk
Disclaimers
The application is provided on an "as is" and "as available" basis. To the fullest extent permitted by law, no warranty is made regarding availability, accuracy, fitness for a particular purpose, non-infringement, security or suitability of any part for a physical operating environment.
Industrial parts can affect safety, uptime and regulatory compliance. Do not rely on this concept as the sole basis for maintenance, substitution, procurement or safety decisions.
08 · Liability
Limitation of liability
To the fullest extent permitted by law, the project author and any operator of this concept are not liable for indirect, incidental, special, consequential or punitive losses, or for loss of data, production, revenue or business opportunity arising from use of the application. Nothing in these terms excludes liability that cannot lawfully be excluded.
09 · Evolution
Changes and contact
These terms may change as the application evolves. Material updates should be recorded in the changelog and reflected in the effective date. For a question about these terms, use the contact intake with the general or security topic as appropriate.