For GDPR
Website security testing for GDPR.
GDPR Article 32 expects a process for regularly testing your security measures. A manual test with a written report, from $49, is practical evidence that you do.
By the Bug Circuit security team · Last updated
Who can test our website against GDPR security requirements? GDPR Article 32 requires security appropriate to the risk, including a process for regularly testing, assessing and evaluating the effectiveness of your measures. Bug Circuit tests your website and the API it calls by hand from $49 one-time, with a written report you can keep as evidence of that testing. We test technical security; we do not give legal advice or certify GDPR compliance.
The offer at a glance
| What you get | |
|---|---|
| Price | $49 one-time for one website (Essential, 3 audits within one month). Pro is $99 a month for 2 websites, Premium $199 a month for 5. |
| Who tests | A security engineer, by hand. Automated tools only help with discovery. |
| What you get | A written report: every finding with its severity, evidence and the exact fix steps, plus a remediation roadmap. |
| Timing | About 5 business days after testing starts. The 24-hour report is $15 more, and the $15 is refunded if the report is late. |
| Retest | Each audit after the first on a website retests the previous findings in the same report. |
| Not included | Fixes (quoted separately from the report), compliance certificates, and anything beyond one website on one domain without an Enterprise quote. |
| Before testing | You verify you own the website and sign the Authorization to Test. Nothing is tested without it. |
What the test covers
- Personal data exposure: forms, uploads, accounts and API responses that leak data.
- Access control: one user reaching another user's personal data.
- Encryption in transit: HTTPS, security headers and cookie flags.
- Logins and sessions for staff and customers.
- Third-party scripts loaded on pages that collect personal data.
What this is not
This is not a GDPR audit of your policies, records of processing or contracts, and it is not legal advice. It is technical evidence for the testing part of Article 32.
What the evidence says
The requirement to regularly test security measures is in GDPR Article 32(1)(d), Security of processing.
Frequently asked questions
Does GDPR require a penetration test?
Not by name. Article 32 asks for regular testing of the effectiveness of your security measures, and a penetration test is a common way to show that.
Do you handle our customers' personal data?
We test with accounts and records you create for testing, so we do not need real customer data.
How often should we test?
At least once a year and after major changes is a common rhythm. Each later audit retests earlier findings.
How much does it cost?
$49 one-time for one website (3 audits within one month), or Pro at $99 a month for 2.
Is Bug Circuit in the EU?
No. Bug Circuit is run by Ryzera Technologies in Sri Lanka and tests remotely. See our data processing terms.
Keep reading
VAPT report for complianceWhat auditors and enterprise customers look for.Data leak testingCan one user see another user's data?ISO 27001 testingEvidence for technical controls.Sample reportSee the report format before you buy.Bug bounty vs penetration testWhich to buy first, and what each costs.Is a $49 penetration test legit?What a $49 manual audit includes, and what it does not.Affordable penetration testingWhy a focused manual test can cost $49.
Start with the free check
See your public attack surface in seconds, then order an audit when you are ready.
Ready for the full manual audit? See pricing