Security

Read-only by design. Your code never leaves GitHub.

You're giving us a view of how your company spends and builds. Here is exactly what we touch, what we store, and what we never will.

Read-only access

Every connector uses the narrowest read scope the vendor offers. We never write, comment, merge or change settings in your systems.

Metadata only

We store PR titles, branch names, file paths, timestamps, reviewers, ticket fields and costs. Never file contents, diffs, prompts or AI outputs.

Encrypted everywhere

TLS in transit. Data and connector secrets encrypted at rest, with secrets kept separately from application data.

Your region

India-region hosting (Mumbai) is available, so your data can stay in the country.

Delete in one click

Disconnect any source, or delete your whole workspace, at any time. Deletion is complete within 7 days, backups included.

No individual scoring

Team-level views by default. Person-level cost views can be limited to admins or turned off entirely.

Exactly what each connector reads

SourceAccessWhat we read
AnthropicAdmin API key (read)Cost and usage reports; Claude Code daily per-user metrics
OpenAIAdmin key (read)Organization costs and usage by project and model
CursorAdmin API keyTeam members, daily usage and spend
GitHubGitHub App, read-onlyPR metadata, changed file paths, reviews, CODEOWNERS, Copilot seat activity
Jira / LinearOAuth, read-onlyIssues, epics, sprints/cycles, status history
Stripe (optional)Restricted read keyProducts, prices, subscription revenue totals; no customer card data
ledger-hook (optional)Per-org ingest tokenSession time, tool, repo, branch, ticket key, cost; no prompts or code

Where we are on compliance

We're an early-stage company and we'll say so plainly: we do not have SOC 2 yet. We follow its controls (access reviews, least privilege, audit logging, encrypted backups) and will start a formal audit as customers require it. If your security team has a questionnaire, send it over and we'll answer it in full.

our contact form