We Built a Marketing Consent Checkbox Nobody Asked For
There's a small piece of the NetMon signup form that almost certainly cost us a few
conversions. It's a single checkbox, unticked by default, sitting apart from the Terms of
Service agreement, that says — in plain language — whether you'd like to hear from us about
product news and offers. Nobody has to check it to use NetMon. Nobody has to check it to pay
us. It does nothing for us if it stays empty forever.
We built it anyway. On purpose. And we've never once been tempted to bundle it into the "I
agree to the Terms" tickbox the way almost every SaaS signup form on earth quietly does.
Here's why that's not a compliance footnote. It's the whole point.
The easy version, and why we didn't build it
The easy version of consent is one checkbox: "I agree to the Terms of Service and Privacy
Policy." Tick it, you're in. Somewhere in the eight thousand words nobody reads, there's a
clause that also opts you into marketing email. Legally defensible, in a lot of places.
Practically, it's a trick — you're using someone's desire to start using your product as
leverage to get permission you'd never get if you asked for it honestly.
UK GDPR is explicit about this, in Article 7(2): consent has to be distinguishable from
other matters, in clear and plain language, and it can't be a condition of getting the
service. So the legal reason for splitting the checkbox is real. But if the only reason
you'd separate marketing consent from service terms is "the regulator will fine us
otherwise," you've missed what the rule is actually protecting — which is the difference
between a customer choosing to hear from you and a customer being manoeuvered into it.
We didn't build the separate checkbox because a lawyer told us to. We built it because the
alternative is a lie of omission, and NetMon's entire product is built on the premise that
you should always know exactly what's happening on your network, not what a vendor decided
was convenient to tell you.
What "showing your work" actually looks like in a database
Here's the part that doesn't show up on the signup page at all, and it's the part I'm
actually proud of. Every time someone grants or withdraws marketing consent, we don't
overwrite a `marketing_opt_in` flag from `false` to `true` and back again. We write a new
row. Grant, withdraw, grant again — that's three rows, not one field flipping state. It's
append-only, kept for the life of the account plus seven years, and nothing about it is ever
edited in place.
Why does that matter to anyone who isn't an auditor? Because a flag that can be silently
flipped is a flag nobody can trust, including us. If a customer ever asks "did I actually
agree to this, and when, and did I ever change my mind" — which happens more often than
you'd think, usually months after the fact — we don't have to reconstruct a story. We have
the receipts, in order, permanently. The audit trail isn't decoration bolted onto the
feature. It's the feature working correctly.
The same discipline runs through how we treat two different kinds of customer data. NetMon
syncs business information — device counts, site counts, which plan a company is on — to our
CRM for every organisation, because that's a legitimate business interest and it's not
personal to any individual. But we only sync a named person's contact details if marketing
consent for that person genuinely exists, and we check that fresh every single time we run
the sync — never cached, never assumed still true from last week. Withdraw consent, and your
contact record doesn't get flagged as "opted out" somewhere in our CRM forever. It gets
deleted. Two data flows, two different rules, because they're two different kinds of trust,
and pretending they're the same thing to save engineering time is exactly the shortcut that
gets companies in the news for the wrong reasons.
Trust is a technical decision before it's a marketing one
Here's the thing about marketing advice that says "be authentic" or "earn trust" — it's true,
and it's also almost useless, because it doesn't tell you what to actually go and build. Trust
isn't a tone of voice. It's not a phrase in your About page. It's decisions like: does
withdrawing consent in our product actually delete your data somewhere else, or does it just
stop showing you the checkbox? Does "you agreed to this" mean we can prove it, or does it mean
we assume we can?
The best marketing doesn't feel like marketing because it isn't performing trustworthiness —
it's the visible edge of a company that made trustworthy decisions when nobody was going to
check. Nobody using NetMon will ever read our `consents` table schema. Nobody signing up for
Pro or MSP will ever know we enforce Data Processing Agreement acceptance on the server, not
just in a browser popup that a determined user could route around. That's exactly why it
matters that we did it that way. The things you build when you assume no one's watching are
the truest signal of what you actually believe about your customers' data.
We didn't build a marketing consent checkbox nobody asked for because it was required. We
built it because the alternative — the bundled, invisible, everyone-does-it version — would
have meant we were the kind of company that treats "yes" as something you can quietly assume
instead of something you earn. And if we're comfortable cutting that corner on a checkbox,
what corner do you think we'd cut on your network data?
That's the pitch, if you can even call it that. Not "trust us." Just: here's exactly what we
built, and why, so you don't have to.
