Data controls

• Learning events (reviews, outcomes, concepts, streaks) live on your device and, if you are signed in, sync to our backend. A successful account deletion removes the associated primary database rows.
• Account data (email, tokens) is stored on the backend until you delete your account; tokens are revoked on sign-out or deletion.
• Your auth token is stored locally in the operating system keychain, encrypted at rest.
• Code sent for a review is transmitted to the AI provider to generate the explanation. We do not persist raw reviewed code beyond generating that explanation; the provider's own retention governs their side.

Learning and account data are kept until you remove them. Primary-record, backup, provider, and operational-log timelines are still being finalized during the beta; this page does not promise deletion from systems we have not yet verified.

Cloud analysis begins only after an explicit review action. Full payload preview and per-repository consent controls are still being completed. There is no file exclusion list yet: a file you select or open is sent once it passes the secret scan. In a Brief, untracked files that .gitignore covers are left out.

The app has no export button yet. For a copy of your data, email support@unvibe.site. You can delete your account to remove it from your device and our servers. If you never created an account, your lessons stay on your computer, and our server keeps only a random install ID with a few dates and usage counts, never your code or prompts. Depending on where you live, you may have additional rights under laws such as GDPR or CCPA.

Unvibe does not build its own training dataset from your code. During the beta, explanations are generated by the Google Gemini API, and Google's Gemini API terms decide how Google may use that content. If you add your own provider key in the app, requests go to that provider under its terms instead. The privacy policy has the full details.