Welcome to Barangay San Jose

Request barangay documents, track your application, and read public records published by the barangay.

Your data is protected under RA 10173.

Documents you can request

Available at Barangay San Jose

Most documents are ready in 1–3 working days. Pick up at Barangay Hall, Mon–Fri, 8 am–5 pm.

Not sure which document you need?

Choose what you need it for to see a suggested match.

Getting started

Request a document in three steps

  1. 1
    Create your account

    Create an account and verify your email.

  2. 2
    Submit a request

    Choose the document you need and tell us the purpose.

  3. 3
    Track and collect

    Follow your request status online and get notified when it's ready.

More from the barangay

Transparency center

Latest public announcements

Loading announcements...

Office hours

Monday to Friday, 8:00 AM – 5:00 PM

Barangay Hall

Barangay San Jose, Biringan City

Transparency center

SK Public Bulletin Board

Browse official announcements, financial records, projects, and meeting minutes.

Latest Announcements

Official records

Browse Public Records

Browse the full archive

Loading public records…

Account access

Log in

Enter your credentials to continue to the portal.

New to the portal?

This page isn’t available.

The page you're looking for may have been moved or removed.

Address you tried: /index.php/index.php

This page isn’t available.

The page you're looking for may have been moved or removed.

Address you tried: /index.php/index.php

Account recovery

Forgot your password?

Enter the email address for your portal account. We’ll send a secure link if it matches an account.

Resident enrollment

Create your account

Create an account to browse the portal and track your document requests.
* Required. Middle name, suffix, civil status, gender, and phone number are optional. Verify your email before submitting a request.

Personal details

Resident information

You must be 16–100 years old to register.

Contact

Choose your street and Purok, then enter your house or lot number.

Account

  • 8+ characters
  • Uppercase (A-Z)
  • Lowercase (a-z)
  • Number (0-9)

Passwords match

Resident workspace

Document requests

Welcome back, . Submit a request or review its progress.

New request

Request a document

All fields are required.

Request summary

Select a document to view its details.

Proof of residency

This uploaded proof may contain sensitive information. It is stored for the sample request workflow and available to project administrators; this prototype is not an official barangay service.Your ID is only used to verify that you live in the barangay. It is not shown on public records.

You can track this request under Track request.You can track this request under Track request.

Request history

Track my requests

My profile

Your details

Official record
Phone number
Home address
Birthdate / age
Civil status
Gender

To correct your name or phone number, visit the barangay office. You can update your home address, birthdate, and gender here.

Login and security

Email

Password

••••

Last changed: Not available

Login and security

Change email

Enter your new email address and current password.

We'll send a verification link to your new email. Your current email stays active until you verify the new one.
We ask for your password to confirm it's you.

Login and security

Change password

Create a new password for your Barangay San Jose portal account.

  • 8+ characters
  • Uppercase (A-Z)
  • Lowercase (a-z)
  • Number (0-9)

Passwords match

At a glance

Overview

Current service activity and items that need attention.

Needs action—0 approved requests

Requests

By document type

Loading request totals…

Needs attention

Oldest waiting

Loading requests…

Legal

Privacy Policy

Last updated November 1, 2026

This is an academic prototype, not an official barangay service. It may process information entered into its forms as described below. This notice models the protections expected for real personal information under the Philippine Data Privacy Act of 2012 (Republic Act No. 10173); the academic-project notice does not mean submitted data is fictional or automatically deleted.

Information we collect

Depending on the features you use, the portal may collect:

  • Identity and account details, including your name, email address, optional phone number, residential address, date of birth, and optional civil status and gender. Age is calculated from the stored date of birth when displayed; age is not stored as a separate value.
  • Profile photos you choose to upload
  • Proof-of-residency files required for online requests, which may contain information from a government-issued ID
  • Payment reference numbers and receipt files submitted for review on paid document requests
  • Document request information, including the document type, stated purpose, tracking number, status, and related processing or payment status
  • Business request details such as the business name, type, address, and activity when a business clearance is requested
  • Request-linked collection records, including assessed amount, payment channel, receipt reference, staff account, and any correction or reversal
  • Staff directory information entered by a super-administrator, including staff name, position, contact details, and linked portal role
  • Document sample preparation records, including a sample document number, request reference, staff account, preparation time, and a content hash
  • Registration, verification, request, and account activity dates and records
  • Technical and security information, such as IP address, browser or device details, session information, rate-limit records, audit entries, and server or error logs
  • Browser storage: a language preference in local storage and a temporary session copy of an administrator disclosure draft when needed; saved drafts are also stored with the administrator account
  • Messages and contact details you send to the project through the portal or listed email

Information entered into the forms is handled as potentially real personal information. Do not provide another person's information unless you are authorized to do so. The academic-project label does not guarantee that submissions are test data.

How we use it

The prototype uses account details to create and secure an account, verify email, and support account recovery. It uses resident information to pre-fill a resident’s own request, request details and residency proofs to review requests, and payment references and receipt files to reconcile request-linked fees. Business details support business-clearance requests. A staff directory supports internal contact and role assignment. A watermarked sample document may be previewed or printed after the request is approved and the fee is confirmed. Administrators who opt in may receive an email when a resident submits payment proof. Technical records help secure and maintain the application. The prototype does not offer advertising or analytics features.

This academic prototype has not documented a final lawful-basis assessment for each processing purpose or a specific legal basis for processing government-issued ID information. This notice describes the project’s intended handling but does not by itself establish a lawful basis. Any real operator must complete that assessment before live use. Registration records acceptance of the Terms and acknowledgment of this Privacy Notice with one checkbox; that checkbox is not blanket consent for every use of information.

Accounts & uploads

Residents can create an account and sign in without administrator approval. Email verification is required before submitting an online document request. The request form requires a National ID or Certificate of Residency. Residents can review and update their home address, birthdate, and gender in their profile; age is recalculated from the birthdate. Access is role-limited: service clerks can review resident accounts and request proofs; cashiers can view payment and collection details; document issuers can access only the request information needed for document preparation; and super-administrators can manage staff roles. Walk-in request details are entered by an administrator to demonstrate the in-person workflow. Do not use another person’s account to request a document for a child or other resident; the prototype does not yet provide a verified representative or guardian workflow.

The portal currently does not provide blotter-record or 4Ps-data modules. Do not enter those sensitive records in request purposes, notes, uploads, or other free-text fields. The printable output is permanently marked as a sample and is not an official barangay document.

Request proofs, payment receipts, and disclosure attachments are stored outside the public web root by default. Request proofs and payment receipts are served only through administrator-only endpoints. Published disclosure attachments are intentionally available to the public; administrators should not publish an attachment containing personal information unless disclosure is authorized and necessary.

Personal information of applicants

Barangay San Jose processes personal information in accordance with Republic Act No. 10173 (Data Privacy Act of 2012) and its Implementing Rules and Regulations.

  • What we collect: when a request is made for another person, the applicant's name, date of birth, address, copies of IDs, and authorization or guardianship documents, supplied by the requester. The date of birth (age) and civil status are sensitive personal information under the law.
  • Why: only to verify the requester's authority, process the request, and issue and release the document.
  • Basis: the applicant's consent, which the law allows to be given by a lawful representative or an agent specifically authorized by the applicant, shown by the signed authorization letter. For a minor, the parent or legal guardian acts for the child. By submitting a request as an authorized representative, the requester confirms that the applicant has been informed and has agreed.
  • Who can see it: authorized barangay staff only. It is not shown on public records, and each time staff open a representative document, it is recorded in the activity log.
  • How long: kept only as long as necessary for the purpose, which is [retention period set by the barangay], and then deleted or disposed of securely.
  • Your rights: as a data subject, you may ask to access, correct, or object to the processing of your personal information, ask for it to be blocked or removed where the law allows, and file a complaint with the National Privacy Commission. Contact: [privacy contact or Data Protection Officer of Barangay San Jose].

Data retention

Unverified accounts with no request are marked archived after 30 days. Archiving disables access but does not itself delete the account record. Password-reset tokens expire after one hour and email-verification links after 24 hours; expired tokens may remain in the database until cleanup runs. Successfully sent email bodies are cleared and their queue records are removed after 30 days.

When an administrator deletes a resident account, the application deletes the resident record, linked document requests, residency and payment proof files, profile photo, and queued messages associated with the account. Related request audit details are redacted, while a non-identifying deletion event remains in the audit log. This action does not establish an automatic deletion schedule for other resident accounts, audit logs, failed email metadata, disclosure attachments, or backups. No general retention period for those records has been approved, so they may remain until manually deleted or otherwise removed by the project operator. A real service must set and implement periods consistent with applicable barangay records rules before accepting operational data.

Security

The application includes password hashing, role-based access checks, administrator multi-factor authentication, session protections, request protections, and restricted storage for request proofs. These are application controls, not a guarantee about the live host, database permissions, staff practices, or backups. A production operator must verify those controls and maintain an incident-response process. If a breach meets the legal notification requirements, the responsible controller must notify affected people and the National Privacy Commission as required by law. Report suspected exposure to the contact below.

Third-party services

The application is configured to use a website host and database, an SMTP email-delivery service, and Google reCAPTCHA for automated-abuse checks. Those providers may process the technical information or email content needed for their services. The specific hosting and email providers, their processing locations, and the applicable service agreements depend on deployment settings and are not identified in this codebase. A real operator must identify them and confirm whether information is processed outside the Philippines before launch.

Cookies

The portal uses an essential session cookie to keep you signed in and protect account actions. Google reCAPTCHA may use cookies or similar technical signals when its checks run. The application saves the selected language in local storage, saves administrator disclosure drafts to the administrator's account, and may keep a temporary session copy while recovering unsaved draft changes. The codebase contains no optional advertising or analytics cookies. Blocking cookies may prevent sign-in and protected features from working.

Your rights

Subject to the conditions and exceptions in RA 10173, you may ask to be informed about processing; access or receive a copy of your personal information; correct inaccurate or incomplete information; object to or withdraw consent from certain processing; request erasure or blocking where allowed; request data portability where applicable; and file a complaint with the National Privacy Commission. You may also seek damages where the law provides that right.

To make a privacy request or report suspected misuse, email the project contact below. Identify the account or request and explain what you are asking us to do. We may request reasonable information to verify your identity. The project contact will review the request and explain any legal or records obligation that limits what can be done. You may also file a complaint with the National Privacy Commission under its applicable process.

Changes

We may revise this policy when our services, practices, or legal obligations change. The revised version and its effective or last-updated date will be posted on this page. For material changes, we will provide notice through the portal or by email when reasonably practicable.

Responsible project contact

Barangay San Jose Digital Portal academic project. Send privacy questions or requests to deleonjuliusakeem@gmail.com. A formally designated Data Protection Officer or real barangay personal information controller is not identified by this prototype.

Contact

Barangay San Jose Digital Portal deleonjuliusakeem@gmail.com

Legal

Terms & Conditions

Last updated November 1, 2026

This is a prototype, not an official barangay service. By creating an account or using its account features, you agree to these Terms. The separate Privacy Notice explains how information entered into the prototype is handled.

Acceptance

By creating an account or using account features, you agree to these Terms. If you do not agree, do not create an account. These Terms apply together with the Privacy Policy and any instructions shown for a feature. Registration uses one checkbox to record agreement to these Terms and acknowledgment of the Privacy Policy; that acknowledgment is not consent to optional uses of personal information.

Accounts & services

The prototype allows users to register, submit proof of residency with an online request, track requests, and view sample public disclosures. Users may sign in and browse before verifying their email, but must verify it before submitting an online request. This prototype cannot issue an official barangay document or guarantee a real barangay service. Provide accurate information for the exercise and keep your password and authenticator codes confidential.

Requests made by an authorized representative

1. Who may request. A document may be requested for another person only (a) by that person's parent or legal guardian, if the person is under 18 years old, the age of majority under Republic Act No. 6809 and Article 234 of the Family Code, or (b) by an authorized representative specifically authorized in writing by the applicant, if the applicant is 18 or older.

2. Required documents. The requester must upload the documents listed on the request form. These requirements are the same as those stated in the barangay's Citizen's Charter, under Republic Act No. 11032 (Ease of Doing Business and Efficient Government Service Delivery Act of 2018). Uploaded electronic copies are accepted as electronic documents under Republic Act No. 8792 (Electronic Commerce Act of 2000). The original documents and a valid ID must be shown at pickup.

3. Valid ID. Any valid government-issued ID is accepted, including the PhilID or ePhilID, which the barangay accepts as sufficient proof of identity under Republic Act No. 11055 (Philippine Identification System Act), subject to authentication.

4. Accuracy and responsibility. The requester is responsible for the accuracy of everything entered and attached. Giving false information, submitting a forged or altered document, or using another person's identity without right may be punishable under Philippine law, including falsification and use of falsified documents under Articles 171 and 172 of the Revised Penal Code, and computer-related forgery and identity theft under Republic Act No. 10175 (Cybercrime Prevention Act of 2012). The barangay may also refuse the request, suspend the account, and report the matter to the proper authorities.

5. Verification. The barangay may contact the applicant to verify the request, may require the applicant to appear in person, and may refuse a request made by an authorized representative, especially for certificates about a person's personal circumstances.

6. Processing time. Processing time is counted from the date the barangay receives the complete requirements, as provided in Republic Act No. 11032 and the barangay's Citizen's Charter.

7. Release. A document is released only to the applicant or to the authorized representative named on the request, upon showing an original valid ID, and its release is recorded.

Your responsibilities

You agree not to:

  • Provide false, misleading, or fraudulent registration details
  • Upload forged or altered proof-of-residency documents
  • Impersonate an applicant or submit a request as an authorized representative without authority
  • Use the portal for illegal activity or to harm others
  • Upload files containing malware, or attempt to bypass portal security, access controls, or rate limits
  • Upload or share copyrighted material without permission or another lawful basis
  • Share another person's sensitive information without authority or a lawful purpose

Fees and pickup

Document types and payment-status fields in this prototype are examples for the exercise. The prototype does not process or collect payments or issue official documents. For paid requests, residents can submit a reference and receipt for administrator review after paying through a method confirmed directly with the barangay. Listed fees must be confirmed before real use. Free requests do not require payment proof.

Administration rights

Project administrators may review submitted files and requests to demonstrate a review workflow. Walk-in records are sample entries. No decision in this prototype is an official eligibility determination, and no request can result in an official document. If you have a concern about a project account or sample request, contact the project email below.

No warranties

This prototype may be unavailable, delayed, or changed for maintenance, security, connectivity, or project reasons. We do not warrant uninterrupted or error-free access. A portal status or confirmation is not an official decision or government document.

Liability

To the extent permitted by Philippine law, the project operator is not responsible for losses caused by a user's failure to protect account credentials, inaccurate information supplied by a user, third-party services outside the project's control, or interruptions beyond reasonable control. Nothing in these Terms excludes liability or a remedy that cannot lawfully be excluded, limits rights provided by law, or excuses a party from its legal duties.

Third-party content

User-submitted content remains the responsibility of the person who submits it. External websites and third-party services are governed by their own terms and privacy notices; we do not control their availability or practices. We may review or remove portal content as described in the Moderation Policy.

Changes

We may revise these Terms or change portal features to reflect service or legal changes. The current version and its date will be posted here. We will provide notice of material changes through the portal or by email when reasonably practicable. Changes apply from the posted effective date, subject to any rights that applicable law gives you.

Termination

We may restrict, suspend, or close access when reasonably necessary for security, legal compliance, service operation, or a violation of these Terms. Where practicable, we will explain the reason and how to contact us about the decision. Closing access does not remove records that must be retained for a lawful purpose.

Governing law

These Terms are governed by the laws of the Republic of the Philippines. Any dispute will be handled by the appropriate Philippine authority or court, subject to applicable law.

Contact

Barangay San Jose Digital Portal deleonjuliusakeem@gmail.com

Legal

Moderation Policy

Last updated October 31, 2026

This prototype is not an official barangay service. This policy explains how project administrators handle account, request, and sample disclosure submissions.

Prohibited content

We may reject or remove submissions that include:

  • Threats, harassment, abusive language, hate speech, or discriminatory statements
  • Spam, repeated junk submissions, or attempts to disrupt the service
  • Fraudulent, forged, altered, or misleading registration details or supporting documents
  • Instructions or files intended to facilitate illegal activity or compromise the portal
  • Personal or sensitive information about another person shared without authority or a lawful purpose
  • Material that infringes copyright or another person's rights

How we review

Project administrators can review online proof-of-residency files and requests to demonstrate a review workflow. They may ask for clarification or reject a sample submission. No review is an official government decision, and no document is issued by this prototype. Published disclosure content and attachments are public; administrators should not post personal information unless its publication is authorized and necessary.

Reporting problems

To report harmful content, suspected fraud, unauthorized disclosure, or a moderation concern, email deleonjuliusakeem@gmail.com. Include the relevant tracking number or page, describe the concern, and tell us how we can contact you. Do not email passwords, authenticator codes, or unrelated sensitive documents.

Removal & rejection

Depending on the issue, project administrators may restrict access to a file, return a sample request for correction, or reject, unpublish, or remove content. They should provide a reason or next step when reasonably practicable while protecting other people's privacy.

Repeat violations

Repeated or serious violations may lead to additional review, temporary restrictions, account suspension, or account closure. The response will take into account the nature and seriousness of the conduct and any applicable legal or safety needs.

Decisions and review

Submitting a registration or sample request does not guarantee review by a particular date or any real-world service. If a submission is rejected or content is removed, contact the project email below with your account email or tracking number to ask for clarification. There is no in-portal appeal feature or guaranteed response time.

Document request rules

A resident may have up to three pending document requests at a time. A request may be cancelled only while it is Pending. Choose a cancellation reason; if you choose Other, provide at least 10 characters of explanation. Within a rolling 24-hour period, each cancellation applies a cooldown to all new document requests: 3 minutes for the first cancellation, 10 minutes for the second, 1 hour for the third, and 1 day for the fourth and later cancellations. The cooldown is calculated from the latest cancellation using server time. Staff may lift a cooldown, and the action is recorded.

After staff marks a request Ready for Pickup, collect it within 7 days. If you cannot attend, request a new date with a reason. The new date must be a working day within 7 days after the scheduled date, and each request allows up to two reschedule attempts. A secretary reviews each request and the resident is notified of the result. Requests not collected by the deadline may be marked Expired. A resident requesting a document as an authorized representative for another person must provide accurate details, identify their relationship to the applicant, confirm they are authorized, and ensure the applicant presents a valid ID at pickup. False or unauthorized claims may lead to restrictions or account suspension after review.

Email and personal data

The portal may email residents about account verification and document request events, including submission, cancellation, status changes, and pickup reschedule decisions. Email delivery can be delayed or fail; residents should also check their portal request status. Applicant and authorized-representative details, uploaded proof, reasons, status history, and audit records are used to demonstrate and administer this workflow. Access is limited by staff role, and information should not be included in public disclosures unless publication is authorized and necessary.

Personal information is handled under the Data Privacy Act of 2012 (Republic Act No. 10173) and the portal Privacy Policy. The portal collects only information used for the requested workflow, applies access controls, and retains request and audit records for administration and accountability. Do not submit another person’s information unless you are authorized to do so. This prototype is not an official barangay service and does not replace a formally designated personal information controller or Data Protection Officer.

User responsibility

Check information and files before submitting them, use the portal only for your own authorized account and requests, and respect the privacy and rights of other people. When acting for another person, you are responsible for the accuracy of the information and for having authority to submit it. Report suspected account compromise or an incorrect moderation action promptly.

Contact

Barangay San Jose Digital Portal deleonjuliusakeem@gmail.com