Can the wrong person see your business’s data, or your customers’?
On some sites, changing one number in a link opens another customer’s order, or the chat assistant will read out a customer’s address to anyone who asks. We check whether that works on yours, what your AI assistant can be talked into promising, and how your site copes with a busy afternoon. If something is open, we show you exactly where and prove the fix without locking out your own customers.
For small businesses and AI-built apps that went live before anyone checked who can see what.
A written report either way, including when the answer is “you’re fine.”
Three checks, one visit
What we check
Can one customer reach another customer’s data? How does your site behave when it gets busy, and why? What can your AI assistant be made to do? All three answered with evidence, in one written report.
Can customer A reach customer B’s data?
Orders, quotes, invoices, saved addresses, account details. If an identifier in a link or request is all that stands between two customers, we test whether yours holds.
Is it a login problem or a permission problem?
Many sites check that you’re logged in, then forget to check that the record belongs to you. Those are different failures with different fixes, so we separate them.
How does the site behave when it gets busy?
We watch the site with one visitor, then with several at once, inside a ceiling agreed in writing, in a quiet window, with a stop condition we honour. We report what a customer actually feels: how long pages take, whether any fail, and how much each visit has to download.
If it’s slow, why?
We open the page as it’s delivered to a customer and name the cause: an oversized script, a page that can’t be cached, missing compression. Then we point at the exact setting or line to change.
Can a stranger make your AI assistant act?
If a chat assistant or AI agent sits on your site, we check what an outsider’s words can make it do, whether typed into the chat or left in a review it reads. Could it show the wrong customer’s record, or send an email nobody approved? If a person is meant to approve its actions, we check that step holds. So far the method is proven on an AI model running on our own computer; yours would be the first live assistant we run it against.
What will it promise a customer?
In Alberta, what your AI assistant tells a customer counts the same as what a salesperson says. We test whether it can be talked into discounts, refunds or free shipping you never offered, and check every answer against your written terms.
Can a stranger run up your AI bill?
We check the AI plugins on your site against published security holes, look for AI keys left in the page, and see whether one visitor can send your assistant unlimited messages.
Who can read its conversations?
Chat logs hold what your customers typed. We find out where they are stored and whether anyone outside your business can read them.
Does the fix actually fix it?
After a change we test two things: the hole is closed, and your own customers still get into their own accounts. A fix that locks out the owner isn’t a fix.
Priced in the open
What it costs
One visit covers all three checks. You pay for the ones you want, and you can stop after any of them.
The checks
$500 for one check. $750 for any two. $1,000 for all three, because it is the same visit and the same report. Cross-account access, speed under load, and the AI assistant check. If we can’t test it properly, you don’t pay.
The fix and the retest, $250
We pin down the exact change (the line of code, or the server setting). Then we either hand it to your developer, or make it ourselves on a copy and publish only with your approval. Then we re-run the same test and prove the hole is closed and your own customers still get in. If the fix needs real development work, we quote that separately before starting. All three checks plus the fix and retest come to $1,250.
Nothing found? You still get it in writing
If the checks come back clean, the report says so and lists exactly what we tested. You have something in writing to show anyone who asks.
Prices are in Canadian dollars, agreed in writing before we start. No GST is added.
Before you book
What you get
Every time
- A written report with evidence, whether or not we find anything.
- Plain language, with any problems listed in the order we’d fix them.
- The exact code change if something is open, and the exact setting if something is slow.
- If you add the fix and retest: proof the fix didn’t break your own customers’ access or make the site slower.
- A load window agreed in writing first, with a stop condition we’ll honour: error rate, response time, or your word.
- Written permission and agreed limits before we touch anything.
What we won’t claim
- That your site is secure. We can tell you what we tested and what we found.
- That we tested everything. We test what we agreed to, and we name what we didn’t.
- That your site “handles 10,000 visitors.” We can say it handled twenty, on this page, on this date.
- That you’ll be a set percentage faster. We measure after the change and report the number we got.
Who you’re dealing with
About Bowden Security
Bowden is a family name. It’s Liam O’Connor’s middle name, and he named the company after his Nana.
Liam is a small-town boy from Morinville, Alberta, who grew up in Edmonton. The businesses he wants to help are the ones that make a city feel like home: the corner coffee shop, the family-run store, the tradesperson with an online booking page. They’re the least likely to have anyone checking their website for them, and they have the most to lose when a customer’s trust goes.
Bowden Security exists so they know what they’re up against, and which of their doors are open, before someone else finds out. Edmonton first, and small businesses anywhere else that need it.
He came from IT security and networking, which is where the useful paranoia comes from: watching how easily a convenience feature becomes an open door. A remote-access tool nobody removed. A sharing setting left open. A test account from 2019.
A lot of software is now built fast, often with AI, and shipped before anyone asked who can see what. That is the gap this exists to close, for small businesses on a platform and for founders who built their own app.
We’re starting small and saying so. Our checks so far have all been for businesses we’re connected to. On one of those live sites, two speed runs (5,801 and 6,801 requests) finished with no failures and found a 367 KB script inside the page that every visitor downloaded again on every visit.
Every report is reviewed before it reaches you, and every finding comes with the evidence behind it, so you or your developer can check it yourselves.
Start here
Tell us what your site does, and we’ll tell you if this check fits.
Email is best. Every message goes straight to Liam.
Edmonton, Alberta, Canada. Small businesses here and anywhere else.
General enquiries: info@bowdensecurity.com