AudioScript.Privacy policy

SUPPORT & CONNECTION HELP

Your own
Google Drive.

Every AudioScript user authorizes their own Google account. You do not need to enter a Google client ID, register a cloud project, or receive the developer's credentials.

Connect from the desktop app

  1. Open Connections & settings in AudioScript.
  2. Under Google Drive, choose Connect with Google.
  3. In Google's window, choose the account you want and review the requested permission.
  4. Return to AudioScript. The app finds or creates AudioAppDB in that account, automatically.
  5. Enable Synchronize projects with Google Drive when ready. To use another computer, install the same AudioScript distribution and connect the same Google account there.

If Google asks you to reconnect

Choose Reconnect / change Google account and authorize the same account. Google may require a new authorization if you revoke access, account or administrator policies change, or a previous authorization expires. Projects remain in local storage and in Drive; signing in is separate from deleting project data.

Authorizations issued while an app is in Google's Testing mode expire after seven days. After the application moves to Production, reconnect once to replace a Testing authorization. Production removes that specific Testing limit; it does not prevent every possible future sign-in request.

Switching accounts

Changing Google accounts pauses synchronization. Review the destination before enabling it again. Local projects remain on the computer, so changing the Google account is not a switch to a separate local project library.

Disconnect or remove access

Choose Disconnect Drive to remove the saved connection from this installation. To revoke Google's permission, remove AudioScript from your Google Account connections. Your files are retained. See the privacy policy for retention and deletion details.

Contact

Use the user support email shown on AudioScript's Google authorization screen, or the developer contact through which you received the application. Include the app version and a short description of the problem. Do not include passwords, API keys, authorization tokens, or private scripts.