Basic account identity
openid · email · profileProvides your Google account identifier, name, email address, and profile image so SendToDrive can create your account, sign you in, and show which Google account is connected.
Transparent Google access
Google OAuth permissions, explained
SendToDrive uses Google OAuth to sign you in and connect the Google Drive folder you choose. Here is exactly what the main connection can—and cannot—do.
Google Drive access only
The short version
You never give SendToDrive your Google password. Google displays the consent screen and issues limited tokens after you approve it. SendToDrive requests basic account information plus the drive.file scope—not the broad scope that can access every file in your Drive.
Permissions requested
These are the permissions used by the main SendToDrive sign-in and Google Drive connection.
Per-file Google Drive access
https://www.googleapis.com/auth/drive.fileLets SendToDrive create Drive files and work with files or folders you open or share with the app through Google Picker. Google classifies this as per-file access, not full-Drive access.
Offline access
access_type=offlineAllows Google to issue a refresh token so your upload pages can keep delivering files when you do not have SendToDrive open. Refreshing a token does not expand the permission you already granted.
What the connection does—and does not—allow
SendToDrive can
- Show Google Picker and validate the Drive folder you choose.
- Create uploaded files and the subfolders required by your upload-page rules.
- Read limited folder, file, and storage-quota metadata needed to operate the workflow.
- Rename or move app-related files to trash when required to finish or clean up an upload.
The main connection does not
- Ask for or store your Google password.
- Request the broad drive, drive.readonly, or drive.metadata scopes.
- Browse or download unrelated files elsewhere in your Google Drive.
- Give uploaders permission to view your Drive or Google account.
How the connection is used
The permission follows a narrow, user-directed workflow.
- 01
You approve access
Google shows the account and Drive permissions before you approve the connection.
- 02
You choose a folder
You select or share the destination folder through Google Picker.
- 03
You share an upload page
Uploaders use your SendToDrive link without receiving access to your Google account.
- 04
Files go to your Drive
File contents upload from the uploader's browser to the selected Google Drive folder.
Connection data SendToDrive keeps
SendToDrive stores only the connection and operational data needed to provide and secure the service.
- Basic account profile and Google account identifier.
- OAuth access token, refresh token, expiry, and granted scope.
- The identifier and name of the Drive folder you select.
- Limited file metadata, upload status, and technical logs.
Uploaded file contents are not stored as file copies on SendToDrive servers.
You stay in control
You can review or remove SendToDrive's access at any time from your Google Account third-party connections page.
- 1Open your Google Account third-party connections.
- 2Select SendToDrive and review the access shown by Google.
- 3Choose Remove access if you no longer want the connection.
Removing access prevents new Google Drive actions and may stop your upload pages until you reconnect. It does not delete files already stored in your Drive, and it does not by itself delete your SendToDrive account or operational records.
Official references
Google's own documentation describes the drive.file scope, offline access, and user controls referenced on this page.
Connect Google Drive with clear boundaries
Create an upload page using the folder you choose, without sharing your Drive with uploaders.
Google Drive is a trademark of Google LLC. SendToDrive is an independent service and is not affiliated with or endorsed by Google.