Support

Email support@veripsa.com. To help us respond quickly, please include:

• Your GitHub organization or account name, and the repository involved.
• A link to the pull request, and what you expected versus what you saw.
• The approximate time it happened (so we can correlate events).

Please don't paste source code or secrets — Veripsa is content-free by design, and support does not need repository contents to help.

• Installing, configuring, or uninstalling the Veripsa Core GitHub App.
• Understanding a check or comment Veripsa Core posted on a pull request.
• Plans, billing, and coverage questions.
• Privacy and data requests, including erasure.
• Reporting a bug or a suspected security issue — for security specifically, see /security/disclosure for what to include and our coordinated-disclosure stance.

Veripsa Core is advisory and content-free: it may read file contents transiently during processing, but it does not store source code. It does not resolve merge conflicts or decide what gets merged — your branch-protection settings do that. So support can't:

• Review, debug, or write code in your repositories.
• Resolve git merge conflicts or perform merges for you.
• Guarantee that every collision is detected or that flagged collisions are real conflicts.

Veripsa is run by a small team, so we don't offer a contractual support SLA today. We aim to reply to email within a few business days, and we prioritize suspected security issues and service outages. If you're evaluating Veripsa for an organization with specific support needs, email us so we can scope the right support path.

• Privacy Policy — what data Veripsa Core processes and stores.
• Security overview — how your data is isolated and protected.
• Security disclosure — how to report a suspected security issue.
• Terms of Service — the terms for using Veripsa Core.