Security at Glider11
Trust is foundational to an AI builder. Here’s how we protect your account, projects, and billing — and how to reach us if something looks wrong.
Encryption in transit
Glider11 serves traffic over HTTPS/TLS so data between your browser and our servers is encrypted.
Modern authentication
Sign-in is powered by Supabase Auth, including email and supported OAuth providers.
Sandboxed previews
Generated apps render in an isolated Sandpack preview, separated from Glider11’s control plane.
Access controls
API routes authenticate users before reading or changing project data tied to their account.
Least privilege
Internal access to production systems is limited to people who need it to operate the product.
Responsible disclosure
We welcome good-faith vulnerability reports and will work with researchers to resolve issues.
Infrastructure overview
Glider11 is a cloud-hosted Next.js application with a managed Postgres database (via Prisma/Supabase), object and auth services from our providers, and Paddle for subscription payments. We keep dependencies updated and monitor for abusive traffic patterns.
Payments
Card processing is handled by Paddle as merchant of record. Glider11 stores plan and entitlement state needed to unlock features — not full payment card numbers.
Your responsibilities
- Use strong, unique passwords and protect OAuth sessions.
- Do not paste secrets into prompts you wouldn’t store in a project.
- Review generated code before publishing sensitive workflows.
- Keep teammate access and published URLs intentional.
Read the policies
Security practices work alongside our Privacy Policy and Terms of Service.