LeaveApp
← Back to home

Privacy Policy

Effective 25 October 2026 Version demo-v1 Simulated demo

This page explains what the LeaveApp demo stores, what it does not collect, and what would change in a production deployment.

Do not enter real information. This build is a simulated demo. It uses sample accounts and browser storage only. Do not submit real student, parent, or college data.

1. Scope

This policy covers the LeaveApp demo: a simulated college leave-permission portal for the Computer Science & Engineering Department at Parul University. It is not an official university system and has no connection to real student records.

The demo exists to show how students could request leave and how an HOD could review and record a decision.

2. What this demo stores

The demo stores the following information in your browser:

  • Simulated user accounts with demo email addresses and demo passwords.
  • Sample student profile details: name, enrollment ID, branch, semester, division, roll number, and student mobile.
  • Sample parent or guardian name, relationship, and mobile number.
  • Sample leave requests, reasons, dates, categories, statuses, and decision comments.
  • The current demo session role, so the demo can send students and HODs to the correct page.

These values are examples. They are not real student records.

3. What it does not collect

  • No real student records or official college data.
  • No real parent or guardian contact details.
  • No payment or financial information.
  • No analytics, advertising, or tracking scripts.
  • No passwords sent to a server, because the demo has no backend.
  • No cookies for authentication. The demo uses browser storage for its simulated session.

The page loads the DM Sans font from Google Fonts. That request is made to Google’s font service. It is not used for analytics or advertising.

4. Where data lives

Demo data is stored in your browser’s localStorage. The demo session is stored in sessionStorage. Nothing is sent to a database because there is no database in this build.

You can remove the demo data by clearing site data for this page in your browser settings. Closing the tab clears the demo session. A future demo reset control may also clear the stored data.

Because this is browser storage, another person using the same browser profile could see the demo data. Do not use real information.

5. Sensitive information

Student and parent contact details are sensitive. In a real deployment, they would need role-based access, secure transport, and an audit trail. The demo has none of those protections.

  • Do not enter real names, phone numbers, enrollment IDs, or parent details.
  • Do not use the demo to store or share actual leave requests.
  • Do not treat the demo’s browser storage as private or permanent.

6. Production requirements

A production version would require, at minimum:

  • Written approval from the college and the department.
  • Server-side authentication and authorization on every request.
  • A protected database with encrypted transport.
  • Password hashing with a suitable algorithm such as Argon2id or bcrypt.
  • Secure, HTTP-only session cookies and session expiry.
  • Server-side rate limiting and lockout.
  • Role-based access for students, HODs, and administrators.
  • Audit logs for decisions and access to sensitive records.
  • An officially authorized attendance data source — not scraping or shared student credentials.

These are requirements, not features that currently work. The demo does not claim production security.

7. Changes to this policy

This policy may change as the project moves from the demo stage to a reviewed production plan. Updates will carry a new effective date and version label.

Current version: demo-v1 · Effective 25 October 2026.