BetterScreenShot Google Drive Data Use

Purpose of Google Drive access

BetterScreenShot uses Google Drive access only when a user chooses to connect a Google account and share or manage a BetterScreenShot result. The integration is not required for capture, editing, recording, OCR, QR recognition, Studio, History, backup, Recovery Center, browser capture, or local automation.

Google user data BetterScreenShot uses

The integration may process:

• Google authorization credentials needed to keep the optional connection active.
• The connected account's display name, email address, and profile image when Google returns them, so the app can show which account is connected.
• Files BetterScreenShot creates in the user's Drive through the integration.
• File identifiers, names, sizes, web links, creation times, and permission information needed to display and manage BetterScreenShot-created files.
• Upload and permission errors returned by Google, including authentication, quota, rate-limit, offline, deleted-file, and Workspace-policy responses.

BetterScreenShot requests the limited https://www.googleapis.com/auth/drive.file scope. This scope is designed for files the app creates or that the user deliberately opens with the app. BetterScreenShot does not request broad permission to browse an unrelated Drive library.

How the data is used

Google user data is used to:

• Complete a user-initiated OAuth connection.
• Create or reuse a private BetterScreenShot folder in the connected Drive.
• Upload the selected rendered result.
• Create a view-only anyone-with-the-link permission when the user chooses the sharing workflow.
• Copy the resulting link to the Windows clipboard.
• Show BetterScreenShot-managed public links.
• Remove one or all managed public-link permissions when the user requests it.
• Show connection, render, upload, cancellation, permission, and recovery status inside the app.

Google user data is not used for advertising, behavioral profiling, sale, credit decisions, or training a general-purpose artificial intelligence model.

What is uploaded

Only an explicitly selected supported result is uploaded:

• An edited screenshot is flattened into a rendered PNG.
• An edited GIF is rendered using the current Studio project and export settings.
• An edited recording is rendered using the current Studio project and export settings.
• An already rendered supported History item may be uploaded directly when no additional render is needed.

BetterScreenShot does not upload the editable .bssproj package, the complete History database, unrelated screenshots, separate source tracks, Recovery Center contents, diagnostic packages, clipboard history, or an arbitrary folder of files as part of this workflow.

File and link permissions

The BetterScreenShot folder is not made public. The selected uploaded file can receive an anyone and reader permission with file discovery disabled. Anyone who obtains that link may be able to view the file. Users should review the result for private information before sharing it.

BetterScreenShot can remove the public-link permission from one managed file or run the v0.5.47 bulk action to make all managed shared links private. Removing the permission does not delete the file from Drive.

Authorization and local storage

The connection uses the system browser, OAuth 2.0 Authorization Code flow with PKCE, state validation, and a temporary loopback callback on 127.0.0.1. BetterScreenShot refuses to keep a connection when secure Windows credential protection is unavailable.

The reusable refresh credential is encrypted using Electron safe storage backed by Windows protection and stored locally with the app's settings. Temporary OAuth state, verifier, and callback values are kept only for the active connection attempt.

Sharing with third parties

BetterScreenShot sends Google authorization and Drive requests directly from the app to Google's OAuth and Drive APIs. The publisher does not receive the uploaded file through a BetterScreenShot cloud server.

Google processes account, authorization, upload, storage, preview, and permission data under Google's terms and privacy policies. A recipient processes the file when the user gives that person a shared link.

Retention, deletion, and disconnecting

• The local authorization remains until the user disconnects, removes app data, revokes access in the Google account, or Google invalidates the credential.
• Uploaded files remain in the user's Google Drive until the user deletes them.
• Public-link permissions remain until the user removes them in BetterScreenShot or Google Drive.
• Disconnecting clears the locally stored connection and attempts token revocation. It does not delete uploaded files and does not automatically remove existing anyone-with-the-link permissions.

When privacy is the goal, first use Make all shared links private, confirm the result, and then disconnect.

User controls

Users can:

• Choose whether to connect Google Drive.
• Choose the individual result to render and upload.
• Cancel queued or active rendering and upload where the workflow permits.
• Copy, open, or review a managed link.
• Make one managed link private.
• Make all managed shared links private with exact-count confirmation.
• Delete uploaded files in Google Drive.
• Disconnect BetterScreenShot.
• Revoke BetterScreenShot access from the Google Account permissions page.

Google API Services User Data Policy

BetterScreenShot's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Questions or requests

Email bss@guneykaragoz.com with the subject BetterScreenShot Google Drive data. Do not send Google passwords, authorization codes, tokens, or confidential files.

Also review the Privacy Policy, Terms of Use, and Google Drive sharing guide.