How data moves through Landvex.

From field capture to delivered intelligence — every step documented

Full traceability. Every intelligence output can be traced back to its source observations. This document describes each transformation step, the controls applied, and the data retained at each stage.

8-Step Pipeline
1
Field Capture
Zoomer photographs target via quiXzoom app with GPS lock and EXIF metadata.
Show details
  • Zoomer accepts mission in quiXzoom app
  • GPS coordinates locked at capture start
  • Photo taken with full EXIF metadata: device model, timestamp, GPS coordinates, focal length
  • Submission uploaded with: image, GPS trace, timestamp, device fingerprint, mission ID
2
Identity Verification
Submitting Zoomer must be KYC-verified before any payout eligibility is established.
Show details
  • KYC verification is completed once, before the contributor's first payout
  • Each submission is linked to a verified contributor ID
  • Contributor ID is a pseudonymised hash — it is not stored in the intelligence output delivered to clients
3
GPS Validation
Submitted coordinates validated against mission target with tolerance thresholds.
Show details
  • Submitted coordinates validated against mission target coordinates
  • Tolerance: <50 metres for standard missions; <10 metres for precision missions
  • GPS accuracy class assigned: coarse / balanced / precise
  • Submissions outside tolerance: auto-rejected or flagged for human review
4
AI Image Review
Automated quality scoring across specification compliance, technical quality, and content relevance.
Show details
  • Image analysed for: specification compliance, technical quality, content relevance
  • Object detection confirms the target is present in frame
  • Quality score assigned on a scale of 0–100
  • Submissions below threshold: rejected with a reason code
  • Approval rate target: 85% or above
5
Human Review (edge cases)
AI-borderline submissions routed to a human reviewer with full decision logging.
Show details
  • AI-borderline submissions (score 40–60) routed to a human reviewer
  • Reviewer applies the mission specification to reach a final decision
  • Decision logged with reviewer ID and timestamp
  • Appeals process available for rejected submissions
6
Normalisation
Approved submissions converted to structured data points with full source attribution.
Show details
  • Approved submissions converted to structured data points
  • Entity extraction: location, object type, condition class, change signal
  • Temporal indexing: observation timestamped; version history maintained
  • Source attribution preserved throughout the normalisation process
7
Intelligence Aggregation
Observations aggregated by geographic unit; index scores calculated with confidence weighting.
Show details
  • Observations aggregated by geographic unit: district, city, region
  • Index scores calculated: Opportunity, Growth, Vitality, Infra Stability, Investment Confidence
  • Contradiction detection: aggregated observations compared against official data sources
  • Confidence scores calculated from: observation count, recency, and cross-validation results
8
Output and Delivery
Intelligence reports generated with full source citations and traceable audit trails.
Show details
  • Intelligence report generated with source citations
  • Each data point is traceable to its source observations via an audit trail
  • Delivery formats: web dashboard, API, structured report (PDF / JSON / CSV)
  • Data retention: per client contract — default is intelligence outputs retained 3 years, raw observations 90 days post-delivery
  • Deletion: right to erasure supported; deletion confirmed within 30 days
Audit Trail

Every intelligence output can be traced back to its source observations. On request, Landvex provides a complete audit package including: observation timestamps, GPS accuracy classes, AI review scores, human review decisions, normalisation logs, and aggregation methodology.

Contact: legal@landvex.com

Data Residency
EU-only — AWS eu-north-1, Stockholm
All data is stored in the EU on AWS eu-north-1 (Stockholm, Sweden). No data is transferred outside the EU without explicit client instruction and appropriate safeguards in place.
Request Documentation

Enterprise clients may request a complete data lineage package for their contract, including normalisation logs and aggregation methodology.

Request data lineage documentation for your contract
Related Documents
Sub-processors
Third-party processors used in the Landvex pipeline. GDPR Article 28 compliant.
Trust Centre
Infrastructure security, data quality guarantee, and verification chain.
Data Processing Agreement
GDPR Art. 28 DPA and Standard Contractual Clauses.
Data Quality
Methodology, accuracy metrics, and quality guarantees.