Information you submit
The contact form asks for the information needed to understand and respond to an enquiry.
- Name, work email, and optional company
- Your message and selected enquiry type
- Any systems and timing details you choose to include
Privacy
Privacy and data handling, plainly stated.
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.
TODO: owner — privacy notice effective dateTODO: owner — controller jurisdiction
Policy status
The operator details that still need owner confirmation.
QuietNode is publishing the handling model now without inventing legal identity, location, or dates. These placeholders must be replaced before this notice is treated as final legal text.
- Legal operator
- TODO: owner — registered legal entity name
- Registered address
- TODO: owner — registered business address
- Legal founding date
- TODO: owner — legal founding date
- Privacy contact
- hello@quietnode.studio
What this notice covers
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.
This is a transparent operational summary, not a substitute for owner- and counsel-approved privacy terms.
Security-control descriptions on this site are self-attested implementation statements. QuietNode has no independently certified controls or completed independent audit to claim.
Data collected
Only the information needed to run the site and respond.
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.
Optional site analytics
When the analytics environment variable is configured, QuietNode loads Plausible and records page and funnel events.
- The integration is designed without cookies or form-field contents
- CTA and form events carry operational context such as page or enquiry type
- No analytics script is loaded when the integration is not configured
Abuse-prevention signals
The contact endpoint uses a hidden honeypot and may use the request IP for short-lived rate limiting.
- These signals protect the enquiry route from automated submissions
- They are not used to build marketing profiles
- Serverless rate limiting is a best-effort technical control
How it is used
Enquiries in, a useful response out.
QuietNode uses marketing-site information for the purpose that brought it in: responding, scoping, scheduling, and protecting the enquiry route.
Respond and qualify
Use the details you provide to answer your question, understand the workflow you want to evaluate, and route a security request.
- Reply to an enquiry
- Prepare for a walkthrough
- Provide requested security material
Schedule next steps
After a successful contact request, an owner-configured scheduling link may be offered for a follow-up conversation.
- Scheduling is optional
- The booking page loads only after a successful enquiry when the owner has configured it
- The provider's own terms and privacy policy apply
Operate and protect the site
Use limited technical signals to deliver the site, diagnose failures, and reduce contact-form abuse.
- Site delivery
- Error diagnosis
- Rate limiting and spam filtering
Service providers
The systems that may support the marketing site.
These providers support the public website and enquiry flow. They are separate from connectors or model endpoints a customer chooses inside a QuietNode deployment.
ProviderPurposeWhen used
Vercel
Production website hosting and request delivery
Used for the deployed marketing site
Resend
Delivery of contact-form messages to the QuietNode inbox
Used only when production email delivery is configured
Plausible
Cookie-free site and funnel analytics
Loaded only when the analytics environment variable is configured
Scheduling provider
Booking a follow-up meeting
Shown only when the owner configures a scheduling URL and you choose to use it
TODO: owner — confirm the production subprocessor list, locations, and change-notice process
Separate data paths
Marketing-site data is not product-runtime data.
QuietNode products are designed for customer-hosted deployment. The public site has a separate, limited path for enquiries and optional analytics.
Marketing website
Information you choose to send
Contact details and enquiry context are delivered through the configured website providers so the team can respond. Optional analytics are enabled only through the public-site environment setting.
Customer deployment
Runtime data stays under customer controls
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.
Retention
The public retention schedule is not yet finalized.
QuietNode will not manufacture a retention promise before the owner has confirmed the operating schedule and counsel has reviewed it.
Website enquiries
TODO: owner — set contact-message and inbox retention periods
Analytics and scheduling
TODO: owner — confirm provider retention settings and deletion procedure
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
Ask what is held, or request a correction or deletion.
Email the privacy contact with enough detail to locate the enquiry. QuietNode may need to verify identity before acting. The applicable rights process and response timing still require owner and counsel confirmation.
TODO: owner — publish request verification, jurisdiction, and response-time process