Privacy Policy & Data Protocol
Last updated: October 2026
At Zobinzo, protecting your privacy is not an afterthought—it is the foundation of our entire system. This document outlines how files are processed, stored, and permanently destroyed.
1. File Uploads & Processing Architecture
When you upload a document to any Zobinzo online utility:
- Transport Layer Security: Files are transmitted exclusively over encrypted TLS/HTTPS connections.
- Sandbox Isolation: Uploaded files are placed in an unguessable UUIDv4 directory in a private vault directory protected with server access controls denying all direct public web access.
- Single-Session Tokens: When your file is processed, a random token is generated. Direct file paths on disk are never exposed to the web browser.
2. Automated 60-Minute Purge Cycle
We do not maintain permanent file storage. All files associated with your task—including input files, intermediate temporary streams, and output results—are subject to our automated garbage collection cron job. Files older than 60 minutes are permanently unlinked and erased from the filesystem.
3. Rate Limiting & Protection
To prevent denial of service and automated scraping, we employ sliding-window rate limiters. Transient IP address hashes are kept in temporary cache memory for up to 60 seconds to enforce rate thresholds and are subsequently expired.
4. No Behavioral Tracking or Third-Party Analytics
Zobinzo does not use third-party behavioral trackers, cross-site advertising networks, or invasive analytics beacons. We respect your browser's privacy and Do Not Track signals.
5. Contact Us
If you have questions regarding this privacy policy or our data lifecycle routines, please reach out to us via our contact page.