Privacy Policy

1. Secure Server-Side Processing and Retention

Website ZIP Optimizer source files and results are scheduled for deletion after the configured retention window, currently 24 hours. Limited job records may remain for payment reconciliation, abuse prevention, support, and accounting, but we do not intentionally store the source-code contents in application logs.

2. Information We Explicitly Collect

Ordinary tool input is transmitted to and processed by the Django application. It is not saved as a reusable tool-content record, but it is not invisible to the server or its operators. The platform also processes the following information:

• Contact Interactions: If you utilize our contact forms or send an email to our engineering team, we collect your name, email address, and any textual context you provide to resolve your ticket.
• Technical Metadata: Application, proxy, CDN, firewall, and hosting logs may record IP addresses, user-agent details, requested paths, response status, and timestamps for operations, security, and abuse prevention. Retention depends on the deployed services and their configuration.
• Paid ZIP Job Metadata: We retain job identifiers, filenames, file counts, size and savings measurements, processing status, timestamps, payment references, and an email address when supplied by Stripe Checkout.

3. Cookies and Analytics Disclosure

The current repository uses Django CSRF and session cookies for form protection, authentication state, messages, and access to private guest ZIP-job references. No first-party analytics script or analytics cookie is configured in this repository. A hosting provider or CDN may still produce operational traffic logs, and a future deployment must update this policy before enabling additional analytics or tracking.

4. Security Architecture

To protect the metadata running through our platform, we enforce strict production protocols:

The public site is intended to be served over HTTPS (TLS). Production access controls, proxy rules, and firewall policy are deployment responsibilities and should be reviewed with the hosting configuration rather than inferred from the Django application.

5. Third-Party Content Delivery

To optimize Core Web Vitals and asset load speeds, we load static styling libraries, vector font symbols, and framework scripts using trusted Content Delivery Networks (CDNs) and Google Fonts. When your browser fetches these styling assets, the external CDN node may process your IP address and basic device user-agent string as part of standard network handshake protocols.

Payments for Website ZIP Optimizer are handled by Stripe. Stripe receives and processes checkout and payment information under its own privacy terms. ScriptZip receives payment status, transaction references, amount, currency, and customer details needed to verify and support the paid job; ScriptZip does not receive or store full card numbers.

6. Access, Correction, and Deletion Requests

Depending on applicable law and the records ScriptZip actually holds, you may request access to, correction of, or deletion of personal information associated with an account, payment-support record, or direct communication. A request may require identity verification and may be limited by security, accounting, dispute, or other legal retention duties.

• Describe the account, ZIP job reference, payment reference, or support message involved.
• Do not send passwords, API secrets, or full payment-card details in a privacy request.
• Operational logs and third-party payment records follow the applicable provider settings and legal requirements.

Send requests to the privacy contact below.