A Clearer Picture / Payments
Payments & Data Handling.
Payment processing, business records and website analytics are three different things. Here's how we describe them without mixing them up.
Last updated: 9 November 2026
1. This website does not take card payments
On this public marketing website, the module builder requests a quote and the contact forms send enquiries. They are not card-payment forms. Please never enter card numbers, security codes or banking passwords into an enquiry.
2. A payment provider handles checkout
Where a connected product or customer website offers payments, the actual checkout depends on the configured provider and payment method, such as Stripe. Card entry should be handled by that provider's secure payment flow. Provider terms, privacy practices, transaction fees, refunds and settlement arrangements may apply.
3. Business records are not raw card data
Denver's Desk can keep business information associated with a payment: invoices, order references, amounts, payment status, refunds, balances and processor transaction identifiers. That information may be needed for business records and reconciliation. It is not the same as storing full payment card numbers or CVVs. Do not interpret this page as a claim that Denver's Desk stores no payment-related information whatsoever.
4. How Website Analytics Works
Denver's Desk includes a consent-gated first-party analytics client on this public site. Analytics only begins after a visitor accepts it, and it can then record the approved website events described below.
When a visitor accepts analytics, the site can record the event types already wired here: page views, external link clicks, contact submissions and quote requests. Each event includes the configured website identifier, a generated event/session identifier, the page path, time and referring-site origin where available.
The analytics payload is deliberately separate from the business data inside enquiry, order, invoice or payment flows. It does not deliberately send form answers, card numbers, invoice lines, order lines or payment amounts. Browser and hosting providers can still receive ordinary technical request information such as IP address and browser details when a request is made. See the Privacy & Analytics Notice for the visitor-facing privacy explanation.
5. Different businesses, different setups
Websites can be independent, connected to Denver's Desk, or integrated with other systems. The specific provider, record flow, refund process and data responsibilities must be confirmed for each customer setup. This page is an overview of the public website and common integration boundaries, not a promise that every payment integration is live or that every customer's data flow is identical.
