FAQ

Yes – we build with GDPR in mind from the start. Data protection is something we design in rather than bolt on, so the technical foundations are there: secure handling of personal data, sensible data retention, and the mechanisms needed to support things like consent and data-subject requests.
The full picture is project-specific, though. GDPR compliance also depends on how you operate the application – what data you collect, why, and how you manage it day to day – so it’s something we get right together, based on your particular use case.
Where you need it, we can also help with the legal side- privacy policies, terms and conditions, and similar – through our legal partner.

You do – for the work we create specifically for you. Once the project is paid for in full, all copyright in the code and works we’ve built for you transfers to you. We don’t hold onto what you’ve paid us to make.
A couple of standard exceptions, the same as in our terms:

• Third-party and open-source components – libraries, frameworks, and similar building blocks aren’t ours to give away. They stay under their own licences – but those licences let you use the finished product freely, for exactly what it was built for.
• Our own pre-existing tools and know-how – anything we created before, or independently of, your project stays ours. Your product is fully yours; the general tools we used to build it aren’t transferred.

The bottom line: the product we build for you is yours to own, use, and develop further – with the usual licensing that applies to any modern software.

Yes – always. We sign an NDA before we get into the detail of your idea, as standard practice, for your protection and ours. You can use your own template or one of ours, whichever you prefer.
So your idea is treated as confidential from the very first conversation – that’s simply how we work, not something you have to ask for.