Skip to content
wobbi

Privacy policy

Updated: 2026-10-16

Scope

This policy describes data handling by the Wobbi website you are visiting. Its deployment operator runs the backend and handles related requests. Maintaining the open-source project does not automatically make someone the operator of this website.

Your information and device storage

Entries, links, follow-ups, custom fields, attachments, covers and drafts are processed in your browser. Information is encrypted before being written to a local folder, persistent browser cache or Google Drive. Your library password and decryption keys are not sent to the application backend. While unlocked, plaintext is available in your browser for display and editing. The browser also stores connection information, theme, language and device preferences. Local-folder use does not require Google authorization.

Google data and access scope

When you connect Google Drive, Wobbi requests openid, email and drive.appdata permissions. Your Google account identifier and email identify the connected account. Drive access is limited to this app's dedicated hidden data folder and is not used to read your other Drive files. The folder holds encrypted information, attachments, covers and technical records required for synchronization and recovery. Files are transferred directly between your browser and Google. Device drafts stay in the local encrypted cache.

Backend and authorization credentials

The Cloudflare backend handles Google authorization, credential refresh and coordination of single-device access. It stores account identifiers, email, connection and occupancy records, and encrypted Google authorization credentials. Your browser obtains a short-lived access token when needed. The backend does not proxy library file bodies or receive your library password, decryption keys or plaintext forms. Google provides authentication and Drive storage. Cloudflare hosts the website and authorization coordinator. These providers process network requests and necessary technical logs under their own policies and this website's configuration.

Use and sharing

Data is used only for the information management, identity confirmation, storage, synchronization, backup and access coordination you request. Wobbi does not sell Google user data, use it for advertising or training general-purpose AI models, or provide it to third parties unrelated to these functions.

Retention and deletion

Encrypted device copies and drafts remain until you clear them or the browser removes site data. Clearing browser data in Storage and security removes this device's connections, caches, drafts and unsynced changes. It does not delete your local folder or data already saved to Drive. You can delete the library files in your selected local folder or remove Wobbi's hidden app data under Google Drive Settings → Manage apps. Retained historical versions may still contain encrypted copies of a deleted entry. You control the retention and deletion of downloaded backups.

Revoke Google access and remove connection records

You can revoke Wobbi's access through your Google Account's third-party connections. Revocation prevents further Google access but does not automatically delete existing device or Drive data. Disconnecting ends the current website session. Encrypted authorization credentials, account information and technical records may remain on the backend until replaced or deleted by the deployment operator. Contact the website operator to request deletion of those records. Service logs follow the operator's Cloudflare retention settings.

Contact and feedback

This website is run by its deployment operator. For questions about this site's authorization, account records or privacy, contact that operator using the support email shown on the Google authorization screen. Open-source project issues can also be reported through the GitHub link below. Do not include passwords, keys or private information in public reports.