This page describes the QuietNode marketing website and enquiry flow. Customer-hosted product data follows the deployment controls and written terms agreed for an evaluation or service engagement.
QuietNode Studio is a one-person studio. There is no registered legal entity yet. When there is one, this page will name it.
Website visits, contact and security-docs requests, optional site analytics, and an optional scheduling handoff. A signed evaluation or service agreement governs product deployments and customer data in those deployments.
The site sets no cookies of its own and does not sell or share personal data.
Security-control descriptions on this site are self-attested implementation statements. QuietNode has no independently certified controls or completed independent audit to claim.
The marketing site does not ask for warehouse credentials or customer data. Do not place secrets, production records, or regulated data in the enquiry form.
The contact form asks for the information needed to understand and respond to an enquiry.
Plausible loads only when the analytics environment variable is set. When it is not set, the site runs no analytics at all.
The contact endpoint uses a hidden honeypot and may use the request IP for short-lived rate limiting.
I use marketing-site information for the purpose that brought it in: replying, scoping, scheduling, and protecting the enquiry route.
I use the details you send to reply, to understand the workflow you want to look at, and to answer a security question.
After a successful contact request, the site may offer a scheduling link for a follow-up conversation.
Use limited technical signals to deliver the site, diagnose failures, and reduce contact-form abuse.
If I wrote to you first, I found your name and work address in a public business source, such as your company’s website or a professional profile. I wrote because your role relates to what QuietNode builds. Reply “stop” and you will not hear from me again. Your address goes on a suppression list so that it is never written to again.
These providers support the public website and enquiry flow. They are separate from any connector or model endpoint a customer chooses inside a QuietNode deployment.
Production website hosting and request delivery
Used for the deployed marketing site
Hosts the QuietNode mailbox where enquiries arrive
Used for every enquiry and every reply
Cookie-free site and funnel analytics
Loaded only when the analytics environment variable is configured
Booking a follow-up meeting
Shown only when I have set up a scheduling link and you choose to use it
This is the complete list today. If it changes, this page changes and its effective date moves.
QuietNode products are designed for customer-hosted deployment. The public site has a separate, limited path for enquiries and optional analytics.
Marketing website
Contact details and enquiry context are delivered through the providers above so I can reply. Analytics run only when the analytics environment variable is set.
Customer deployment
Product state, connector access, credentials, and audit records are designed to remain in the customer environment. If a customer configures an external model endpoint, prompts follow that customer-chosen route.
You can ask for deletion at any time, whatever the schedule below says.
Messages are kept while a conversation is active and for up to two years after it ends, then deleted.
Plausible, when it is enabled, keeps aggregate page and event counts under its own terms. A booking made through the scheduling provider follows that provider’s terms. Ask, and I will delete what I hold.
Customer-hosted product retention is configured within the deployment and documented in the applicable written agreement; it is not set by this marketing-site notice.
Choices and requests
Wherever you live, you can ask what I hold about you, ask for it to be corrected or deleted, or object to my using it. Email the privacy contact with enough detail to find your message. I answer within 30 days.
If you are in the UK or the EU, you can also complain to your data protection authority.