Vivli
Vivli helps you read and learn from books you import. This policy describes what data Vivli processes, where it may be stored or transmitted, and the third-party services involved. Vivli is not a fully local-only app when you use an account, sync, Ask Vivli, or crash reporting.
Account data
If you create an account, Vivli processes your email address and authentication identifiers. Sign-in may use email and password, Sign in with Apple, or Google sign-in. Authentication and account records are handled through Supabase Auth. Passwords are handled by the authentication provider and are not stored by Vivli in plaintext.
Reading data
Vivli may process books you import (including file content stored on your device), reading progress, highlights, notes, bookmarks, collections, and imported-content metadata such as titles and authors. Content may remain on your device. When you are signed in, selected library and reading data may be synchronized to Vivli’s cloud account so you can use Vivli across devices.
Vivli Brain data
Vivli may process Brain-related data derived from your reading and use of the app, including concepts, relationships, graph structure, memories, insights, learning events, conversations associated with Brain features, and embeddings or similar representations when those are generated and stored for your account. Some of this data may be stored locally and, when you are signed in, may sync to Vivli’s backend.
Ask Vivli and AI processing
When you use Ask Vivli, your question and relevant context derived from your reading or library (for example selected text or book-related context) may be sent securely through Vivli’s servers to OpenAI to generate a response. Do not include information you do not want processed for that purpose. Vivli does not claim that Ask Vivli keeps that content solely on your device.
Crash and error diagnostics (Sentry)
If crash reporting is enabled for a build, Vivli may send diagnostic information about crashes and errors to Sentry to help improve reliability. Events are configured to avoid sending passwords, tokens, and similar secrets, and user association uses an opaque user identifier rather than your email when possible. Session replay is not used.
Supabase (backend infrastructure)
Vivli uses Supabase as backend infrastructure for authentication, database storage, file/object storage where applicable, and Edge Functions that power features such as Ask Vivli and account deletion. Signed-in account data and synchronized content are processed through this infrastructure.
Local storage
On your device, Vivli may store imported book files, caches, preferences, session tokens in secure on-device storage where supported, and optional local analytics events if you enable them in Settings. Local copies may remain until you clear app data, sign out and clear local state, or delete your account through the in-app flow.
Optional analytics
If you enable Anonymous Analytics in Settings, usage signals may be stored locally on your device. They are not sold. This local preference is separate from crash reporting via Sentry.
Cover and metadata lookups
To help find book covers or related metadata, Vivli may query third-party catalog services such as Open Library and Google Books using title or author information you provide or that is derived from imported content.
Third-party services
Depending on which features you use and how the app is configured, Vivli may rely on: Supabase (auth, database, storage, Edge Functions); OpenAI (Ask Vivli responses); Sentry (crash and error diagnostics when enabled); Apple and Google (sign-in); Open Library and Google Books (cover/metadata lookup); and Expo/EAS (app distribution and updates infrastructure).
Account deletion and retention
You can sign out, export Brain data, delete Brain data, or delete your account from Settings. When you delete your account, Vivli attempts to remove associated account data from Vivli’s systems according to the implemented deletion process, including known server-side user records and related storage objects, and to clear local account data on the device used for deletion. Residual copies may temporarily remain in backups, logs, or provider systems outside Vivli’s direct control. Vivli does not claim a specific retention period beyond that deletion behavior.
More detail on deleting your account: vivli.app/delete-account.
Contact and public copies
Contact: support@vivli.app
Public Privacy Policy: https://vivli.app/privacy
Public Terms: https://vivli.app/terms
Support: https://vivli.app/support