Privacy Policy

Who we are

AlistoBrgy is an independent student-developed educational application. It is not affiliated with, endorsed by, authorized by, or operated by any Philippine government agency, barangay, or local government unit.

App moderator is an application role for managing community content and accounts. It does not establish government employment or government verification.

AlistoBrgy supports community disaster preparedness through community alerts, hazard reports, evacuation maps, contacts, safety guides, supplies and chat. This policy describes the reviewed Android implementation and the legal website. Questions or privacy requests: AlistoBrgyBocos@gmail.com.

Account and community data

• Account details include your name and email. Password sign-in is handled by Firebase Authentication. If you choose Continue with Google, Google Sign-In provides account information for authentication.
• You can optionally add a phone number and profile photo. Your profile also stores your application role and account status.
• Posts include chat messages and hazard reports, with descriptions, types, optional locations and photos. App moderators can publish alerts, evacuation centers, routes, contacts, supplies and safety tips.
• Reports of inappropriate chat messages can include copied message content for moderation. Blocking a sender hides their messages locally; it does not delete those messages for everyone.

These data support authentication, displaying community information, synchronization, moderation and account management. The reviewed app does not include advertising or analytics SDKs. This is not a guarantee that service providers keep no operational records.

Location and walking-route recording

Location is requested when you choose a feature such as showing your position, finding nearby evacuation information, attaching a report location or recording a walking route.

Walking-route recording starts when you choose Record route by walking. On Android, its location foreground service can continue collecting route positions while the app is not visible or the screen is locked. An ongoing notification titled Recording your route tells you that recording is active and directs you to open the app and tap Stop.

Tap Stop to stop recording. Leaving the recording feature also cancels its location stream. Device settings or system restrictions can interrupt recording. The absence of the separate background-location permission does not mean location stops when the screen locks.

Recorded route points are kept locally unless an app moderator saves them as a shared evacuation route. Locations attached to reports and saved shared routes are synchronized as part of those records.

Local storage and offline use

The app keeps settings, account-specific notification history and cached community records on the phone. Previously downloaded information, built-in safety guides and some saved maps/routes can be viewed offline. Supported edits or reports may be queued locally and synchronized after connectivity returns.

Offline information may be incomplete or outdated. First-time sign-in, server-side deletion, fetching new shared data, uncached map tiles, online walking directions and opening external references require connectivity. A previously authenticated account with a cached profile may retain offline access. Offline availability is not guaranteed for every screen or map area.

Who can see information

Shared alerts, evacuation resources, contacts, supplies, tips and community chat are intended for signed-in users. Chat displays the sender's name and app role.

Hazard reports are intended for their author and app moderators. Profiles are intended for the account holder and app moderators who manage accounts. These are intended access boundaries, not a guarantee against unauthorized access; deployed permissions and account administration are the owner's responsibility.

App moderator is an application role for managing community content and accounts. It does not establish government employment or government verification.

Services and network requests

• Firebase Authentication handles accounts and sign-in. Cloud Firestore stores profiles, community content and photo records; the reviewed implementation stores compressed images in Firestore rather than using Firebase Storage. Firebase Cloud Messaging handles push tokens and topic subscriptions. The app also checks shared data and displays local notifications; delivery is not guaranteed or a real-time emergency-monitoring service.
• Google Sign-In is used when you choose that sign-in option. Firebase and Google services may process information outside the Philippines under their service terms and configuration.
• Map tiles come from OpenStreetMap for the street layer, Esri/ArcGIS for satellite imagery, or OpenTopoMap for terrain, depending on the selected layer. Walking-direction requests go to routing.openstreetmap.de. These services receive network request information such as your IP address; map requests identify requested areas and direction requests include start/end coordinates.
• If you choose to open directions in another app, AlistoBrgy passes the destination coordinates and travel mode to Google Maps, or destination coordinates and a location label to another maps app. That external service handles the request under its own practices and may separately request your location.
• Cloudflare hosts this legal website and receives requests when you visit it, including network information such as your IP address. The optional Cloudflare notification relay is disabled in the reviewed app configuration. The app does not currently send sign-in tokens or content through that relay. Website hosting and the inactive notification relay are separate uses.

Account deletion and retention

Account and shared records are stored to provide the service until removed through the app or an owner-reviewed request. This policy does not assert a fixed retention period for every data category.

In the app, open Settings → Security → Delete my account and complete reauthentication. Without the app, use Account deletion instructions or contact AlistoBrgyBocos@gmail.com from your account email. The owner may need to verify that you control the account.

Deletion scope and possible retained information

The in-app deletion process is designed to remove your Firebase Authentication account, profile, your hazard reports and their associated photos, and your community chat messages. It also cleans up account-related data on the phone where deletion is performed.

Deletion takes several steps across Firebase services and local storage. A network, permission or photo-deletion failure can leave the process partially completed. The app reports the failure and supports retrying unfinished steps; it must not be treated as complete until completion is confirmed. If you cannot sign in or retry, contact AlistoBrgyBocos@gmail.com. Do not send your password.

Community resources published by an app moderator, such as alerts, evacuation centers, routes, contacts, supplies and safety tips, may remain for other users. These records can retain author identifiers or other information included in the content; removal of a profile does not automatically anonymize every record.

Copies in moderation reports, other people's saved or shared content, other-device caches and historical orphaned photos may not be removed by the account-deletion flow. Ask support about remaining personal information so the owner can review it.

Firebase service records and any configured backups are separate from the live records deleted by the app. Their retention and any necessary cleanup depend on the service and the owner's configuration. No fixed backup-retention period, immediate purge of every copy, or request-completion deadline is promised here.

Security, children and privacy requests

The reviewed app uses HTTPS service connections and Firebase access controls. No system is perfectly secure. Keep your phone and credentials protected, and avoid posting sensitive information unnecessarily.

The app is not intended for children under 13. If you believe a child has provided personal information, contact AlistoBrgyBocos@gmail.com for review. The owner must maintain an appropriate audience policy and response process.

You can edit your profile in the app and contact AlistoBrgyBocos@gmail.com to request access, correction or deletion of personal information, or raise a privacy concern. Applicable rights and the information needed to handle a request depend on the circumstances and applicable law.

External government information references

PAGASA — weather information and advisories published by PAGASA.

DOST-PHIVOLCS — earthquake, volcano and tsunami information published by PHIVOLCS.

HazardHunterPH — a separate hazard-assessment tool; it is not the AlistoBrgy map.

These links take you to external sources. They do not mean that these agencies authored, approved or verified AlistoBrgy's independently compiled safety guides, community posts, contacts, evacuation centers or routes. A general reference does not establish the source of a particular claim. Community information is not an official government advisory. Consult the original source for current information.

Policy versions

This website shows the revision date above. Installed app versions can contain older embedded legal text; the current website corrections do not modify an already installed app or its behavior. Material changes to processing require an appropriate policy and app update.