Student Document Vault Web App with Verified Sharing and Expiry Alerts

A Student Document Vault is a web app that stores a student's marksheets, certificates, Aadhaar card, PAN card, passport and college ID in one organised, searchable place, and shares any of them through a verified link that expires after a set number of days. The vault records an expiry date for every document that has one and alerts the student 30 days before it lapses, with reminders at 14 and 7 days, so no form is blocked by an expired paper. Sharing is verified: the recipient gets a one-time code by email or phone, the link opens only after the code matches, and every open — including failed attempts — is written to an access log. The owner can revoke a link and disable downloads. In the demo, 12 sample documents totalling 8.4 MB render across 3 views from a single 33 KB HTML file, and the vault flags 4 documents expiring within 30 days, including 1 already expired.

Students keep the same documents scattered across phone galleries, email attachments, chat apps and photocopy shops, and rediscover the mess at the worst moment — a scholarship deadline, an admission form, or a verification visit. A certificate that expired months ago only surfaces when an office rejects it, and a marksheet sent as a plain chat attachment can be forwarded to anyone with no record of who opened it. The vault fixes both problems in one place: every document has a known location, a category and an expiry date, and every share is a controlled, expiring, logged link instead of an open file. The demo shows this working end to end with realistic student documents, so the idea can be judged from the running app rather than from a description.

The flow runs from upload to alert to share. A student uploads a document, names it, picks one of 4 categories, and enters an expiry date if the document has one; documents without an expiry, such as an Aadhaar card or a marksheet, are stored with no expiry and never raise alerts. The vault files the document with its name, size and upload date, and compares every dated document against today's date each time the dashboard loads, sorting alerts from the nearest expiry outward. When a document enters the 30-day window, an alert appears on the dashboard and in the alerts view, with reminders at 14 and 7 days. To share, the student picks a document, sets a 7 to 15 day expiry and permissions, and sends the link; the recipient verifies with a one-time code, and each open is written to the access log. Revoking a link stops access at once, while the document stays in the vault.

1. The student uploads a document (PDF, JPG or PNG, up to 10 MB per file as a design target), names it and picks a category.
2. An expiry date is entered where the document has one; documents with no expiry are stored with no expiry and never raise alerts.
3. The vault stores the document's name, file name, size, upload date, category and expiry date in browser local storage.
4. On every dashboard load, the expiry engine compares each dated document against the current date and sorts alerts from the nearest expiry outward.
5. Documents entering the 30-day window raise an alert on the dashboard and in the alerts view, with reminders at 14 and 7 days; expired documents are marked and blocked from sharing.
6. To share, the student selects a document, sets a 7 to 15 day link expiry and view-only or download permission, and copies the link.
7. The recipient verifies with a one-time code, the document opens, and the attempt is written to the access log; the owner can revoke the link at any time.

Tech stack:

• HTML5 · CSS3 · JavaScript (vanilla, no framework)
• Browser local storage (Web Storage API)
• Single-file demo app (no build step)
• JSON sample dataset (12 documents)
• Flexbox · CSS Grid responsive layout
• Modern desktop browser (Chromium runtime)
• Git

The vault's strongest capabilities are its verified share links, its expiry alerts, and its plain, searchable document store. A verified share link carries a 7 to 15 day expiry, view-only and download controls, and an access log that records every open with its time and verification result, so the student always knows who saw a document and when. The expiry alerts watch every dated document and flag it 30 days before expiry, with reminders at 14 and 7 days, and mark anything past its date as expired so it cannot be shared until renewed. The document store itself keeps 12 sample documents across 4 categories — Identity, Academic, Certificates and Financial — with file names, sizes, upload dates and expiry dates for each, plus search and category filters that narrow the list. A settings view states plainly what the demo stores in the browser and what the optional server build adds, so nothing about verification or storage is oversold.

• [Document upload and categorisation] Upload a document, give it a name, pick one of 4 categories — Identity, Academic, Certificates or Financial — and enter an expiry date where one applies. The vault stores the file name, size and upload date with each entry.
• [Verified share links with expiry] Create a share link for any document with a 7 to 15 day expiry, view-only or download permission, and a copyable link. The demo shows the one-time-code verification step in the flow; real OTP delivery by email or SMS is an optional server customisation.
• [Expiry alerts dashboard] Every dated document is checked against the current date and flagged 30 days before expiry, with reminders at 14 and 7 days. Expired documents are marked clearly and cannot be shared until renewed.
• [Access log] Every open of a shared link is recorded with the recipient, date, time and verification result, including failed attempts that were denied access.
• [Search and category filters] Search documents by name or file name and filter by category, so a marksheet or certificate is found in seconds even as the vault grows.
• [Link revocation and download control] Revoke any share link at any time and disable downloads on a share, while the document itself stays safely in the vault.
• [Storage and privacy transparency] A settings view states exactly what the demo stores in the browser and what the full server build adds, so the limits of the front-end demo are never hidden.

• Complete single-file demo web app (HTML/CSS/JavaScript) with working upload, search, filter, share-link, access-log and expiry-alert flows
• Sample document set of 12 realistic documents with file names, sizes, upload dates and expiry dates
• Setup instructions for running the demo in any modern browser
• Project report outline and documentation (architecture, data flow, verification design, limitations)
• Project abstract PDF (background, problem, objectives, methodology, architecture, outcomes, applications, future scope)
• PPT presentation for final review
• Viva Q&A preparation document (local storage, share-link design, expiry logic, verification vs server builds)