Strict 12-Hour Auto-Expiration • Zero Account Required

Share files. Stay in control.

Secure temporary file sharing with cryptographically random tokens, instant QR codes, SHA-256 integrity monitoring, and automatic file destruction.

Click to select or drag and drop a file

Supported: PDF, PNG, JPG, TXT, CSV, DOCX, XLSX, PPTX, ZIP • Max 100 MB

⚡ FILE SELECTED
filename.pdf
0 KB

Simple, Controlled Temporary Sharing

How FileGuard protects files during transit, rest, and destruction

01

Upload & Hash

Your file is saved in isolated server-side storage with an unpredictable internal UUID. An authoritative SHA-256 reference hash is calculated immediately.

02

Share Link & QR

Receive a cryptographically random 256-bit tokenized URL and QR code. The token itself is hashed at rest to guard against database leak disclosure.

03

Verify & Destroy

Recipients download the file only after real-time SHA-256 integrity verification. After exactly 12 hours, the file is automatically purged from disk.

Engineered for Information & Network Security

Defensive design principles implemented across all layers of the stack

SHA-256 Integrity Verification

Files are re-hashed on download and against administrative audit requests. If any byte is altered in storage, downloads are immediately blocked.

Strict 12-Hour Expiration

Enforced authoritatively by server clocks. Expired links are rejected instantly, and background workers securely unlink and erase storage copies.

Cryptographic Share Tokens

Generated via Python's secrets CSPRNG. Stored hashed at rest using SHA-256 so compromise of metadata never reveals active download links.

Digital Forensics Module

Administrative dashboard compares application database records against OS filesystem metadata (stat ctime, mtime, atime) with live tamper simulations.

Security & Academic Transparency Notice

FileGuard implements cryptographic integrity verification via SHA-256. A matching hash verifies that the served bytes match the exact upload snapshot; it does not constitute malware scanning or zero-knowledge end-to-end encryption. Files are stored unencrypted at rest within a restricted filesystem directory and automatically deleted after 12 hours.