Effective date: March 1, 2026 · Last updated: March 17, 2026
HyperBabel Co., Ltd. ("HyperBabel," "we," "us," or "our") operates the HyperBabel API platform. This Privacy Policy explains how we collect, use, disclose, and protect information of our developer customers ("you") who use our services.
HyperBabel's customers are developers and organizations, not end-consumers. You are responsible for your own users' data and must maintain your own privacy policy for your end users.
1. Information We Collect
a) Account Information
Name, email address, company name, and website URL provided at registration
Account role and subscription plan
b) Usage & Billing Data
Monthly API call counts, message volume, video/stream minutes, translation character counts
Subscription status and billing history (payment card data is handled exclusively by Paddle — we never store raw card numbers)
c) API & Service Data
API keys (stored as secure hashes — plaintext never retained after initial display)
Sandbox message content, channel configurations, and file uploads made during Sandbox testing
Webhook endpoint URLs and delivery logs
d) Technical Data
IP address, browser type, and request timestamps (retained for up to 7 days for security purposes)
Error logs associated with your API requests
2. How We Use Your Information
Service Delivery — To authenticate your API requests, enforce subscription quotas, and deliver the platform.
Billing — To calculate usage charges and generate invoices via our payment processor (Paddle).
Security — To detect and prevent fraud, abuse, and unauthorized access.
Communication — To send service alerts, API deprecation notices, and billing notifications.
Improvement — To analyze aggregate usage patterns and improve platform reliability.
We do not sell your personal data to third parties and do not use your data for advertising.
3. Data Sharing & Disclosure
We share your information only in limited circumstances:
Service Providers — Billing processor (Paddle), globally distributed cloud infrastructure providers, and email delivery services, each bound by data processing agreements.
Legal Requirements — When required by law, court order, or governmental authority.
Business Transfers — In connection with a merger, acquisition, or sale of assets (with appropriate notice).
4. Cookies & Tracking
The HyperBabel console and public website use only essential cookies for authentication session management. We do not use third-party advertising trackers or behavioral analytics cookies. For more details, see our Cookie Policy.
5. Data Security
All data in transit is encrypted with TLS 1.2+ (HTTPS enforced)
Passwords and API keys are stored as bcrypt/SHA-256 hashes — never in plaintext
Access to production systems is restricted to authorized personnel
Routine security audits and vulnerability assessments are conducted
6. Data Retention
Account data: Retained as long as your account is active. After account deletion request, purged permanently within 30 days.
Sandbox/SDK messages: Retained for at least the period of your subscription plan (Free: 30 days, Basic: 90 days, Scale: 365 days).
Billing records: Retained for 7 years to comply with financial regulations.
Access logs: 7 days (rolling).
7. International Data Transfers
HyperBabel operates on globally distributed cloud infrastructure with multi-region data centers. When data is processed outside the EU/EEA, we rely on appropriate safeguards including Standard Contractual Clauses (SCCs) as approved by the European Commission.
8. Your Rights Under GDPR
If you are located in the EU/EEA, you have the right to access, rectify, erase, restrict processing of, and port your personal data. To exercise these rights, visit GDPR & Data Privacy or contact [email protected]. We will respond within 30 days.
9. Children's Privacy
HyperBabel is a B2B developer platform and is not directed at children under the age of 16. We do not knowingly collect personal information from children.
10. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by email and via a notice in the Developer Console at least 14 days before changes take effect.