Drive Change Owner

Drive Change Owner is a Google Drive add-on that lets you take ownership of Google Drive files and folders from another user — all from inside Drive, with no admin privileges and no command line.

Think of it as a self-serve ownership migration tool. If a colleague left your domain and their files are still under their name, you migrated accounts and inherited a folder tree, or you simply need to consolidate ownership under your own account — this add-on handles the entire tree, including subfolders, shared files, and cross-domain edge cases.

It runs as a sidebar inside Google Drive with autocomplete for the source user, selection of one or more folders or files, and progress cards that show status and support resume across Google’s execution time limits.


How It Works

1. Select in Drive

Open Extensions > Drive Change Owner in Google Drive. Select one or more folders or files, then choose the source user whose ownership you want to take over.

2. Traverse and classify

The add-on recursively visits every descendant of the selected folders:

  • Same domain: files and folders owned by the source user are transferred to you using the Drive Permissions API (transferOwnership), keeping all permissions and sharing settings intact.
  • Cross-domain or blocked transfer: items are copied in place under your ownership, their content is moved into the new copy, and the original is deleted — so the end result looks identical.
  • Not source-owned items: are left untouched inside the folder tree.

3. Resume across time limits

Google Apps Script has a ~6-minute execution limit. The add-on automatically saves progress and schedules a time-based trigger to continue where it left off, so large folder trees complete in one operation.

4. Progress and completion

The card UI shows which folder is currently being processed, the number of files found, copied, and deleted. When the run completes, a Reset button clears the state and the add-on is ready for the next task.


How We Cannot Access Your Data

This is the most important guarantee of the product, and it is baked into the architecture.

It runs inside Google, on your OAuth

The add-on is Google Apps Script — it executes entirely inside Google’s own runtime, in your own authenticated session. Every operation uses the OAuth scopes you granted when you installed the add-on (https://www.googleapis.com/auth/drive). No data ever passes through our servers. There is no proxy, no relay, no external API call that transfers your file contents or metadata to us.

The code is open source

The entire add-on source is published at github.com/subtext-mz/drive-change-owner. Anyone — including your security team — can read, audit, and verify exactly what the add-on does with OAuth tokens, file metadata, and any error output.

No user data stored by us

The add-on uses Google Apps Script User Properties for temporary resume state (which folder it was on, how many files were processed). These properties stay in your Google account’s encrypted property store. We do not collect, store, or transfer:

  • File names, contents, or metadata
  • Email addresses (beyond what you type into the source-user field, which stays in the card session state)
  • Folder structures or sharing settings

Cloud Run backend (auditable, bearer-protected)

The product includes a Cloud Run backend for job orchestration. This backend:

  • Is never called with your Google session.
  • Uses a publisher-managed bearer token stored in Google Secret Manager and an Apps Script Script Property — never exposed to end users.
  • Serves only coordination endpoints (/health, /api/v1/jobs/*) — it has no Drive API access using end-user credentials.
  • Runs on Cloud Run with Google-managed encryption in transit and at rest.
  • All external network calls go through Google’s own Drive API and the Cloud Run backend.

Compliance Alignment

SOC 2 + ISO 27001

The add-on runs as Google Apps Script inside Google Workspace, which is SOC 2 Type II and ISO 27001 certified. The Apps Script execution environment inherits these certifications. No customer data touches our infrastructure.

The Cloud Run backend runs on Google Cloud Platform, which holds SOC 1/2/3, ISO 27001, and PCI DSS certifications. Infrastructure-as-code deployment (Cloud Build, Secret Manager) provides an auditable, repeatable deploy pipeline.

GDPR

We process no personal data on our systems:

  • The add-on executes inside the user’s own Google Workspace environment — Google is the data processor, and you (the domain administrator) have a data processing agreement (DPA) with Google.
  • We do not store, log, or transfer any user email, file content, folder metadata, or IP addresses.
  • The open-source code is verifiable; there are no tracking pixels, analytics calls, or telemetry.

The backend handles only job-coordination metadata (a jobId UUID, a Firestore document describing job state) — no Drive file contents, no user emails beyond what is recorded in a Firestore job document (which you control access to via standard GCP IAM).

C5 (German cloud compliance)

Google Workspace and Google Cloud Platform are C5-attested (Type 2). Because the add-on runs entirely within Google’s infrastructure and our backend (when used) runs on Google Cloud Platform, the attestation scope covers the full execution path.

CE+ (Common Europe+)

Google’s infrastructure meets the CE+ certification requirements for cloud services in the European Economic Area. Data stays within Google’s processing boundary; no additional data exfiltration risk is introduced by the add-on.

Data processing agreement (DPA)

Since we do not process your data on our systems, no separate DPA is needed for the add-on itself. For the backend, data stays in the GCP project you (or your publisher) control — standard GCP DPA terms apply between Google and the project owner.


Summary

ConcernHow we address it
Can you see my files?No. The add-on runs in your Google session. No data reaches us.
Can you see my folder structure?No. Only your own OAuth session sees folder metadata.
Do you log emails or activity?No telemetry, no analytics, no logging of user data.
Is the code auditable?Yes. Fully open source at github.com/subtext-mz/drive-change-owner.
What compliance certs apply?The add-on inherits Google Workspace’s SOC 2, ISO 27001, GDPR, and C5 attestations.
What about the backend?Auditable, bearer-protected, runs in your GCP project (or ours, depending on deployment).

Drive Change Owner. Privacy is architectural, not a promise.