Document Security in the Cloud: How to Ensure Privacy When Printing

When you print sensitive files — bank statements, academic records, identity documents, medical reports, or legal contracts — privacy is your highest priority. In traditional campus print shops, your file gets loaded onto a shared public computer where it might sit in the Downloads folder or browser history for weeks, accessible to anyone who sits down next.

With the rise of wireless and cloud printing, files travel across the internet before reaching the physical printer. This raises important questions: Who has access to your documents in transit? Where are your files stored? Who can see them? How long are they kept? At MIMO, we believe document privacy is a fundamental student right — not an optional feature. Here is an in-depth, technical explanation of how cloud printing works under the hood and exactly what steps we take to protect your files at every stage.

1. Encryption in Transit: Keeping Interceptors Away

The moment you select a file and tap "Upload" on printmimo.tech, your document begins its journey from your phone to our cloud servers. Campus Wi-Fi networks are shared environments — potentially hundreds of other users are connected to the same network access points. Without encryption, anyone on the same network could theoretically intercept the data packets flying through the air using readily available tools.

MIMO uses HTTPS (Hypertext Transfer Protocol Secure) with TLS 1.3 (Transport Layer Security, the current gold standard) for all data transmission. TLS 1.3 creates an encrypted tunnel between your mobile browser and our servers using 256-bit AES-GCM symmetric encryption, negotiated through an elliptic-curve Diffie-Hellman key exchange. In plain language: your file is wrapped in an unbreakable mathematical lock before it ever leaves your phone.

This encryption prevents:

• Packet Sniffing: Attackers on the same Wi-Fi network cannot intercept or read your uploaded files.
• Man-in-the-Middle Attacks: No third party can silently intercept and modify your data between your phone and our server.
• Session Hijacking: Even if someone captures your network session, they cannot reuse your authentication tokens due to TLS session binding.

2. Secure Cloud Storage: What Happens After Upload

Once uploaded, your file is stored temporarily in a highly secured, access-controlled storage bucket on Firebase Cloud Storage (operated by Google Cloud infrastructure). Here is exactly how access is restricted:

• No Public URL Access: Firebase Storage Security Rules are configured to strictly block all direct public URL access to user files. Unlike a basic file hosting service, nobody can guess your file's storage path and download it.
• Authenticated Access Only: Only authenticated server-side routines — running as verified service accounts — can issue download tokens for your file. These tokens are single-use and expire within minutes.
• Document Isolation: Your file is stored at a unique, cryptographically random path that includes your user ID, a UUID (Universally Unique Identifier), and a timestamp hash. Even a MIMO engineer cannot easily guess the storage path for a specific user's file.
• Server-Side Encryption at Rest: Firebase Cloud Storage automatically encrypts all stored files using AES-256 encryption at rest. The encryption keys are managed by Google Cloud KMS (Key Management Service) and rotated regularly.
• No Content Analysis: MIMO's backend systems never open, read, index, parse, or analyze the content of your documents. Your files are treated as opaque binary blobs — the system knows the file size, type, and name, but never the content.

3. The Kiosk Download: Secure Streaming to the Printer

When you enter your 4-digit code at the physical MIMO kiosk, the following secure sequence occurs:

1. The kiosk's local controller (a Raspberry Pi running a hardened Linux system) sends your 4-digit code to our backend API over an HTTPS connection with mutual TLS authentication — meaning both the server and the kiosk verify each other's identity with digital certificates.
2. Our backend verifies your payment status in real-time from Firestore. If payment is confirmed, it generates a short-lived, single-use signed download URL for your file. This URL expires in 60 seconds and can only be used once.
3. The Raspberry Pi downloads your file directly into RAM or a secured temporary directory on its local flash storage, using the signed URL.
4. Your file is immediately passed to the local CUPS (Common UNIX Printing System) print queue, which feeds the printer driver.
5. The printer driver converts your document into rasterized page data (dots per inch) and sends it to the physical printer via USB.
6. Your file in RAM is cleared as soon as the CUPS job starts processing. The temporary file on disk is marked for immediate deletion once the print job completes or fails.

At no point does your document reside in any accessible web-facing directory on the kiosk. The Raspberry Pi's network interface only opens outbound connections to our backend — it does not accept any inbound connections from the public internet.

4. The Shred Protocol: Permanent File Deletion

This is the most important part of our privacy architecture. The moment the CUPS printer daemon confirms that your pages have physically ejected from the printer:

1. The local Pi listener permanently deletes all temporary spool files from its local flash storage using a secure overwrite procedure.
2. It sends a callback to our backend API confirming print completion.
3. Our backend immediately invokes a Firebase Cloud Storage deletion API call that permanently removes the original uploaded file from cloud storage. This deletion is irreversible — Google Cloud Storage does not maintain a recycle bin for deleted objects.
4. The Firestore print job document is updated to "completed" status and the 4-digit print code is invalidated. Even if someone finds your code, it cannot be used to reprint or re-download your document.

What happens if you don't print? If you purchase a print code but never enter it at a kiosk, our automated cleanup system runs every hour and purges all files associated with expired print codes (after 24 hours). Your document is permanently deleted and a full automatic refund is triggered to your original payment method. There is no need to request deletion — it happens automatically.

5. Authentication and Account Security

Your MIMO account is secured by Firebase Authentication, which handles login sessions, password hashing, and token management using industry-standard security practices:

• Bcrypt Password Hashing: Your password is never stored in plain text. It is hashed with bcrypt and a unique salt before storage, making it computationally infeasible to reverse even if a database were ever compromised.
• JWT Session Tokens: Every API request from your browser or mobile session is authenticated with a short-lived JSON Web Token (JWT). Tokens expire every hour and are automatically refreshed — a stolen token becomes useless quickly.
• No Cross-User Access: Backend Firestore Security Rules are configured so that each user can only read and write their own print job documents. There is no API endpoint that returns another user's files or print history.
• HTTPS-Only Cookies: All session cookies are marked with the Secure and HttpOnly flags, preventing JavaScript injection attacks (XSS) from stealing authentication tokens.

6. What We Never Do With Your Data

To be completely transparent, here is a list of things MIMO will never do with your data:

• We never read, scan, index, or analyze the contents of your uploaded documents.
• We never sell, share, or transfer your personal information or document history to third-party advertisers or data brokers.
• We never retain your files beyond the immediate print transaction window.
• We never store your UPI credentials, card numbers, or net banking passwords — all payment data is handled entirely by Cashfree's PCI-DSS Level 1 certified payment gateway.
• We never use your documents to train AI models or improve any automated content analysis systems.

7. Best Security Habits for Students

While MIMO enforces maximum hardware and software security at every layer, here are simple habits you can adopt to ensure complete privacy on your end:

• Always Use Your Personal Device: Never upload sensitive documents from a shared computer lab terminal. Always use your own smartphone or laptop to access printmimo.tech.
• Log Out After Use on Shared Devices: If you ever access MIMO from a friend's device, log out explicitly. Don't rely on session expiry alone.
• Collect Your Printout Promptly: Once your print code is entered and the job starts, stay near the kiosk to collect your pages immediately. Documents left in the output tray can be picked up by other students.
• Verify the Kiosk ID: Always note the kiosk ID (displayed on the screen, e.g., SV-002) to know exactly where to collect your printout in case there are multiple kiosks nearby.
• Use Strong Account Passwords: Set a unique password for your MIMO account that is different from your university login. Enable password manager autofill to avoid reuse.
• Check Your Print History: If you ever see an unexpected entry in your print history or notice a print job you did not initiate, contact MIMO support immediately at support@printmimo.tech.