How we handle review data.

We store the email you submit and the signup source in Convex so the founder can contact you about VibeApprove and arrange onboarding. Joining does not create an account or start a subscription. You can ask us to remove your email through the support page.

When a workspace connects GitHub and Slack, VibeApprove receives the pull request URL, repository and commit metadata, changed file paths and diff evidence needed to prepare a review. The workspace also stores settings, approval states, review events, and the identity mappings needed to enforce those settings.

WorkOS handles sign-in. If analytics is enabled for this deployment, PostHog receives account identity, page visits, and product usage events. Session recording and automatic click capture are disabled so private review content is not recorded through those features.

Review context is processed to summarize a change, surface impact and uncertainty, show evidence in the dashboard, and keep a decision attached to the reviewed commit. The AI provider receives only the review context needed for that run. Billing checkout, when enabled, is handled through the configured Polar sandbox flow; confirmed credit and subscription state are stored with the workspace billing record.

Review evidence, approval history, and billing records are kept for your workspace. Disposable webhook receipts and expired sign-in connection state are removed after 30 days. During the private beta, the founder handles export and deletion requests.

To request access help or a data question, use the support path described on the support page.