Privacy Framework

Privacy Policy

Effective Date: May 17, 2026 • Version 1.0

1. Our Data Security Commitment

At Printify, we design self-service stationery printing systems with privacy in mind. We understand that your uploaded documents are highly personal, confidential, and intellectual. As a proprietary SaaS platform, our core architectural design centers around data minimization—meaning we store only the bare minimum of details needed to get your document from the cloud to the physical printer.

CRITICAL PRIVACY SAFEGUARD: MIDNIGHT PURGES

We do not permanently archive your files. Every night at 12:00 AM (midnight), an automated Vercel cron job sweeps all print containers. All completed, cancelled, or abandoned PDF documents are completely and permanently deleted from our Supabase storage buckets. We retain only light metadata (such as the number of pages, monochrome/color designation, and calculated price) strictly for local accounting and business analytics dashboards.

2. Information We Collect

To successfully deliver printing orders, we process and temporarily collect:

  • Uploaded Documents: Temporary PDF files stored securely using authenticated tokens in Supabase buckets.
  • Print Telemetry: Spool metadata including monochrome/color status, page counts, copy counts, and duplex settings.
  • Account Credentials: Basic email identification for coordinators and authorized users.
  • Hardware Telemetry: Basic local printer names and status flags (Online/Offline) communicated through the Tauri spooler bridge.

3. Local Printing Bridge Telemetry

The Tauri-based local printing bridge runs locally on operator workstations. It executes silent print spooling via SumatraPDF. The bridge strictly processes documents within the context of your print shop and communicates with the Supabase API to fetch waiting documents. No contents are ever cached or analyzed locally.

4. Cookies and Web Storage

We use lightweight browser `localStorage` and authenticated session cookies to keep coordinators logged in and maintain local configuration states (such as selected printers and API server links). No tracking or profiling cookies are used.

For any questions, data access requests, or policy inquiries, please contact our administrative node at GitHub.