Keepsprig · Privacy policy
Keepsprig Privacy Policy
Keepsprig stores an encrypted library on your device. Optional previews, Google Drive sync, and on-device AI each have separate data-handling boundaries.
Publication notePre-release draft for the Android development build. Review it against the final release and provider configuration before store submission.
Your local library
Keepsprig is presented by bee n moss. It does not require a Keepsprig account or host your library on a developer server. URLs, titles, descriptions, notes, categories, tags, and search content are stored in encrypted local records, without a separate plaintext search index.
Device authentication and lock-on-background protect access in the Android development build. Locked sharing writes an encrypted capture for import after unlock. Choosing an existing category while sharing requires a separate foreground unlock where protection is enabled.
Preview requests and opening links
Preview fetching contacts the saved public website and, where needed, its image host directly from your device. Those sites can observe the request, including your IP address. Requests do not include your browser cookies or social login credentials, and Keepsprig does not load social embeds to access private content.
The default fetches when you open link details. Automatic mode fetches after unlock; Off stops preview work. Opening the original link leaves Keepsprig and uses the destination’s own services and policies.
Optional Google Drive sync
If you connect Google Drive, Keepsprig requests permission for its private app-data storage rather than creating an app login. It uploads encrypted library snapshots when you manually sync while unlocked. Google can see storage metadata such as file sizes, counts, and timing.
In default Google-account protection, the content key is also stored in private Drive app data, so Google or someone with account access can decrypt the library. This is not end-to-end encryption against Google. Optional separate-key protection instead wraps that key using a recovery secret you hold and do not upload.
Disconnecting removes the local sync binding but retains local and remote copies and does not itself revoke Google’s permission grant. iCloud and automatic background sync are not implemented.
Portable encrypted backups
An exported .keepsprig file has an independent recovery key. You choose its destination through Android’s document picker. Keep the file and key separately; recovery needs both, and bee n moss cannot reset a lost key. Copies exported or shared outside the app are under your control.
Optional on-device AI
Android on-device categorization is off by default and uses Google ML Kit/AICore on supported devices, with an explicit model-download step where required. Classification uses bounded saved titles/descriptions and existing category names; URL-shaped text is redacted. URL fields, personal notes, tags, images, provider tokens, and vault keys are excluded.
Inference runs locally while unlocked, but the SDK can collect device/app information, identifiers, latency, input/output sizes, events, and error data for diagnostics and usage analytics. Local inference does not mean zero telemetry. Keepsprig does not log inference content or raw model output. Availability and inference quality remain under validation; unsupported or failed AI leaves manual categories and local rules usable.
Future services and support
No advertising or payments are enabled. The Android app currently makes no calls to the optional cloud-AI gateway; provider integration, consent, and paid access are future work. This policy must be updated before enabling those services.
Contact through this website sends us the information you choose to provide. Include only the details needed to explain a problem; do not send your library backup, recovery keys, credentials, or private saved content unless you deliberately choose to share it.