BSD-3-Clause map rendering technology used by the web GIS.
Privacy & Legal
Plain-language information about how BagulinAgriTech handles agricultural records, personal information, consent, authorized use, recommendations, third-party services, and record lifecycle controls.
Effective: October 4, 2026 · Project/municipal support deployment
Information processed, purpose, access, security, lifecycle, retention, and requests.
02Terms of UseAuthorized use, data accuracy responsibilities, prohibited use, availability, and attribution.
03Data & ConsentFarmer, farm, GPS, assessment, and signature/consent handling for field and research workflows.
04Agricultural Recommendation BasisHow BSWM and Department of Agriculture reference data supports fertilizer recommendations.
05Third-Party ServicesMapLibre, OpenStreetMap, Esri imagery, browser printing, and device/browser capabilities.
06Licensing & AttributionProject content, third-party components, and required source attribution.
1. Scope
This notice describes the information processed by the BagulinAgriTech web system when authorized personnel manage farmers, agricultural locations, soil assessments, IoT readings, maps, reports, accounts, and audit activity.
2. Information processed
Field and agricultural information
- Farmer name/identifier and assessment profile information.
- Farmland and Farm Plot identifiers, plot size, crop and crop-profile attributes.
- GPS coordinates and barangay/location information.
- pH, nitrogen, phosphorus, potassium, sampling/readings, fertility results, fertilizer recommendations, and generated reports.
System and security information
- User account identity, role, login/security events, and audit activity.
- Synchronization, IoT/device, data-source, timestamps, and operational metadata.
- Offline browser storage used by the Technician workflow until data can be synchronized or cleared according to the workflow.
3. Why the information is used
- To conduct and review soil assessments and preserve their history.
- To produce BSWM/DA-based fertilizer decision support and assessment reports.
- To map official/current fertility information and support municipal agricultural monitoring.
- To maintain data quality, accountability, audit history, synchronization, security, and system administration.
4. Record lifecycle and retention
BagulinAgriTech distinguishes operational, historical, and deleted records. Approved assessments can contribute to current official views. Archived/Superseded assessments remain historical and are excluded from current official analytics. Records moved to Trash are soft-deleted and excluded from operational views; authorized Super Admin users can restore or permanently purge eligible records after confirmation and dependency checks. Retention periods should follow approved project, municipal, research-ethics, and institutional requirements.
5. Access and security
Access is role-based. The system includes authenticated sessions, password protections, audit activity, authorization checks, and lifecycle controls. No system can guarantee absolute security; authorized users must protect credentials and avoid exporting or disclosing records outside approved purposes.
6. Field information should be collected for a defined purpose
Information involved
- Farmer identity and agricultural profile details entered in the assessment workflow.
- Farmland and Farm Plot records, crop/profile attributes, plot size, and GPS coordinates.
- Soil readings, assessment results, fertilizer recommendations, review decisions, and generated reports.
- Account, security, audit, synchronization, and IoT/device metadata used to operate and protect the system.
Consent and field practice
- Authorized personnel should explain the purpose of collection before recording identifiable farmer or location information when required by the study or operating procedure.
- Only information necessary for the assessment, mapping, recommendation, monitoring, security, or approved research purpose should be collected.
- Records should not be exported, copied, or shared outside authorized workflows without a legitimate project/municipal purpose and applicable approval.
1. Authorized use
BagulinAgriTech is intended for authorized project, municipal, administrative, and field personnel. Users must access only the functions and records permitted by their assigned role and approved purpose.
2. Data accuracy and field responsibility
Users are responsible for entering, reviewing, and correcting assessment information carefully. GPS, plot size, crop profile, sampling quality, soil readings, and review status affect the system's outputs. Records known to be test, duplicate, invalid, or erroneous should follow the system's Trash workflow; legitimate historical records should use Archive/Supersede.
3. BSWM and Department of Agriculture reference data
BagulinAgriTech generates fertilizer recommendations by matching the recorded soil assessment and selected crop profile against reference recommendation data sourced from the Bureau of Soils and Water Management (BSWM) and the Department of Agriculture (DA). Where a source rate is expressed per hectare, the system scales that rate to the recorded Farm Plot area; per-tree and per-plant source rates remain source rates.
The system does not guarantee improved crop yield. The recommendation is decision-support information that supports fertilizer planning and soil nutrient management. Actual crop response and yield can vary because of weather, irrigation, crop variety, pest or disease pressure, application timing, sampling quality, field condition, and farm-management practices.
4. Prohibited use
- Do not access another user's account or bypass assigned permissions.
- Do not deliberately falsify farmer, location, soil, review, audit, or IoT records.
- Do not use exports or screenshots to disclose identifiable records outside an authorized purpose.
- Do not present system-generated recommendations as a guaranteed yield, guaranteed profit, or substitute for all professional agricultural judgment.
5. Availability and external services
Online maps, browser/device features, network synchronization, and other external dependencies can be unavailable or incomplete. Users should verify critical information before field application or official use.
6. External services used by enabled features
Street-map tiles/data may be requested by the browser when the online basemap is enabled. Visible OpenStreetMap contributor attribution must remain available on rendered maps.
Satellite imagery may be requested by the browser for Hybrid/Satellite map modes. Provider/source attribution shown by the map must remain visible; availability depends on the external provider.
Apache-2.0 3D globe/map rendering library loaded for the Earth view. Cesium and imagery-provider credits must remain visible.
Printing, local/offline storage, geolocation, and supported Bluetooth/device features are used only when the corresponding workflow is invoked.
Requests to external map providers can expose ordinary connection metadata, such as IP address and browser request information, to those providers under their own policies. BagulinAgriTech does not use third-party advertising or intentionally deploy non-essential advertising trackers in this build.
8. Project content and third-party components
BagulinAgriTech project code, branding, documentation, and project-created assets remain subject to the rights and permissions applicable to the project and its institution. Third-party libraries, map/data providers, fonts, icons, and other dependencies remain subject to their respective licenses and terms. Source attribution for agricultural recommendation data must be preserved as BSWM/Department of Agriculture reference data where that dataset is used.
9. Requests, questions, and changes
Questions about access, correction, retention, or use of BagulinAgriTech records should be directed to the authorized BagulinAgriTech administrator or the Municipal Agriculture Office/project contact responsible for the deployment. Any request remains subject to applicable institutional, research, municipal, and legal requirements.
This notice may be updated when the system's data practices, features, deployment context, or external services materially change. New analytics, advertising, payment, or non-essential tracking features should receive a separate privacy/legal review before release.
Questions
Contact the responsible deployment team
For deployment-specific privacy, research, or records-management questions, contact the authorized BagulinAgriTech administrator or Municipal Agriculture Office/project representative.