Security, Privacy, and Data Handling FAQ
Slater hosts your production JavaScript and connects to Webflow via a single script, running on AWS‑backed infrastructure with staging/production separation. For items not publicly documented (e.g., data retention, model providers), contact jared@edgarallan.com.
Slater hosts your production JavaScript and connects to Webflow via a single script, running on AWS‑backed infrastructure with staging/production separation. For items not publicly documented (e.g., data retention, model providers), contact jared@edgarallan.com.
How Slater connects to your Webflow site
- You paste a small Slater script into your Webflow project settings (commonly the site footer). This establishes the connection and loads your project’s code files on published pages.
- Webflow treats all custom code as an advanced modification; review carefully during deployment.
Hosting and environments
- Hosted files: Slater provides hosted production JavaScript files so your site can fetch the latest published code.
- Staging vs. production: Slater supports publishing to either environment, and the Smart Script can detect webflow.io vs. a custom domain to load the right files.
Platform and infrastructure
- Infrastructure: Slater runs on AWS and serves hosted files for reliability.
- Availability/SLA: No public SLA is stated. If you require uptime guarantees, contact jared@edgarallan.com.
Data handling and privacy
- Source code storage: Slater stores your project code to power editing, versioning, and publishing. Specific retention timelines are not publicly documented.
- AI features: Slater provides AI‑assisted authoring and explainers. Slater supports current OpenAI models. Prompts/outputs are saved indefinetly.
- Access controls: Team collaboration is supported; however, detailed role‑based permissions and audit logs are not publicly available.
Security best practices for Webflow + Slater
- Review any third‑party libraries you load and keep versions consistent across environments.
- Publish and validate in staging first; then promote to production once verified.
- Use your browser DevTools to confirm the correct environment file is loading and no network or console errors occur.
FAQs
- Where are files hosted? On Slater’s hosted infrastructure; Slater uses AWS S3 to ensure reliability of production files.
- Is custom code supported by Webflow? Yes, but it’s considered advanced and outside standard support—test thoroughly.
- Does Slater encrypt data at rest? No. Slater files are meant to run in the client and sensitive code should not stored on Slater.
- Is Slater compliant with specific standards (e.g., SOC 2, GDPR)? Slater does not have any formal claims. For procurement reviews, contact jared@edgarallan.com.