Backstage OpenClaw Drive

This is not the website forms

The public website at backstageinteractive.com has its own Privacy Policy and Terms of Use. Those pages cover the studio site and its contact forms. The forms ask for a note, a website-review request, or a Google Business Profile audit. They do not ask anyone to sign in with Google, and they do not request Google Drive.

This page describes a different thing: a private tool, on a Google account I use for it, with the connector aimed at a Drive folder I named. A person sending the homepage form is not using this tool, and this tool is not how the website stores form messages.

What is in place

These are the practices for this tool.

• OpenClaw runs on a DigitalOcean server. Daily backups are enabled. The documented standard for that daily plan is seven days of rolling retention. That figure comes from DigitalOcean’s documents, not from a fresh audit of this account’s expiry setting. A full-server image is not edited to remove one file. Restoring a backup has not been tested.
• The Google app is in Testing mode, not a production publishing status. A dedicated account authorized Drive with the scope https://www.googleapis.com/auth/drive. That scope can view, create, edit, and delete Drive files the account can access.
• The connector is set to a folder named Backstage Work. That limit is in the connector configuration. Google does not enforce it as the boundary of the scope.
• One test used a 171-byte file. The upload, the download, and a byte-for-byte comparison passed. The file remains in Deliverables and belongs to the dedicated automation account. That is one test, not routine automation.
• When OpenClaw’s AI reads a Drive file, it reads the file contents. The relevant content is sent to Abacus.AI for processing only, to carry out the request. OpenClaw does not store that content anywhere other than Google Drive, apart from the copies described in the retention section, such as temporary transfer copies.

Not current

Routine Drive exchange is not enabled. Chief integration is not enabled. A rule for removing transfer and staging copies is written for if that exchange is turned on. It is a future requirement, not an active workflow, and not a build schedule.

Retention, training, and Limited Use

I adopted a retention and deletion policy on November 7, 2026. Saved work stays until I delete it or set an expiry. Other copies follow manual targets. Automatic cleanup is not fully implemented, and adopting the policy deleted nothing. The schedule is in the privacy policy.

Revoking the Google authorization ends that authorized access. It does not erase copies already downloaded. Deleting the active credential file does not remove credentials that remain in older backups.

OpenClaw does not use Google Drive data to train AI models. We use Abacus.AI under terms that do not permit using this data to train models.

Backstage OpenClaw’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy (opens in a new tab), including the Limited Use requirements.

Privacy policy for this app

The privacy policy for this tool is a separate page: Privacy Policy for Backstage OpenClaw Drive. It is not the website Privacy Policy.

Questions

The public contact path is the form on the studio homepage. In the note, say it is about Backstage OpenClaw Drive. That form is the website’s form. It does not connect to Drive.

The OAuth consent screen already has a support address for the dedicated automation account. That address is not printed here. Whether to publish it is a separate choice. This website’s public contact stays the homepage form.

Website terms

The Terms of Use govern use of the public website. They are not a terms page for this private tool. This site does not add a separate terms page for it. The tool is not a public service.