Security
How Lodeline keeps each workspace's data apart and its credentials safe.
Workspace isolation
Row-level security is on for every workspace table. The app connects with a database role that does not own those tables and cannot bypass it, and each request is bound to one workspace, so a query cannot return another workspace's rows.
Credentials
- Cursor and Copilot tokens and Slack webhooks are encrypted with AES-256-GCM, with versioned keys.
- Ingest keys are write-only, shown once, and stored only as a SHA-256 hash.
- Cursor and Copilot are read with read-only tokens. Nothing we hold can change your coding tools.
Data intake
Every request is authenticated before its body is read, keys are compared in constant time, each ingest key has its own rate limit, and request size is capped.
Access
Owner, admin and member roles are checked on the server for every action. Deleting a workspace asks you to sign in again first.
Transport
HTTPS only, with HSTS and a content security policy.
Report a vulnerability
Email security@lodeline.ai.