KayLab Privacy Policy

Effective date: September 11, 2026

KayLab connects a user-authorized Google Flow browser session with KayLab Local API Server running on the same computer. This policy explains the data involved in that operation.

Data KayLab handles

• An administrator-issued API key, stored locally in Chrome storage. The local API Server sends it over HTTPS to the KayLab licensing service only to validate the license.
• A one-way device hash derived from limited device characteristics to enforce one license key per device. Raw device characteristics are not sent to the licensing service.
• Prompts, selected reference images, and generated-media results, processed only to perform a user-initiated media request through Google Flow.
• Local settings, queue state, and media-library state, stored in Chrome local storage on the user’s device.

How data is used and shared

KayLab uses the API key and device hash to validate and enforce the license. Prompts, references, and media results are exchanged with Google Flow only to complete the user-requested generation. KayLab does not sell personal information or use this data for advertising.

Retention and deletion

Users can remove the extension to clear its Chrome local storage. Administrators can release a device binding, suspend a license, reissue a key, or delete a license through KayLab License Admin. The local API Server keeps temporary media/file mappings in memory; they are cleared when the server restarts.

Security

License validation is transmitted over HTTPS. The extension communicates with the local API Server only at 127.0.0.1. Users should keep API keys private and run only KayLab software obtained from the official distribution link.

Contact

For privacy questions, contact the KayLab support group on Zalo.