Who operates BitKurd Cloud
BitKurd Cloud is operated by KarzanTech in Iraq. It helps existing customers view and manage a linked broker account through a cloud service. You choose your management settings and start management. Once enabled, your saved rules can execute automatically on the connected server without a separate tap for every action, including while the phone app is closed. You can also send individual management commands. Where Auto Trading is available for your account, you separately authorize the selected bot configuration with Start. The bot can then open and manage broker trades automatically on the connected server, including while the phone app is closed. Live trading can lose real funds; there is no profit guarantee.
The native iOS app and the Android app distributed through Google Play are companions for existing customers. They do not offer registration, purchases, payment evidence submission, referral enrollment or Admin screens.
Support and privacy enquiries: dev@karzantech.com.
Information the service handles
Your service account
Name, email address, account identifier, access status, salted password hash, and sign-in/session records. The iOS and Google Play companions sign in to accounts that already exist and let you change your service password. Password changes and recovery requests create security records such as request identifiers, timestamps, attempt counts and reported outcomes. When email recovery is enabled, the service also handles a recovery-code hash and a protected email-delivery record.
Your broker connection
Account label, broker, server, login number, selected symbol and trading credentials needed by the assigned server terminal to connect.
Account activity
Balance, equity, currency, positions, pending orders, available trading history, management settings, requests and their reported outcomes.
Auto Trading
Selected bot version and configuration, symbol, position-sizing mode, risk percentage or lot size, timeframes, stop and target parameters, protection settings and service-access status. The service retains Start and Pause requests, configuration acknowledgements, bot orders and positions, requested cancellation or closing actions, and their reported progress and outcomes.
Support & diagnostics
Messages you send, contact details, timestamps, app platform/build, connection errors and records used to operate and protect the service.
Normal network requests also expose connection metadata to the hosting infrastructure. Operational logs support service delivery, security and troubleshooting; they are handled under the retention and deletion commitments below.
The website and the Android APK distributed directly outside Google Play can separately receive plan/payment records, receipt images and referral applications, including broker/deposit information and evidence. Those collection screens are excluded from the native iOS and Google Play companions. This page provides no purchase or enrollment links.
Why information is used
- Authenticate your session, apply your account's access permissions and handle password changes or available account recovery.
- Establish your requested broker connection, show account information and carry out your enabled settings or individual commands.
- Apply your separately authorized Auto Trading configuration, send broker orders and maintain the corresponding control, execution and troubleshooting records.
- Keep statements, request outcomes and troubleshooting information available.
- Respond to support requests and detect misuse or unauthorized access.
- For the separate website and directly distributed Android APK, review submitted payment or referral evidence and maintain the corresponding access status.
We use this information to provide the service you request, maintain account security and handle support and administrative records. Contact us to ask about a particular use of your information.
Security and device permissions
API communication uses HTTPS. Service passwords are stored as salted hashes; password change and reset replace the stored hash. A password change or successful reset revokes existing service sessions and passkeys. Recovery codes expire and have limited attempts. A code waiting for email delivery is encrypted in the service outbox and its recoverable payload is cleared after delivery, expiry or cancellation. Broker credentials must be recoverable by the assigned server to connect: database credentials are encrypted, and authorized operational files are protected by access controls. This is not end-to-end encryption that hides broker credentials from the service operator.
Optional biometric unlock, such as Face ID, Touch ID or supported Android fingerprint or face authentication, is performed by your device's operating system. BitKurd Cloud receives an authentication result, not your face image or fingerprint template. The native app stores its remembered session using device secure storage. Remember Me requests a session of up to 30 days; sessions can expire or be revoked earlier.
Support in the iOS and Google Play companions is text-based, and their normal customer flows do not request photos, camera, microphone, contacts or precise location. Do not send passwords, one-time codes or API keys in support messages.
Keeping and deleting information
We keep information while it is needed to provide your account, connected management and authorized Auto Trading, maintain account security, respond to support requests, or meet a specific documented retention need. A 30-day remembered sign-in is an authentication setting; it is not the retention period for account information.
Request deletion in the app
Open About → Delete my BitKurd account, review what will happen, enter your current BitKurd password and give explicit confirmation. Do not enter your broker password. If you cannot access the app or this option, email dev@karzantech.com from your registered email. Never send a password by email.
Once the request is accepted, normal service access is blocked and existing sessions and worker authority are revoked. Linked server management is stopped and disconnected through a verified retirement process. Already submitted broker actions may still need reconciliation. The request does not close your broker account or close, change or cancel broker positions and orders; manage any remaining trades directly with your broker.
Timing and progress
Our policy is to complete account deletion within 30 days of acceptance. Your receipt shows the request reference, current status and target date. “Requested”, “Disconnecting linked accounts” or “Deletion needs review” means deletion is still in progress. Only the completed status confirms deletion of the BitKurd account. If a check is unresolved or the target date passes, the request must remain visibly pending; contact support with its reference.
Deletion removes ordinary profile/authentication and recovery records, support content, referral records, private customer media, Auto Trading access records and the retired cloud account records. Payment records and separate copies, including server files or delivered Telegram notifications, are checked independently. A service-database deletion alone is not a claim that those separate copies have been erased.
Retained records and backups
Private backup copies are retained for no more than 30 days after the deletion request is accepted. Other records may remain only for a specific documented reason with an identified basis and a future retention deadline. The receipt identifies retained categories, reasons, basis and deadlines. Expired retention does not itself prove that an external copy has been erased; any outstanding cleanup must be checked and recorded.
The read-only deletion receipt is available for 30 days after completion. A minimal pseudonymous deletion marker remains to prevent restoration of the deleted identity from an old backup. It contains the request identifier, original internal user identifier and verification hash, rather than the original name, email or linked-account details. This restore-protection marker remains after the receipt expires.
Removing a linked broker connection, pausing management and deleting your BitKurd Cloud identity are different actions. Archiving or signing out does not itself delete your service account.
Your choices and questions
You can review your account settings, change your service password, choose whether to use biometric unlock and sign out to end access from the app. Email-based password recovery is available only when the service has enabled it; otherwise contact the administrator for help. Use the relevant Trade manager or Auto Trading Pause control and check its confirmed result. On a compatible updated terminal, Auto Trading Pause can cancel that bot's pending orders and lets you choose whether to keep or close its open positions. Positions you keep retain their existing broker stop-loss and take-profit settings. A sent request is not proof that broker actions have completed, and a basic Pause alone does not close positions or cancel pending orders. Trade manager and Auto Trading controls are separate. Closing the phone app or signing out does not itself stop cloud management or an enabled bot.
For questions about access, correction, deletion or how information is handled, contact dev@karzantech.com. We will review requests for access, correction or deletion and explain any verification or applicable limitation.
We update the date on this notice when its terms change and will notify affected users of material changes through an appropriate service notice.