MapleSecure Full 30-year timeline →
About the Architect

Who created MapleSecure, and why?

MapleSecure is built by Joel Gathercole, founder of Joel & Nanz Inc. and the Privacy Officer for the company. He spent 20 years at TriageLogic, rising to Director of IT, where he was personally responsible for securing enterprise infrastructure carrying some of the most sensitive data that exists: patient records, clinical triage, healthcare workflows. He has also administered servers for more than 26 years. MapleSecure exists because the security posture he maintained for a healthcare enterprise is not actually expensive to extend to a Canadian small business — nobody had simply bothered to do it.

For 20 years, Joel Gathercole's name was on the line for data that could ruin lives if it leaked.

At TriageLogic, what started in 2006 as a VoIP engagement became a two-decade tenure ending as Director of IT. Healthcare data. Patient records, clinical nurse triage, the details people share only with someone they trust to keep them. Securing that is not a project with a completion date — it is access control, encryption, key management, audit trails, patch discipline, incident response, and knowing at all times exactly where every piece of data physically sits and which laws govern it. Twenty years of that becomes a permanent way of thinking.

The habit goes back further. Joel has been administering servers for over 26 years and running his own infrastructure since the BBS days of the 1990s, when he was personally accountable for every message stored on his own drive.

Then he started working with Canadian small businesses, and found the gap.

It is not that small businesses do not care about security. It is that everything built to a serious standard was priced and packaged for enterprises with a compliance department, and everything priced for a small business was security theatre — a padlock icon and a marketing page. So SMBs default to emailing contracts as unencrypted PDF attachments, signing documents through US platforms that keep a copy under US jurisdiction, and storing client identity documents in whatever cloud folder was free. Not through negligence. Through having no realistic third option.

MapleSecure is that third option. Secure document exchange and e-signature, passkey-based authentication rather than passwords that get reused across a dozen sites, encrypted storage, verifiable audit trails, and hosting on Canadian infrastructure so client data stays under Canadian law and PIPEDA rather than crossing a border by default. The controls are the ones Joel ran at healthcare scale; what changed is the packaging and the price, not the standard.

The data-sovereignty point deserves stating plainly, because most vendors avoid it. When a Canadian business signs a client contract through a US e-signature platform, that document — with names, addresses, financial terms, sometimes identity documents — sits on US servers subject to US legal process. That is rarely disclosed at the point of sale, and most owners have never been told. Joel spent two decades where knowing the answer to that question was his job, and he was not willing to build a product that quietly got it wrong.

MapleSecure is part of the MapleWorkSuite ecosystem from Joel & Nanz Inc., built in New Brunswick. Built by someone who spent 20 years being the person who got the call when something went wrong — and would rather Canadian small businesses never make that call at all.

Joel and Nancy, the two founders of Joel & Nanz Inc.
Joel and Nancy, Joel & Nanz Inc., New Brunswick.

Verified historical record

Independently timestamped on the Internet Archive — the evidence behind the 30-year claim:

The same architect, across the Maple network

Every product came out of a different part of the same 30-year timeline. Each page explains which experience produced it: