Privacy Policy

1. Zero-Storage Philosophy

StickCode is built on a "Privacy by Design" architecture. Our engine is a stateless processor. We believe that your data belongs to you, and our role is purely to provide the mathematical transformation for optimization and security.

2. Processing vs. Collection

Live Demo & API

When using our live engine demo, data is sent to our server via a secure TLS-encrypted tunnel. The processing happens in volatile memory (RAM) and is immediately purged once the response is sent back to your browser. No data ever hits our hard drives.

Local Libraries

For licensed users, processing happens entirely on your own infrastructure. StickCode does not "phone home" with any of your data payloads.

3. Information We Collect

We only collect information necessary to provide and manage your license:

• License Management: For license validation, we store non-sensitive hardware identifiers (Fingerprints) and license keys.
• Billing Information: Handled securely via third-party providers (FreeNbuy). We never store your credit card details on our servers.
• Technical Logs: Routine server logs (IP addresses, browser type) are kept for security purposes and are automatically deleted after 30 days.

4. Security Standards

StickCode uses industry-standard encryption protocols (AES-256-GCM), HKDF-SHA256 key derivation for licensed builds, and native Brotli compression (quality 0–11). Our own internal systems are hardened against unauthorized access to ensure the integrity of our software distribution.

5. Third-Party Sharing

We do not sell, trade, or otherwise transfer your personally identifiable information or your processed data to outside parties. This does not include trusted third parties who assist us in operating our website or servicing you (like payment processors), so long as those parties agree to keep this information confidential.

6. Policy Updates

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Effective Date" at the top.