Where your data lives

First, what a "worker" is.

Your site isn't a folder of files on a rented server somewhere. It runs as a Cloudflare Worker: a small, self-contained program that lives on Cloudflare's network and answers each visitor from the nearest city. Think of it as your site's own little vending machine. It can only hand out what's stocked inside it and pass enquiries through a slot. That "only" is doing real work in everything below.

Your website can't reach anyone else's data.

This is the structural one. Your site runs as its own worker, and if it has a database, that database belongs to your site alone. When a visitor sends an enquiry, it travels one-way over an internal channel: the full record is kept for your business, and a central lead store keeps a routing copy (their contact details, what they asked about, and whether it reached you). No site can read that central store back, so a bug, a bad edit, even a compromised site can't paw through another business's enquiries, because that read path doesn't exist.

Enquiries go to you, and stay put.

An enquiry is your customer's name, contact details, message, and any files they attach. It lands in the lead store, gets delivered to your inbox, and shows in your dashboard. Attached files sit in private storage, never on a public link; downloads use signed links that only work from our emails and your dashboard, and files age out automatically rather than accumulating forever.

Everything runs on Cloudflare.

Your site, its enquiry pipe, the dashboard and the email all run on Cloudflare's network, the same infrastructure a large share of the web sits behind, in an account we operate. Cloudflare's default placement decides where data is stored, so we don't guarantee a particular country. One platform, one place to secure, no plugin zoo quietly phoning home from your pages.

Who can actually see your data.

You, and anyone you add to your site, through your dashboard. Sign-in is by email link or your Google account, no passwords for us to lose. Your site's manager agent, which works for you. Jezweb staff, who run the platform and can open any site's dashboard for support. And the two services that run it: Cloudflare, which hosts it, and Anthropic, whose AI reads each enquiry to sort out spam. That's the list. We don't sell data, we don't share it between clients, and we don't use your customers' enquiries to advertise anything to anyone.

No change the agent makes lands without your say-so.

When you ask for an edit, the agent builds it, shows you a preview, and publishes only on your approval. Every publish the agent makes is versioned, so there's a history to look back on and a way back if you change your mind.

Where the AI fits, honestly.

AI agents read your enquiries to summarise and prioritise them. If you add the chat assistant to your site, it talks to visitors using only facts you've approved. This runs through business API agreements with the model providers, the tier where your content isn't used to train their public models, and we meter every conversation. What the AI knows about your business is the file you can read in your dashboard, not a mystery.

No trackers you didn't ask for.

By default your site carries no Google Analytics, no ad pixels, no third-party trackers. Visit counts come from our own server-side beacon, which adds nothing to your page weight and follows nobody around the internet. If you run Google Ads or genuinely use Analytics, we wire your own IDs in. Your call, made once, on the record.

Your site is separated from every other site, and that is already done.

This is the strongest thing on this page, so it is worth being exact about. Your site runs as its own worker on Cloudflare's Workers for Platforms, the machinery built for precisely this kind of separation, and most sites have their own dedicated database and their own file storage. Not a partition, not a customer column in a shared table: your own. Your orders, bookings and files live there. Two things are also kept centrally, in Jezweb's shared platform database: the routing copy of each enquiry described above, and, if you run a membership club, the list of members who can sign in.

This used to be the paragraph describing what we were going to build. It is finished and running for most sites on the platform; a few sites do not have their own database yet. The one deliberate exception is the enquiry pipe described above, which stays central because routing, spam triage and delivery are the things it does; enquiries move one way, into your dashboard, and nothing flows back the other way.

If that distinction matters in your industry, ask and we will walk you through exactly which bytes sit where. We would rather explain it plainly than let the word "isolated" do vague work.