Security & Trust
Your code, on your terms
IonWarp reviews pull requests, so it touches the thing you protect most. This page states plainly how that access works and what we keep.
How IonWarp accesses your code
IonWarp installs as a GitHub App on the repositories you choose — and only those. Access is scoped by GitHub's own permission model, visible in your organization's settings, and revocable at any time by uninstalling the app.
IonWarp reads your code; it never writes to your repository. The GitHub App holds Contents: read-only — pull-request comments, inline reviews and one-click suggested changes are the only things it can post.
Webhook deliveries from GitHub are verified against their signature before anything is processed; an unsigned or mis-signed payload is rejected at the door.
Where reviews run
Each review runs in a sandbox container that is separate from the application and from your own infrastructure. Your repository is checked out into a directory private to that run.
Sandbox containers are kept warm and can serve more than one session, so isolation does not rest on a container being new. Every session — a review, a repository scan, or a chat — runs inside its own envelope: a per-run environment that holds only that run's credentials, and per-run directories for the checkout and its output. When the session ends, the envelope is wiped — the environment, the checkout, and the output directories — before the container can serve anyone else. A reused container therefore never hands one customer's code, credentials, or output to another customer's session.
What we store
IonWarp stores the review artifacts you see in the dashboard: findings, pull-request metadata, scorecard results, and run telemetry. That durable ledger is what powers the findings history, autofix rounds, and the public resolution-rate metric.
Review data is deleted 90 days after it was last updated. That window is one number in IonWarp's configuration (retention.customer_data_days); every record we keep about a review — the task, its findings, scorecards, learnings, screenshots, sandbox memories, and support tickets — is stamped with it when written, and a nightly sweep deletes whatever is past it.
Deleting a project deletes its review data with it.
Enterprise
The Enterprise tier adds SSO/SAML, audit logs, GitHub Enterprise support, a custom security review of your setup, and an SLA — the same list published on our pricing page.
Questions or disclosures
Security questionnaires, compliance questions, or a vulnerability to report — reach us through the contact page and we'll route it to the right person.
