Ever Teams follows industry security best practices. This page outlines the security model and how to report vulnerabilities.
Security Model
Authentication
| Mechanism | Description |
|---|
| Magic Code | Email-based passwordless authentication |
| Password | Traditional password authentication |
| OAuth / Social | Google, GitHub, Facebook, Twitter SSO |
| JWT Tokens | Server-side session tokens with refresh rotation |
| CAPTCHA | reCAPTCHA protection on auth pages |
Authorization
| Mechanism | Description |
|---|
| RBAC | Role-Based Access Control with granular permissions |
| Tenant isolation | Multi-tenant architecture with per-organization data isolation |
| API proxy | All API calls routed through server-side proxy (secrets never exposed to client) |
Data Protection
| Practice | Description |
|---|
| HTTPS/TLS | All production endpoints use HTTPS |
| Secrets management | Environment variables for all secrets, never committed to code |
| Password hashing | Bcrypt hashing for stored passwords (backend) |
| Session security | Secure, HTTP-only cookies with SameSite |
| Input validation | Server-side validation on all API endpoints |
Production Security Checklist