KnoBox

Privacy Policy

This is a straightforward summary of how KnoBox handles your data — plain-language, not a substitute for formal legal review before wider release.

KnoBox is not fully local. To power AI summaries, tagging, semantic search, and chat, KnoBox sends data to its own cloud backend — this section explains exactly what that means.

What's stored on your device

A full copy of your bookmarks, AI summaries, tags, and chat history is cached locally in this app's own database, so everything stays available offline and stays fast.

What's sent to the cloud, and why

When you save a link, its URL and the page's own text content are sent to KnoBox's backend (built on Supabase) so it can be fetched, summarized, and tagged. That text, along with your search and chat queries, is sent to Anthropic's Claude AI to generate the actual summaries, tags, and answers, and to Voyage AI to generate the embeddings that power semantic search. Your saved bookmarks, summaries, tags, and chat messages are also stored server-side, so they can be regenerated if you reinstall on the same device.

Every install is scoped by a random device identifier, not tied to your name, email, or any personal profile — using KnoBox this way never requires an account.

Signing in (optional)

You can optionally sign in with your email to sync your library across multiple devices. Signing in uses a one-time 6-digit code sent to your inbox — KnoBox never asks for or stores a password. If you sign in, your email address is stored by our authentication provider (Supabase) and used only to identify your account and scope your synced data to it; it's never sent to Anthropic, Voyage, or any other AI vendor, and never used for marketing. Signing in links the bookmarks already saved on that device to your account, going forward and retroactively.

KnoBox Pro

If you purchase KnoBox Pro, the transaction is handled entirely by Google Play — KnoBox never sees or stores your payment details. We receive your purchase's subscription status from Google Play to confirm entitlement, associated with your account.

App Lock

"Require unlock to open" uses your device's own biometric or PIN verification (Android's BiometricPrompt). KnoBox never sees or stores your fingerprint, face data, or PIN — that verification happens entirely within Android's own secure layer and never touches the network.

Crash reporting

If crash reporting has been configured for this build, anonymized crash and diagnostic data may be sent to help fix bugs. No bookmark content is included.

Your choices

Export your data to a JSON file, or delete an individual bookmark (which removes it from the server too), anytime from Settings or the bookmark itself. "Clear local cache" only wipes the on-device copy — it doesn't delete anything stored server-side. If you're signed in, Settings lets you permanently delete your account, which removes everything it owns server-side (bookmarks, summaries, tags, chat history) immediately and can't be undone. Uninstalling the app without deleting your account first removes everything stored on-device, but server-side data tied to your account or anonymous device identifier isn't automatically deleted.

Contact

Questions about this policy can be directed to the developer listed on this app's store listing.