1. General provisions
1.1. Purpose of this Policy
This Privacy Policy explains which information KantTools processes, why it is needed and when it may leave the Service infrastructure.
1.2. Main principles
KantTools aims to collect only information needed for account access, licensing, payments, support, security and the features requested by the user.
1.3. Relation to the Terms
This Policy is part of the documents governing use of KantTools and should be read together with the Terms of Use.
1.4. If you disagree
If the user does not accept this Policy, they should stop using the Service and contact support about account or data questions.
2. Information processed by KantTools
2.1. Account and authentication
We may process an account identifier, display name, avatar, sign-in provider identifiers, session data and messages needed to authenticate the user.
2.2. License and device
We may process a license key, plan, activation status, device identifier, app version and security events needed to provide and protect access.
2.3. Payments
Payment providers process payment details. KantTools receives order, status, amount, currency, provider and transaction identifiers, but does not receive full bank card details.
2.4. User-selected content
When a user starts a feature, we process the files, text, audio or video needed to perform that request. The user decides which content to submit.
2.5. Technical information
We may receive logs, timestamps, error details, browser or app information and approximate technical data needed for reliability and security.
3. Why information is used
Information is used to sign users in, provide licenses and features, process payments, answer support requests, prevent abuse, diagnose failures, improve reliability and meet legal obligations. We do not use account data for unrelated behavioral advertising.
4. AI features
4.1. What is sent to a model
Only the input needed for a requested AI operation is sent to the relevant model provider. The exact payload depends on the feature and the content selected by the user.
4.2. Model providers
A model provider may process the request under its own terms. KantTools selects providers for the applicable feature and limits the transmitted data to the requested operation.
4.3. Request history
Some requests and results may be stored for the feature, account support, abuse prevention or debugging. Available deletion controls are shown in the product interface. Request identifiers, model, timestamps, processing status, usage and account-linked charging records may also be retained for usage accounting and error review.
5. WATA and Tribute payments
5.1. WATA
WATA and participating banks process the payment on their side. KantTools receives the status and transaction information needed to activate access and handle support.
5.2. Tribute
Tribute processes one-time payments and subscriptions where offered. Subscription management and payment records may also be governed by Tribute's own policy.
6. Authentication and integrations
When the user chooses Telegram, Google or another supported integration, the relevant provider sends the identifiers needed to create or link an account. Provider processing is also governed by that provider's policy.
7. Sign-in notifications
We may send notifications about sign-ins, new devices, key changes, payments and important account events through available product or Telegram channels.
8. Marketplace and support
8.1. Published materials
A Marketplace publication may include the author name, preview, description, file metadata and other information deliberately supplied for publication. The author should not upload confidential information.
8.2. Support requests
Support messages and attached diagnostics are used to answer the request, verify ownership, investigate problems and protect the Service. A request may be retained for support history and security.
9. When information is disclosed
Information may be disclosed to service providers that host, secure, process payments, deliver notifications or provide an explicitly requested AI feature. It may also be disclosed when required by law, to protect rights or to investigate abuse. We do not sell personal data.
10. Storage and security
KantTools uses access controls, encrypted connections, signed payment notifications, session limits and other reasonable technical measures. No online service can guarantee absolute security, so users should protect their account and keys.
11. User rights and deletion
11.1. Access and correction
A user may request basic account information, correct inaccuracies, change available settings, unlink an integration or device, issue a new key and delete an available AI session.
11.2. Deletion request
Send an account deletion request to @kantsupportbot. After verification, KantTools deletes or anonymizes information that is no longer needed and has no other lawful retention basis. Deletion ends related access and does not automatically cancel a Tribute subscription.
11.3. Information that may remain
Minimal payment, refund, dispute, security and abuse records may remain when required by law, needed to protect rights or necessary to prevent an immediate bypass of restrictions. They are limited to that purpose.
11.4. Backups and publications
Deleted information may remain for a limited time in backups until scheduled rotation. A public Marketplace card is removed from publication; material relevant to a rights complaint may be kept until review is complete.
12. Local storage and cookies
The website and app use session tokens, local storage and technical cookies for sign-in, language, interface settings and request security. They are not used for third-party behavioral advertising.
13. Changes and contact
This Policy may be updated when features, architecture, providers or legal requirements change. The update date is shown at the beginning. Privacy questions and data requests can be sent to @kantsupportbot.