Last Updated: August 2026
CloudBit OS operates serverlessly regarding your document data. When you edit text, draft markdown, compile code, or organize folders, all document contents transfer directly between your web browser client and the official Google Drive API. We store zero document files on intermediate CloudBit OS application servers.
CloudBit OS requests incremental Google OAuth 2.0 authorization with minimal scopes:
drive.file: Accesses only files created by or explicitly opened with CloudBit OS.drive.appdata: Stores hidden desktop workspace preferences (theme, wallpaper, accent color).Your Google OAuth refresh token is encrypted server-side using AES-256-GCM before being stored in our Supabase PostgreSQL database. Clients never receive raw refresh tokens. You can revoke Google OAuth permissions at any time from your Account Profile or Google Security Portal.
You maintain total ownership of your data. Executing account deletion from CloudBit OS immediately purges all database records (user profile, app settings, session tokens) and revokes active OAuth grants directly on Google's authorization server.