✓ Architecture & Data Protection

Security & Architecture

How LabDrop protects student data, eliminates digital footprints on public lab computers, and guarantees ephemeral file destruction.

Unlike conventional cloud drives that store files permanently and require account credentials, LabDrop is engineered specifically around zero data persistence and end-to-end ephemeral isolation. We designed this architecture so students can safely transfer academic work without risking exposed sessions on public workstations.

Core Security Pillars

1. Automatic 30-Min Purge

Every guest transfer is assigned a strict 30-minute lifecycle. A recurring daemon on the server permanently removes files and database entries upon timer expiration.

2. Zero Account Footprint

No phone numbers, social logins, or personal identities are required. You upload, scan the QR code on your phone, and close the browser without leaving login cookies.

3. In-Transit TLS 1.3

All communication between the lab PC, our application nodes, and recipient mobile devices is encrypted using high-grade TLS 1.3 / SSL cryptographic protocols.

4. Executable Malware Guard

To prevent malicious students or compromised PCs from propagating viruses, dangerous binary file extensions are blocked at the ingestion layer.

Detailed Technical Architecture

1. Ephemeral Lifecycle & Hard Deletion

When files are dragged into the LabDrop workspace, they are assigned a cryptographically random UUIDv4 transfer token and a 4-digit numeric verification code. The files are uploaded to isolated, time-bounded S3-compatible cloud buckets.

Our background cron worker checks active transfers every 60 seconds. Any session whose timestamp exceeds the expiry window (30 minutes for guest transfers, or 7 days for saved transfers) is deleted using bulk DeleteObjectsCommand instructions directly on the storage provider, ensuring that data cannot be undeleted or exfiltrated later.

2. Optional PIN Protection & Salted Verification

When sharing sensitive research, lab test answers, or personal projects, senders can toggle PIN Protection. The 4-digit PIN is salted and hashed using secure cryptographic primitives before submission.

A recipient attempting to access the transfer code must provide the exact PIN before any pre-signed file download URLs or ZIP download endpoints are returned by our API.

3. Prevention of Campus Network Malware

University computer labs are common propagation vectors for USB autorun viruses and malicious batch scripts. LabDrop actively prohibits the upload and transfer of the following executable formats:

  • Windows Binaries & Installers: .exe, .msi, .com, .scr, .pif
  • Script Executables: .bat, .cmd, .vbs, .vbe, .wsf, .wsh, .ps1

Files matching these signatures are rejected instantly by our upload middleware with clear notifications.

4. Pre-Signed Time-Limited Download URLs

LabDrop does not expose public, unauthenticated static links to user files. All download requests are mediated through short-lived, pre-signed AWS S3 URLs. These URLs automatically expire, rendering them useless if shared or intercepted after the session ends.

5. Zero Payload Inspection

LabDrop does not parse, read, scrape, or monetize the contents of user uploads. The platform acts as a secure, temporary transit bridge. Our optional AI features (Viva Prep & Exam Summaries) only process files when explicitly triggered by the user via the "Generate Exam & Viva Prep" action.

Responsible Disclosure & Security Contact

If you believe you have discovered a vulnerability, security bug, or edge-case in LabDrop's infrastructure, we encourage responsible disclosure. Please reach out directly to: