The two-minute version. The legal document is the privacy policy.
Who owns the data?The organisation that commissions a project owns its project data. Knowledge shared by a community stays theirs to decide about; we use it only as agreed, in writing, per project.
Who can see it?Project data: the client and the people they name. Open datasets: everyone. Restricted Observatory layers: the role they were made for, and each restriction says why (privacy, sensitive species, client confidentiality, community agreement, licensing).
What can we publish?Methods and accuracy, always. Datasets only where the owner agrees and nothing sensitive is exposed. See Open Data.
Sensitive informationSacred sites, harvestable resources and vulnerable species locations are generalised or withheld from public outputs. Sensitivity is discussed with the people concerned, not decided for them.
How do communities participate?We explain what we would collect and why, listen, seek consent, walk the plots together where practical, and return results in a usable form. Where Indigenous land or knowledge is involved we follow UNDRIP and FPIC. Our approach.
Withdrawal and correctionA community or client can ask us to correct, restrict or withdraw information we hold about them or their place. Write to [email protected]; we answer within two weeks.
Personal data and dronesHandled under the privacy policy, aligned with Nepal's Privacy Act, 2075. Flights over settlements are announced locally beforehand.
What we do not claimWe do not claim a blanket data-sovereignty policy we have not adopted. The agreement is stated per project.