Most prompt managers store your data on their servers. CloudPrompt doesn't. Every prompt you save goes directly to your own Google Drive — encrypted, private, and under your control.
Get CloudPrompt — FreeIt's a question almost no prompt manager wants you to ask.
When you save a prompt to a typical prompt manager, it gets uploaded to a database the company controls. The marketing copy says "synced to the cloud." The reality is "stored on a server you can't see."
If the data lives in someone else's database, you don't own it — you have access to it. Access can be revoked, throttled, paywalled, or breached. That's a fundamentally different thing from ownership.
Small SaaS tools come and go. The prompt library you spent months building can disappear with 30 days' notice. Some tools offer export — many don't. Either way, you're betting on someone else's runway.
Internal product names. Code snippets. Client briefs. Strategy documents. The prompts you write reflect what you're working on — and you probably don't want all of that sitting in a third-party database with unclear retention.
No proprietary database. No black box. Just a folder in your Google Drive.
The data path
Creates a single folder
CloudPrompt makes one folder named CloudPrompt in the root of your Drive. That's the entire footprint.
Stores prompts as JSON
prompts.json is plain, human-readable JSON. You can open it in any text editor — no proprietary format.
Uses drive.file scope
Google's most restrictive Drive scope. CloudPrompt can only access files it created. Period.
Cannot see your other files
Your tax docs, photos, work files — invisible to CloudPrompt. Google enforces this at the API level, not as a promise.
When the data really is yours, things get simpler.
Download your entire library as JSON or CSV from Settings → Backup & Restore → Export. Or just open prompts.json directly from Google Drive. Your data is never locked in.
Same Google account = same prompts everywhere. Install CloudPrompt on your laptop, desktop, and work machine — all three sync through your Drive automatically. No CloudPrompt account, no separate login.
CloudPrompt caches your library locally so you can read prompts without an internet connection. When you're back online, changes sync to Drive automatically — no manual conflict resolution.
Uninstall the extension and delete the CloudPrompt folder from your Drive. Your data is gone — there's no copy on our servers, because there are no servers. No "30-day deletion window," no support ticket required.
You don't have to trade functionality for data ownership.
Ctrl+Shift+Y)
If we don't need it, we don't ask for it.
storage
Caches your prompts locally for fast access and offline use. Stays on your device. We can't read it.
identity
Authenticates with Google via OAuth 2.0. We see only the OAuth token — never your password.
tabs
Used only for the sign-in flow on Edge, Brave, Comet, and Opera (where Chrome's native auth doesn't work). Reads the URL of the temporary sign-in tab to extract the token, then closes it. We don't see your other tabs.
contextMenus
Powers the right-click Insert CloudPrompt and Save to CloudPrompt menu items. We only see the text field you chose to insert into — at the moment you select a prompt.
drive.file
Google's most restrictive Drive scope. Lets CloudPrompt read and write only files it creates. Your other Drive files are invisible to us — Google enforces this, not us.
Yes. Open Google Drive, navigate to the CloudPrompt folder, and open prompts.json. It's a plain JSON file — readable in any text editor or directly in Drive's preview pane. Every prompt, folder, and tag you've created is right there. You can even edit the file directly if you want (though using the extension is much easier).
Uninstalling the extension clears the local cache from your browser. Your prompts.json file remains in your Google Drive — your data isn't lost. Reinstall CloudPrompt later (or on another device) and reconnect the same Google account, and your full library reappears. To delete everything permanently, just remove the CloudPrompt folder from Drive.
No, and not because we promise we won't — because Google won't let us. CloudPrompt uses the drive.file OAuth scope, which only grants access to files the extension itself creates. Your other documents, photos, and folders are invisible at the API level. Even if we wanted to access them, we couldn't.
Yes, with the same encryption Google Drive uses for everything else: TLS in transit and AES-256 at rest. Your prompts.json file inherits Google's enterprise-grade Drive encryption. CloudPrompt itself doesn't add a separate encryption layer because the OAuth-protected, drive.file-scoped storage is already secure — and adding our own encryption would mean storing keys somewhere, which is exactly the architecture we're avoiding.
CloudPrompt caches your prompts locally, so you can keep accessing your library even if Drive is briefly unavailable. When Drive comes back, your changes sync automatically. For the longer-tail scenario — Google Drive itself disappearing — you can export your full library to JSON or CSV at any time from Settings → Backup & Restore. Your data is portable by design.
Free forever. No CloudPrompt account. Your Drive, your data, your call.