Trust
Security overview
Last updated:
Content-free by design
Veripsa Core reads file contents transiently to produce operational metadata, then discards them. Source file bodies are not stored or displayed on customer surfaces. It keeps only minimal content-free service metadata — repository and pull-request metadata needed to run advisory checks and scope them to opaque GitHub account identifiers. Because source file bodies are not retained, source code cannot be exposed from our storage. The service metadata we do keep is data, and we protect it as customer data. See the Privacy Policy for the full list.
Per-account isolation
Every Veripsa Core record is scoped to the installing GitHub account and enforced with tenant-isolated database controls, so one customer's data is never readable by another. The same isolation posture is the substrate the platform side (account model, billing records) will use as those surfaces open.
Data protection
- No source code stored. We retain only a content-free record of repository structure, reservations, and advisories.
- Least-privilege access. The application connects to its database with a restricted role, scoped to the access it needs.
- Encryption in transit.Traffic to the service and to GitHub's API is protected with TLS.
- Encryption at rest. The content-free working set is held in a managed database that encrypts data at rest at the platform layer; backups are encrypted under the same posture.
- Managed hosting.The service runs on Render with a managed database; we rely on the provider's infrastructure security and patching.
- No card data. We never handle payment card details; early access has no active checkout or card collection.
GitHub permissions
Veripsa Core requests only the GitHub App permissions it needs to read repository structure and post checks and comments on pull requests. You choose which repositories it can access, and you can change that scope or uninstall the App at any time from GitHub. Here is every permission the install screen will show you, and why it is requested:
| Permission | Level | Why |
|---|---|---|
| contents | read | Read repository structure and file text transiently to derive the documented content-free metadata. File bodies are not stored. |
| pull_requests | write | Post the advisory comment on covered pull requests and manage the optional veripsa-ack label. |
| checks | write | Post the advisory check run on PR head commits. |
| merge_queues | read | Keep merge-group state consistent with repositories that use a merge queue. |
| metadata | read | Standard GitHub App requirement. |
Veripsa never requests contents: write — it does not push commits, open pull requests, or change branch protection. It also does not request the issuespermission: GitHub exposes PR conversations and labels through issue-backed APIs, and Veripsa uses them only for the PR's own managed comment and veripsa-ack label.
Data deletion
Uninstalling the App purges your account's content-free working set from our database, and you can request erasure at any time. See the Privacy Policy.
Reporting a vulnerability
If you believe you've found a security issue, please email support@veripsa.com with the details and steps to reproduce. Please give us a reasonable chance to investigate and fix the issue before disclosing it publicly.
The full reporter-facing flow — what to include, our coordinated- disclosure window, and our safe-harbor stance for good-faith research — lives on the Security disclosure page.
Honest scope
Veripsa is a young product run by a small team. We've described the measures that are in place today and have not claimed any formal compliance certifications (such as SOC 2 or ISO 27001). If your organization needs a security review or specific assurances, contact support@veripsa.com.