Powstania Warszawskiego 15
31-539 Kraków
Apps Value is a Polish company under EU law, building mobile apps for businesses across the Nordics, Benelux, the DACH region and beyond. GDPR compliant app development is not a checkbox we add before launch: data stays in an EU region in your own cloud account, the processing agreement is with an EU entity, and the whole project runs on your working hours.
Most "app development for Europe" pages are written from outside Europe. Ours is written from inside it: an EU registered company, an EU processing agreement, EU hosting by default, and a team that is awake when you are.
Different markets, one requirement in common: personal data has to be handled under GDPR by a partner whose obligations are enforceable in the EU, not explained in a footnote.
Denmark, Sweden, Norway and Finland. Field, inspection and service companies with high expectations on data ownership, and a strong preference for owning the cloud environment and the code. We deploy into your account from day one.
Dutch and Belgian companies used to short lines and direct answers. Same working day, calls in English, decisions in days rather than weeks, and a fixed number instead of an hourly meter.
Germany and Austria, where the data protection officer is in the room from the first call. Processing agreements, sub-processor lists and audit trails are part of scope, and priced with it, not discovered later.
Swiss clients working under the revised FADP alongside GDPR. We are building a community app for a Swiss client this year, and Zurich is a short flight from Kraków when a meeting has to happen in person.
Same time zone as London give or take an hour, English speaking team, and for UK data the UK GDPR handled alongside the EU version, with hosting placed where your users are.
Where we are from. Public and regional bodies as well as private companies, including Liniowiec, an offline navigation app for over 1,000 km of Polish inland waterways.
Compliance that is added before launch is expensive and usually incomplete. These four decisions are made at the workshop and written into scope, so the app is compliant by construction.
Your backend and database run in an EU region, in a cloud account you own. Frankfurt, Amsterdam, Stockholm, Warsaw, Zurich for Swiss clients: you choose the region and it goes into the scope document. Backups stay in the same jurisdiction.
Because the account is yours, there is no migration when the project ends and no dependence on us to get your data out. Full export is a feature we build, not a favour we do.
Data minimisation is a product decision. Every field the app collects has a reason written next to it, consent is asked where consent is the lawful basis, and access, correction and deletion requests are flows in the app and admin, not tickets to engineering.
This is also where analytics and crash reporting are decided, because they are the most common way personal data quietly leaves the EU.
You sign a data processing agreement with a Polish company under EU law. It names the sub-processors, which for a mobile app always includes Apple and Google and usually a cloud provider and an email service, and it says which of them process outside the EU and under which transfer mechanism.
Your data protection officer gets this list at the workshop, not at the audit. If a service on it is a problem for you, we swap it before it is built in.
Source code in a repository under your account from the first commit. Developer accounts at Apple and Google in your company's name. The cloud in your name. Documentation of the data model and the integrations, so a different team could take over.
The one thing that stays with us is responsibility for what we agreed: the scope guarantee covers the delivered scope, and on larger contracts a one year warranty runs from launch.
Bring them. Region, processing agreement and sub-processors are exactly what the first call is for, and it saves a round of questions later.
Kraków is on Central European Time. For most of Europe that means the entire working day overlaps, which changes how a project feels: a question asked at ten is answered by eleven, and a demo happens in your afternoon, not at your breakfast.
Liniowiec is a Flutter navigation app for Polish inland waterways: over 1,000 km across more than 18 rivers, with offline maps as the core of the product and routes that arrive on the device by themselves when an administrator adds them.
The decision that made it work is a database schema designed properly before building, with versioned routes and correct relations between the data. The next stage extends the map stack, adds water level data and brings the app to WCAG AA.
A React Native community app for a client in Switzerland, launching this year, built under a non disclosure agreement. What we can say: a hard launch date, a scoped first version, and the data handled the way a Swiss client expects it to be handled.
The same rules apply to any European engagement: an EU or Swiss region for hosting, a processing agreement you can show your lawyer, and a fixed number for a defined scope. The commercial model is on fixed price app development.
Every project is scoped in a discovery workshop and priced as a fixed number per stage, invoiced in euros from an EU VAT registered company, with payment on acceptance of each stage. The scope guarantee is simple: everything agreed in the scope works, and if it does not, fixing it is our job.
Who does what, which systems exist, where the data has to live. Bring your DPO if you have one.
Output is a scoped document, a named EU region, a data inventory and a fixed number in euros.
The scope document and the processing agreement become attachments to the contract, under EU law.
Each stage ends with acceptance. Your own team tests during development, on the same working day as ours.
Stores, cloud and repository were already in your name. Warranty runs from launch, support optional.
Yes. Apps Value is a Polish company registered in Kraków, operating under Polish and EU law. Contracts, invoices and the data processing agreement are with that entity, and disputes fall under EU jurisdiction.
In an EU region of your choice, in a cloud account in your company's name. For Swiss clients a Swiss region is available. Backups stay in the same jurisdiction, and the region is named in the scope document.
Yes, as processor, under EU law, with a sub-processor list that names each service, its region and its transfer mechanism. Your DPO gets it at the workshop and can request changes before anything is built.
For any mobile app, Apple and Google, through the app stores and push notifications. Everything else can be chosen for EU processing. Where a service outside the EU is the right choice, we say so up front and document the transfer mechanism.
In euros, from an EU VAT registered company, per stage on acceptance. For business clients in other EU member states the reverse charge mechanism normally applies; your accountant will recognise the format.
Yes. Kraków has direct flights to most European hubs and we travel for kickoffs and key milestones. Day to day work runs on video, on your working hours.
Both, from one codebase for iOS and Android. The choice is made at the workshop based on your existing systems and the platform features you rely on. Liniowiec is Flutter; the Swiss community app is React Native.
We handle UK GDPR alongside EU GDPR, place hosting where your users are, and document the transfer basis between the two. Working hours overlap by seven hours on a normal day.
Bring how the work runs today, which region your data must stay in, and who signs off on data protection. You will get a straight answer on scope, a named region, and a fixed price in euros for a first version.
Thomas SiudutCo-Founder and CEO, Apps Value30 minutes, no preparation needed. Bring your DPO if you like.