This page sets out the terms for using this website, and how evaluations, security controls, and human approvals fit together.
QuietNode Studio is run by one person. There is no registered legal entity yet. The control model below follows the current product and security documentation.
It is information, not an offer. Nothing here is a contract, a commitment to a feature or a date, or a guarantee of how the software will perform on your systems.
The text, design, and code of this site belong to QuietNode Studio. You may quote it with a link back.
An evaluation or deployment begins only after the parties agree its scope, access boundaries, approval workflow, and applicable commercial terms in writing.
The website explains QuietNode's current product model and provides a way to request information or a walkthrough.
A signed evaluation or service agreement defines the commercial and operational relationship for a deployment.
When a signed agreement addresses a service issue, that agreement—not this public summary—governs the engagement.
QuietNode's governance controls work alongside—not instead of—the customer's identity, repository, data-platform, review, and deployment controls.
The customer is responsible for having permission to connect the systems, repositories, data, and model endpoints placed in scope.
The customer chooses who can approve work and keeps its own review, branch-protection, and deployment controls in force.
Use QuietNode only for the systems and work authorized in the written evaluation or deployment scope.
QuietNode documents controls and maps them to common security frameworks for readiness review. Those mappings are self-attested. QuietNode has no independently certified controls or completed independent audit to claim here.
QuietNode is designed to run in the customer environment, with customer-controlled data, credentials, secrets, and model routing.
QuietLens holds read-only access, enforced in code. It records the question, the query it ran, and the evidence for review.
QuietMend is designed to ask for short-lived access scoped to the ticket, work only in DEV, and raise a pull request a person merges. It is in development and has never run against live systems.
Every QuietLens action is logged in a hash-chained audit log. QuietMend is designed to record its plan, access request, approval, and pull request on the ticket.
QuietLens answers with evidence. QuietMend is designed to prepare changes as pull requests. The customer reviews the evidence, assigns authorized reviewers, and approves or rejects the proposed outcome.
QuietNode prepares
A diagnosis, ticket, plan, or pull request is delivered with the scope and evidence recorded for review.
Customer decides
An authorized human verifies the evidence and keeps the customer’s existing production controls in force.
A deployment may connect to repositories, data platforms, ticketing systems, model endpoints, or other services selected and configured by the customer.
The customer decides which external systems and model endpoints are placed in scope.
The customer is responsible for its rights to use those services, systems, and data.
External services remain governed by their own contracts, availability, and privacy terms.
Any use of QuietLens or QuietMend is governed by a separate written agreement. Without one, no licence is granted.
To the extent the law allows, QuietNode Studio is not liable for any loss arising from your use of this site.
These terms name no governing law or venue. There is no registered legal entity yet to name one.
Questions about these terms
Contact QuietNode Studio before relying on this summary for an evaluation or deployment.