This deployment is operated by JuanResponse. For privacy questions, correction or removal requests, or data-subject rights requests, contact the JuanResponse support team.

• Reports and offers: type of help, category, urgency, title, description, barangay or area, optional exact location, photos, and optional contact name or phone.
• Accounts and responder access: name, phone, password credentials, role, organization details when provided, incident membership, claim and moderation actions, and security logs.
• Resource directory updates: resource names, status, capacity, occupancy, barangay or area, address, public contact details, and notes intended for public coordination.
• Donation confirmations, when donations are enabled: amount, payment method, reference number, optional donor name, email, phone, message, receipt screenshot, anonymity preference, verification status, and any request reference selected by the donor.
• Technical data: timestamps, device/browser data, IP-derived request logs, upload metadata, abuse reports, operational security logs, and analytics data only when analytics is explicitly enabled.

We process data to publish situational reports, match needs with offers and responders, verify and moderate reports, prevent fraud or abuse, manage responder access, protect life and safety during incidents, verify and account for donation confirmations when enabled, comply with legal obligations, and maintain incident accountability records.

Depending on the context, processing may rely on consent, account or service necessity, legitimate interests in safety and security, vital interests involving life or health, public safety or emergency response, legal obligation, or other lawful bases under Republic Act No. 10173 and National Privacy Commission issuances. Sensitive personal information is handled only where necessary and with additional safeguards.

• Public views may show report titles, descriptions, categories, urgency, status, photos, barangay or approximate map locations, and resource directory addresses, contacts, and availability notes.
• Restricted fields include report contacts, exact report locations, responder notes, donation confirmation details, receipt screenshots, verification records, and security or audit logs.
• Trusted responders and incident staff may access restricted fields only when needed for response, verification, safety, moderation, or incident operations.

Public users see only public fields. Trusted responders, moderators, incident staff, LGUs, emergency services, hospitals, shelters, NGOs, or other response partners may receive report data when needed for safety or response. Donation confirmation details are limited to staff who verify, account for, or report on donations. Hosting, database, object storage, map, support, email, payment, and analytics providers may process data only for configured operational purposes.

Requesting help, submitting reports, and offering help are free and do not depend on donations. When donations are enabled, donation details are used to verify transfers, prevent duplicate or false confirmations, maintain accounting records, send donor acknowledgments when requested, and meet applicable solicitation or reporting obligations. Public totals, if shown, are summaries only and do not reveal donor contact details.

Public maps should use approximate report locations. Exact coordinates, if submitted, are restricted to authorized response roles. Upload only media that is necessary for response or verification. Avoid IDs, graphic images, children's private details, exact home addresses, diagnoses, or private family information unless urgently necessary for safety.

Data should be kept only while useful for response, safety follow-up, moderation, legal obligations, security, audit, or accountability. The operator should define and publish a deployment-specific retention schedule for reports, uploads, contacts, accounts, donation records, donation receipts, and logs, then delete, anonymize, or archive records after the applicable period.

Data subjects may have rights to be informed, access their personal data, request correction, object or withdraw consent where applicable, request erasure or blocking, request portability where applicable, claim damages, and file a complaint with the National Privacy Commission. Parents, guardians, heirs, or authorized representatives may exercise rights for minors, incapacitated persons, or deceased persons when allowed by law.

Operators should use least-privilege access, role-based controls, trusted responder vetting, confidentiality expectations, secure transport, monitoring, and incident-response procedures. If a personal data breach is suspected, operators should contain the issue, preserve evidence, assess risk, and notify affected data subjects and the National Privacy Commission when required.

This Privacy Policy may be updated as the incident, deployment, or law changes. Significant changes should be communicated in the app or through the current incident communication channels.