1. About the document and contacts
The policy applies to kevmi.one website, personal account, payment pages, support, and the Kevmi bot. For data questions, write to support@kevmi.one. Specify which account or order the request relates to; do not send passwords, CVV, confirmation codes, or private keys.
2. What data is used
When logging in via Telegram, we receive a verified Telegram ID, available name and username, and chat identifier. The account stores stores, their identifiers and settings, applications, website addresses, business descriptions, and contact details that you provided.
To process an order, we use amount, currency, description, order number, information provided by the store, selected payment method, statuses, and technical operation identifiers. Do not place unnecessary personal data in the order description or metadata.
Support requests and email correspondence contain sender address, subject, text, attachments, and technical delivery information. Technical data may include IP address, request time, browser information, and security events.
3. What the data is for
Data is needed for login and account protection, store isolation, invoice creation, sending payment requests, payment status verification, application review, notifications, support, and investigation of disputed operations. The basis for processing depends on the situation: performance of the requested service, mandatory requirements of applicable law, protection of the service and users, or consent when necessary.
4. Payment details
Card details are passed to payment infrastructure to process the operation. Kevmi does not store PAN or CVV in the personal account database and does not use them for recurring charges. Enter details only in the designated payment form; do not share them in chat, metadata, or support requests. Crypto payments leave public records in the relevant network.
5. Processors and data transfer
The service uses hosting infrastructure and Cloudflare, Telegram for login and notifications, Resend and email infrastructure for messages, payment providers, and Inception for AI functions. They receive information necessary for the specific function and may process it in other countries under their own terms. Required data may be shared with competent authorities when there is a mandatory legal basis. Sale of personal data is not a function of Kevmi.
6. AI and site verification
When contacting the AI, the question text and a limited dialog context are transmitted. If you have enabled access to your account data, the assistant may request records of your stores, payments, events, requests, and inquiries with support responses. The reading tool does not transmit integration secrets or card details. Access can be disabled before the next question. When verifying a store, the provided description and available public site pages are analyzed. The AI does not receive the right to independently approve a store or conduct payments. Do not include secrets, bank details, or unnecessary personal information in requests.
7. Cookies and browser storage
Session cookies enable login and request protection. Browser storage is used for language, theme, selected store, and on-device chat history. Clearing cookies will end the session, and clearing local storage will remove local history and settings. Technically necessary tools are not intended for advertising profiling.
8. Storage and protection
HTTPS, access control verification, store separation, protected secrets, and backups are used. Data is kept as long as needed to provide the service, resolve requests, protect against abuse, and fulfill applicable obligations. The retention period depends on the data category; payment and audit history is not automatically deleted with the session. Backups may retain data until their scheduled replacement.
9. Your requests
You can request information about processing, correction, access, deletion, restriction, or other rights under applicable law via support@kevmi.one. To protect the account, we may verify your connection to it. Deletion may be limited by mandatory retention, an incomplete operation, or the need to resolve a dispute; the basis for the limitation will be stated in the response. Notifications are configured in the account and bot; the /stop command disables notifications.
10. Policy updates
The current version is published on this page with a date. Significant changes requiring additional notice or consent under applicable law are handled separately.