WebGuard Privacy Policy

Effective date and notice version: September 11, 2026 (2026-09-11)

Pilot limitation: WebGuard is limited to authorized test accounts and test websites while its organizational privacy documentation and approvals are being completed. It must not be used to monitor personal browsing, minors, students, employees, or members of the public without the operator's approved privacy impact assessment and onboarding notice.

WebGuard is a browser-security extension for an authorized Nueva Ecija cyber-response pilot. Its purpose is to detect and block configured web threats and, for a signed-in account, report a minimized security incident to the authorized management server.

Data controller and privacy contact

The participating organization operating a WebGuard deployment is the personal information controller for that deployment. Before real-user use, its onboarding notice must state the organization's legal name, address, Data Protection Officer, and official DPO contact. For this restricted technical pilot, contact the verified publisher at jomelstaana090@gmail.com. This technical contact does not replace the participating organization's formally designated DPO.

Information handled

The extension may examine a full URL temporarily in the browser to apply threat rules. The server retains only the affected site's origin, such as https://example.com/; page paths, query parameters, fragments, and URL credentials are removed before storage. A detection may include the domain, threat category, reason, severity, action, timestamp, incident identifier, and the signed-in user's name, email, user ID, and role.

Account and support functions may process a name, email address, optional phone and badge number, hashed password, role, session state, support messages, and account-security events. Security events may include an IP address and limited network metadata when needed to investigate attempted abuse. Passwords are hashed. One-time codes expire and are not stored by the extension as readable text.

Purpose and lawful basis

Browser monitoring and signed-in incident reporting are enabled only after an express consent action for the current notice version. Account authentication, access control, fraud prevention, security investigation, and legally required records may also be processed when necessary to provide the requested pilot service, comply with law, or protect legitimate security interests, subject to the rights of data subjects. A participating organization must document the lawful basis for each real-user deployment before use.

WebGuard does not sell personal data and does not use it for advertising, credit decisions, unrelated profiling, or general employee or student performance monitoring.

Access, sharing, and service providers

Staff can access only their own detections and support requests. Authorized administrators can access deployment-wide security records and account-management functions. Service providers currently used to operate the pilot may include Render for application hosting, MongoDB Atlas for database hosting, and Resend for authentication email delivery. Twilio may be used only when SMS delivery is configured. Providers receive only the information needed for their service. The deployment operator is responsible for applicable data-processing agreements, region choices, subprocessors, deletion assistance, and breach obligations.

Retention and deletion

Unsynced alerts are retained in the browser for no more than 7 days. Server alerts are automatically removed after 90 days, support requests after 180 days, and security audit events after 365 days by default. The operator may configure shorter periods. Records may be retained longer only when a documented legal obligation or active legal claim requires it.

Withdrawing consent from the extension popup stops monitoring, removes the local alert cache, deletes the account's server alerts and support requests, and anonymizes identifying fields in related security events. Provider backups and logs follow each provider's documented deletion cycle.

User choices and rights

Monitoring is off until the current privacy notice is accepted. Consent is recorded with the notice version and acceptance time. A user may pause protection without deleting data, or select Withdraw and Delete My Data in the popup. A data subject may also request access, correction, a copy of applicable data, objection or restriction, deletion or blocking, and information about processing through the privacy contact or in-product support function. A complaint may be filed with the National Privacy Commission.

Security and incidents

Data in transit uses HTTPS. Management records require an authenticated, current session and backend-enforced role checks. Sensitive operations are restricted to administrators. The operator must maintain an incident-response procedure and make legally required notifications to affected data subjects and the National Privacy Commission.

Children and students

The restricted pilot is not directed to children. Do not install WebGuard for a minor or use it in a school deployment until the participating institution has approved the privacy impact assessment, lawful basis, age-appropriate notice, required parent or guardian process, and a voluntary participation procedure with no improper penalty.

Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact

Privacy and data-subject requests for this restricted technical pilot: jomelstaana090@gmail.com. A real deployment must replace or supplement this with the responsible organization's legal identity and DPO details.