Data processing agreement
Version 1.4, published and in force from 13 October 2026. It replaces version 1.3 (and with it version 1.0), which applied until then; versions 1.1 and 1.2 never took effect.
If the language versions differ, the Dutch text prevails.
This data processing agreement is an annex to the EPC-Expert Pro terms and conditions and governs the processing of personal data by Wild Oak BV, trading as EPC-Expert Pro, on behalf of the customer, in accordance with Article 28 of the General Data Protection Regulation (GDPR). It applies automatically as soon as the customer creates an account and processes personal data of third parties (end clients) in the service.
Processor: Wild Oak BV, trading as EPC-Expert Pro, Boechtstraat 27 bus 2, 1860 Meise, company number 1039.490.996
Boechtstraat 27 bus 2, 1860 Meise
Contact: info@epc-expert-pro.be
1. Parties and roles
For the data of its end clients (address, contact details, photos and measurements of the property), the customer is the data controller within the meaning of the GDPR: it determines the purpose and means of that processing. For that same data, Wild Oak BV is the processor: it processes the data exclusively on behalf of and on the instructions of the customer, never for its own purposes.
For the customer's own account data (name, email address, company details, payment status), Wild Oak BV is the data controller; this is governed by the privacy policy, not by this agreement.
2. Subject matter, duration, nature and purpose of the processing
This agreement governs any processing of personal data that Wild Oak BV carries out on behalf of the customer when providing EPC-Expert Pro: storing, displaying, calculating, exporting and transferring file data to the VEKA database, and supporting that processing with AI features. The customer instructs Wild Oak BV to also derive anonymised, aggregated statistics from it, as described in chapter 16 of the terms and conditions.
The agreement applies for the term of the main agreement (the terms and conditions) and for as long as Wild Oak BV retains customer data, including during the 90 days after it ends, until the data is deleted under chapter 4 of this agreement and chapter 17 of the terms and conditions.
3. Categories of data subjects and data
The data subjects are: occupants and owners of the property, the client themselves when they are a natural person, their contact persons, and people recognisable in a photo. The data processed is: name, address and contact details of the client; the EAN number, cadastral data and energy consumption of the property; photos of the property and its installations, including photos in which people may be recognisable; the property's location; plans and measurements; the text a user types themselves in a question to A+; documents the end client uploads themselves via the client preparation link, automatically pre-sorted with AI; and, where applicable, a signature.
Wild Oak BV does not process special categories of personal data within the meaning of Article 9 GDPR, unless the customer itself places such data, outside normal use, in a free-text field or attachment; that is then the customer's own responsibility.
4. Wild Oak BV's obligations
Wild Oak BV processes personal data solely on the basis of the customer's documented instructions, unless a legal obligation requires otherwise. The customer's instructions are set out in this agreement, the terms and conditions, and the settings they choose in the app. By accepting the terms and conditions, the customer also instructs Wild Oak BV to access their account for support and quality control, as described in chapter 18 of the terms and conditions. If the law obliges us to process data differently, we notify the customer in advance, unless the law prohibits this. If we consider an instruction to violate the GDPR, we let the customer know immediately. Everyone at Wild Oak BV who has access to customer data is bound by confidentiality.
Wild Oak BV takes appropriate technical and organisational security measures, as described in annex 2. It assists the customer, within reasonable limits, in responding to data subject requests (access, rectification, erasure, portability) and in meeting the customer's obligations regarding security, data breaches, data protection impact assessments and prior consultation (Articles 32 to 36 GDPR).
Wild Oak BV notifies the customer of a security incident that may affect the customer's personal data within 48 hours after becoming aware of it, with the information available at that time about the nature and scope of the incident.
Subject to reasonable notice and during normal office hours, the customer may verify compliance with this agreement based on the documentation Wild Oak BV makes available for that purpose (including this agreement, the security overview in annex 2, and relevant sub-processor certifications where they exist). If that documentation demonstrably falls short, the customer, or an independent auditor bound by confidentiality, may carry out an audit once a year or after a data breach, with 30 days' notice and at the customer's expense, unless the audit reveals a material shortcoming.
After the main agreement ends, Wild Oak BV returns the data by export, and permanently deletes it after the period and according to the procedure in chapter 17 of the terms and conditions.
5. Sub-processors
The customer gives Wild Oak BV general authorisation to use the sub-processors listed in annex 1. Wild Oak BV notifies the customer of a new sub-processor, or a change to an existing sub-processor, at least 30 days in advance. Within that period the customer may raise a reasoned objection. If we find no solution to a well-founded objection, the customer may cancel immediately, with a refund of the prepaid part and the unused credits.
Wild Oak BV imposes the same obligations on each sub-processor as set out in this agreement, to the extent relevant to that sub-processor's task. Wild Oak BV remains fully liable to the customer for its sub-processors' compliance.
6. Transfers outside the European Economic Area
A number of sub-processors process data outside the EEA or may gain access to it: Anthropic and Voyage AI (AI features), Google (coordinates, day route, Solar and 3D roof reconstruction), Resend (email), hCaptcha and Cloudflare. The safeguard for each party is listed in annex 1: the EU Standard Contractual Clauses and, where the party is certified, the EU-US Data Privacy Framework. The current transfer basis of each sub-processor may change; Wild Oak BV monitors this and updates annex 1 where necessary.
The other sub-processors in annex 1 process data within the European Economic Area.
7. File context sent to the AI features
When the customer or a user asks A+ a question, only the technical, construction-related context of the file relevant to that question is sent: for example the building type, year of construction, insulation values, or the number of photos per category. This selection is made through a fixed list of allowed fields, set out in the source code.
From the file itself, we deliberately do not send a client's name, address, email address or phone number, nor free-text notes or file names. A plan, photo or nameplate that the user has read is, however, sent to the AI service in full. If a name or address appears on it, for example in the title block of an architect's plan, it is sent along. The same applies to whatever the user types themselves in a question.
Documents the end client uploads through client preparation are automatically pre-sorted with AI: the document or photo is sent to the AI service in full, without file name or other file data. This suggestion is never binding: the assessor confirms, corrects or rejects it themselves before the file ends up under a card or piece of evidence.
8. The client portal (client preparation)
When the customer has its end client upload documents or photos through the client portal, the customer remains responsible for informing that end client about the processing of their data, in accordance with Articles 13 and 14 GDPR.
The upload link expires 30 days after the scheduled appointment, or 30 days after it is created if there is no appointment. Documents uploaded through that link become part of the file and from that point follow the same rules as the other file data.
9. Liability
Wild Oak BV's liability under this data processing agreement follows chapter 21 of the terms and conditions, with the same cap, the same exclusions and the same exceptions, including a data breach caused by a fault of Wild Oak BV.
10. Term, amendment and precedence
This agreement applies for as long as Wild Oak BV retains customer data, including during the 90 days after it ends, until the data is deleted under chapter 4 of this agreement and chapter 17 of the terms and conditions. Amendments to this agreement follow the same procedure as amendments to the terms and conditions.
In the event of a conflict between this data processing agreement and the terms and conditions regarding the processing of personal data, this data processing agreement prevails.
Annex 1: sub-processors
This table lists the sub-processors Wild Oak BV currently uses for the EPC-Expert Pro application. We only include parties we can confirm in our own code and configuration.
| Sub-processor | Purpose | Region | Safeguard |
|---|---|---|---|
| Supabase | Database, authentication and file storage for the application | France, Paris (EU) | Storage within the EEA; any access from outside the EEA falls under the EU Standard Contractual Clauses |
| Cloudflare | Hosting and security for the website and the application | Global network | EU Standard Contractual Clauses where applicable |
| Mollie | Processing payments and subscriptions | Netherlands (EU) | Processing within the EEA |
| Sentry | Application error reporting | Germany, Frankfurt (EU) | Storage within the EEA; any access from outside the EEA falls under the EU Standard Contractual Clauses |
| Google (Geocoding, Routes, Solar API, Cloud Run) | Converting an address to coordinates, day-route optimisation, estimating roof orientation and sun exposure, and 3D roof reconstruction | United States (Geocoding, Routes, Solar); Cloud Run in Belgium (europe-west1) | EU Standard Contractual Clauses |
| Resend | Sending email from the application: transactional emails and export emails | United States | EU Standard Contractual Clauses |
| Anthropic | AI features: A+, reading a floor plan from an architect's plan, the nameplate scanner, the catalog look-up and sorting documents from client preparation | United States | EU Standard Contractual Clauses |
| Voyage AI | Searching and ranking the inspection protocol for A+ | United States | EU-US Data Privacy Framework (via MongoDB) and Standard Contractual Clauses |
| hCaptcha | Captcha after failed sign-in attempts | United States | EU Standard Contractual Clauses |
| Hetzner Online GmbH | Server for the VEKA data entry | Germany (EU) | Processing within the EEA, data processing agreement Art. 28 GDPR |
This list may change. A new sub-processor or a change of region is announced as described in chapter 5 above. We also request open government data from Digitaal Vlaanderen (a Flemish public authority); this is not a sub-processor. We also use OpenStreetMap Foundation (United Kingdom, adequacy decision) for map tiles for the day route and parcel map, and Google Fonts for typefaces in the app; both receive the user's IP address.
Annex 2: security measures
Wild Oak BV takes, among others, the following technical and organisational measures. Where a sub-processor holds its own certification (for example ISO 27001 or SOC 2), we refer to that sub-processor's own documentation rather than restating that certification here.
- Encryption of data in transit (TLS) and at rest at the database provider
- Database-level access control per customer (row-level security), so a customer can only reach its own files
- Two-factor authentication available for every account
- A brake on repeated failed sign-in attempts
- Support access to the customer's account is only for a reason recorded internally, is limited per session, and is fully logged internally; never for payments, the customer's security settings or deleting the account, as described in chapter 18 of the terms and conditions
- Automatic database backups
- Separate development and production environments
- Access to production data limited to those who need it for their role
- A procedure for monitoring and reporting security incidents
- For the VEKA data entry on our server: a sealed-off container per data entry session, wiped afterwards
- Data from that session lives only in memory, never on disk
- Outbound traffic from that sealed-off browser goes only to the VEKA database, the government sign-in pages (authenticatie.vlaanderen.be and the federal sign-in service) and the provider of the digital key the customer chooses (itsme, myGov.be or Smart-ID)
- Identity check of the signed-in assessor before anything is filled in
- No database keys or long-lived access tokens on that server
- If the customer chooses a security code, the app encrypts the username, password and code for that single data entry session with a key that exists only in the container's memory. The encrypted block is deleted as soon as the server retrieves it, and after a few minutes at the latest. The password and code are never stored or logged in readable form; the username only if the customer chooses to have it remembered
- An employee of Wild Oak BV may watch the data entry on the server live, only during a session in progress, to follow it and resolve errors; the live viewing itself is not recorded (in a session where live viewing is possible, screenshots for the report and error tracing are kept for fourteen days, other run files for 30 days; never during sign-in, when live viewing is interrupted), and at the customer's request live viewing can be switched off for their account
Change log
Version 1.4 (published and in force on 13 October 2026; replaces version 1.3): annex 2 (security measures) has a new item 16 on live viewing of the data entry on the server by an employee of Wild Oak BV, only during a session in progress and without recording of the viewing (in a session where live viewing is possible, screenshots kept for fourteen days, other run files for 30 days; live viewing is interrupted during sign-in), in line with the new article 6.3 of the terms and conditions. It is switched off for the customer's account on request. No new sub-processors are added.
Version 1.3 (published and in force on 8 October 2026; replaces version 1.0 and versions 1.1 and 1.2, which never took effect): annex 2 (security measures) was adapted to the rewritten chapter 6 of the terms and conditions, under which the VEKA data entry now takes place only on a server operated by Wild Oak BV. Outbound traffic from that sealed-off browser (item 12) now also goes to the federal sign-in service and to the provider of the digital key the customer chooses (itsme, myGov.be or Smart-ID), and a new item 15 describes how the username, password and code are handled when the customer chooses a security code: encrypted with a key that exists only in the container's memory, the encrypted block is deleted as soon as the server retrieves it and after a few minutes at the latest, the password and code are never stored or logged in readable form, and the username only if the customer chooses to have it remembered. In annex 1, the restriction that the Hetzner server is active only if the customer chooses it was removed. The previous text of annex 1, Hetzner row (version 1.2), read: “Server for the VEKA data entry, only if the customer explicitly chooses this”. No new sub-processors are added: itsme, myGov.be and Smart-ID are the customer's own identity providers. The previous text of item 12 (version 1.2) read: “Outbound traffic from that server goes only to the VEKA database, authenticatie.vlaanderen.be and itsme”.
Version 1.2 (published on 25 September 2026, effective from 24 November 2026): annex 1 (sub-processors) and annex 2 (security measures) were extended for the VEKA data entry on a server operated by Wild Oak BV, the new option described in chapter 6 of the terms and conditions. Annex 1 now includes Hetzner Online GmbH (Germany, EU) as the hosting party for that server, active only if the customer chooses this themselves. Annex 2 was extended with: a sealed-off container per data entry session, wiped afterwards, data kept only in memory, outbound traffic limited to the VEKA database, authenticatie.vlaanderen.be and itsme, an identity check before anything is filled in, and no database keys on that server.
Version 1.1 (published on 25 September 2026, effective from 24 November 2026): chapter 4 (customer instructions) and annex 2 (security measures) were updated to match the changed chapter 18 of the terms and conditions. Wild Oak BV may, for support and quality control, access the customer's account with the same rights as the customer, no longer only read-only; this happens for a reason recorded internally, is limited per session, and is logged internally.
Version 1.0 (25 September 2026): first publication of the data processing agreement.