Twitter Google Drive and Dropbox integration privacy

What the extension does

Tweet Media Archive lets you paste or right-click X/Twitter, Instagram, Threads, TikTok, Reddit, LinkedIn, Facebook, 4chan, direct media URLs, or public file links and save the resolved media or files to your Dropbox, Google Drive, or local Downloads folder. For Twitter Google Drive integration or Twitter Dropbox integration setup, use the storage guides below; this page explains the permissions and privacy model behind those saves.

Direct answer for Twitter cloud integrations

For Twitter Google Drive integration, the extension saves the actual resolved X/Twitter media file into the Google Drive folder you choose after you connect Drive. For Twitter Dropbox integration, the extension saves the actual resolved X/Twitter media file into the Dropbox folder you choose after you connect Dropbox. The extension uses the URL you paste, the cloud account you authorize, and the destination folder setting only to perform the save you requested.

If you want setup steps instead of privacy details, use the dedicated Twitter Google Drive integration guide or Twitter Dropbox integration guide.

Storage setup guides

If you are looking for setup rather than privacy details, these guides explain how the extension connects pasted social media URLs to cloud storage and keeps actual media files in the folder you choose.

Chrome Web Store privacy summary

The extension handles user data only to provide its media-saving feature. This policy describes what is collected or processed, how that data is handled and stored, and which services it is shared with when you choose to use them.

Website content and resources: media URLs, post URLs, bookmark/profile-media URLs, direct file URLs, right-clicked links or media, visible media candidates, source media files, public files, filenames, file sizes, and saved file links or paths needed to download and save the content you choose.
Web browsing activity: only the specific X/Twitter, Instagram, Threads, TikTok, Reddit, LinkedIn, Facebook, 4chan, direct media, or public file pages you paste, right-click, or ask the extension to process. The extension does not monitor general browsing history.
Authentication information: optional Dropbox, Google Drive, Google broker session, X/Twitter, Instagram, and Threads credentials or cookies needed for the storage or account-session features you explicitly connect.
User activity inside the extension: settings, selected storage provider, supported-website toggles, upload progress, upload history, free-upload count, and payment or subscription status.
Data sharing: data is shared only with Dropbox, Google Drive, the Convex-hosted Google OAuth broker, the supported sites and public file hosts you ask the extension to process, ExtensionPay, Chrome/Google services used by the browser APIs, and Vercel analytics for this website as described below.

Information you provide

Media or file URLs you paste into the extension, including supported X/Twitter, Instagram, Threads, TikTok, Reddit, LinkedIn, Facebook, 4chan, direct media, and direct public file links.
Links, selected text, page URLs, frame URLs, and media URLs you choose through the right-click Download media menu.
Your selected storage provider: Dropbox, Google Drive, or local Downloads.
Folder settings, including Dropbox folder, Google Drive folder, saved folder options, and optional local download folder.
Preferences such as auto-start on paste, overwrite existing files, supported-website toggles, single-post filename prompts, and whether to save local copies.
Optional Dropbox or Google Drive authorization.
Optional custom Dropbox app key or Google OAuth client ID if you choose to use your own OAuth app instead of the included one.
Optional X, Instagram, or Threads sign-in cookies when you choose to connect those accounts for posts that require a signed-in session.
Payment or subscription status provided by ExtensionPay.

How data is used

URLs are used to resolve image, video, audio, or public file downloads from supported services and hosts.
Resolved media files or public files are saved to the Dropbox, Google Drive, or local Downloads folder you select.
For Reddit videos with separate video and audio tracks, the extension may fetch both tracks and merge them locally into an MP4 file before saving.
The right-click Download media feature uses the clicked link, selected text, image, video, audio, page URL, or visible media candidates on the current page to show a save picker and download only the media you choose.
If you click a share button in history or gallery, the extension may fetch the selected saved media file or link and pass it to your browser or operating system share sheet.
The included Dropbox app key is used only to start Dropbox OAuth and upload files to the Dropbox account you authorize.
The included Google OAuth client uses a Convex-hosted OAuth broker to request Google Drive authorization, refresh short-lived Drive access tokens, and upload files to the Google account you authorize.
Optional X, Instagram, or Threads cookies are used only to access media that your signed-in browser session can already view.
Payment status is used to apply the free upload limit and paid unlock.
Chrome storage, identity, downloads, context menus, notifications, offscreen, cookies, scripting, and declarative network request permissions are used only for these extension features.

Right-click saves and page access

The extension has HTTPS page access so the Download media context menu can work on supported social sites, public media CDNs, and direct public file links.
A content script runs on HTTPS pages to remember the element you right-click or interact with, read the current page's media/link candidates when you ask to save, and show an inline save picker when possible.
For X/Twitter video menus, the content script may add a Download media action next to the site's own video-menu options when that supported-site toggle is enabled.
The right-click flow may temporarily store a short-lived local request containing the chosen URL, page URL, source URL, and candidate media list so the picker or popup can complete the save.
The content script does not send general page contents, your browsing history, or unrelated webpage data to the developer.

Dropbox authorization

The extension includes a Dropbox app key so most users can connect without creating their own Dropbox app.
When you connect Dropbox, Dropbox shows its own authorization page. If you approve it, Dropbox returns access credentials to the extension.
Those Dropbox credentials are stored locally in your browser profile and encrypted before storage.
The extension uses those credentials to create the configured Dropbox folder if needed and upload the media files you choose to save.
If you save a custom Dropbox app key, it is encrypted locally. Changing it requires Dropbox reauthorization.

Google Drive OAuth

The extension includes a Google OAuth client ID and uses a Convex-hosted OAuth broker for the default Google Drive connection.
Google Drive access uses the Drive file scope. That lets the extension create and manage files it creates or files you explicitly open/share with it. It does not grant broad read access to every file in your Drive.
When you connect Google Drive with the included client, Google shows its own consent page. If you approve it, Google returns an authorization code to the broker.
The broker exchanges that authorization code with Google, stores the long-lived Google refresh token server-side, and gives the extension a broker session plus short-lived Google Drive access tokens.
The extension stores the broker session and short-lived Drive access tokens locally in your browser profile and encrypts them before storage. It does not store the included-client Google refresh token in extension storage.
The extension and broker use those credentials only to create or find the configured Google Drive folder and upload the media or files you choose to save.
If you save a custom Google OAuth client ID, the extension bypasses the broker. Custom OAuth values and returned Google credentials are stored locally in your browser profile and encrypted before storage. Changing the custom client clears the current Google Drive authorization so you can reconnect with the new client.

Where data is stored

Settings are stored in Chrome sync storage when available, so Chrome may sync them across browser profiles signed into the same Chrome account.
Stored settings include the selected provider, remote folder names, folder options, auto-start preference, overwrite preference, supported-website toggles, single-post filename prompt preference, local-copy preference, and local download folder.
Upload history stores pasted URLs, uploaded filenames, provider, remote file link/path, optional local saved path, file size, and save time. This history is stored locally in the browser profile.
An optional profile/bookmark archive index stores canonical post URLs, source profile or bookmark URLs, source type, source label, and save time locally in the browser profile so future profile or bookmark-folder saves can skip posts already archived.
Active upload progress is stored locally so the popup and history window can show running uploads.
Short-lived right-click save requests are stored locally while the save picker or popup is open and are cleared after use or expiration.
Cloud authorization records such as Dropbox authorization, custom OAuth values, broker sessions, and short-lived access tokens are stored locally in the browser profile.
Dropbox access tokens, custom Google OAuth access or refresh tokens, Google broker sessions, short-lived Google Drive access tokens, custom OAuth values, and optional X/Instagram/Threads cookies are encrypted before local storage.
For included Google OAuth, the long-lived Google refresh token is stored by the Convex-hosted broker, not in extension storage.
The Convex-hosted OAuth broker stores hashed broker session records and Google refresh tokens needed to refresh Drive access after user consent.
A best-effort copy of the free-upload counter may be stored in Chrome sync for the same Chrome profile.

Sharing and third-party services

The extension does not sell user data or share it with advertising networks, data brokers, or unrelated third parties. It sends data to third-party services only when needed for the feature you use.

Dropbox receives the files, filenames, folder paths, and Dropbox authorization data needed to upload media to the Dropbox account you authorize.
Google Drive receives the files, filenames, folder names, and Google authorization data needed to upload media or files to the Google account you authorize.
The Convex-hosted Google OAuth broker receives Google OAuth authorization codes, stores Google refresh tokens server-side, refreshes short-lived Drive access tokens, and revokes broker access when you disconnect Google Drive.
X/Twitter, Instagram, Threads, TikTok, Reddit, LinkedIn, Facebook, 4chan, and public file hosts receive the specific requests needed to resolve or download the URLs you paste, right-click, or the bookmark/profile-media pages you ask the extension to process.
ExtensionPay receives or provides payment and subscription status used to unlock paid functionality. The extension does not store credit card details.
Chrome and Google browser services may process extension settings, sync storage, identity authorization, downloads, offscreen documents, cookies, and Google OAuth consent flows as part of the Chrome APIs used by the extension.
If you choose local Downloads, the extension uses Chrome's downloads permission to save files in your browser Downloads folder instead of sending the file to Dropbox or Google Drive. Chrome's offscreen document feature may be used to prepare local blob downloads for merged Reddit videos.
If you use the share button, your browser or operating system share sheet receives the selected file or link and sends it only to the app or device you choose.
The bundled Mediabunny library runs inside the extension to merge Reddit MP4 audio and video tracks locally. It is not a network service and does not send data to the developer or a third-party server.
This website uses Vercel Web Analytics to understand page visits and conversion clicks. Vercel Web Analytics does not use cookies and stores anonymized analytics data.

Limited Use statement

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. User data is used only to provide or improve Tweet Media Archive's single purpose: saving media you choose to your selected destination.

What is not collected

The extension does not sell your data.
The extension does not use your data for personalized ads, credit-worthiness, lending, or unrelated profiling.
The extension does not run its own analytics service.
The extension does not upload your saved history to a developer-operated server.
The extension does not continuously track all websites you visit.
The extension does not send the pages you browse or right-click targets to the developer as browsing analytics or telemetry.
The extension does not send Reddit video remuxing work to a developer server.
The included Dropbox app key and Google OAuth client ID do not give the developer access to your Dropbox or Google Drive account.
When you use the included Google OAuth client, the extension does not store the long-lived Google refresh token in browser extension state.
Google Drive access uses the narrower Drive file scope, not full Drive read access.

Your controls

You can disconnect Dropbox or Google Drive from the extension setup page. Disconnecting Google Drive clears the local broker session and asks the broker to revoke stored Google access where supported.
You can switch to or away from local Downloads from the extension setup page.
You can turn individual supported websites on or off from the extension setup page.
You can turn off profile/bookmark archive memory and clear the local archive index from the setup page.
You can clear saved X, Instagram, or Threads account access from the setup page.
You can use a custom Google OAuth client ID from Advanced setup if you want Google Drive authorization to bypass the included broker.
You can clear upload history from the history window.
You control each share action from the browser or operating system share sheet before anything is sent to another app or device.
You can remove the extension from Chrome to delete extension-local browser data.

Contact

For privacy questions, DM me on X / Twitter.

Privacy for Twitter Google Drive and Dropbox integrations