Secure by default: how we protect Glider11 projects
Auth, isolation, payments, and responsible disclosure — the security posture behind Glider11.
August 1, 20266 min read
Back to blog
Accounts and access
Glider11 authenticates users through Supabase Auth. Projects belong to your account; API routes verify identity before reading or mutating project data.
Previews stay sandboxed
Generated apps run in an isolated Sandpack preview. That separation helps keep experimental UI from touching Glider11’s own control plane.
Payments and privacy
Subscriptions are processed by Paddle. We minimize the card data we handle and document practices in our Privacy Policy and Security page.
If you discover a vulnerability, email security@glider11.com. We take responsible disclosure seriously.
Build the next version
Take what you learned here into the Glider11 builder.