Help Center topic
Security overview
Hosting, data handling, PII and Bablic's software development lifecycle.
7 articlesSearch all
- Browser translation modelHow Bablic translates in the browser: one script loads the MOXIE framework, validates your key and domain, then applies cached translations.
- HostingBablic's Translation API runs on AWS with AES-256 encryption at rest and AWS KMS, application clusters in four regions, and CloudFront edge caching.
- How to handle PIIHow Bablic handles personally identifiable information, why payment card data is never captured, and why PII should be flagged as non-translatable.
- What data is stored?Bablic stores source and translated text pairs plus request metrics: the content to translate, browser type, IP info from X-Forwarded-For, and URL.
- Referer securityBablic checks the referer header on every translation request against your allowed domains, so other sites can't access your project's translations.
- Software development lifecycleHow Bablic ships code safely: static analysis and functional QA, peer review against the OWASP top 10, and quarterly third-party security tests.
- Hosting JavaScript & SRIWhy Bablic's JavaScript library can't be self-hosted, and how Subresource Integrity (SRI) relates to a client library that updates with its API.
