EXTENUP / DRIVE BATCH RECEIPT

Privacy policy

Updated 15 September 2026. Applies to the 0.1.2 release candidate and this file-selection companion. The extension is not yet publicly released.

Drive Batch Receipt, developed by extenup, downloads explicitly selected ordinary Google Drive files individually and keeps a per-file receipt on your device. Contact: extenup@gmail.com.

Purpose and information used

Choosing files prepares a preview. Initial downloads begin only after a separate Start action; retrying an eligible failure also requires your explicit action. At most 100 selected IDs are supported per batch. Folders, shortcuts, Google-native document exports and whole-Drive scanning are not supported; unavailable or unsupported selections remain visible.

The app uses your Google account permission ID to bind a batch to its original account. An account email or display name may be shown in the current page’s memory after authorization. It reads selected file IDs, names, MIME types, expected sizes, modification/version information and download permissions.

The local receipt records batch/account identity, the original selected IDs, metadata and status, attempt IDs, exact Chrome download IDs, timestamps, byte counts, observed local filenames/paths and static diagnostic codes. These names, identifiers and paths may be sensitive.

Where files and authorization go

File contents travel from Google to Chrome’s download system and your device. Application code does not upload those contents to an extenup server. The extension does not request browser history or cookies permissions, scan all Drive files or inspect arbitrary Chrome downloads. Chrome may send cookies as part of its own normal download behavior.

The only requested Google scope is drive.file. Google defines this as permission to read and modify selected or previously authorized files, not read-only access and not access limited to the current batch. This extension uses Drive read requests; it does not edit, delete or share Drive files.

This public HTTPS companion receives a temporary Google access token in browser memory through an origin-, tab- and nonce-bound channel. Google’s official Picker uses it to show files. The companion and its updates are part of the authorization trust boundary. It returns only your selected file IDs to the extension.

The companion’s top-level page address contains no token. The app does not save tokens in page storage or receipt records, send them to this site’s hosting server, or keep a server-side token database. Google’s official Picker uses the token in its Google-hosted embedded frame URL and authenticated requests. Selection, cancellation, navigation or the local lease limit clears the companion session. A public page does not make your token or files public.

The worker may keep a token in memory for your explicit batch. The five-minute local handoff lease is not Google’s token expiry. Worker suspension or loss of authorization pauses future scheduling. Reconnection is explicit, checks the original account and does not start downloads automatically. The app attempts transient token/cache cleanup, but abrupt context loss cannot guarantee asynchronous cleanup. Google’s account grant is separate and lasts until you revoke it.

Retention and your controls

One product receipt is retained in chrome.storage.local without automatic expiry. It is not synced to a developer account. Clear receipt removes it after conservative checks of recorded downloads. Active, pending or uncertain work can prevent clearing.

Clearing the receipt does not delete downloaded files, Chrome download history, historical developer-probe records or Google authorization. Removing the extension clears its extension-local storage. Manage files, browser history and Google account access separately.

Explicit retry checks the original account/file metadata and previous exact Chrome download IDs. Completed, resumed or uncertain transfers are not automatically requeued. These are point-in-time observations, not a guarantee against a later manual Chrome resume.

Other services and uses

There is no advertising, analytics SDK, AI processing, sale of data or paid service in this version. Google and this site’s hosting providers may process ordinary connection/account information under their own policies; this notice does not promise that infrastructure has no access logs.

Drive Batch Receipt’s use of information received from Google APIs complies with the Google API Services User Data Policy and the Chrome Web Store User Data Policy, including their Limited Use requirements. Data is used to provide the requested selection, download and receipt features, not advertising or general-purpose AI training.

Support screenshots or files are voluntary, not automatically sent. Avoid including private files or account details unless necessary for your support request.

Receipt accuracy and changes

Chrome completion and expected size/MIME comparisons are not cryptographic integrity verification. The extension does not hash arbitrary downloaded content. Unknown outcomes and incomplete browser history are shown as needing attention, not verified success.

Material changes to permissions, data destinations, retention or monetization require updated disclosures. Final live QA and Store review remain separate from publication of this notice.