Privacy Policy

01Scope and operator

This policy covers AEX Wallet for Android and iOS and related wallet services, including wallet creation and recovery, asset queries, payments, swaps, market data and DApp access. Features vary by platform, version and region; the relevant processing depends on the features actually enabled.

AEX Wallet is operated by Kairos Markets Ltd ("AEX", "we" or "us"). Contact address: 1001 South Main, Suite 500, Kalispell, MT 59901, USA. Privacy contact: aexservice@hotmail.com.

Independent third-party sites and services are not covered by this policy. Review their own policies when opening DApps, advertisement links or block explorers.

02Information and purposes

Optional profile information, third-party visits and file uploads are your choice. A feature may not work without information it needs; this does not let you skip configured authentication.

Account and authentication

Account ID, nickname, avatar and authentication details you configure, such as email, help create, identify, recover and protect your account. Verification services also process verification credentials and necessary interaction information.

Device and connection

Device or application identifiers, public keys, OS and app versions, language, IP address, connection information and session credentials support request validation, compatibility, account protection and troubleshooting.

MPC wallet protocols

Wallet identifiers, public addresses, protocol messages, encrypted material related to key shares, creation and recovery status, and signing-session information support collaborative key generation, recovery and signing.

Assets and transactions

Networks, tokens, public addresses, balances, quote parameters, amounts, order status, transaction hashes and fees support asset displays, quotes, authorized transactions and reconciliation.

Content you choose to save

Wallet address-book names, addresses and notes, favorites, avatars and selected files support their respective features. The wallet address book may sync with the service; it is not your phone's contact list.

Diagnostics and support

Errors, crashes, necessary operational information and the descriptions, screenshots and contact details you provide help maintain reliability and handle requests. Android integrates Firebase Crashlytics; diagnostic services may differ by platform.

03Keys, backups and recovery

AEX uses MPC wallet workflows in which the device and wallet service participate. Local wallet material stays on the device, while the service handles records and encrypted material needed for its protocol and recovery roles. This architecture does not mean the server processes no key-related data.

Local recovery backups are encrypted with your chosen backup password before being saved to the location you select. iOS exports through the system file picker; available Android local and cloud options depend on the current interface. Backup-status requests record necessary account and device information, without including the local backup password you entered.

If you select iCloud Drive, Google Drive or another file provider, that provider processes the file and account information under its policies. Logging out, uninstalling AEX or deleting a local file does not automatically delete backups elsewhere.

Keep encrypted backups and their passwords separately and securely. Losing recovery material, passwords or verification methods may prevent wallet recovery. Do not send full private keys, backup passwords or one-time codes to support or any website.

04Device permissions and choices

Camera

Used for scanning codes. Denying access affects scanning.

Photos and files

Selected content is processed when you choose an avatar, code image or backup. Installing the app does not authorize uploading your entire photo library.

Biometrics

The operating system performs biometric checks. AEX receives the result, not your face or fingerprint template.

Permission controls

Manage permissions in system settings. Alternative verification or input methods depend on the feature.

05Public blockchains and transactions

After broadcasting, addresses, amounts, tokens, timing and transaction data may become public on a blockchain. Others can inspect or analyze them and associate addresses with other information. Blockchain records generally cannot be reversed, corrected or deleted.

Asset queries, quotes, fee estimates and receipt checks require AEX or relevant providers to process the necessary network, public-address and transaction parameters. Deleting an account, uninstalling the app or revoking device permissions does not remove blockchain records.

06Providers and third parties

We work with the following categories of providers to deliver the features you use, protect the service and perform necessary maintenance. We provide relevant providers with information needed for the applicable purpose. Independent third-party services also apply their own policies.

AWS and Cloudflare

Service hosting, databases, storage, delivery and network protection involve relevant business, connection and security information. The current primary AWS deployment region is Singapore.

Alibaba Cloud CAPTCHA

Verification interactions, device and network information and verification credentials help detect automation and abuse.

Microsoft email services

Recipient addresses, verification-message content and delivery status are processed for email delivery. The current AEX service address is aexservice@hotmail.com.

Market data, trading routes and blockchain nodes

AVE, enabled routing providers and RPC nodes process relevant tokens, networks, public addresses, quotes and transaction parameters.

Firebase Crashlytics

Android crash diagnostics may process device, app and crash information to investigate stability problems.

Apple, file providers and third-party DApps

Apple supplies distribution and platform services. Your file provider processes saved backups. DApps, wallet-connection services and advertisement destinations process connection, address and interaction information according to actual visits and authorizations.

Necessary disclosure may also be required for lawful regulatory or judicial requests, security incidents, fraud or rights disputes. Changes of operator or business transfers that affect data processing require applicable notice and other safeguards.

07This website and browser storage

The code for these two legal-information pages includes no advertising or analytics SDK, requires no login and collects no form submissions. It saves only language and appearance preferences locally in the browser. Clearing site data removes these preferences, not wallet data.

Hosting and network-security providers may still process IP addresses, request times and security logs. DApps, advertisement destinations and cloud file services may use their own cookies or storage. This page does not imply that those third parties do not track activity.

08Retention and processing locations

We determine retention periods by the need to deliver a feature, meet applicable legal duties, protect accounts and resolve pending transactions or disputes. Relevant criteria include whether the account is active, whether records remain necessary for wallet recovery or reconciliation, and mandatory retention requirements.

Account and wallet records relate to account use and recovery needs; authentication and security records support verification and incident investigations; business records support transactions, reconciliation and disputes. We do not retain personal information indefinitely merely because it might be useful. Backup cleanup and online deletion may not occur simultaneously. When requesting deletion, you can ask about applicable retention grounds, backup cleanup arrangements and processing limitations.

Our primary AWS services are deployed in Singapore. Email, CAPTCHA, CDN, diagnostic and other providers may process information outside your country or region, depending on their actual infrastructure. We take necessary measures under applicable data-protection requirements for cross-border processing. Contact our privacy address for information about relevant locations and arrangements.

09Your choices and data requests

You can manage available profile settings, permissions and authentication methods in the app and system settings. Contact aexservice@hotmail.com to request access, correction, export, deletion or withdrawal of applicable consent. We will verify the requester, explain the scope, limitations and estimated handling time, and respond within applicable legal time limits. Never send full private keys, backup passwords or one-time codes.

Before deleting MPC wallet material, the effects on asset access and recovery need to be explained and your intention confirmed. Preserve your assets and recovery material first. Logging out, erasing local data and deleting a server-side account are different actions.

Some records may need to be retained for legal duties, pending transactions or disputes; we will explain the applicable reasons. AEX cannot unilaterally delete public-chain records or information provided directly to independent third parties. The current version does not offer one-click server-side account deletion. Send data or account-deletion requests to the contact above; logging out is not deletion.

10Security, eligibility and changes

Measures include transport protection, access controls, local encryption, request validation and necessary log management. These need ongoing maintenance. No network or wallet system can guarantee that attacks, disclosure, loss or interruptions will never occur.

Digital-asset services are not intended for people who do not meet applicable legal eligibility requirements. You must have the required legal capacity and must not use a service where doing so is prohibited. Contact AEX about information provided by a person who does not meet these requirements.

We will update this policy and provide appropriate notice of material changes to the operator, information categories, purposes, sharing or rights. Where renewed consent is legally required, we will obtain it before the relevant change. The date at the top identifies this version.