Privacy statement

Who Bouw365 is, and who this applies to

Bouw365 is software for Dutch contractors and small construction companies. You use it to manage your customers, quotes, projects, planning, hours and invoices.

This statement is about the platform itself: the application at app.bouw365.nl, including when you use it in the browser on your phone. Whether there is an installed app, and what it uses from your device, has a section of its own further down. The marketing website bouw365.nl has its own, shorter notice. That one covers a visit to the website, not what happens inside your account. This is the document that notice points to.

There are two kinds of reader, and this statement is written for both:

• You have an account with Bouw365 yourself. You are a contractor, or you work at a construction company that uses Bouw365.
• You are a customer of such a company and you received a quote, an invoice or a link to a customer portal. Your data then passes through this software, but the construction company is who you should turn to. The next section explains why.

You can ask us about this statement, and about the data in your own account, at info@bouw365.nl. That is the standing address at which Bouw365 answers privacy questions. Who controls the data inside your account is set out in the next section.

Bouw365 is a trading name of Dromenbouw, a sole proprietorship (eenmanszaak) registered with the Dutch Chamber of Commerce (KVK) under number 95836861, VAT ID NL005176149B49, with its registered address at Locatellistraat 4 A, 5654 JE Eindhoven, the Netherlands. Wherever this statement says that Bouw365 is the controller, Dromenbouw is the party that is.

What this document is and is not: it describes what the software does. It is not legal advice, and nowhere does it say that Bouw365 complies with the GDPR. That is a judgement for a lawyer to make, not something a text can decide about itself.

Two roles: what Bouw365 decides, and what you decide

This is the most important section of this statement, and it is not a legal nicety. Two kinds of data run through Bouw365, and one of them is our responsibility while the other is yours.

The first kind is data about you as an account holder and about your business. Your name, your email address, your login details, your company details, your subscription. Bouw365 decides what this data is needed for and how it is handled. For that data Bouw365 is the controller, and a question about it comes to us.

The second kind is the data you enter. About your customers, your contacts, your subcontractors, your suppliers and your own staff. You decide what you record, why, and how long you keep it. For that data you are the controller and Bouw365 is the processor: we handle it because you hold a subscription, not on the basis of any arrangement of our own with your customer.

What that means in practice:

• If one of your customers asks what data you hold about them, or asks you to erase it, that is your obligation. Not ours.
• Bouw365 gives you tools for it, and we are responsible for those tools working properly. What they can do and where they fall short is set out in the section on your rights.
• If such a request reaches Bouw365 by mistake, we refer it on to the construction company. Bouw365 does not decide what happens to a contractor's customer data.

So: if you are reading this as an account holder, both halves are about you. One covers your own data, the other covers what you do with other people's. If you are reading this as the customer of a contractor, that contractor is your point of contact, and the rest of this document mainly tells you how their software handles your data.

What happens if data leaks follows that same split, and you would rather know it beforehand. If data about you as an account holder leaks — your login details, your company details, your subscription — Bouw365 is the party that has to judge what happened and whether it must be reported. If data you entered about your customers leaks, you are the controller: the judgement and the report are yours, even when the cause lies with us. In that case the GDPR puts us under a duty to assist you with it.

What is in place for that belongs here too, because a duty without a path is an empty duty. The honest answer is: not much. This software has no reporting procedure written into it, no button that starts a notification, and no agreed window within which you hear from us. We looked for one while writing this text — in the code and in our own processing register — and found nothing. What does exist is your own company's log: it records who did what and when, including a support session by an administrator, and that is the first place to look during an investigation. If you notice something, or you need something from us to make your own assessment, email info@bouw365.nl. This is a known open point, and it is written here because you ought to know it — not because it should stay that way.

One caveat belongs with this. The split above follows from how the software works and has not been tested by a lawyer. It is recorded as a starting point in Bouw365's own processing register, and that register says of itself that it is an assumption.

What Bouw365 holds about you as an account holder

This is the half for which Bouw365 is the controller.

About your business:

• trading name and company name, registered address, phone number, Chamber of Commerce (KVK) number, VAT number and IBAN
• your subscription: which plan, since when, what has been paid and what is outstanding
• your logo, your brand colours and your terms and conditions, if you upload them

About you personally:

• your first and last name and your email address
• your password, never as text but as a one-way fingerprint (bcrypt): a fingerprint that cannot be turned back into your password, not even by us
• if you switch on two-factor authentication: your authenticator secret and your recovery codes
• your profile photo and your signature as an image, if you set them
• your role in the company, your contract hours and the private link to your calendar feed
• your notification preferences, your language choice and your progress through the tour of the app

What for: to let you log in, to make the app work, to invoice your business and to be able to reach you about your account. This data is not used to track you across websites or apps, and not to sell you anything beyond your subscription.

When you sign up, we also record how your business found its way to Bouw365, as far as that is known: your answer to the question how you found us (that question is optional), the name of the website you came from to the sign-up page — only that name, not the address of the page — and the campaign code if there was one in the sign-up link. No cookie or tracker is needed for this: the sign-up page sends it along with the form. What for: seeing through which channels customers arrive. The legal basis is a legitimate interest of Bouw365, and it is recorded once and never added to afterwards.

One thing is recorded per user, and it belongs here because the name of the table hides it. Every time the help assistant in the app gives an answer, a row is written: who asked, which conversation it belonged to, what page you were on, and when. In our system that row is called 'feedback', but it is written every time — including when you never click thumbs up or thumbs down.

What it is for: measuring how often the assistant has to say it does not know. That figure decides whether it is any use. But anyone who sorts those rows by user can read back which screens you were using the assistant on, and when. That is a browsing trail. Our App Store declaration says so too: browsing history and usage data, with analytics as a purpose. The legal basis for it is not the performance of your subscription but a legitimate interest of Bouw365. The same goes, in this section, for what is recorded of your progress through the tour, and elsewhere in the system for the records that serve as proof. Whether such an interest carries the recording is a question for a lawyer, not for this text.

What does not happen to it: the trail stays inside Bouw365. Nothing goes to an ad network, nothing goes to a data broker, and it is not combined with data about you from other parties. If you delete your account, these rows are deleted — not anonymised but gone.

There are three moments at which this data leaves the platform, and no others. At registration your Chamber of Commerce number goes to the Dutch Chamber of Commerce to check that it exists; no names are sent with it. A postcode and house number go to PDOK, a Dutch government service, to fill in the street and town; no names are sent with those either, and not your IP address. And for your subscription, your company name, the email address of the person taking it out and the amounts go to Mollie, the party that collects the payment.

One thing about that last point is worth saying separately. Mollie only collects your own subscription to Bouw365. The invoices you send to your customers are paid outside Bouw365. Not a single payment from a customer of yours passes through Mollie.

What you enter about your customers and your staff

This is the half for which you are the controller. Bouw365 stores and processes it for you, but what goes in is up to you.

What the app offers for it:

• customer details: name, address, email address, phone number, and if you fill them in also Chamber of Commerce number, VAT number and IBAN
• contacts and work addresses, with free-text notes about how to get onto a site
• leads, quotes, measurements, projects, extra work, invoices and credit notes
• site-visit reports, with free text about what the customer wants and what is still unclear
• site photos, daily notes from your field workers, and messages in the project chat and the customer portal
• reports with fields you design yourself, and the signature they are signed off with
• about your own people: role, contract hours, skills, certificates, hours worked, absence and signed-off work instructions

Four of those deserve your attention, because you are responsible for them and the software does not solve them for you.

Absence has a type called 'sick'. That is data about someone's health, and heavier rules apply to it than to ordinary staff records. The app shields the type and the explanation server-side from anyone who should not see them, and leaves them out of the calendar feed. What the app does not do is decide whether you are allowed to keep that record in this form. That is a question for you and your occupational health service.

You design report fields yourself. The app checks that a value matches the type of the field, but not whether the field should exist at all. A date field named 'Resident date of birth' works perfectly well. Whatever you put in a template ends up in every report made from it.

There is a measurement about your own people that is easy to miss. If you switch the norm engine on for a task, the app records how many hours were budgeted for that task and how many were actually booked against it. Those actual hours come from the time sheets of the people who worked on it. If one person did the task, that is a record of how long that person took over that work. Switching it on is an office decision and not the field worker's, and this touches employment law and not only privacy.

Free text passes through no filter anywhere. A lead titled 'Jansen family renovation', a daily note about the people living in a house, a note on a work address: it stays exactly as you typed it, including after you have anonymised the customer. No automated clean-up can reliably recognise a name in running text, and Bouw365 therefore does not attempt it.

Two things leave the platform because a user taps something, going to a party that user chooses. Anyone who puts their planning into their own calendar app passes the task name, project name, street, house number, town and the notes on a scheduled job to the maker of that calendar app. And anyone who taps 'Navigate' in the app sends the street, house number and town of the work address to Google Maps; the postcode is not included. In both cases the user decides who receives it, and Bouw365 cannot see which party that turned out to be.

One thing goes out automatically. When you enter a postcode and house number for a customer or a work address, the app looks up the street and town at PDOK, a Dutch government service. Only that postcode and house number are sent, through the Bouw365 server: no names, and not the user's IP address.

The link to such a calendar feed is a private link with no expiry date. Anyone who gets hold of it can keep reading that team member's planning until the link is replaced by hand. That can be done in the app.

What the app on your phone uses

This section is about what Bouw365 uses from your device, and the short answer is: little, and never behind your back. The camera and the microphone only come on because you switch them on. Your location is never requested. Below is what happens for each of them — and where something does not happen, that is written down too, because it is just as much information.

Camera. When you add a photo, the app opens your phone's file picker and asks for the rear camera. Your device asks your permission for that. Bouw365 does not switch the camera on itself, is not watching through it, and does not read your photo library. You choose which photos you send, and you can select more than one at a time.

What happens to that photo afterwards belongs here too, and something changed there on 11 September 2026. The app rebuilds the photo, on your own device, before anything is sent. Everything your phone writes into the file disappears in the process: the GPS location where the photo was taken, and also the make and model of your device and the camera settings. What is left is the image itself. The dimensions are capped right away at 2048 pixels on the longest side, so that a photo can get out even when the signal is poor. What comes out is a JPEG — or a PNG, if you put a PNG in: a JPEG has no transparency, and it would turn transparent parts black. After that the file goes to Bouw365's storage, with a small display version alongside it.

This happens to every photo you add to a file, and not only on the field worker's screen: on a task or a daily report, on a quote or a receipt in the office part, on a diploma or certificate you upload for a member of staff, and on a photo you attach to a project message. The last two skipped the step until 11 September 2026; since that date they take the same route, and there is an automatic check on the software that raises the alarm as soon as a new way to send a photo appears that would skip this step. If your browser cannot read the file — an iPhone HEIC on a computer is the ordinary case — the photo is refused with a message, and not sent unprocessed after all. That is awkward, and it is deliberate: the other choice would mean your location goes out precisely then.

Two images take a different route, and that belongs here because otherwise the sentence above is read too broadly: your profile photo and your company logo. Those are not rebuilt on your own device but only on our server, after the file has been sent. So the original — with everything your camera wrote into it, the GPS location included — does reach our storage, where it is then overwritten by the processed version. If that processing fails, for instance because the file type is not supported, the original file stays behind and there is no clean-up step that removes it. These are rarely camera shots, but 'on your own device, before anything is sent' does not hold for these two.

One piece of data is deliberately rescued before the rest is thrown away: the moment you took the photo. It travels along as a separate field, so that a photo you took in a basement at nine in the morning does not end up in the file under the later moment it was sent. If the file carries no capture time — a screenshot, or a photo you pick from your gallery — that field stays empty and nothing is claimed about when the photo was taken.

Two limits to that processing, and both of them belong here. The first: it happens in the app on your device and not on our server. Nothing checks on receipt that it happened, so an outdated or modified version of the app could skip the step. That is why it is written here as 'the app takes it out before anything is sent' and not as 'we store no location data' — the latter would be a promise about something we do not enforce at our end. The second: it does not work retroactively. Photos uploaded before 11 September 2026 sit there unprocessed, including the GPS location where they were taken. For such a photo taken at a customer's home, that puts their home address in the file, not as a typed-in address but as a measurement. There is no button today to delete a single photo that has been sent; those only disappear when the whole company is closed down. A photo still waiting in the queue on your own device you can delete yourself — see 'Working offline' below.

Microphone. In a few places there is a button to dictate instead of type. It uses your browser's speech recognition. Bouw365 does not receive the audio and does not store it anywhere; what ends up in the field is the text. But what your browser does with the audio is your browser's business, and in most browsers the recognition does not happen on your device but at the browser maker's end. That cannot be established from our software, and it is set down here as a warning rather than as reassurance.

Notifications. Notifications live in the app itself, some of them also go out as email, and since 12 September 2026 Bouw365 can send them to your device while the app is closed. Such a notification carries the same title and text as in the app, and those can contain the name of a customer or a project — 'Extra work requested — Kitchen Jansen'. That is a choice: a notification that does not say what it is about is not a notification but a beep. The consequence belongs here plainly, and it is this: that text appears on your device's lock screen, so anyone who sees your phone lying on the table can read it without opening the app and without knowing your passcode. Amounts, margins and cost prices are never in it; it goes no further than the title and the text of the notification.

Permission for those notifications is asked by your browser, not by Bouw365, and only after you have pressed the button yourself. It works per device and per browser: turn it on on your phone and it is still off on the company tablet. Turning it off works with the same switch. There is one thing we cannot do, and it belongs here before you choose: if you refused it in your browser's dialog, Bouw365 cannot ask again. That choice lives in your browser's settings, and only you can undo it there.

To be able to deliver a notification, Bouw365 stores one address per device, created by your browser, with two keys next to it. When you log out, that address is thrown away right away — also because a site phone goes from hand to hand, and the next user should not get your notifications on their screen. The delivery itself runs through your browser's push service: Google for Chrome, Edge and Android, Apple for Safari and for the web app on an iPhone or iPad, and Mozilla for Firefox. That service gets your device's address, the time, and the notification in encrypted form. Google, Apple and Mozilla receive no readable content in the process — the title and the text are encrypted with keys only your own device holds. What they do see is that there was a notification for your device, and when.

Location. The app never asks for your location. Your field workers are not tracked: no continuous location fixing, not as a default setting and not as an option either. That is a product principle. The only measured location anywhere in the system was the one inside the photos above, and since 11 September 2026 it is taken out on your own device before the photo is sent. For photos uploaded before that, it is not.

Device data. Your IP address and information about your browser are recorded at four moments, and at no others: when a customer accepts a quote, when a customer approves extra work, when a customer signs a report, and when a member of staff signs off a work instruction. Those are moments of proof, recording who approved what and when. If a customer rejects a quote or a piece of extra work, or asks a question, no IP address is kept.

Working offline. If your field worker has no signal, the app keeps a handful of actions in the storage of their own browser until there is a connection again, and since 11 September 2026 it keeps the photos themselves there too. That means a photo can sit on that device for a while — until the app is opened again somewhere with a signal. What sits there is the processed photo: without a location, with the capture time beside it. Clocking hours is deliberately not one of them, because a timestamp replayed later is the wrong timestamp; for a photo that does not apply, because it carries its own moment of capture. What sits in that queue sits on that device and nowhere else, until it is sent.

Two things about that queue belong here honestly, and both have been arranged this way since 11 September 2026. The first: the queue survives signing out. A browser's storage is tied to the address of the app and not to your session, so on a tablet you share with colleagues the not-yet-sent photos of the previous user are still there after they sign out. They are not thrown away — that would destroy a photo that exists nowhere else — but they no longer go out under your name either: since that date every waiting photo carries who took it, and a photo belonging to someone else stays put with a message saying it belongs to another user. The second: you can delete a waiting photo yourself, with a confirmation that says it will then be nowhere at all. That is the only delete button there is for a photo, and it only works while the photo is still on your device — once it has been sent, what is written above under the camera applies.

Contacts, calendar, Bluetooth, health data on your phone: none of it is read.

Who sees the data

Inside your company, people see what belongs to their role. Field workers are not shown purchase prices, margins or company-wide figures, and neither is the customer portal. That is enforced on the server and not merely hidden on screen.

Bouw365 itself can also look inside your environment, and that belongs here rather than in the small print. A platform administrator can open a support session in your account, for instance to investigate a fault. That session is read-only: nothing can be changed while it is running. It lasts half an hour at most, and the access ticket for it is single-use and valid for two minutes.

That you can check up on this belongs in the same breath. The start of such a session is recorded in two places, and one of them is yours: a line goes into your own company's audit trail, and you can read it back in the app under Audit. It names who looked in and the reason they gave. The second line goes into a log kept by the platform administrators, outside your company.

What those logs do not do belongs here too. They record the start of the session, not what the administrator looked at during that half hour. And you get no automatic notification of it today — you have to look in that screen yourself.

Outside your company, the parties below receive data, because the software needs them to work. The list is not maintained by hand. It is derived from the same register the software itself runs on, so if a party is added it appears here of its own accord.

One flow in that list carries more weight than the rest and does not stand out in a table: the invoice email. When you send an invoice, the PDF goes along as an attachment through the email provider. That PDF holds your company details (name, address, Chamber of Commerce number, VAT number, IBAN, phone number, website and your logo), your customer's details (name, address, email address, and if you filled them in their Chamber of Commerce number and IBAN as well), the invoice lines, and, if you switch that setting on, the signature of whoever sent it. The customer's VAT number only appears when VAT is reverse-charged. For a sole trader that is often a home address and a personal bank account, belonging to two people at once, in one file.

There is no ad network in that list, no analytics service and no party that resells data. There is no tracking software in the app: nothing links your behaviour across websites or apps, and nothing goes to a data broker.

Two recipients are deliberately absent from the list, because you choose them and Bouw365 does not: the calendar app a team member puts their planning into, and Google Maps when someone taps 'Navigate'. What goes there is described in the section on your customers' data.

And for completeness, because 'these parties and nobody else' ought to be true: while the software is being built, the web framework we use sends anonymised build statistics to its maker. That happens on the machine Bouw365 is built on, not in your browser, and no user data is sent with it.

What goes to the United States

Some of the parties above are US companies. For most of them it is a matter of storage, hosting and sending email. One party receives substantive free text, and it deserves its own explanation: Anthropic, the maker of the AI behind five features in the app.

This is what leaves the platform, feature by feature:

• The AI quote draft: the customer's name and town, the title of the lead, the four free-text fields from the site-visit reports, the measurements, the lines from your price book, the sections and line descriptions already in your estimate, and the instruction you type yourself. The customer's email address, phone number, VAT number, Chamber of Commerce number, IBAN and address are not included, and neither are your purchase prices and margins.
• The AI invoice draft: the customer's name and town, the project name, the draft lines, the lines of earlier invoices on that project, the completed extra work, the lines from the accepted quote, the lines from your price book and the instruction you type yourself. Here too: no address, no email address and no internal figures.
• The extra-work radar: the daily note on a task, verbatim, whoever writes it — a field worker or someone in the office — plus a summary of the agreed scope without amounts and without customer details.
• The site-visit assistant: the raw note you type or dictate. Not a single database field is sent along.
• The help assistant in the app: your question, your language, the page you were on and the text of at most three help articles. No customer details and no figures about your business.

Two things you need to know, because they do not stand out by themselves. The extra-work radar runs in the background: whoever writes the daily note is not shown, at that moment, that their text is leaving the platform. And in both the extra-work radar and the site-visit assistant, free text goes along word for word. Whatever someone writes down about a resident's health or home situation, along the lines of 'she has trouble walking, the shower needs to be step-free', is then part of what is sent.

For the AI quote draft and the AI invoice draft, exactly what was sent is kept. It sits in the database next to the draft, so that you can see later what a proposal was based on.

Then the question you are probably asking next: is an AI model trained on that? We cannot establish that, so we make no claim about it either way — not that it happens, and not that it does not. What becomes of the text once it reaches the provider depends on the terms and arrangements that apply there, and those are not in our software. A statement that reassured you on this point would be making a claim about another company that it cannot check.

What we can tell you is what our own side does. The call goes to the provider's ordinary endpoint, and there is no setting switched on in our software that rules such use out or limits how long the provider keeps the content. If you want certainty about what happens to it, Anthropic's own terms are where that is set out — and what is written there can change without us noticing.

There is one key for all companies together, and no European endpoint is used. Whether this transfer to a country outside the EU is lawful, and on what legal basis, is a legal question. This statement describes what happens and does not answer it.

How long data stays

An honest answer belongs here, and it is not the answer you read in most privacy statements. Bouw365 does not delete anything automatically after a set period. There is no clock running down and then wiping data.

What does exist, and it is a different thing:

• Each company has a setting for how long you want to hold on to customer data. That setting deletes nothing. What it does is this: every Monday morning you get a notification in the app and an email listing the customers who have been inactive since before that period and whom you have not yet anonymised. Reviewing and clearing them out is up to you. The default value is a common rule of thumb for the Dutch statutory retention obligation on business records, and it is not legal advice.
• There are exactly two periods the software enforces itself, and both of them are on a downloaded file rather than on your records: a requested hours-export file expires after seven days, and the export package you receive when a company is closed down is cleaned up after thirty days.

Beyond that, data disappears at two moments. When you anonymise or delete it yourself, and when the company is closed down, at which point the entire administration is cleared out.

One category deliberately stays, including after an erasure request: sent quotes and sent invoices are never altered. At the moment of sending, a frozen copy is made, and the customer details in it are as they were then. That is not an oversight. A sent invoice is a document subject to a retention obligation, and an invoice that changes afterwards is no longer an invoice. It does mean that anonymising a customer does not touch those copies, and you ought to know that.

Something similar holds for a message you delete in the project chat. It disappears from view but not from the database. The text stays in four places: the row itself, a search index attached to it, the log entry that the deletion itself wrote and that holds the old text, and — if someone was mentioned in it — the notification made from it, carrying the first 140 characters and the author's name. Three of those four are nowhere to be seen in the app.

That the software enforces no retention period does not mean there should not be one. Setting it sits with Bouw365 for the account data and with you for your customers' data. It is recorded as an open point in Bouw365's own processing register.

Your rights, and how to exercise them

You have the right to know what data is held about you, to have it corrected, to have it erased, to object, to have the processing restricted while one of those requests is running, and to receive your data in a common file format so you can take it elsewhere. Where to go depends on which half of the second section applies to you.

If you are the customer of a construction company, you go to that company. They entered your data and they decide what happens to it. If you cannot resolve it with them, you can lodge a complaint with the Dutch data protection authority, the Autoriteit Persoonsgegevens.

If you are an account holder, most of it can be done in the app itself. You edit your profile and your company details in the settings. Deleting your account is there too, under Account.

What happens when you delete your account:

• you are removed from the companies you belong to, with a line in that company's log recording that you left
• your profile photo and your signature are deleted from storage
• your name and email address are overwritten and your password is wiped; logging in becomes permanently impossible
• your notifications, your preferences, your recovery codes and your progress through the tour are deleted
• what belongs to the construction company stays: the quotes you sent, the invoices you issued, the projects you worked on

If you are the last owner of a company you cannot simply delete your account; you have to close that company first. A closure has a thirty-day cooling-off period, and you can withdraw it during that time. On the very next night after you request it, a full export package is built: all the data as files, plus your quotes, invoices and credit notes as PDFs. That package is the only copy you are left with of your records, because those are deleted afterwards.

Two traces do stay, so "everything is deleted afterwards" is not quite the whole story. The first is the closure itself: the company name, who requested it and when each step happened, because that is what shows whether the subscription was actually cancelled. The second is the platform administrators' log. That log does not hang off your company and is not cleaned up by a closure. It holds the administrator's email address, their IP address, and a free field recording what a given action changed from and to — and that free field can carry data from your company. No period is attached to either trace.

For the requests that reach you about your own customers, the app has two buttons on the customer page. One produces a file with that customer's data, for an access request. The other anonymises the customer, their contacts and their work addresses.

What those two buttons do not do belongs in the same breath, because otherwise you will think a request has been dealt with.

The access file is a selection, not a complete set. What is in it: the customer's own details, their contacts, their work addresses, one line per lead, one line per project, and the invoice headers for each project. From the customer's own details the Chamber of Commerce number, the IBAN, the link to your accounting package and the date of an earlier anonymisation are left out, and leads created from a manual quote are omitted without the file saying so.

Heavier than those columns is everything that hangs off a lead or a project, because that is left out entirely: the free text of the site-visit reports, the frozen quotes carrying the customer's full name, address, email address, Chamber of Commerce number and IBAN, the photos, the messages in the project chat and the customer portal, the reports, the extra work, and the draft lines an AI invoice proposal kept. Invoices that are not attached to a project are missing too.

The anonymisation overwrites the name, email address, phone number, notes, VAT number and address of the customer, their contacts and their work addresses, but leaves the Chamber of Commerce number, the IBAN and the reference to your accounting package in place. Free text is not searched, and the frozen copies inside sent quotes and invoices stay as they were.

For your subcontractors and suppliers there is no button at all. A self-employed person you recorded as a supplier sits in the app with their name, email address and phone number, and there is no way to anonymise or delete them — not automatically and not by hand either. If they ask, the only way out today is closing the whole company down.

So anyone who wants to handle a request in full cannot rely on the list above. It is what we found when we went through the code, and not necessarily everything. These points are recorded as findings in Bouw365's own processing register and are known; they are not left out here because they are unflattering.

Cookies and what sits on your device

There are no tracking cookies, no analytics cookies and no advertising cookies. For that reason there is no consent banner either: there is nothing to choose, and a banner asking consent for something that does not happen is misleading.

What does sit on your device:

• a login cookie, so that you stay logged in from one page to the next
• a language cookie, remembering whether you want the app in Dutch or English
• in your browser's storage: the queue of actions you carried out offline, and the photos you took offline, until they have been sent
• in the customer portal: the name you filled in with a message, so that you do not have to type it again every time

The last two sit on your device only. They do not go to Bouw365 unless you actually send the action they belong to. You can clear them by deleting the site data in your browser; doing so will also lose you an offline queue that has not been sent yet, including the photos sitting in it.

Changes and contact

This statement was last updated on the date shown at the top of this page. If what the software does changes, this text is updated. The list of parties that receive data comes out of the software itself and moves with it automatically.

One such change happened on 12 September 2026, and it belongs here because leaving it out would let this document turn quietly untrue. Since that date Bouw365 can send push notifications. That makes your browser's push service — Google, Apple or Mozilla — a party that receives data from us, and those three have been in the list above ever since. Until that date this statement said the opposite about Apple; it was updated in the same rollout as the feature itself, not afterwards. Whoever builds the next feature that takes data to a new party updates this text before that feature goes live. That obligation is written here, in the document itself, and not only in our internal notes.

Questions about this statement, or about the data in your own account: email info@bouw365.nl. If it concerns data a construction company has entered about you, that company is your point of contact; see the section on the two roles.

You can always lodge a complaint with the Autoriteit Persoonsgegevens, the Dutch data protection authority.

Finally, once more, because the first section said it too: this statement describes what the software does. It does not establish that Bouw365 complies with the GDPR. That judgement belongs to a lawyer, and it is not made here.