In this guide
If you commission an app or a website that collects names, emails, payments or anything else about people, data protection law applies to what gets built. This checklist is written for the business owner, not the lawyer: what to agree with your developer, what to ask for in the product and what stays your own responsibility.
General information, not legal advice. Rules change and apply differently to each business, so confirm your own position with a solicitor, your accountant or the relevant authority.
1. Know who is who
Under the GDPR, the organisation that decides why and how personal data is used is the controller. A supplier that handles data on your behalf is a processor. In a typical commission you are the controller and your developer, hosting provider and email tool are processors or sub-processors. The Irish Data Protection Commission explains these roles on its controller and processor relationships page.
2. Map the data before the design
List every piece of personal data the product will touch: sign-up forms, contact forms, analytics, payment details, support messages, logs. For each, note the reason, where it is stored, who can access it and how long you will keep it. If you cannot explain why you need a field, remove it. Collecting less is the simplest privacy feature there is.
3. Put the processor contract in writing
GDPR Article 28 requires a contract between a controller and a processor. The DPC's practical guide to controller-processor contracts sets out the minimum terms and says, among other things, that the processor must help you meet your breach-notification duties and allow audits. Ask your developer how this will be covered, and do not leave it until after launch.
4. Ask for these features in the build
- Clear privacy notice, linked at every point where data is collected.
- Consent captured only where consent is your lawful basis, with a record of when and what was agreed.
- A way to export a person's data and to delete it on request, including from backups on a sensible schedule.
- Role-based access so staff see only what they need.
- Audit logs for sensitive actions.
- Encryption in transit and at rest, and hosting options in the EU where your provider offers them.
- Retention rules that remove data automatically when you no longer need it.
5. Plan for a breach before it happens
If a personal data breach is likely to pose a risk to people, the controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, according to European Commission and DPC guidance. A processor must tell the controller without undue delay. Agree who calls whom, how quickly and through which channel, and keep the numbers where you can find them.
6. Watch third-party tools and cookies
Analytics, chat widgets, fonts and embedded videos can send visitor data to other companies. Ask your developer for a list of every third-party service on the site and decide whether each is necessary. Where non-essential cookies or similar technologies are used, you will need to handle consent properly.
7. Keep ownership of the paperwork
Software helps, but a privacy notice, records of processing and staff awareness are organisational tasks. A good developer will give you plain-language notes about how the product handles data so your own review is easier. Zenocta's GDPR-aware software engineering service is engineering support of that kind and is not a compliance certification.
A short pre-launch test
Before go-live, ask for a walk-through: submit a form, request your data, delete the account and confirm what is left behind. If your developer cannot demonstrate it, it is not ready. When you want to talk through a real project, use contact and see pricing for how projects are priced.
Try it live
Open the real thing: demos run in a new tab with sample data, apps link to their own page.
- GServiceGDPR-aware software engineeringPrivacy features built into the product: consent, export, deletion, retention.
- WServiceWeb application developmentWeb apps built with access control and audit logging.
- SBrowse allSecurity at ZenoctaHow Zenocta approaches security in the software it builds.
- ABrowse allAll Zenocta servicesCustom software, apps, websites, AI automation, ERP and CRM from one team.
- TBrowse allTalk about your projectSend a few lines about what you need and get a scoped proposal.
Frequently asked questions
01Does using a GDPR-aware developer make my app GDPR compliant?
No. Compliance depends on your whole organisation, including policies, training and legal advice. A developer can build features that support your obligations, such as consent records, export and deletion.
02Do I need a contract with my developer?
If your developer or host processes personal data on your behalf, GDPR Article 28 requires a written contract. The Data Protection Commission publishes a practical guide to what it should include.
03Can my app or website be hosted in the EU?
Where the chosen hosting provider offers EU regions, yes. Confirm the options during scoping, together with any other providers that touch your data.



