Questions founders ask before they scan

Yes, it’s built for them. Small and medium companies want to know what’s wrong on their website and how to fix it, usually without a compliance team to ask.

Peeky scans your site against the rules of each market you sell in, such as the EU, UK and US, and every finding comes with a fix your developer can use as it is. Legal sign-off and full audits stay with lawyers and auditors.

The home page shows how that looks for four kinds of team.

It’s a good moment for it. A first scan catches the usual early slips, like analytics that start before the banner is answered, or a payment provider your privacy policy never mentions.

Each finding comes with a prompt you can paste into an AI coding assistant, so most fixes fit in an afternoon. Next month’s scan shows whether they held.

Trial is free for one website in one jurisdiction. See the plans.

Mostly, yes. The report is in plain words, and in a shop most fixes are settings in your apps. A banner with no Reject button, a countdown that restarts on every visit, a reviews widget that doesn’t say how reviews are checked.

When something does need code, the fix and the prompt are ready for whoever you ask.

See a real finding.

Yes. Scan each site before handover so it ships clean, then keep the monthly scan going as part of the maintenance plan you sell. With Accreditation, the badge sits in the client’s footer and shows what the latest scan saw.

Plus is €79 once, per company, so each client company gets its own. See the plans.

Yes, with Organizations. Add the companies from a deal pipeline, an accelerator intake or a grant round, with each one’s agreement, and every one gets the same checks, written down the same way. You don’t need an audit team of your own for the first screen.

After that Peeky scans each site every month, so a change shows up in the next report instead of at the next review. It reads public pages only, so treat it as a first look, not a sign-off. See Organizations on Pricing.

Almost always. If your site collects anything about visitors, analytics included, the rules in the EU, UK and US expect a privacy policy people can find from any page.

Peeky checks that yours loads and that it names the services your site talks to. When something’s missing, the report suggests the wording and the fix prompt can add it. A lawyer should still read the final policy, because only they can say whether it covers what your business does.

The rule is in the Handbook: EU-09, UK-10 and US-13.

Not always. You need one when your site sets cookies it doesn’t strictly need, and analytics, ads and most chat widgets count.

If you have a banner, Peeky checks that nothing loads before the visitor answers, and that saying no is as easy as saying yes.

The Handbook has the rule in EU-01 and UK-01.

Not from the outside, and Peeky won’t say it either. Only a regulator or a court can.

What Peeky does is visit your public pages and note what it saw against 16 EU checks: cookies, privacy policy, data requests, reviews, subscriptions and withdrawals, accessibility and the connection. You get a fix for each finding. Your lawyer decides what it means.

See how a scan works.

That’s not something a scan can decide. Peeky can show you what it saw, and a court or your lawyer says what it means.

The US check looks at ADA Title III and the Unruh Act. Peeky runs automated accessibility tests on your public pages and writes up what they found. Tests like these catch only part of what matters, so someone still needs to try the site with a keyboard and a screen reader.

The Handbook entry is US-06.

Your public pages, and the members area if you give Peeky a sign-in for a demo account. Peeky opens them in an ordinary browser, answers the cookie banner both ways and reads the policies you link to. It never port-scans or tries to get in where it isn’t allowed.

Cookies are about a quarter of it. The other checks cover privacy policies, data requests, reviews and countdowns, subscriptions, accessibility, marketing email and the connection itself.

Every check is on How it works.

It checks cookies, and a lot more. Cookies and consent are about a quarter of the checks. The rest look at privacy policies, data requests, reviews and countdowns, pricing and subscriptions, accessibility, marketing email and the connection itself.

A cookie checker lists what your site sets. Peeky also reads what your policy says about it, what your reviews and prices show, and whether a visitor can find how to cancel. Every check is on How it works.

Yes. Peeky notes which cookies and requests show up before anyone touches the banner, and what changes once a visitor says no or yes.

Anything that starts tracking before a yes is what EU-01 looks at.

It’s a close look at how a website behaves, measured against a set of rules. A person or a firm usually does it.

A PeekWell scan is lighter. Peeky visits your public pages the way a visitor’s browser does and writes down what it saw. The report is for information and doesn’t replace a formal audit.

See how a scan works.

Partly. Peeky runs automated accessibility tests on your public pages, in the EU, UK and US checks.

Tests like these can’t tell how a site feels with a screen reader. Treat the findings as a good start, and have a person try the site too.

The Handbook entries are EU-10, UK-12 and US-06.

Yes, the ones a visitor can see. Peeky checks whether countdowns and “only 2 left” counters reset themselves, and notes costs added late and boxes ticked in advance.

Whether a timer misleads anyone is for a regulator to say. Peeky writes down what the timer did.

Read the rule in EU-12, UK-14 or US-08.

Not quite. Peeky can see when reviews and testimonials give no way to check them, or read like they were paid for. It can’t know who wrote a review.

Anything it flags is marked as a possibility, not a fact.

The Handbook has EU-11, UK-13 and US-01.

It’s enough to build your cookie list, which is what it’s for. Cookiebot’s own help pages say its scanner flags two things: cookies that aren’t blocked before consent, and data sent to countries without an adequacy decision.

Peeky also clicks Reject and watches what keeps running, then reads your privacy policy against what your pages really send.

The Handbook has EU-02, on a Reject that doesn’t stop the tracking.

WAVE is a good free check, one page at a time. Peeky runs automated accessibility tests on the pages it visits in every scan, next to everything else, so a slip shows up the next month.

For a full audit with screen-reader testing, bring in a specialist. The Handbook entry is EU-10.

Usually three. A consent banner if your site uses analytics or ads, a privacy policy that matches what you do, and a regular check that the site behaves the way both say.

PeekWell is that check, and it covers accessibility, reviews, prices and subscriptions too. See how it compares with other tools.

A score on top, then a list of findings. Each one says what Peeky saw, why it matters and what to do next, with the evidence underneath. Checks that passed are in there too.

The summary comes first. The detail is there when your developer needs it.

A full sample finding is on How it works. The Handbook shows how the score is calculated.

Yes. Every finding ends with a fix your developer can use as it is, and a prompt you can copy.

Peeky also links the rule behind it. The fixing is still yours, and the next scan shows whether it worked.

See one in full on How it works.

Usually, yes. In the EU and UK, people can ask what you hold about them, and the rules expect your site to show them how.

Peeky checks that a way to ask exists and that a visitor can find it. It can’t see how fast you answer.

The Handbook has EU-07 and UK-09.

In short, that people see the renewal terms before they buy and can cancel as easily as they signed up. The details differ by place.

Peeky reads your pages for the terms and checks how easy the way to cancel is to find. It can’t test a live cancellation.

The Handbook has EU-13, UK-14 and US-09.

Partly. Drip pricing is when extra costs show up one step at a time, after you’ve seen the first price.

Peeky notes costs added late on the public pages it can see. It never goes through a checkout, so what happens at the till stays out of view.

The Handbook entry is US-08.

Yes, briefly. Security headers are instructions your server sends with each page, telling the browser how careful to be.

Peeky checks that the connection is encrypted and that the usual headers are there. That’s a look at what your server sends, not a security test.

The Handbook has EU-15, UK-15 and US-15.

Yes, the ones that show on your pages. Peeky looks at how your sign-ups ask for permission and whether there’s a clear way to opt out.

It can’t see the emails you send.

The Handbook has UK-11 and US-14.

In part. The EU check runs accessibility tests on your public pages and ties what it finds to the Act.

Automated tests can’t judge everything the Act is about, and whether it applies to you is a question for your lawyer.

The Handbook entry is EU-10.

It can help you get ready. The report is a dated list of what Peeky saw on your public pages, check by check, and it’s easy to hand over.

It isn’t a sign-off, though. Investors usually ask for more than a look at public pages. With Accreditation, the monthly scans also show how your site has held up over time.

See what each plan includes.

Someone you work with asked us to look, or we looked because we thought you’d want to see it. Either way, Peeky opened your public pages in an ordinary browser, like any visitor. It never tries to get in where it isn’t allowed.

To see what it found, open the link in the email and type the address it was sent to. That preview was made for your site, and you don’t need an account. Only the people we invited can open it.

You can also ignore it. If your legal team already knows what your site needs, keep doing what you’re doing. Reply to the email and we won’t write again.

If you want the whole report, sign up and move to Plus. You’ll see every finding with its fix, and with Accreditation Peeky scans again every month. Prices are on Pricing.

A small graphic on a website that tells visitors something about the business. Some are just an image anyone can paste in.

PeekWell’s accreditation badge works differently. It shows what the latest monthly scan observed, and it switches off when the score doesn’t hold.

See a sample badge.

The result of your latest monthly scan, across every check PeekWell runs. It shows while that scan holds the score, and it switches off by itself when a scan doesn’t.

It goes with a public accreditation page, where the detail lives, so a customer or an investor can see the date and the result.

The sample on How it works lets you step through five months.

Yes, with Accreditation. It’s €19 a month, comes with Plus, and includes the badge and the public page.

The badge shows what the latest scan saw. If a month’s scan doesn’t hold the score, it comes down.

Prices exclude VAT. See the plans.

The score from your latest monthly scan, a card for each region and the score history.

The page says what the scan observed and when. It’s for information only and not legal advice.

A sample page for an imaginary site is on How it works.

No. Nobody approves your website, and no regulator stands behind the badge.

The accreditation page and the badge record what Peeky observed on your public pages in the latest monthly scan, and when. They don’t say your website follows any rule.

See what the page shows on How it works.

Trial is free. Plus is €79 once, per company. Accreditation is €19 a month, and it comes with Plus.

Prices exclude VAT. Pricing has pounds and dollars too.

Because websites change, and so do the rules. A new script, a rewritten policy, a new reviews widget. One scan shows one day.

Each monthly scan runs every check again. When a rule changes or a new law starts, the checks are updated and the next scan uses them. The accreditation page is built on this: the badge shows while the latest monthly scan holds the score.

See Accreditation.

Yes, once. Trial gives you one website in one jurisdiction, with the score, the summary and one finding in full. You don’t need a card.

See what Trial includes.

Yes. Accreditation is monthly, so you can cancel whenever you like. It runs to the end of the month you’re in, then the public page and badge come down.

Plus is a one-time payment, so there’s nothing to cancel.

More on Pricing.

A year of PeekWell with monthly scans is €307. A cookie scanner such as CookieInspector is $119.99 a year for consent on five sites. PeekWell covers consent, your privacy policy, accessibility, consumer rules and security basics, on up to ten websites in each of three jurisdictions.

A specialist accessibility audit starts in the thousands, and an outsourced DPO from €125 a month. Prices are before VAT, as each tool published them on 15 October 2026. See what it costs next to other tools.

A DPO advises you, trains your team and deals with the regulator, and the website is a small part of that job.

PeekWell gives a DPO, or you, the evidence for that part every month for €19. See the plans.

No. The report says what Peeky saw and what the rule expects. What that means for your business is a question for your lawyer.

For information only. Not legal advice.

The Terms say the same.

No, and they work well together. Cookiebot and CookieYes run your banner. Peeky tests that banner from the outside, four ways, and checks the rest of your site in the same visit.

A banner from a well-known provider can still be set up in a way that misses one market’s rules. Tracking on until someone opts out may suit US visitors, but in the EU and the UK nothing should load before a yes. The fix is usually a setting in your banner tool.

The Handbook has EU-03 and UK-02.

No. Peeky reads your pages the way a visitor’s browser does, and the members area when you give it a sign-in for a demo account. It never port-scans, never tries to get in where it isn’t allowed, and never runs security tests of any kind. PeekWell is not a security testing service and cannot be used as one.

What Peeky reads, and what it can’t, is on How it works.

Not quite. A clean report means Peeky didn’t see a problem on the pages it scanned. It can’t see your contracts or the emails you send, and it doesn’t speak for any regulator.

See what Peeky can’t see.

For a small or medium company’s website, it can. OneTrust runs privacy programmes for large organisations: consent, data requests and vendor risk, priced by quote.

If the website is what you needed it for, PeekWell checks it end to end for €79 once, per company, and €19 a month, next to a low-cost banner tool. See the comparison.

For legal advice, yes. Peeky tells you what it found, which law it touches, how regulators have treated it and how to fix it. For your privacy policy, that goes as far as suggested wording and a prompt that makes the change.

Your lawyer reads the final text and gives the opinion. Hand them the report and the evidence is already there.