Quality Ops privacy policy

Last updated 8 November 2026

Quality Ops is a desktop app for macOS made by Onscale 3D ("we"). This policy explains how Quality Ops handles data, including data from Google accounts the user connects.

Where data lives. Quality Ops stores its data in a database on the user's own computer. The Drive feature never sends Google user data to any server we run. If an organization turns on sync, Quality Ops may send its other app data, such as project plans and documents, through Onscale 3D's servers, but sync never carries Google sign-in tokens, file lists, or Drive file references (account, file ID, name and link), and the Drive feature never sends downloaded files to a server. See "Downloaded files" below for files the user adds to Quality Ops themselves. Apart from files the user adds themselves, Quality Ops does not send Google user data to us or to anyone other than Google, and contacts Google only when the user takes an action in Quality Ops, such as opening a location in the Drive screen, signing out, or deleting an organization that has connected accounts.

Google user data we access. When the user connects a Google account, Quality Ops asks for access to Google Drive (https://www.googleapis.com/auth/drive). It uses that access to:

• read the account's email address and name, to label the account in the app;
• list and search the user's Drive files, Shared with me and shared drives, and show their names, types, owners, dates and sizes;
• open, download, upload, rename, move and trash files, and create folders, only when the user chooses that action.

Files may belong to, and be controlled by, the client organization that owns the Google account. That organization's terms govern how the user may handle them.

How Google user data is used. Google user data is used only to provide these features to the user. File listings are fetched when the user opens a location or searches, shown on screen, and not stored. Opening a file hands its link to the user's web browser, and Quality Ops keeps no copy. Downloaded files are saved only where the user chooses, and stay there until the user deletes them, including after the account is signed out. Uploads send only the files the user picks. Trash moves a file to Google Drive's trash, where it can be restored under Google's trash rules; Quality Ops never permanently deletes files.

Downloaded files. A file the user downloads is saved where the user chooses, outside Quality Ops' control. If the user later adds that file to a project, document or attachment, Quality Ops treats it like any file the user adds, and if the user's organization has turned on sync, it is synced like other content. Quality Ops does not track where a file came from. Quality Ops does not use such files for advertising, profiling or AI training. Synced content is encrypted, and Onscale 3D's administrator tools cannot show it. Onscale 3D does not read synced content except with the user's or organization's consent, to investigate abuse or a security incident, or to meet a legal requirement.

Data we store on the computer. For each connected account, Quality Ops stores the email address, display name, Google permission ID, the organization the user assigned, and the encrypted sign-in token described below. Removing the account deletes these from the app's database. Quality Ops also keeps one backup copy of its database per day on the same computer for 14 days, so these details can remain in those backups for up to 14 days after removal; the sign-in token in a backup has already been revoked with Google.

Sharing. We don't sell, transfer or share Google user data with anyone. It isn't used for advertising, for building user profiles, or for training AI or machine learning models. The Drive feature sends none of it to Onscale 3D: Google user data it handles is visible only to the person using Quality Ops on their own computer, and no copy reaches Onscale 3D's systems through that feature. The one path to our servers is a file the user downloads, saves and later adds to synced content themselves, described under "Downloaded files". We have no processors or third parties that receive Google user data, other than the infrastructure that stores synced content for the user's organization if sync is on.

Storage and protection. Quality Ops keeps a Google sign-in token on the user's computer, encrypted with a key held in the macOS Keychain. Short-lived access tokens are kept only in memory. All communication with Google uses HTTPS. Each request uses only the token of the account the file belongs to, so accounts for different organizations are not mixed.

Retention and deletion. Signing out of an account, or removing it, in Quality Ops asks Google to revoke the app's access and deletes the stored token from the computer. The token is deleted even if Google can't be reached at that moment; in that case, access can be removed at the address below. Access can also be removed at any time at https://myaccount.google.com/permissions. Uninstalling Quality Ops and deleting its data folder, including its backups, removes everything it stored, other than files the user downloaded.

Children. Quality Ops is a business tool and isn't directed to children.

Privacy rights and requests. The Drive feature keeps no Google user data on our systems, so we hold nothing from it to provide, correct or delete beyond what is on the user's own computer. Files the user added to synced content are the user organization's content, and can be removed in Quality Ops or by contacting us. Questions or requests can go to the contact below.

Changes. If we change this policy, we will update the date above and post the new version at this address before the change takes effect. If a change affects how Google user data is used, we will update it before releasing the feature.

Contact. tj@onscale3d.ai