Developer Privacy Notice
Effective September 20, 2026 · Developer beta
Information KleeQuiz processes
The Developer Platform can process API-key identifiers/hashes, key labels, credit balances, billing ledger entries, request IDs, endpoint/usage metadata, timestamps, response status, latency, portal-session tokens, security/rate-limit data, and information you provide when requesting support or access.
Uploaded documents
PDF/DOCX documents sent to the generation endpoint are temporarily written to server storage while the request is processed. In this production package, temporary source uploads and temporary generation-run artifacts are configured for deletion after processing by default. Limited usage, billing, security, and error metadata can be retained. Operational backups or provider logs may persist for their normal retention periods.
Model training
This beta API package does not use uploaded developer documents to train the KleeQuiz AI model. If that practice changes, this notice should be updated before the change is deployed.
Payments
Stripe processes checkout/payment information. KleeQuiz receives identifiers and event data needed to confirm the purchase and credit the correct developer key. KleeQuiz does not intentionally store full payment-card numbers.
How information is used
Information is used to provide API responses, authenticate keys, maintain balances, process payments, prevent abuse, investigate errors, secure the service, provide support, and understand aggregate service usage.
Third-party infrastructure
KleeQuiz can use hosting, DNS/CDN, email/support, and payment providers to operate the service. Those providers process information according to their roles and agreements.
Your choices
You can revoke a developer key through KleeQuiz support/admin controls and can contact support@kleequiz.com with privacy, access, correction, or deletion questions. Some billing/security records may need to be retained where legally or operationally required.
Security and changes
No online service can promise perfect security. Keep API keys secret and rotate/revoke them if compromised. This notice may change as the beta platform evolves.