pedrogalego — Privacy Policy and Terms of Service

Last updated: 2 May 2026

About this page

This page covers the privacy policy and terms of service for pedrogalego, an OAuth 2.0 client registered with Google that authenticates the rclone command-line tool, and rclone-based applications, against Google Drive accounts owned by Pedro Galego.

The app exists for personal, single-user use across the developer's own devices. It is not offered to the public, has no users other than Pedro Galego, and is not part of any commercial product or service.

For any questions, contact pedro@pedrogalego.com.

Privacy Policy

Who runs the app

The OAuth client is registered and operated by Pedro Galego, sole developer and sole user, based in Porto, Portugal.

What data the app accesses

When authenticated against a Google account, the app uses the Google Drive API to access:

  • Files and folders the authenticated account owns or has been shared with, including content stored in Shared Drives the account is a member of
  • File metadata such as names, sizes, modification dates, and MIME types
  • Shared Drive memberships and metadata where applicable

The app requests the https://www.googleapis.com/auth/drive scope (full Drive access). This scope is necessary because the app's purpose is to provide unrestricted, rclone-based filesystem access to the developer's own Drive accounts across multiple devices, including the ability to read and write existing files not created by the app itself.

What the app does with that data

The app passes Drive content through rclone, which:

  • Reads and writes files between Google Drive and the local device on demand
  • Caches file content locally to support virtual filesystem mounts (for example via macFUSE on macOS or comparable FUSE implementations on other platforms)
  • Stores OAuth access and refresh tokens in local configuration files managed by rclone

The app does not transmit Drive content or metadata to any third-party server, analytics provider, or cloud service. There is no backend infrastructure. There are no servers operated by the developer. All processing happens locally on the developer's own devices.

Where data lives

  • OAuth tokens are stored in local rclone configuration files on each device the developer uses, which may include macOS computers, Windows computers, and mobile devices running Android or iOS
  • File content is streamed between Google Drive and the local device on demand, and may be cached locally according to rclone's virtual filesystem cache settings
  • Metadata is held in memory and in local caches during active sessions, and is not persisted beyond rclone's standard cache lifetime

No data accessed by the app is uploaded, transmitted, sold, shared, or otherwise disclosed to any party outside the developer.

Devices and accounts

The app may be authenticated against multiple Google accounts owned by the developer, including personal accounts and Google Workspace administrator accounts under domains the developer controls. It may run concurrently on multiple devices owned by the developer.

Retention

OAuth tokens are retained on local devices until either the developer manually deletes the local rclone configuration, or the developer revokes the app's access through the Google Account permissions interface.

Revocation

Access can be revoked at any time at https://myaccount.google.com/permissions. Revoking access immediately invalidates all tokens issued to the app for that Google account.

Contact

For any questions or concerns about this privacy policy, contact pedro@pedrogalego.com.

Terms of Service

Acceptance and scope

These terms govern the use of the pedrogalego OAuth client. The sole authorised user is the developer, Pedro Galego. The app is not offered to, licensed to, or intended for use by any other person or entity.

Provided as-is

The app is provided "as is", without warranty of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, or non-infringement.

Limitation of liability

In no event shall the developer be liable for any claim, damages, data loss, or other liability arising from use of the app, including issues caused by rclone behaviour, Google API behaviour, network conditions, or device misconfiguration.

Compliance

Use of the app is subject to Google's API Services User Data Policy and to the terms of service of any Google account authenticated against it. The developer is responsible for ensuring such use complies with the policies of any Google Workspace domain whose accounts authenticate the app.

Changes

These terms may be updated to reflect changes in the app's behaviour or scope. The Last updated date at the top of this page reflects the most recent revision.