Minimise at capture
The first safeguard is not post-production: it is a narrow field of view, proportionate resolution, suitable timing, no unnecessary audio, and active avoidance of windows, private activity, people, and registration plates.
Civil Engineering
Public legal research report
Privacy in technical surveys.
A cautious publication framework for aerial photography, photogrammetry, LiDAR, SLAM, and topographic evidence around Chiappella.
What this report is — and is not
This is ColivingLiguria's documented, source-linked compliance position. It is not legal advice, an authorisation to fly, proof that a specific capture is lawful, or a substitute for a lawyer, data-protection professional, appointed surveyor, ENAC rules, or the applicable geographical UAS zone. Each actual operation requires its own documented check.
01 · EXECUTIVE POSITION
Raw does not mean publishable.
A technical survey may incidentally collect information relating to identifiable people. The absence of a clearly visible face is not decisive: movements, location, context, vehicles, entrances, or combination with other information may still make a person identifiable.
The public map and any future orthomosaic therefore use a distinct publication layer. The raw capture remains protected; only a purpose-limited, reviewed, genuinely anonymised derivative may be considered for public release.
02 · MANDATORY PIPELINE
Four gates before publication.
Quarantine the raw capture
Raw photographs, video, telemetry, and point clouds may remain personal data even when faces are not clear. They stay encrypted, access-controlled, logged, time-limited, and outside public repositories and ordinary shared folders.
Produce a separate publication layer
People, plates, private interiors, personal objects, and unnecessary third-party detail are removed or irreversibly obscured. Automated detection assists the review but never replaces the final human inspection.
Publish through an allowlist
Only reviewed derivatives enter the website. Publication records the purpose, source date, review date, reviewer, transformations performed, and the exact output approved for release.
03 · THIRD-PARTY LAND
Visibility from above is not permission to publish.
Prioritise owned or expressly authorised assets, public infrastructure, and the minimum surrounding geometry needed for orientation.
Do not target private life, windows, enclosed gardens, terraces, courtyards, or repeated movements of identifiable people.
Crop, mask, generalise, or remove unnecessary detail relating to third-party property before any public layer is generated.
Never attach allegations about owners, building offences, disputes, or private conduct to the public map.
04 · DATA SEPARATION
Three datasets that never collapse into one.
Raw acquisition
Original imagery, telemetry, point clouds, metadata, and integrity records. No website, no ordinary Drive sharing, no public preview.
Working model
Controlled technical derivative for measurement, modelling, and review. Access follows role and purpose; it is not automatically publishable.
Sanitised atlas layer
Only the minimal, human-reviewed output approved by the publication allowlist, with no identifiable people or unnecessary private detail.
05 · CHIAPPELLA FUTURE LAYER
The definitive map will follow the survey.
The present Chiappella level is deliberately an orientation view. It does not claim cadastral precision, topographic completeness, certified access, or ownership boundaries.
- 01Complete the professional topographic survey and drone capture.
- 02Generate and technically validate the orthomosaic and control geometry.
- 03Remove personal data and unnecessary third-party detail, then perform documented human QA.
- 04Publish only the separately approved atlas layer and its declared accuracy limits.
06 · DECISION GATES
Questions that must be closed before capture.
Is the purpose specific, documented, and compatible with every later use?
Can the same result be obtained with less area, detail, duration, or resolution?
What legal basis and balancing test apply if identifiable data may be collected?
Is a data-protection impact assessment required because the monitoring is systematic, large-scale, or otherwise high-risk?
Who is controller, processor, authorised operator, reviewer, and deletion owner?
What is the raw-data retention period, and how is deletion evidenced across copies and backups?
07 · OFFICIAL SOURCES
The law and guidance behind this position.
01Regulation (EU) 2016/679 — Articles 4, 5, 6, 24, 25 and 3502Italian Data Protection Authority — drones reference page03Italian Data Protection Authority — decision of 4 July 2024 on data collected with drones04EDPB Guidelines 3/2019 on processing through video devices05Italian Criminal Code, Article 615-bis — unlawful interference with private life
Operational stop rule
If purpose, legal basis, flight perimeter, privacy safeguards, retention, roles, or publication review are not documented, the capture or publication does not proceed. Uncertainty is recorded; it is not converted into permission.