Where your data lives
Most web companies answer this question with a privacy policy nobody reads. Here's the actual map: what we hold about your business, where it physically sits, who can touch it, and the parts we've made impossible rather than just against-the-rules.
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 holds no database.
This is the structural one. The worker that serves your site has no database attached. Not a locked one, none. When a visitor sends an enquiry, it travels one-way over an internal channel into a central lead store, and your site has no way to read that store back. A bug, a bad edit, even a compromised site can't paw through enquiries, yours or anyone else's, because the 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. One platform, one place to secure, no plugin zoo quietly phoning home from your pages.
Who can actually see your data.
You, 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. And Jezweb's operators, who run the platform. 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 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 is versioned, so there's a history to look back on and a way back if you change your mind. Your website can't drift somewhere you didn't take it.
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 in its own namespace on Cloudflare's Workers for Platforms, the machinery built for precisely this kind of separation, and it has its own dedicated database and its own file storage. Not a partition, not a customer column in a shared table: your own. Your members, orders, bookings and files live there and nowhere else.
This used to be the paragraph describing what we were going to build. It is finished and it is running for every site on the platform, which is why the wording changed. 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.
Ask us the awkward questions
If your industry has data rules, or you just want to know exactly where a customer's phone number ends up, ask. The answers above are the real architecture, and we're happy to go a level deeper.
Ask about your data