Overdrive Workspace
HelpSupportSecurityPrivacyTerms

Security Overview

Last reviewed: October 14, 2026

Overdrive Workspace is a read-only Google Workspace™ Drive™ exposure audit tool for Workspace administrators, provided by Overdrive Tools. Connecting it means trusting it with visibility across your organization, so this page sets out what that access is — and what it isn't.

This page is a plain-language summary for information only. It does not form part of, or add to, any contract, and it creates no warranty or commitment. Our Terms of Service and Privacy Policy govern, and if anything here differs from them, they prevail.

Read-only by design.

The audit product requests read-only access only. It has no permission to change, delete, move, or share anything in your workspace. It can only look.

Metadata only — never your file contents.

It reads sharing events, app grants, and directory information. It does not open, read, or store the contents of your files.

Your logs stay yours.

Audit events are turned into findings and then discarded — we don't keep a copy of your raw logs. Google's audit log stays the source of truth; Overdrive Tools is a lens over it.

Encrypted and isolated.

Your data is encrypted in transit and at rest, and logically separated from every other workspace. Your access token is stored server-side, encrypted, and is not sent to the browser.

No selling. No ads. No training.

We don't sell your data, show ads, or use your workspace data to train AI models. People on our side look at it only when you ask for support, to investigate a security issue, when the law requires it, or — for organizations that have joined our Design Partner Program — as that program allows.

What Overdrive Tools can access

Overdrive Tools connects through Google's OAuth 2.0 with the scopes it needs for the audit. The audit product requests read-only scopes only — no write access of any kind.

  • Audit reports (read-only) — Google Workspace™ audit log events, specifically Drive™ sharing events and OAuth application authorization events, to detect external exposure and third-party app grants.
  • Directory (read-only) — user names, email addresses, organizational units, 2-step verification status, suspension status, and groups and group memberships, used to tell internal from external principals and surface exposure by suspended or departed users.
  • Verified domains (read-only) — the domains registered to your organization, used to classify sharing recipients as internal or external.
  • Drive™ file metadata (read-only, paid plans) — file names, owners, and sharing permissions, read through domain-wide delegation that your administrator grants. This is how Overdrive Tools sees the current sharing on every file. Never file contents.

Not accessed: file contents, Gmail™ messages, calendar events, contacts, or anything not listed above. The audit product does not request any write scope. If we ever offer optional remediation, it would be a separate, opt-in feature that requests its own scope with a clear explanation.

What we store — and what we don't

Overdrive Tools follows a "scan broadly, store narrowly" principle: we keep only the derived findings needed to show you exposure, never raw audit logs or file contents.

We store

  • Workspace record — organization name, verified domains, connection status.
  • Scan summaries — time, scope, and totals for each audit scan.
  • Risky-file findings — file ID, title, sharing type, external principals, and risk score for files with external or public exposure.
  • External principals and per-user risk aggregates.
  • Daily user counts, used for billing.
  • AI classification cache — a one-way hash of a file name with its category. Never the name itself.
  • An encrypted OAuth refresh token — server-side only, not sent to the browser.

We do not store

  • Raw Google audit log events — processed transiently, then discarded.
  • Any file contents.
  • Private, internal-only files with no external exposure.
  • Full directory snapshots — only what's needed to classify sharing recipients.

Encryption and token handling

Data is encrypted in transit (TLS) and at rest. Your OAuth refresh token — the credential Overdrive Tools uses to call Google APIs on your behalf — is encrypted at rest, stored server-side only, and not sent to the browser. We apply technical and organizational measures including access controls and secrets management.

No system or transmission over the internet is completely secure, and we can't guarantee absolute security. This page describes the measures we take, not a guarantee against all risk.

Tenant isolation

Each connected workspace's data is logically separated, and our access controls are designed to prevent any workspace from reading another workspace's findings, principals, or tokens.

AI file-name classification

To recognize sensitive files, such as login sheets and invoices, Overdrive Tools can classify an exposed file from its name. When this is on, the name of an exposed file — and nothing else — is sent through OpenRouter to TypeSafe's model. Requests are sent only under OpenRouter's zero-data-retention setting, and TypeSafe states it does not train models on inputs. No file contents, owners, email addresses, or file IDs are sent. Classifications are automated and may be inaccurate. Workspace owners can turn this off in Settings.

Infrastructure and sub-processors

Derived data is stored in the EU (Frankfurt, Germany). We use the following sub-processors, each bound by written data-protection terms. The authoritative, maintained list is in the Privacy Policy.

Sub-processorPurposeLocation
Supabase, Inc.Database (PostgreSQL), auth, storageEU Central — Frankfurt, Germany
Vercel, Inc.Application hosting, serverless functionsUnited States (edge globally)
Google LLCGoogle APIs (data source); Google Cloud Platform™ for OAuthUnited States
Lemon Squeezy (LemonSqueezy, LLC)Payment processing and subscription billing (Merchant of Record)United States
OpenRouter, Inc.Routes AI file-name classification requests to the model provider. Receives the names of exposed files only — never contents, owners, email addresses or file IDs.United States
TypeSafe AI, Inc.AI model (Jev) that classifies file names, reached through OpenRouter. Receives file names only, under OpenRouter's zero-data-retention setting.United States (San Francisco, CA)
Google LLCWebsite and product analytics (Google Analytics): the same events with the same limits as PostHog — route-pattern page addresses only, and no data read from Google Workspace APIs.United States
PostHog Inc.Product analytics: page views and session recordings on our public website pages only, plus a few usage events from the app (sign-up, workspace connected, scan completed, purchase) with the user ID and workspace domain, and no page addresses. It receives no data read from Google Workspace APIs.United States
Postmark (ActiveCampaign, LLC)Delivery of the app's emails: account, scan, alert and billing emails.United States

Retention and deletion

  • Free scan: results are kept for 30 days. After that, unless you subscribe, we delete them, revoke and delete the access token, and stop accessing your workspace.
  • Paid plan: findings are kept while your subscription is active. When a paid plan ends, scanning stops and your data stays viewable for 90 days, as of the last paid scan. After that it's deleted, unless you reactivate first. We email your administrators about 14 days before.
  • When you disconnect or delete your account: your OAuth refresh token is promptly revoked and deleted, and all derived findings, aggregates, and workspace records are deleted within 30 days. Only anonymized aggregate statistics that cannot be tied back to your organization may be retained. If your administrator granted domain-wide delegation, remove it in the Google Admin console™ — we can't remove it for you.

You can request deletion at any time at info@overdrive.tools. The Privacy Policy has the details.

Incident response

If we become aware of a personal data breach affecting your workspace's data, we notify your administrators by email without undue delay.

Data residency and GDPR

Derived data is stored in the EU (Frankfurt). Overdrive Tools is headquartered in Israel, which the European Commission, the UK, and Switzerland recognize as providing an adequate level of data protection. Transfers to US sub-processors rely on the EU–US Data Privacy Framework where the sub-processor is certified, or on standard contractual clauses or another lawful mechanism. We can provide a Data Processing Agreement on request. Full detail, including data-subject rights, is in the Privacy Policy.

Reporting a vulnerability

We welcome responsible disclosure. If you believe you've found a security issue or a potential incident, email info@overdrive.tools with the details and steps to reproduce. Please:

  • test only against a workspace you administer, and never access, modify, or retain other customers' data;
  • avoid anything that degrades the Service for others, such as denial-of-service, spam, or social engineering;
  • give us a reasonable window to investigate and remediate before any public disclosure.

We don't currently run a paid bug bounty, and reporting an issue does not entitle you to a reward. Nothing on this page authorizes testing beyond these limits.

HomeHelpSupportSecurityPrivacy PolicyTerms of ServiceRefund PolicyContact

Google Workspace, Google Drive, Gmail, Google Admin, Google Cloud Platform, and Google Workspace Marketplace are trademarks of Google LLC. Overdrive Tools is not affiliated with or endorsed by Google.

© 2026 Overdrive Tools