These Platform Policies describe operational rules of the AlphaQuantVibe Workspace: account, broker connection, automation boundaries, and data handling. They supplement the Terms of Service and Privacy Policy.
1. Broker Connection & Emergency Revocation
Each user connects their own broker account using API keys they personally provision. Keys are encrypted at rest (AES-256-GCM) and used solely to operate the Service on the user's behalf. Tokens are rotated automatically each trading day at 06:00 IST before market open.
Emergency revocation: you may revoke broker access at any time from Settings → Token Management. Revocation cancels all pending automated orders and purges the cached API key from in-memory caches and the database within 60 seconds.
TODO: 🟠 SEBI Algo Framework §6(c) — kill switch + revocation flow documented.
2. Paper vs Live Mode
Trades are tagged with an immutable trading_modemarker (paper or live) at order generation. Paper and Live data streams are kept strictly separate end-to-end. Trial users operate in Paper mode by default.
Paper-mode trades are entirely simulated. No order reaches any exchange or broker. Paper-mode P&L is theoretical and modelled using realistic broker charges; actual live performance can and will differ materially due to execution latency, partial fills, slippage and market impact.
TODO: 🔴 CPA 2019 §2(47) — explicit non-simulation statement; isolation guarantee.
3. Automation Boundaries & SEBI Algo Framework
Automated execution honours the user's configured trade mode, daily trade limits, capital allocation and risk caps. Manual approval flows (Telegram or in-app) are available for users who prefer to review every order before placement.
All automated strategies on the Service are registered with the user's broker as user-tagged algos under SEBI's Algo Trading Framework for Retail Investors (Feb 2025). Where issued, the Exchange-assigned Algo ID is recorded against every algorithmic order placed on your behalf. Per-user order-rate limits (typically 10 orders/second/account at Zerodha) are enforced by the broker.
TODO: 🔴 SEBI Circular Feb 2025 (Algo Trading Framework for Retail Investors) §4–§5 — Algo ID tagging mandatory.
4. ML Governance Policy
Production ML models progress through Observer → Assist → Control modes only after passing pre-defined statistical and economic gates. Users may inspect the current governance state from inside the workspace. Model performance metrics will be reported to SEBI per the AI/ML circular when applicable thresholds (AUM or user-count) are crossed.
TODO: 🟡 SEBI AI/ML Circular SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2023/14 — quarterly reporting once thresholds cross.
5. Data Quality & Source Policy
Market data is ingested from broker APIs (Zerodha Kite, ICICI Breeze), NSE BHAVCOPY end-of-day files, and approved third-party data partners. The Service makes best efforts to validate data freshness and integrity but cannot guarantee absolute completeness in all real-time conditions.
TODO: 🟢 List upstream data providers.
6. Service Availability (Tiered SLA)
- Trial / Explorer: best-effort; no contractual SLA.
- Pro: 99% uptime during Indian market hours (09:15–15:30 IST, Mon–Fri).
- Elite: 99.5% uptime during market hours + 2-hour P1 response SLA.
Maintenance and deployments are scheduled outside market hours wherever possible.
TODO: 🟠 CPA 2019 §2(46) — paid tiers expect stated uptime. Per-tier SLA matrix below.
7. Acceptable Use & Abuse
Attempting to bypass tier gates, scrape proprietary signals, extract model artifacts, or share accounts is prohibited and will result in immediate account suspension. See Terms of Service §5 for the full list.
TODO: 🟡 Cross-reference Terms §5 to avoid duplication.
8. Security Disclosure (Safe Harbor)
We welcome responsible security disclosures. Please report vulnerabilities to security@alphaquantvibe.com — we commit to acknowledging within two business days.
Safe Harbor: researchers acting in good faith under this program will not be subject to legal action, provided they (i) do not access user data beyond what is necessary to demonstrate the vulnerability, (ii) do not disrupt service, and (iii) afford us 90 days to remediate before any public disclosure.
TODO: 🟡 Add good-faith researcher safe-harbor.
9. Policy Updates
These Platform Policies may evolve as the Service grows. Users will be notified of material changes inside the workspace and via an email to the registered address at least 14 days before they take effect.
TODO: 🟡 DPDPA §6(2) — also email dormant users.