KartaXabar Privacy Policy
Version 2026-11-15.2. Controller: PAYMENT TECH AI, MASULIYATI CHEKLANGAN JAMIYAT. This policy covers the mobile apps, website and Telegram Mini App.
1. Contact and requests
Contact [email protected] or +998 91 663 77 44, Mustakillik MFI, Zarafshan kuchasi, 61-ui, gp Laish, 141000, Uzbekistan. Request access, correction, export, withdrawal of consent or deletion through support. We may verify account ownership; support must not receive your PIN, CVV or OTP.
2. Information processed
Account information includes your phone number, user identifier, supplied display name, accepted document versions and consent time. Authentication uses short-lived OTP challenges, protected verification values and session records; plaintext OTPs and session tokens are not intended to be logged.
Your ledger contains account names, currencies, income, expenses, amounts, dates, categories, notes, budgets, debts, recurring bills and reminders. Do not put unnecessary sensitive information about yourself or others in notes.
If you connect a supported bank card, card number, expiry and bank verification code are transmitted for the provider request. Provider identifiers, masked numbers, last digits, holder/bank names, connection status and available transaction history may be stored. We do not request PIN or CVV.
Optional external login or Telegram linking supplies the provider-verified identifier and necessary profile fields, not the provider password. Disabled login methods do not collect information.
Technical information includes IP address, request time, User-Agent, security restrictions and delivery status. SMS logs use status, country, last four phone characters and a keyed hash rather than OTP/message text. Support correspondence includes its content and reply address.
3. Purposes and grounds
We process information to provide the requested account, authentication, ledger, synchronisation, bank connection, export and support functions; to record accepted terms; and to secure the service and prevent fraud and abuse. Processing required by law or a valid authority request is limited to that obligation. Optional permissions and integrations are based on your choice, with separate consent where required. Withdrawal does not retrospectively invalidate prior lawful processing.
4. Device permissions and copies
Notifications support reminders and can be disabled in system settings. The current mobile release does not request SMS inbox, call log, contacts, microphone or precise location access. Export creates a file that you choose to share. Session credentials use platform secure storage; the local ledger resides in app-private storage. iOS device backups may contain the local ledger and are controlled through your device/Apple settings. Android app backup is disabled. Deletion cannot remove files you previously exported elsewhere.
5. Recipients
Eskiz and telecommunications operators receive the phone number and SMS content needed to deliver login messages. Supported banking providers receive requests needed for the selected bank function. Telegram independently processes information under its own terms when you use it. Hosting providers supply server infrastructure; Cloudflare may process network information for delivery and security. Access is limited to the necessary service purpose. Authorities receive data only on a lawful basis and within the necessary scope. We do not sell ledger records to advertisers or use them for cross-company advertising tracking.
Firebase Analytics and advertising SDKs are not enabled in this release. Registering a Firebase project does not by itself send device data to Firebase. Before enabling server push through FCM/APNs, this policy must be updated for device tokens, platform and required notification content.
6. Location and international processing
Servers and international network providers may process information outside Uzbekistan. Applicable legal safeguards and transfer grounds must be established. Accepting this policy does not override mandatory storage or cross-border requirements. Information about hosting location and safeguards can be requested from support. KartaXabar does not offer collection of biometric or genetic data. The Operator is responsible for establishing the applicable lawful transfer mechanism.
7. Retention
Active account, profile and ledger records remain while you use the service or until you delete them. Confirming account deletion removes the active profile, sessions, ledger, preferences, cards and related history, account links, reminders and device records.
An OTP is valid for five minutes. Expired OTP and external-login verification records are removed by the daily cleanup after a one-day grace period, normally within two days after expiry. Access sessions normally last 15 minutes and refresh sessions 30 days. Expired refresh-session records are removed after the same one-day grace period and daily sweep. Revoked sessions may remain until refresh expiry to detect reuse.
SMS delivery/security logs and phone/IP quota events are retained for 90 days, up to 91 days including the daily sweep. Phone/IP lock identifiers no longer associated with an active account, challenge or retained event are removed in the same cleanup. Application server file logs use 30-day rotation and a 2 GB total cap; web-server logs use 10 daily archives. Container diagnostics are size-limited to 30 MB.
Daily database backups are deleted after 30 days by the daily sweep, with an operational maximum of 31 days. A pre-deletion copy can remain in restricted backups during this period; it is not used for active service or advertising. If a restore is needed, account-deletion requests must be reapplied before reopening the service.
Support correspondence is retained for up to 180 days after resolution. A legal obligation, active dispute or lawful authority request may require separate retention, limited to the necessary information and period. We explain applicable exceptions to the extent legally permitted.
8. Deletion and rights
Use Profile → Personal information → Delete account, https://kartaxabar.uz/delete-account or [email protected]. Uninstalling does not delete the account. Your bank, Telegram, Apple or Google accounts remain with their respective providers. Exports you shared outside the service are outside the Operator's control.
Subject to applicable law you may learn whether information is processed, access it, correct inaccuracies, export ledger data, request restriction or deletion, withdraw consent, and complain to competent authorities or a court. Where a legal exception prevents deletion, the reason and retained scope should be explained.
9. Security and children
We use HTTPS, session revocation, OTP attempt limits, protected device credential storage and restricted administrator access. No system guarantees absolute security; protect your device. Incidents are addressed and notifications made as required by applicable law. The service is not directed at children; contact support about unlawfully collected child information.
10. Updates
The version and date appear above. Material new purposes, recipients or data categories require an updated policy and renewed consent where applicable. A service change does not automatically authorise advertising or bank transactions.