Data & Trust

The free deterministic scan never sends your code to any AI at all — the secret scanner and dependency check run inside NittiM's own server process, and the only external call is to GitHub to fetch the snapshot.

Deep Verification sends a prioritized digest of the code to the Anthropic API for the audit. That is an API relationship under commercial terms that do not use API inputs or outputs to train models — NittiM has no data-sharing or training arrangement of any kind, and NittiM itself retains nothing from the digest after the audit returns. See Anthropic's commercial terms for their side of that boundary.

NittiM can never modify your code. The fis-audit GitHub App holds exactly two permissions — repository contents: read-only, and metadata: read-only — and subscribes to no events. GitHub shows you that permission screen before you approve it and enforces it regardless of what NittiM'scode does; you can confirm it any time at github.com/settings/installations. If you use a pasted token instead, create it fine-grained, read-only, scoped to the one repository you're auditing, and revoke it right after — NittiM works identically either way.

Reports are kept until you choose to delete them. There is no automatic expiry for live reports.

When a report is deleted, it immediately disappears from all read paths — the report link returns not-found and the API returns 404. The underlying row is then permanently and irrecoverably removed from the database on the next nightly retention pass, which runs at 03:00 UTC. Rows deleted more than 30 days prior are purged on that pass; a row deleted today will be purged on or after the corresponding date 30 days out.

You own every report you generate. To delete one:

DELETE /api/v1/audit/<id>
Authorization: Bearer <your-api-key>

Public reports — audits of public repositories — are accessible to anyone with the link. This is intentional: the link is the share mechanism. If you want a report to stop being accessible, delete it.

Reports of private repositories are never accessible via a shareable link to anyone other than the report's owner or an organization member. The link returns 404 for everyone else.

When you run an audit inside an organization, all members of that organization can read the report. An organization owner or admin can also delete it. Reports are scoped to a single organization — members of a different organization cannot access them.

Reports are stored in Supabase (managed Postgres, us-east-1). All data is encrypted in transit (TLS 1.2+) and at rest (AES-256). Access to the database is via a service-role key held in Vercel environment variables — it is never exposed client-side and never committed to source control.