CitizenClimate — Data Integrity & Methodology Protocol
For Verification & Validation Bodies (VVBs) · Document Version: October 2026 (app version 1.25)
What's new since the April 2026 version
-
Project site boundaries: upload a KML, KMZ or GeoJSON file, or draw the boundary on a map (Section 12)
-
Daily AI verification of new submissions; faulty entries are archived with a reason and their rewards reversed (Section 13)
-
Plan Vivo (PV Nature) biodiversity module: enrolment, Target Groups and automatic GBIF taxonomy (Section 14)
-
Plan Vivo Pillar Metrics 1–5, including satellite pillars from Sentinel-2 imagery, with a permanent run log and downloadable audit bundles (Section 15)
-
SDG dashboard: side-by-side community comparison for projects tracking one or two SDGs (Section 9)
-
New screenshots throughout, taken from app version 1.25
Screenshots come from the Usambara Forest Corridor Restoration demonstration project in Tanzania. Its field records are simulated for demonstration; its satellite metrics are computed from real Sentinel-2 imagery.
Summary for Auditors
Data Type | Deletable? | Timestamped? | Georeferenced? | Photo Evidence? | AI Verified? |
|---|---|---|---|---|---|
Survey submissions | No | Yes | Per survey (required or optional) | Where configured | Species fields only |
Faulty submissions | Archived only (with reason) | Yes | Preserved | Preserved | Preserved |
Species observations | No | Yes | Yes | Yes | Yes |
Grievances | No | Yes | No | Optional | No |
SDG survey responses | No | Yes | Yes | Where configured | No |
Biodiversity records | No | Yes | Yes | Yes | Yes |
Media files | No | Yes (upload metadata) | Via parent submission | N/A | N/A |
Key assurances for verification bodies:
-
Every record in the system has a creation timestamp that cannot be modified
-
No data is ever deleted — only archived with an auditable reason
-
GPS coordinates are captured at the device level at the time of field entry, not retrospectively
-
All AI species identifications are performed by independent third-party services and stored verbatim
-
Grievances are permanently recorded and cannot be suppressed by Project Developers
-
VVBs have direct read access to all project data — they do not rely on PD-generated reports
-
All data exports (CSV/JSON) include raw records, not just summaries
-
Every new submission with photos, recordings or free text is screened daily by an automated AI reviewer; faulty entries are archived with a reason, never deleted
-
Plan Vivo Pillar Metrics are calculated by the platform's servers, never typed in; every run is logged permanently and can be re-run independently from its audit bundle
-
Each project's site boundary is stored with its area in hectares and its source (uploaded file or drawn on the map)
CitizenClimate is built on Google Firebase infrastructure (Firestore, Firebase Storage, Firebase Authentication, Cloud Functions). Data residency and Google Cloud audit logging apply in addition to the application-level protections described above.
Summary for Auditors
Data Type | Deletable? | Timestamped? | Georeferenced? | Photo Evidence? | AI Verified? |
|---|---|---|---|---|---|
Survey submissions | No | Yes | Per survey (required or optional) | Where configured | Species fields only |
Faulty submissions | Archived only (with reason) | Yes | Preserved | Preserved | Preserved |
Species observations | No | Yes | Yes | Yes | Yes |
Grievances | No | Yes | No | Optional | No |
SDG survey responses | No | Yes | Yes | Where configured | No |
Biodiversity records | No | Yes | Yes | Yes | Yes |
Media files | No | Yes (upload metadata) | Via parent submission | N/A | N/A |
Key assurances for verification bodies:
-
Every record in the system has a creation timestamp that cannot be modified
-
No data is ever deleted — only archived with an auditable reason
-
GPS coordinates are captured at the device level at the time of field entry, not retrospectively
-
All AI species identifications are performed by independent third-party services and stored verbatim
-
Grievances are permanently recorded and cannot be suppressed by Project Developers
-
VVBs have direct read access to all project data — they do not rely on PD-generated reports
-
All data exports (CSV/JSON) include raw records, not just summaries
-
Every new submission with photos, recordings or free text is screened daily by an automated AI reviewer; faulty entries are archived with a reason, never deleted
-
Plan Vivo Pillar Metrics are calculated by the platform's servers, never typed in; every run is logged permanently and can be re-run independently from its audit bundle
-
Each project's site boundary is stored with its area in hectares and its source (uploaded file or drawn on the map)
CitizenClimate is built on Google Firebase infrastructure (Firestore, Firebase Storage, Firebase Authentication, Cloud Functions). Data residency and Google Cloud audit logging apply in addition to the application-level protections described above.
One App,
Many Uses
CitizenClimate is a mobile app for collecting environmental data in the field. It's used by communities, project developers, and independent auditors to monitor nature-based carbon credit projects — tracking things like biodiversity, land use, community wellbeing, and SDG (UN Sustainable Development Goal) progress. Think of it as a structured field notebook that syncs to the cloud, works offline, and rewards participation.

















