Infrastructurebunny.net and the GDPR: agreement, role and data location.
bunny.net is a infrastructure tool. Most customers use it as a processor, it explains how to get its data processing agreement, and the data location depends on your account. Below: what to check and how to declare it.
Prefilled for you · Free to set up · No credit card
In short
- Category
- Infrastructure
- Usual role
- Usually a processor
- Data location
- Set per account or project
- Agreement
- Obtained through the vendor
What does bunny.net do with personal data?
Deliver and protect application traffic through DNS, CDN and network security services. That is how Privacyboard describes a typical use of bunny.net, as a starting point you can edit.
The data usually involved: iP addresses, HTTP request metadata, security logs and content passing through enabled services.
Is bunny.net a processor or a controller?
Most customers use bunny.net as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for infrastructure tools and it is what Privacyboard suggests.
As a processor, it needs a written agreement with you under Article 28, and you should know which subprocessors it uses. Confirm the role against your own agreement, because the way you use a tool can change it.
Where does bunny.net store personal data?
bunny.net does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable.
How to find yours: Check your account settings, the address you log in to, or the provider’s data processing terms. Support can tell you if you cannot find it.
Even when the main location is in the EU, ask whether subprocessors or support access involve a transfer outside the EEA, and record it if so.
Which legal basis usually applies to bunny.net?
For the usual use of bunny.net, companies most often rely on legitimate interests (GDPR Article 6(1)). DNS, CDN and network security are needed to run and protect the service for everyone who visits it.
The interest you would state: “Delivering our website quickly and protecting it against attacks and abuse.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
The balancing test is yours to do: the interest must be real, the processing necessary for it, and people’s rights must not outweigh it.
This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Sources: GDPR Article 6, lawfulness of processing, EDPB Guidelines 1/2024 on legitimate interest
Does bunny.net have a data processing agreement?
Checked on 5 November 2026. Vendors change their pages, so check the date.
bunny.net does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy.
What we noted when we opened the page: GDPR page says the DPA can be found in the bunny.net dashboard panel and links the sub-processor list. Footer names BunnyWay d.o.o.; no hosting location or transfer tool stated.
A page that exists does not mean you are covered. Whether the agreement applies to you depends on your plan and on what you accepted, so record the decision yourself in your vendor list.
Open the bunny.net reference pageHow to declare bunny.net
- 1
In your privacy policy
Name bunny.net as a recipient, say what it is used for (deliver and protect application traffic through DNS, CDN and network security services) and mention any transfer outside the EEA. Articles 13 and 14 ask you to tell people who receives their data.
- 2
In your vendor list
Add bunny.net with its purpose, the data involved, its role, its region and a link to the agreement. Privacyboard prefills all of this, you confirm or correct it.
- 3
In your processing register
Link bunny.net to the activities that use it, so each record shows its recipients. Article 30 asks the register to list the categories of recipients.
What to check before relying on bunny.net
- Check which services are enabled and what logs they keep.
- Review log retention and any regional processing options.
- Record IP addresses and request metadata in your policy where relevant.
- Record transfers outside the EEA and their safeguard.
Go online for free. Grow when you need to.
Free puts you online. Pro adds requests, domains and your team; Business, your brand only.
Free
$0 forever
No card, no time limit
For getting compliant and going online on your own.
Start for freeKey features:
- Privacy and cookie policies
- Vendor and processing registers
- Requests and breaches tracked
- Impact assessment screening
- Privacy center on privacyboard.io
- Cookie banner on 1 domain
- 1 person
No card needed
ProRecommended
$32 per month
Billed $384 a year Save $84
For taking requests, covering all your sites and working as a team.
Start with ProEverything in Free, plus:
- DPA for your clients
- PDF and Excel exports
- Email reminders
- Request form and replies
- Your own domain
- Banner on 3 domains, every choice logged
- Weekly site scan
- Complete DPIAs and TIAs
- AI assistant connector
- Up to 5 people, with roles
Cancel any time
Business
$109 per month
Billed $1,308 a year Save $240
For proving it to customers and auditors, under your brand only.
Start with BusinessEverything in Pro, plus:
- No Privacyboard mention
- Security section and vendor alerts
- Evidence pack in one click
- Banner on 10 domains, daily scan
- Up to 50 people
- Two-step verification required
- Activity log kept 3 years
Bank transfer on request
Questions, answered.
Is bunny.net GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how bunny.net is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it explains how to get a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.
Does bunny.net have a DPA?
bunny.net does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy. The reference page is https://bunny.net/gdpr/.
Is bunny.net a data processor?
Usually, yes. Most customers use bunny.net as a processor that acts on their instructions. Check your own agreement and how you use the tool, because the role can differ.
Which legal basis applies when I use bunny.net?
For the usual use of bunny.net, companies most often rely on legitimate interests (GDPR Article 6(1)). DNS, CDN and network security are needed to run and protect the service for everyone who visits it. The interest you would state: “Delivering our website quickly and protecting it against attacks and abuse.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
Where does bunny.net store data?
bunny.net does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable. How to find yours: Check your account settings, the address you log in to, or the provider’s data processing terms. Support can tell you if you cannot find it.
Do I need to mention bunny.net in my privacy policy?
Yes, if bunny.net handles personal data for you. The GDPR asks you to tell people who receives their data (Articles 13 and 14). Name the vendor or its category, say what it is used for and mention any transfer outside the EEA.
How do I add bunny.net to my vendor list?
In Privacyboard, pick bunny.net from the catalog. The purpose, the data, the suggested role and a link to its agreement are prefilled, and you confirm each one. Creating a workspace is free.
Similar tools
Compare all infrastructure tools
Privacyboard is not affiliated with bunny.net. Names and logos belong to their owners and are used only to identify the tool. This page summarises public documents as checked on 1 November 2026; it is guidance, not legal advice, and it does not certify any vendor.