Privacy Policy

1. Authentication & API Data

Vortex API requires a secure credentials account to create authorization keys. We collect your username, encrypted password hashes, and optional Google OAuth profile metadata (email, avatar) purely to manage your developer portal access.

Your generated API keys (starting with VX...) authorize requests at our proxies. The keys are validated in real-time, but their associated requests are not stored or analyzed beyond active rate-limit tracking.

2. Server Logging & Telemetry

To maintain system stability, optimize query latency, and prevent brute-force attacks, our edge proxies collect minimal request telemetry:

• Request timestamp and endpoint URL (e.g. /api/youtube/search).
• Encrypted hash of the originating IP address (used strictly for geographical routing and DDoS mitigation).
• Status code returned (e.g. 200 OK or 429 Too Many Requests).

Important: We do not log or record search query keywords, response body contents, or transferred media binaries. Data packets are tunnelled losslessly.

3. Data Retention & Third Parties

Accounts details and billing ledgers (Vortex Wallet balance) are retained as long as your account remains active. You can request account deletion or wallet ledger flushes at any time through our help ticket desk.

We do not sell, rent, or distribute any user metrics, emails, or usage statistics to marketing firms or third-party brokers. All request tracking is hosted internally on isolated server instances.

4. Security & Encryption

All traffic going to and from Vortex API is encrypted using secure SSL/TLS protocols. Access keys are hashed using industry-standard cryptography. We strongly advise developers to protect their local project settings files, use environment variables for keys, and rotate keys if exposure is suspected.