Updated: November 11, 2026

Security

vivibe is built so that most of what it does never needs a server. This page describes how the parts that do are protected. For what data we handle, see the Privacy Policy.

1. Local-first design

The engine that analyses your code runs on your Mac. Repositories are never uploaded. The map, comparisons, the editor and Simulate run on your Mac. During the private beta the app opens only after you sign in with an approved email.

2. Application integrity

  • Signed with an Apple Developer ID and notarized by Apple.
  • Updates are signed; the app verifies the signature before installing.
  • Each release publishes SHA-256 checksums.
  • A Content Security Policy limits the app's web view to the vivibe API.
  • No third-party analytics, crash-reporting or tracking code; usage counts, shared only if you allow it, go only to the vivibe API.

3. Authentication

  • Auth0 with Authorization Code and PKCE, in your system browser.
  • The refresh token is stored in the macOS Keychain (on Linux, in a file only your user can read) and never reaches the app's web view.
  • API requests carry short-lived access tokens, verified by the vivibe API.

4. GitHub access

ControlDetail
PermissionsRead-only: contents, metadata, pull requests
ScopeOnly the repositories you choose
TokensPer repository, expire after one hour, held in memory
StorageStored GitHub tokens are encrypted at rest

5. Infrastructure

  • AWS in Singapore (ap-southeast-1): containers on ECS Fargate, PostgreSQL on RDS.
  • TLS for all traffic.
  • Secrets in AWS Secrets Manager; each service has its own database login.
  • Server logs kept 14 days and never contain your code; database backups kept 7 days.
  • Production access limited to the people who run it.

6. AI requests

AI runs only when you click. A request holds only what that action needs, is not stored after the answer, and is not used to train models, by us or by OpenAI.

7. Coding agents

vivibe reads coding-agent transcripts on your Mac and sends them only when you ask an AI action about them. For Claude Code sessions it starts, its hooks are passed for that session only; your own Claude settings are never changed.

8. Reporting a vulnerability

Email security@vivibe.net with the details and steps to reproduce. Please give us reasonable time to fix it before telling others. We reply as soon as we can and credit you if you wish.