Institutional Service Notice

Privacy Policy

This page explains how the UAF Smart E-Library & University Information Assistant collects, uses, stores, protects, and discloses data when the service is used in an academic and operational context.

Effective Date: March 25, 2026Last Updated: March 25, 2026Service: UAF Smart E-Library & University Information Assistant
Quick Summary
  • The service is intended for students, librarians, administrators, and other authorized institutional users.
  • Core information includes account details, role assignments, library transactions, queue entries, fines, and operational logs.
  • Information is used to run authenticated library workflows, document retrieval, AI assistance, security checks, and administrative reporting.
  • Access is role-controlled through institution-managed identity, database-enforced authorization, and monitored operational boundaries.
  • The AI assistant is designed to answer from official uploaded documents only and should not be treated as a general-purpose advisor.
  • Privacy and account concerns should be directed to the published support contact before production launch.

Section

1. Overview

The UAF Smart E-Library & University Information Assistant is a university-oriented digital platform designed to support library management and access to verified university information. The system allows authorized users to access library services, view book availability, manage borrowing and returns, track fines and queue status, and use an AI assistant that responds using official uploaded university documents only.

This service is intended for real deployment and is built around institution-managed access, role-based boundaries, and database-enforced operational controls. This Privacy Policy explains what information the service processes, why that processing happens, and what limits or rights apply.

Section

2. Information We Collect

The service may collect and process the following categories of information:

  • Account and identity data such as full name, university email address, role assignment, internal account identifiers, and profile metadata needed for system access.
  • Library usage data such as searched books, viewed books, borrow and return activity, due dates, queue entries, fines, and related transactional records.
  • Administrative and operational data such as user-management actions, book-management actions, fine review actions, document upload events, and dashboard activity used to run the platform.
  • AI assistant inputs and retrieval metadata such as user questions, matched document excerpts, citations, document source labels, and indexing metadata for uploaded official documents.
  • Technical and session data such as authentication/session state, timestamps, request logs, browser details, device details, error events, and security signals needed to keep the service stable and defensible.
  • Communications and support data if a user contacts support or submits a privacy or account issue.

Section

3. How We Use Information

Information is used to operate the service, not to manufacture unrelated marketing profiles.

  • Create and manage institution-issued accounts.
  • Authenticate users and maintain secure sessions.
  • Enforce role-based access to books, operations, and records.
  • Run borrowing, returns, queue handling, renewals, and fine tracking.
  • Support administration of books, users, and official documents.
  • Generate AI responses grounded in official uploaded documents.
  • Maintain auditability, diagnostics, security monitoring, and service reliability.
  • Produce operational analytics and dashboard summaries derived from platform activity.

Section

4. Role-Based Access

This service is not designed for unrestricted access. Identity is managed through Supabase Auth, while authorization is enforced in PostgreSQL through row-level security and related access controls. FastAPI acts as a thin API layer rather than the source of truth for business access rules.

  • Students should only see their own account and library activity.
  • Librarians may manage operational library records within approved scope.
  • Administrators may manage broader platform functions, users, documents, and system-level monitoring.

Important Note

Institutional access may include audit logging, administrative review, and role-based visibility needed for service operation, incident response, or compliance with internal university rules. This is a controlled academic system, not a private personal notebook.

Section

5. AI Assistant & Document Processing

The AI assistant is intended to answer questions using official uploaded university documents only. It is not meant to improvise unsupported answers from general model knowledge when no verified source is available. The system is designed to return a fallback message when relevant official material cannot be retrieved above the configured threshold.

Authorized institutional users may upload official documents for indexing and retrieval. When documents are updated or replaced, the architecture is designed to preserve indexing integrity rather than silently overwrite or mix old and new source material.

AI Limitation

Users should not submit unnecessary sensitive personal information in general AI assistant questions. The assistant is meant for official document retrieval and cited answers, not for private counseling, unrestricted profiling, or general confidential disclosure.

Section

6. Cookies / Sessions / Technical Data

The service may use cookies, local storage, or similar session technologies to maintain authentication state, remember login context, and support recovery or invited-user password setup flows. Authentication and redirect handling rely on Supabase session behavior, while backend services validate tokens and the database enforces access restrictions.

If non-essential analytics or preference tracking is added in the future, this notice and any related consent or preference controls should be updated accordingly instead of pretending no such technologies exist.

Section

7. Sharing of Information

The platform is not described as a free-for-all data-sharing system. Information may be shared only where required for legitimate hosting, authentication, storage, notifications, maintenance, institutional operations, legal compliance, or security response.

  • Hosting, storage, and infrastructure providers.
  • Authentication and session providers.
  • Authorized university staff operating the service.
  • Support, maintenance, or notification providers where required.
  • Authorities or regulators where a lawful or formal process requires disclosure.

Section

8. Data Retention

Information is kept only as long as it is needed for operational, academic, administrative, legal, security, or audit purposes. Different categories have different retention needs.

  • Account records may remain while an account is active and for a reasonable period afterward.
  • Borrow, return, queue, and fine records may be retained longer because they form part of library operational history.
  • Official uploaded documents may remain available as long as institutional reference and retrieval require them.
  • Technical logs may be retained for a limited diagnostic and security window.

Retention Limit

Account deletion or deactivation does not necessarily erase every operational or audit record immediately. Some information may need to remain where the institution has a valid operational, security, academic, legal, or evidentiary reason to keep it.

Section

9. Security

The platform uses authenticated access, controlled operational workflows, transactional integrity, protected document processing, and database-enforced authorization boundaries. That design is intended to reduce unauthorized access and inconsistent state, not to promise impossible perfection.

No system can promise absolute security. Users are also expected to protect their credentials, use strong passwords, and report suspicious access or misuse promptly.

Section

10. User Rights & Requests

Users may request access to, correction of, or clarification about personal information held about them, subject to identity verification, technical feasibility, institutional rules, record integrity, and any legal or administrative obligations.

  • Correction of inaccurate profile details.
  • Review of certain account-related information.
  • Deletion or deactivation requests where appropriate.
  • Clarification about how account and operational data is used.
  • Help regarding security or privacy concerns.

Some requests may be limited or denied where records must be retained for operational, legal, academic, or security reasons.

Section

11. International Hosting / Transfers

Depending on deployment and third-party providers, data may be processed on infrastructure located outside a user’s physical location or outside Pakistan. This matters because privacy protections may depend on provider architecture, contractual controls, institutional governance, and the specific laws that apply to the deployment context.

Before production launch, this section should be updated with the real hosting regions and provider categories rather than leaving deployment facts vague.

Section

12. Children / Student Use

This service is designed for use in an academic and institutional environment. Users are expected to use it for legitimate educational, administrative, and library-related purposes. The platform may process student-related data, librarian activity, administrator actions, and official university document interactions as part of those workflows.

Section

13. Policy Updates

This Privacy Policy may be updated over time to reflect changes in the service, security controls, deployment model, legal obligations, institutional requirements, or platform features.

When material changes are made, the “Last Updated” date should be revised and suitable notice should be provided through the application or related communication channels where appropriate.

Section

14. Contact

For privacy-related questions, account concerns, correction requests, or security issues, the current operational contact exposed in the guest experience is:

Privacy / Support Contact: Student Assistance

Email: ahmadsajid41324@gmail.com

University: University of Agriculture Faisalabad

Legal Navigation

Return to authentication or continue to the next legal surfaces as they are implemented.