Privacy Policy

1. Information We Collect

Because Kliky operates locally, the scope of data collected is extremely minimal and restricted only to what is necessary to run our service and validate purchases:

• License Key Validation: When you purchase Kliky and input your license key, the app securely contacts our payment and licensing infrastructure (Polar.sh) to validate your active subscription or lifetime product.
• Basic Device Info: To prevent software misuse and enforce seat limits, our licensing portal associates your license key with an anonymous hash of your hardware profile (operating system platform and generic system metrics). No personally identifiable information (PII) is linked to this.
• Website Traffic: We collect aggregate, non-identifying analytics on our public landing page (such as page visits, download metrics, and browser configurations) to optimize web responsiveness.

2. What We DO NOT Collect

To maintain absolute transparency, Kliky strictly excludes the collection of:

• Any keystrokes, letters, symbols, words, or passwords typed on your keyboard.
• Any logs of applications running in parallel with Kliky.
• Any microphone, speech-to-text, or ambient acoustic logs.
• Any persistent network telemetry regarding your typing speeds or active typing habits.

3. Third-Party Services

We process licensing and purchases using industry-grade secure partners:

Our license verification, product delivery, and payments are managed securely by Polar.sh. You can review their comprehensive standards under the Polar Privacy Policy. Your billing data and credit card information never touch our databases.

4. Data Security

Your local application configuration (such as chosen sound profiles, custom latency limits, active volume levels, and validated license metadata) is stored securely on your machine using encrypted binary storage files.

5. Changes to This Privacy Policy

We reserve the right to modify this policy as Kliky continues to evolve. However, our baseline commitment to **offline-first local key processing and zero keystroke logging** will remain absolute and permanent. Any revisions will be accompanied by an updated revision date at the top of this document.