Security

Every record is scoped to your organization. Direct client access to the database is denied by default: the browser never queries data stores directly. All reads and writes go through server code that resolves your organization from your authenticated session, never from client input, and rejects any request for another organization's data with a not-found or forbidden response.

All traffic is served over HTTPS (TLS). Data is encrypted at rest by our cloud provider. Integration credentials (OAuth and bot tokens) are additionally encrypted at the application layer with AES-256-GCM before they are stored, so a database snapshot alone does not expose them.

Connections to GitHub, Jira, Linear, and Slack are strictly read-only. We never write to, alter, or delete anything in your connected accounts. We do not access, store, or process your raw source code, commit contents, or file diffs. We read metadata: pull-request and issue titles and statuses, review and comment activity, repository and project names, and timestamps.

Sign-in is delegated to Google or GitHub OAuth. Sessions use httpOnly, secure, revocation-checked cookies with an absolute lifetime cap and an idle timeout, and you can end every active session everywhere from your settings. Within an organization, access is governed by roles (owner, admin, member, viewer) that gate privileged actions such as managing integrations and members.

Security-relevant activity, sign-ins, integration connections, report changes, member and role changes, and support access, is recorded to a per-organization audit log that owners and admins can review in-app.

LiveIndex runs on Google Cloud (Firebase App Hosting on Cloud Run). Inbound webhooks are signature-verified (HMAC for GitHub and Slack, a per-organization secret for Jira, and signed events for Stripe) with replay protection, and sensitive endpoints are rate limited.