Cookie Protocol

1. The Technical Nature of Our Imprints

Cookies are minute data constructs (text files) forged by our servers and embedded within your browser architecture when you interact with 5MinPDF. We classify our digital imprints into distinct technical categories:

• Session Imprints (Volatile): These constructs exist only while you traverse the Forge. The moment you close your browser, they are instantly vaporized. They are critical for tracking an active document conversion without mixing your files with another user's data.
• Persistent Imprints (Anchored): These remain on your device for a strictly defined duration. We utilize these solely to remember your structural preferences (such as your language selection or your acknowledgment of our Cookie Banner) so you are not interrogated repeatedly upon return.
• First-Party Architecture: The vast majority of imprints are forged directly by 5MinPDF. They do not report to outside entities.

2. Essential Forge Mechanisms (Non-Negotiable)

Certain digital constructs are mathematically required for our architecture to function securely. Without these, the Forge collapses, rendering our tools unusable. Because of their critical nature, you cannot opt-out of these while utilizing our service.

Security & Routing Imprints

• CSRF Tokens (Cross-Site Request Forgery): A mathematically complex imprint generated to verify that the commands sent to our servers actually originated from you, actively neutralizing malicious third-party hijacking attempts.
• Load Balancing Constructs: When thousands of users enter the Forge simultaneously, these cookies ensure your session remains tethered to a specific, dedicated server node, preventing your upload from breaking mid-process.
• Encrypted Authentication: For members of the Pro or Team Forge, encrypted JSON Web Tokens (JWTs) stored as secure cookies maintain your access rights without forcing you to re-enter your credentials on every page load.

3. HTML5 Local Storage Protocols

Modern web architecture allows for data to be stored locally within your browser rather than constantly transmitted back and forth to our servers via traditional cookies. We utilize this secure methodology for enhanced privacy.

• The Consent Ledger: When you interact with our Cookie Protocol banner, we forge a record directly into your browser's Local Storage (specifically labeled as forgeCookieConsent). This ensures your decision is respected locally, rather than transmitting a tracker to our databases.
• Tool Preferences: Minor configurations, such as your last used compression settings, are housed entirely on your local machine using this protocol.

4. Telemetry & Anonymous Analytics

To continually sharpen our tools and prevent server catastrophic failure, we must understand how the Forge is being utilized. We deploy anonymized telemetry protocols for this sole purpose.

• Performance Metrics: We track broad, faceless metrics—for instance, measuring if the "PDF to Excel" conversion algorithm is taking an average of 4 seconds or 10 seconds under heavy load.
• The Zero-Identity Promise: Telemetry data is stripped of identifying markers. We do not attach your IP address, your geographic location, or your file metadata to these performance logs. They exist solely as raw, structural data to help us optimize the servers.

5. Authorized Third-Party Integrations

5MinPDF is an independent entity, and we maintain a hostile stance toward third-party advertising cookies, marketing pixels, or social media shadow trackers. We permit only highly vetted external imprints necessary for global utility.

• Global Translation Protocol (Google): To ensure the Forge is accessible in over 100 languages, we integrate the Google Translate module. This tool may embed a structural cookie (often identified as googtrans) to remember your selected dialect. This integration operates under Google's enterprise privacy framework, but we do not permit it to harvest your uploaded documents.

6. Sovereignty: Managing Your Imprints

You maintain absolute technical sovereignty over your browser environment. You can command your software to purge or block our constructs at any time.

Execution Protocols

You can modify your browser's security settings to reject all cookies or to alert you when an imprint is attempted. However, be explicitly warned: Purging or blocking "Essential Forge Mechanisms" will cause the PDF processing tools to critically fail, as our servers will lose the ability to securely route your processed files back to your specific session.

• Command sequence for Google Chrome
• Command sequence for Mozilla Firefox
• Command sequence for Apple Safari

If you require advanced assistance in manually wiping the forgeCookieConsent ledger or purging your local storage, dispatch a request to our Architect at privacy@5minpdf.com.