Privacy Policy
Last updated: May 2025 · Applies to the SaveAnywhere Chrome extension.
Our core privacy promise
SaveAnywhere was built with a simple principle: your files and data are yours alone. We do not operate servers that receive your file content. All processing happens locally inside your browser. We collect no personal data, no analytics, and no file metadata.
1. Who We Are
SaveAnywhere is a Chrome browser extension developed and maintained by AMZBoosted. In this Privacy Policy, "we," "us," and "our" refer to AMZBoosted. "You" refers to anyone who installs or uses the SaveAnywhere extension.
Contact: [email protected] | AMZBoosted.com
2. How the Extension Works
Understanding our privacy model requires understanding how SaveAnywhere functions:
You right-click a file URL in your browser and choose "Save to Cloud."
The extension fetches the file directly from the source URL using your browser's network capabilities.
The file is uploaded to Google Drive using the official Google Drive API, authenticated with your own OAuth token stored locally.
AMZBoosted servers are never involved. The data path is: Source Website → Your Browser → Google Drive.
3. Information Accessed or Stored
Stored locally in your browser (never sent to us)
| Data | Purpose | Where stored |
|---|---|---|
| OAuth access & refresh token | Authenticate uploads to Google Drive | chrome.storage.local
|
| Extension settings & preferences | Remember your configuration | chrome.storage.local
|
| Auto-Rules configuration | Evaluate automatic routing rules | chrome.storage.local
|
| Upload history log | Display past transfers in History tab | chrome.storage.local
|
All of the above is deleted permanently when you uninstall the extension.
Data we do NOT collect
- Your name, email address, or Google account details
- File content or file metadata on our servers
- Browsing history or URLs you visit
- Usage analytics, feature events, or crash reports
- IP addresses or device identifiers
- Cookies or cross-site tracking of any kind
4. Google Drive & OAuth Authorization
4.1 OAuth 2.0 Flow
When you connect Google Drive, SaveAnywhere initiates Google's standard OAuth 2.0 authorization flow. You are redirected to Google's own login page — your credentials are entered directly on Google's servers and are never seen or handled by SaveAnywhere or AMZBoosted.
4.2 Scopes Requested
The extension requests only the https://www.googleapis.com/auth/drive.file
scope. This grants permission to upload and manage files that SaveAnywhere creates.
It does NOT grant permission to read, browse,
edit, or delete any other files in your Drive.
4.3 Token Storage
Tokens are stored exclusively in chrome.storage.local
— sandboxed to this extension only. Tokens are never transmitted to AMZBoosted.
4.4 Revoking Access
Disconnect inside the extension (Providers tab), or revoke at myaccount.google.com/permissions.
5. Supported Cloud Providers
The same privacy model will apply to all future providers when added.
6. Chrome Extension Permissions Explained
| Permission | Why it's needed |
|---|---|
| contextMenus | Adds "Save to Cloud" to the browser right-click menu. |
| storage | Stores your OAuth token, settings, rules, and history locally. |
| downloads | Required for optional "Intercept browser downloads" (off by default). |
| notifications | Shows upload completion/failure notifications (can be disabled). |
| identity | Handles the Google OAuth 2.0 flow via Chrome's identity API. |
7. Data Retention & Deletion
Since we do not collect data on our servers, there is nothing for us to retain or delete. All data lives exclusively on your device.
chrome://extensions.
8. Data Sharing & Third Parties
The only "third party" that receives data is Google (when you upload to Google Drive). That transfer happens directly between your browser and Google — we are not involved and have no access to it.
We do not use analytics services, advertising networks, tracking pixels, or any form of behavioral monitoring.
9. Security
- OAuth tokens are stored in Chrome's sandboxed
chrome.storage.local— inaccessible to other extensions or web pages. - All communication with the Google Drive API uses HTTPS (TLS-encrypted).
- The extension declares only the minimum required permissions (principle of least privilege).
- The extension does not inject content scripts into all pages — it only operates via context menus and the side panel.
10. Children's Privacy
SaveAnywhere is not directed at children under 13. We do not knowingly collect personal information from children. Concerns? Email [email protected].
11. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be noted in the Chrome Web Store update notes and reflected in the "Last updated" date above. Continued use of the Extension after changes indicates acceptance.
12. Contact Us
Questions about this Privacy Policy? We're happy to help: