Last updated July 29, 2026
Orbit Drive pools multiple Google Drive accounts you own into a single, unified drive. This policy explains what data we collect when you use Orbit Drive, why we collect it, and how it’s protected — in particular, exactly what access we request from your Google account and what we do (and don’t) do with it.
When you connect a Google account, Orbit Drive requests the drive.filescope only — Google’s narrowest Drive permission. This scope only grants access to files that Orbit Drive itself creates or that you explicitly open with Orbit Drive.
When you use Orbit Drive, we store:
We do not keep a separate copy of your file contents — the files themselves stay in Google Drive. Orbit Drive stores metadata and routes each upload to the right connected account; Google Drive remains the source of truth for the actual file data.
Disconnecting a Google account removes its stored OAuth tokens immediately. You can choose whether disconnecting also deletes the files that account was holding from Google Drive itself, or just from Orbit Drive’s records while leaving the files untouched in Drive. Deleting a file or folder in Orbit Drive removes its metadata from our database; if you choose to also delete it from Google Drive, that deletion happens immediately and cannot be undone.
To request deletion of your entire Orbit Drive account and all associated data, contact us at the email below.
All traffic between your browser and Orbit Drive is encrypted (HTTPS). Google account sessions use OAuth 2.0 with PKCE, and OAuth tokens are encrypted at rest. Orbit Drive sessions use signed, expiring tokens rather than storing your password.
Orbit Drive is not directed at children under 13, and we do not knowingly collect data from them.
If this policy changes, we’ll update the date at the top of this page. Continued use of Orbit Drive after a change means you accept the updated policy.
Questions about this policy, or requests to delete your data, can be sent to support@orbitdrive.space.