1. Who operates REDOWN, and how to contact us
REDOWN is an independently developed browser extension. To contact the developer about this policy, account access or a privacy request, use the public support issue form for non-sensitive questions. Please never include access tokens, passwords, personal files or private URLs in a public issue. For a sensitive issue, open a general issue requesting a private communication channel without sharing the sensitive information itself.
2. Data the extension may process
Depending on your use and settings, REDOWN needs to handle the following types of information to carry out a transfer or manage a cloud destination:
- Cloud account connection data: provider identifiers, authentication status, OAuth access or refresh credentials where issued, and the permissions you authorize.
- File and destination details: filenames, types, sizes, source URLs, originating page URLs where captured, remote bucket/folder/object paths and provider responses.
- User-selected file contents: bytes of files you explicitly choose to upload, fetch remotely, preview, move or manage.
- Operational data: transfer results and history, cloud locations, saved configuration, preferences and error or troubleshooting information.
- Optional preview or indexing details: metadata or thumbnails needed to show supported files, when relevant features are used or enabled.
3. Why this data is used
REDOWN processes this information to authenticate to your chosen provider, show your authorized storage destinations, complete the file action you requested, display transfer status, support navigation and previews, preserve your selected settings and troubleshoot failures. Access to content or metadata should be limited to what is needed for the action you initiate.
4. Data flows, storage and sharing
When you authorize a cloud account, REDOWN communicates with that provider's authentication and storage APIs to identify the connected account and perform the actions you request. Source websites and cloud providers may receive source URLs, request and transfer metadata, file names and file contents as necessary to complete a requested save. Depending on the integration, some file bytes are fetched by remote infrastructure and some are processed through the browser or device. The term "direct to cloud" applies only to supported remote-transfer paths, not every transfer.
REDOWN may retain OAuth authorization state, configuration, remote paths, file names, originating page URLs, selected source URLs, status and transfer history in Chrome extension storage. Some functions may use Cloudflare Workers or provider-hosted infrastructure to complete authorized transfers. Files intentionally saved to a third-party provider remain stored there under the provider's own terms and retention practices. REDOWN does not provide its own general-purpose cloud storage account.
REDOWN does not sell data obtained from connected cloud accounts or use it for targeted advertising or unrelated profiling. It shares information with a connected provider as needed for user-authorized file operations, and may disclose information if legally required. REDOWN does not transfer your private cloud content into another provider unless you select an operation that calls for such a transfer. Read the applicable providers' privacy notices for their separate processing.
5. Provider-specific permissions and data use
5.1 Google Drive
When a Google Drive connection is enabled, REDOWN uses the Google OAuth scope https://www.googleapis.com/auth/drive.file. This scope allows REDOWN to create files and access the specific Drive files made available to the app, rather than granting general access to every Drive file. REDOWN uses authorized Drive file names, identifiers, metadata and contents as needed to create, confirm, preview or manage files through user-facing features. Authorization and transfer records may be retained locally as described above. Files remain in your Google Drive account until you or Google remove them.
REDOWN's use and transfer of information received through Google APIs is limited to providing or improving the user-facing features that you use, security purposes, complying with applicable law, or other circumstances permitted by the Google API Services User Data Policy. REDOWN does not use Google user data for personalized advertising, sell it to data brokers, or use it to train generalized AI or machine-learning models. A change in the purpose for which Google data is used requires an updated disclosure and, where required, renewed consent. Google account access may be revoked through your Google Account's third-party connections settings.
5.2 Dropbox
When enabled and authorized, the Dropbox connection may use account_info.read, files.metadata.read, files.content.read and files.content.write to identify the selected account, locate files and folders, save new files, check results and support other user-requested file actions. REDOWN processes Dropbox file metadata and contents only for the features you use. The resulting files reside in the Dropbox account you connect. Depending on the file source and Dropbox API capabilities, transfers may occur server-side or be browser-assisted. You can revoke REDOWN's access through your Dropbox account's connected-app controls.
5.3 Microsoft OneDrive
When enabled, the OneDrive connection uses Microsoft identity authorization and Microsoft Graph delegated permissions, including Files.ReadWrite and User.Read where requested and granted. REDOWN uses account identity information to show which OneDrive account you connected, and authorized file contents and metadata to upload, verify, preview and manage files in that account through user-requested actions. Access is limited by the signed-in user's permissions and any organization-level restrictions. You can revoke access through your Microsoft account or your organization's application-access controls.
5.4 Cloudflare R2 and other destinations
When enabled, REDOWN uses Cloudflare authorization and the storage locations you configure to work with your permitted R2 buckets and objects. Other storage integrations, if released, have their own authentication and access rules. Connecting one provider does not automatically grant REDOWN access to another.
6. Access, retention and deletion
REDOWN may keep local preferences, connection details and transfer history until you clear them through available controls, browser storage removal or extension uninstall. Uninstalling REDOWN or disconnecting a cloud account does not automatically mean that files already transferred to your own cloud account, cloud infrastructure, or a provider's own records are deleted. Manage remote files through your provider or an authorized REDOWN action. Revoking a connected provider's access may also require visiting that provider's security settings.
Cloud providers may keep their own logs or records subject to their terms and retention policies. Exact local storage and credential cleanup behavior must be verified on the released extension build and updated here if necessary.
7. Security and responsible access
REDOWN aims to request permissions necessary to perform the features you choose and to avoid exposing credentials in logs, reports or public pages. Any cloud authorization gives REDOWN access according to the permissions granted. You should connect only accounts you control and avoid uploading data that you do not have permission to store. No online or cloud service can promise zero risk.
8. This informational website
This website is a static set of pages. Its source implementation includes no website login form, visitor analytics script, advertising pixel or external tracking script. The hosting service necessarily processes ordinary HTTP requests and may maintain hosting and security logs under its own policies. Following links to GitHub or third-party services takes you to those services, which have their own policies.
9. Children, changes and requests
REDOWN is not specifically directed at children. We may revise this policy as REDOWN's capabilities, storage integrations or regulatory requirements change. The effective date will be updated when the policy materially changes. For privacy requests, see the contact instructions above.