micsapp Lokalise Data Handling
Overview
Handle translation data correctly with privacy, compliance, and data governance best practices.
Prerequisites
- Understanding of GDPR/CCPA requirements
- Lokalise SDK installed
- Database for audit logging
- Data classification policies
Instructions
- Data Classification
- Instructions
For full implementation details, load: Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
Output
- PII scanning for translations
- Safe logging practices
- Data retention enforcement
- Audit trail for compliance
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| PII in translations | User-submitted content | Scan before upload |
| Token in logs | Improper logging | Use safe log wrapper |
| Audit gaps | Missing logging | Add audit calls |
| Retention violation | No cleanup | Schedule retention jobs |
Examples
Pre-commit PII Check
#!/bin/bash
# .husky/pre-commit
# Check for PII in translation files
node scripts/scan-translations-pii.js
if [ $? -ne 0 ]; then
echo "PII detected in translations. Please review and remove."
exit 1
fi
Quick PII Scan
const result = await validateBeforeUpload("./locales/en.json");
if (!result.valid) {
console.error("Cannot upload: PII detected");
result.findings.forEach(f => console.error(` ${f.type}: ${f.key}`));
process.exit(1);
}
Resources
Next Steps
For enterprise access control, see lokalise-enterprise-rbac.