Legal
Subprocessors
Last updated:
1. Active subprocessors
We use the smallest possible set of subprocessors. Each row lists the vendor, the purpose it serves, the data category that flows to it, and the processing region.
| Vendor | Purpose | Data category | Region |
|---|---|---|---|
| GitHub GitHub, Inc. | GitHub App platform (App install, webhook delivery, check runs, PR comments); OAuth sign-in to the Veripsa dashboard. | Minimal content-free repository and pull-request metadata; webhook events; opaque GitHub account / repository / installation IDs; the OAuth identity at sign-in (opaque GitHub user ID only). | Global (GitHub-operated; primary US). |
| Render Render Services, Inc. — Core engine | Compute and managed database hosting for the Veripsa Core engine (the GitHub App): the content-free service metadata, advisory records, webhook delivery audit, governed-write audit. | Minimal content-free repository, pull-request, path, symbol, public GitHub handle, advisory, delivery, and lifecycle metadata, plus opaque GitHub IDs. No retained file or diff bodies, intentionally extracted secret values, or dashboard profile fields such as name, email, and avatar. GitHub secret stores are not accessed; tracked file bodies are processed transiently and discarded. | US. |
| Render Render Services, Inc. — Platform | Compute and managed database hosting for the Veripsa platform (this website, dashboard, account status, and early-access plan state). | Opaque GitHub user / installation IDs; organization UUIDs; account and early-access plan status. No payment card data, no profile fields (name / email / avatar are stripped at sign-in rather than stored). | US. |
The Veripsa platform itself does not store payment card data, does not run third-party analytics or advertising SDKs, and does not use a third-party email/CRM/marketing automation vendor — inbound mail is handled by direct email to support@veripsa.com.
2. Not in use today
We do not use third-party analytics, advertising SDKs, product telemetry SDKs, error-reporting SaaS, email/CRM platforms, or additional CDN/edge subprocessors for Veripsa Core today.
If an additional subprocessor becomes active, it will appear in the table above with a new Last updated date.
3. Change policy
Material changes to this list — adding a subprocessor, removing one, or changing the data category or processing region of an existing one — will be reflected on this page with a new Last updated date at the top.
- Target notice window — we aim to publish a material subprocessor change at least 30 days before it goes into effect, so customers can review and object.
- No contractual SLA today — that 30-day window is a target, not a contractual commitment on the default plans. A contractual subprocessor-notification SLA can be included in a Data Processing Agreement (DPA) on request.
- How to be notified — there is no automatic notification feed today. A signup-based change feed is on the roadmap. In the meantime, if you need to be notified, email support@veripsa.com and we will keep you on a manual list.
- How to object — if you object to a new subprocessor, email support@veripsa.com before the effective date.
4. PII posture (reminder)
Veripsa is PII-minimal by construction:
- The Veripsa platform identifies accounts by opaque GitHub IDs (immutable numeric IDs), not by names or emails. Profile fields returned by GitHub at sign-in are stripped from the session rather than persisted.
- Veripsa Core is content-free: file contents are read transiently and discarded. Only minimal operational metadata is retained. The full data boundary is documented in the Privacy Policy.
- Veripsa Core early access has no active checkout or card collection.
Related
- Trust Center — the one-page summary for security and procurement review.
- Privacy Policy — the policy form of the data-boundary statements above.
- Security overview — how the data we do hold is protected.
- Terms of Service — the terms for using Veripsa Core.