Skip to content
VOXELIA 3D

Practical Guide · GDPR, Upload & Image Data

Data protection for building photos and 3D models

Building, roof and facade photos are not automatically harmless. If people, plates, private areas, metadata or precise location context are identifiable, a technical dataset can become personal data. This guide explains how to prepare imagery for 3D, CAD, BIM, orthophoto and viewer workflows with data minimisation in mind.

  • 12 min read
  • Voxelia 3D
  • Germany, Austria & Switzerland
  • Art. 4GDPR scope

    personal data and processing

  • 7principles

    EU Commission summary

  • 3 stepsVoxelia review

    intake, masking, delivery

Why data protection matters for 3D models from building photos

Voxelia processes supplied imagery into 3D models, CAD files, BIM inputs, orthophotos and viewer data. Privacy is therefore not only a capture issue. It also affects upload, processing, storage, sharing and delivery.

The European Commission defines personal data as information relating to an identified or identifiable living person. Processing includes collection, storage, organisation, alteration, use, disclosure and erasure. For imagery, upload and photogrammetric reconstruction can therefore be relevant processing steps.

When building photos can contain personal data

A photo of a roof or facade is not automatically personal data. It becomes sensitive when people are visible or when context makes a person identifiable, for example faces, licence plates, name plates, doorbells, private interiors, exact location metadata or time stamps.

The European Commission also notes that pseudonymised or encrypted data can remain personal data if re-identification is possible. Blurring, cropping or stripping metadata can reduce risk, but is not automatically irreversible anonymisation.

System / datasetSuitabilityBest forPractical note
Roof surface without people or sensitive surroundingsusually suitable3D roof model, PV planning, roof areas, CAD traceGeometry remains usable while irrelevant edge areas can be reduced for delivery.
Facade with passers-by, windows or platesrequires review and maskingorthoplane, facade CAD, damage mappingIdentifiable people, vehicles and private interiors should be masked before broad sharing.
EXIF/XMP with GNSS, timestamp and camera datatechnically useful, privacy-relevantphotogrammetry, georeferencing, quality reviewKeep metadata for reconstruction when needed; reduce it for external delivery.

Image details to review before upload

Privacy risks usually come from incidental information: a car near the facade, a person on a balcony, a name plate at the entrance or a visible private interior. These details may be irrelevant for geometry but still travel through the project folder.

Risk scenarioWhy it mattersTypical symptomCountermeasure
Identifiable peopleFaces or body features can identify a personPeople remain visible in textures, orthophotos or viewersmask before public or broad sharing; use internally only for the defined purpose
Licence plates and name platesThey can become identifying in combination with project contextPlates remain readable in high-resolution imagerymake plates, doorbells and names unreadable before delivery
Private areasBalconies, gardens and windows may reveal private circumstancesIrrelevant edge areas remain in viewer or textureslimit crop, reduce edge areas and review textures before release

Data minimisation without losing geometry

GDPR principles summarised by the European Commission include purpose limitation, data minimisation, storage limitation, integrity and confidentiality. In photogrammetry, this means preserving the information needed for the technical purpose while avoiding unnecessary personal detail.

Original photos can be important during reconstruction because sharpness, overlap, EXIF/XMP and camera parameters affect model quality. After reconstruction, delivery can often be leaner: CAD lines instead of full texture, an orthophoto crop instead of the full surroundings, or BIM elements instead of raw imagery.

Practical workflow for clients before upload

A good privacy workflow is short, repeatable and tied to the intended planning output.

  1. Define output

    Clarify whether you need mesh, CAD trace, orthophoto, BIM, PV model or viewer.

  2. Review imagery

    Check people, plates, interiors, names, neighbouring properties and sensitive edges.

  3. Treat metadata deliberately

    Keep EXIF/XMP when needed for reconstruction; minimise it for external delivery.

  4. Define masking and crop

    Decide what should be masked, cropped or delivered at lower detail.

  5. Document the delivery

    Record which raw data was processed and which exports are delivered.

What should remain in a CAD, BIM or viewer delivery

Planning teams do not always need all source images. Derived geometry, point clouds, cropped orthophotos, CAD lines, IFC elements, roof areas or a protected viewer are often enough.

For PV, roof areas, pitch, azimuth, obstructions and shading context matter. For facades, planes, openings, damage zones and scale matter. Personal image details are rarely needed for those outputs.

FAQ: Privacy for building photos and 3D models

Are building photos always personal data?
No. A building alone is not automatically personal data, but people, plates, names, private areas or metadata can create personal context.
Should all EXIF and GNSS metadata be deleted?
Not always. Metadata can be important for reconstruction and georeferencing, but should be minimised for external delivery when not needed.
Can Voxelia reduce personal details before delivery?
Yes. Depending on the output, crops, textures, orthophotos, viewers and metadata can be prepared with less unnecessary personal context.
Is a 3D model less sensitive than raw photos?
Often, but not automatically. Textured meshes and orthophotos may still show people, plates or private areas.
  • Privacy
  • GDPR
  • Image Data
  • 3D Model
  • CAD/BIM

Related

Related guides

Get started

The first project is on us.

Upload your drone photos. Standard projects are ready in 24–48 hours – for PV*SOL, AutoCAD, GIS or the browser.

First project without a credit card · then from €45 per project · no subscription needed

Keep this ready

Keep the prepared €45 pilot by email

We keep package, scope, and article context. If you do not pay now, the prepared Stripe link can come back later.