Privacy Policy
This explains, in plain language, what personal data AKQX QuantumTrade collects, why we need it, who sees it, how long we keep it, and what you can do about it.
1. Summary
- We collect only what we need to run your account, your trading tools and, if you choose, your broker connection.
- We never sell your personal data and do not use it for third-party advertising.
- Passwords are stored as hashes. Broker API keys and tokens are stored encrypted and used only for the features you switch on.
- You can ask to see, correct or delete your data, withdraw consent, or complain, using the contacts below.
- You must be 18 or older to use AKQX.
2. Who is responsible for your data
The “Data Fiduciary” (the party that decides how and why your personal data is used) is Akash Paikra, operating as AKQX QuantumTrade, an individual founder based in India, who runs https://akqxquantum.tech. (Company details: coming soon.) If the business is incorporated, the new company will take over this role and we will update this policy and tell you.
This policy follows the Digital Personal Data Protection Act, 2023 (“DPDP Act”) and the DPDP Rules, 2025, and, until the Rules fully apply, the Information Technology Act, 2000 and the IT (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011. It applies together with our Terms & Conditions.
Contact: founder@akqxquantum.tech.
3. What we collect
| Category | What | How we get it |
|---|---|---|
| Account | E-mail address, username, password (stored only as a one-way hash), and optionally a phone number. | You give it when you sign up. |
| Sign-in with Google | Your Google account identifier and e-mail address. | From Google, if you choose Google sign-in. |
| Profile and preferences | Display name, avatar, bio, time zone, theme, default symbols, risk preset, layouts, drawings, alert settings, notification choices. | You set them in the app. |
| Security data | One-time codes (stored hashed), two-factor secret (stored encrypted) and backup codes (stored hashed), failed-login counts, lockout time, last login time, signed-in device hint, and session tokens (stored hashed). | Created when you use security features. |
| Broker / exchange credentials | API keys, secrets and tokens for the broker or exchange accounts you connect. We do not ask for your broker login password or trading PIN. | You enter them when you connect a broker. |
| Trading data | Your paper-trading and real-trading orders, positions, fills, profit and loss, algorithm and strategy settings, risk notices you accepted and when, and balance or margin information returned by your broker. | Generated by your use of the Platform and returned by your broker or exchange. |
| Alerts | If you link Telegram: your Telegram chat identifier, so we can send alerts you asked for. | You link it. |
| Payment data (when paid plans exist) | Plan, amount, status and the payment reference from the gateway. Card, UPI and bank details are handled by the gateway; we do not store them. | From you and the payment gateway. |
| Device and usage data | IP address, browser and device type, time of access, and security or audit logs of actions in your account. | Automatically, when you use the Platform. |
| Strategy Builder assistant | The text you type, the strategy drafts produced and the chat history, and, if you connect your own AI provider key, that key (stored encrypted; only the last four characters are shown). | You enter it when you use the assistant. |
| Data you bring | Where you import your own data files (a feature that is coming soon), the files and the results of your analysis, stored privately in your workspace and used only to provide that analysis to you. If you connect your own exchange or broker account, see “Broker / exchange credentials” above. | You provide it. |
| Communications | Messages you send to support and our replies. | From you. |
We do not intentionally collect your PAN, Aadhaar, bank account number, or identity documents. Your broker or exchange collects those for its own KYC.
Your two data options. You can use the market data that AKQX provides (free; provider approvals are pending, coming soon, and availability may change), or work with your own data, live or historical, by connecting your own account or, soon, importing your own files. Market data that AKQX provides is not personal data about you. Data you bring stays private to your account.
4. Why we use it, and on what basis
We use your personal data only for these purposes. Where the DPDP Act requires, we rely on your consent, which you give by a clear action (for example ticking the box at sign-up, connecting a broker, or enabling alerts) and which you can withdraw. For some purposes the law lets us rely on a “legitimate use” instead.
| Purpose | Data used | Basis |
|---|---|---|
| Create and secure your account, sign you in, run two-factor authentication, prevent abuse | Account, security, device data | Consent; legitimate use for security and fraud prevention |
| Provide the features you use: charts, backtests, paper trading, saved layouts and alerts | Account, profile, trading data | Consent |
| Place, manage and reconcile orders at your broker or exchange when you enable automated execution | Broker credentials, trading data | Consent (given when you connect and enable it) |
| Send service messages: verification codes, security notices, alerts you asked for, important changes | E-mail, phone, Telegram ID | Consent; legitimate use for essential service messages |
| Take payments, issue invoices, handle refunds, meet tax and accounting law | Payment data, account data | Consent; legal obligation |
| Keep the Platform running, find and fix faults, measure performance, and protect it from attack | Device and usage data, logs | Legitimate use / consent |
| Answer your requests and complaints | Communications, account data | Consent; legitimate use |
| Comply with law, court orders and lawful requests from authorities | As required | Legal obligation |
We do not use your personal data to make automated decisions that produce legal effects on you, and we do not use it to show third-party ads.
5. Broker API keys and tokens
Your broker API credentials are the most sensitive thing you give us, so:
- They are stored encrypted, not in plain text. The encryption key is kept in server configuration, separate from the database.
- We use them only to do what you enabled: read market or account data and place, modify and cancel orders according to your settings. We do not use them for any other purpose.
- Please create keys with trading permission only and withdrawals disabled, and restrict them by IP address where your broker supports it. We cannot move money out of your broker account with a trade-only key.
- You can disconnect a broker in the app, which removes the stored credentials from active use, and you should also revoke the key at your broker.
- Access to production systems that can decrypt credentials is limited to the operator. We do not read or share your credentials except as the law requires.
7. Transfers outside India
Some of our providers (for example e-mail or SMS delivery, Google, Telegram and AI providers) may process data on servers outside India. Our own hosting server is located in coming soon. The DPDP Act allows transfers abroad except to countries the Government may restrict. We transfer only the data needed for the service and use providers with reasonable security safeguards.
9. How long we keep data
- While your account is active: account, profile, settings and trading data, so the service works.
- After you close your account or ask for erasure: we delete or anonymise personal data within 30 days, except what we must keep by law, for example payment and invoice records for as long as tax and accounting law requires, and records needed to handle a dispute or legal claim.
- Security and access logs: kept for a minimum period required by law (reported to be at least one year under the DPDP Rules) and then deleted.
- Inactive accounts: if an account stays unused for a long time we will give you notice before deleting it.
- Broker credentials: removed when you disconnect the broker or close the account.
Closing your account does not erase records held by your broker, exchange or payment gateway; those parties keep data under their own policies.
10. Your rights
Under the DPDP Act you have the right to:
- Access a summary of the personal data we hold about you and the parties we have shared it with;
- Correct inaccurate or incomplete data, and update it;
- Erase your personal data when it is no longer needed for the purpose, subject to legal retention;
- Withdraw consent at any time, as easily as you gave it. Withdrawing may mean we can no longer provide a feature that needs the data, and does not affect what was done before;
- Grievance redressal: complain to us and get a reply;
- Nominate another person to exercise these rights for you if you die or become unable to.
How to use them: e-mail founder@akqxquantum.tech from your registered e-mail address, saying which right you want to use. We may ask you to verify your identity first. We aim to respond within 30 days and in any case within the maximum period the law allows. Account deletion is handled through this e-mail request: write to us and we will delete your account and data as described above.
You can also change your profile, preferences, notification settings, two-factor authentication and connected brokers from inside the app.
11. Children
AKQX is for adults only. You must be at least 18 years old. We do not knowingly collect personal data of anyone under 18. If we learn that we have, we will delete it and close the account. If you believe a child has signed up, tell us at founder@akqxquantum.tech.
12. Security
We use reasonable security safeguards appropriate to the data, including:
- encrypted connections (HTTPS) between your browser and the Platform;
- hashed passwords, one-time codes and backup codes, and encrypted broker credentials and two-factor secrets;
- optional two-factor authentication, account lockout after repeated failures, and revocable sessions;
- access controls on servers and databases, network restrictions, and regular backups;
- security and audit logs.
No system is completely secure. Please use a strong, unique password, turn on two-factor authentication, and keep your own devices and broker keys safe.
13. Data breaches
If a personal-data breach occurs we will investigate and contain it quickly. Where the law requires, we will inform the Data Protection Board of India and each affected person without delay, and give the Board the detailed report within the time the DPDP Rules set (72 hours). The notice to you will say what happened, what data was involved, what we have done, and what you can do to protect yourself, including steps such as revoking broker keys.
14. AI assistant
AKQX does not offer “AI trading”: trades are placed only by the rules you create. Where we offer an AI-assisted Strategy Builder, the text you type (for example a description of a strategy) and the strategy draft being worked on are sent to an AI provider so that it can produce a response. That provider is either one we work with or, if you connect your own key, the provider you choose (for example Gemini, Groq, OpenAI or OpenRouter). These providers process the data under their own terms and may be outside India (see “Transfers outside India”). The assistant is designed not to receive your exchange or broker credentials or passwords, and you should not type them, or personal details, into it.
If you connect your own AI key, we store it encrypted, show only its last four characters, and use it only to send your requests to the provider you chose. You can remove it at any time. We do not use your personal data to train third-party models.
15. Changes to this policy
We may update this policy, for example for new features, paid plans, incorporation, or changes in law. We will change the “last updated” date and, for material changes, notify you in-app or by e-mail before they take effect. Where the law requires fresh consent, we will ask for it.
16. Grievance Officer and Data Protection Board
Please contact our Grievance Officer first with any concern about your personal data:
| Grievance Officer | Akash Paikra (Founder and Grievance Officer) |
|---|---|
| founder@akqxquantum.tech | |
| Operator | Akash Paikra, operating as AKQX QuantumTrade, an individual founder based in India |
| Address | coming soon |
| Legal entity | coming soon |
We acknowledge every complaint within 24 hours and aim to resolve it within 15 days of receipt. For consumer complaints about paid services we also meet the e-commerce timelines (acknowledgement within 48 hours, resolution within one month). Requests about your personal data are answered as set out in the Privacy Policy.
If you are not satisfied with our response, you may complain to the Data Protection Board of India once the Board's complaint process is operating, as the DPDP Act provides. You must first have used our grievance process.
Questions about this document? Write to founder@akqxquantum.tech.