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

When you print sensitive files—like bank statements, academic records, identity cards, or legal contracts—privacy is your highest priority. In traditional print shops, your file is loaded onto a public computer where it might sit in the "Downloads" directory or browser history for months, vulnerable to anyone who sits down next.

With the rise of wireless and cloud printing, files travel across the internet before reaching the printer. This prompts an important security question: **Who has access to your documents in transit and at rest?** At MIMO, we believe document privacy is a fundamental student right. Here is an in-depth explanation of how cloud printing works under the hood and what steps we take to protect your files.

1. Encryption in Transit: Keeping Interceptors Away

The moment you select a file and tap "Upload" on your phone at printmimo.tech, the document is sent to our servers. To make sure that nobody snooping on the campus Wi-Fi network can intercept your file, MIMO uses **HTTPS (Hypertext Transfer Protocol Secure)**.

All transmission data is encrypted using SSL/TLS protocols. This locks the file in an encrypted tunnel between your mobile device and our cloud servers, preventing packet sniffing, middleman attacks, or interceptors from extracting the payload.

2. Secure Cloud Storage and File Processing

Once uploaded, files are temporarily hosted in a highly secure, restricted-access bucket on Firebase Storage.

• No Public Access: Our backend security rules strictly forbid direct public URL access to user files. Only authenticated server routines can call download endpoints.
• Document Isolation: Documents are associated with unique, randomized session IDs, ensuring that one student's files cannot be accessed or indexed by other users in the system.

3. Kiosk Spooling and CUPS Management

When you enter your 4-digit code at the physical kiosk, the local Raspberry Pi controller queries our backend database, verifies payment authorization, and streams the document directly into memory or a temporary directory using safe HTTPS streaming connections.

The document is then passed to the local CUPS (Common UNIX Printing System) queue to feed the printer spooler. Standard printer drivers execute the print job and convert the document into raw rasterized dots on the paper.

4. The Shred Protocol: Instant File Deletion

This is the most critical element of document security. Once the CUPS printer daemon confirms that the pages have physically ejected from the machine:

1. The local Pi listener deletes the temporary downloaded spool files from its local flash disk.
2. It triggers a callback API on our backend that permanently deletes the corresponding file object from Firebase Cloud Storage.
3. The Firestore document entry's state is modified, rendering the 4-digit code inactive to prevent anyone else from reprint-hijacking your document.

If you purchase a print code but decide not to print your file, the system runs an automated cleanup script that **purges the document and triggers a full refund automatically after 24 hours**. We never save your files long-term.

5. Best Security Habits for Students

While MIMO enforces maximum hardware and software security protocols, you can take simple steps to ensure absolute privacy:

• Avoid Public Shared Terminals: Always use your personal mobile phone to navigate to printmimo.tech.
• Clear Browser Downloads: If you downloaded a document on a shared laptop, make sure to delete it from the system downloads and empty the trash before leaving.
• Verify Kiosk Location: Double-check the ID of the kiosk (e.g. CV-001 or SV-002) to ensure you collect your sheets immediately, preventing papers from sitting unattended in the output tray.