Compliance Certifications
Slater does not currently have any formal compliance certifications such as SOC 2, ISO 27001, or similar standards. The platform's primary focus is on improving website experiences and keeping code secure through established best practices.
Key Points:
- No current compliance certifications (e.g., SOC 2, ISO 27001) are held or listed by Slater.
- Emphasis is placed on maintaining security by following best practices rather than meeting specific certification requirements.
- For updates on future certification plans or more detailed compliance information, customers are encouraged to contact the Slater support team by providing their email or phone number.
Data Encryption and Security Practices
Slater is designed to enhance Webflow website experiences by promoting secure coding. API keys and sensitive data should not be included in Slater javascript files. Direct data encryption features are not built into Slater, as the platform is primarily intended for frontend code enhancements rather than backend data processing.
Recommended Security Practices with Slater:
- Never store private API keys or sensitive data in client-side code within Slater or Webflow projects.
- Handle secrets and privileged operations on backend servers or with serverless functions. Only expose public or safely scoped tokens to the browser.
- Use Slater's team management controls to restrict who can access and update code within your projects, improving overall project security.
- Set up end-to-end encryption or compliance-specific measures outside of Slater, such as on your own backend or through dedicated third-party tools, if required for your use case.
