Security Practices

All sensitive data is encrypted:

• At rest: AES-256 encryption for stored credentials and tokens
• In transit: TLS 1.3 for all network communication
• Broker tokens: Encrypted with platform-specific keys

User authentication uses:

• Email + password (with strong password requirements)
• Optional 2FA (TOTP)
• OAuth tokens for broker authorization
• Session token rotation

Platform infrastructure includes:

• Isolated execution environments per user session
• Role-based access control (RBAC)
• Rate limiting and abuse prevention
• DDoS protection at network edge
• Regular security patches and updates

Comprehensive audit logs track:

• User authentication events
• Trading activity and execution decisions
• System configuration changes
• Broker authorization events
• API access and rate limits

VedKUBER does not store broker account passwords. We use OAuth tokens or API keys provided by brokers. These tokens can be revoked at any time by the user.

Internal practices include:

• Least-privilege access for team members
• Code review for production deployments
• Separation of dev/staging/production environments
• Regular security reviews

In the event of a security incident, we will:

• Investigate and contain the issue
• Notify affected users without undue delay
• Cooperate with relevant authorities as required
• Apply remediation and preventive measures

If you discover a security vulnerability, please email security@vedkuber.in with details. We appreciate responsible disclosure.

VedKUBER operates in accordance with applicable Indian data protection and IT regulations. We are committed to ongoing compliance and security improvement.