Privacy policy
This is the privacy policy for Scoped Drive, linked from the Google sign-in screen and from the home page.
Scoped Drive is a gateway in front of Google Drive. You pick the files and folders an assistant may use. Google’s per-file permission covers those picks and files this app creates. This server then checks every call against the list you keep. That list, and the assistant you connect, are the features of the app.
This deployment is run by the person who set it up. Any verified Google account can sign in, unless that person limited sign-in to a list of addresses. You sign in with your own Google account and tick your own files. The assistant uses that same account. Each person’s files stay separate. The support email shown on the Google sign-in screen is the contact for this app.
Google data we access
Sign-in requests these Google permissions, and no others:
openidandemail, to read the account’s email address and whether Google has verified it. We use that to tell signed-in people apart.https://www.googleapis.com/auth/drive.file, which can see, create, edit, and trash the files and folders you pick in the Google Picker, and files this app creates. It does not grant the rest of your Drive. This server still limits the assistant to items you have allowed. A folder you pick covers that folder on this server. Files that were already inside it may need to be picked too, because Google does not always open every existing file in a picked folder. Files the assistant creates inside an allowed folder are included.
We do not ask for your name, contacts, Gmail, or other Google products.
What an assistant can do depends on the role of the connection you gave it: search, reading text, creating files and folders, editing, renaming, and moving an item to Drive’s trash. This app has no tool to permanently delete a file, to change who a file is shared with, or to move a file between folders.
How we use it
Google user data is used only to provide the features on the home page and in the dashboard:
- Confirm the signed-in account.
- Show the files this app can open so you can allow them, and open the Google Picker so you can choose more.
- Check each assistant request against that list.
- Call Drive for an allowed item and return the result to the assistant you connected.
Those Drive calls use the Google account you signed in with. Allowing an item adds it to this server’s list. Google’s per-file permission and that list are both limits. A sign-in saved before this change may still carry the older broader permission until you sign in again.
File contents are read from Drive only to answer that request. This server does not keep a copy, does not build a database of your files, and does not write contents, file names, or search text to the activity log.
What we store
- The Google refresh token, encrypted at rest, so the server can keep calling Drive after you close the browser. It is stored in Redis (Upstash) or Postgres, whichever this deployment uses.
- The list you ticked: the Drive file and folder ids.
- Access requests, kept for 7 days: a request id, the file id, a short description, the tool name, the connection name, your decision, and the file name only when your sign-in can already see that file.
- An activity log of the last 500 events: time, tool name, allow or deny, and ids. The same lines go to the host’s logs. They do not include file contents.
- A signed session cookie in your browser for about 8 hours. Signing out deletes that cookie. It does not contain your files, and signing out does not delete the stored refresh token or the list you ticked.
- If an assistant connects with OAuth: the name it registered and the tokens for that connection, so you can disconnect it.
- Mailbox text between two assistants, kept for 14 days. The text is encrypted with the same key as the refresh token. One person’s files are not stored with another person’s mailbox.
The app is served over HTTPS. Drive calls and the stored token use that encrypted connection and the encrypted record above.
Who receives it
Google holds your files and handles sign-in. The assistant you connect receives the tool result for items you allowed, including file text when it reads a file. That assistant is a separate service. Sending the result there is the feature you turned on by connecting it and ticking those items. What the assistant does next is covered by its own terms.
The app runs on Vercel. The encrypted token, the list you ticked, requests, activity log, and mailbox text are stored in Upstash Redis or Postgres so the gateway can run. File contents are not stored with them.
Limited use
Scoped Drive’s use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
We do not sell Google user data. We do not transfer it to advertising platforms, data brokers, or information resellers. We do not use it for advertising or to determine credit-worthiness or for lending. We do not use it to create, train, or improve a machine learning or artificial intelligence model.
We do not pass Google user data to anyone other than the assistant you connected, except to keep the service secure, to comply with the law, or as part of a transfer of this deployment after you agree. People do not read your file contents through this server unless you ask, or it is required for security or by law.
Manage or delete your data
- Remove an item in the dashboard to take it off your list. If that item was shared with an older assistant account, the share is removed too.
- Disconnect an assistant on the dashboard overview. That deletes the tokens stored for that connection.
- Remove Scoped Drive at Google Account permissions. Google then stops accepting this app’s sign-in, so the stored refresh token can no longer call Drive.
Access requests expire after 7 days. The activity log keeps only the latest 500 events. Signing out ends the browser session and leaves the stored sign-in and your list in place, so an assistant you already connected keeps the access you granted until you remove it or disconnect the assistant.
Scoped Drive is not directed at children under 13 and does not knowingly collect their information.
See also the terms of service.
Last updated November 18, 2026.