Game Tables Privacy Policy

Last Updated: 8 August 2026

Overview

Game Tables is a Unity Editor plugin that imports data from spreadsheets into Unity assets. It is developed and maintained by Oleg Knyazev (https://oleg-knyazev.com). This policy covers only the Game Tables plugin; it does not cover the oleg-knyazev.com website.

What data Game Tables handles

Game Tables handles the two kinds of source data described below and nothing else. In particular, it does not collect telemetry, analytics, or crash reports.

Google Sheets

When you connect Game Tables to Google Sheets, the plugin requests a single OAuth scope:

  • https://www.googleapis.com/auth/spreadsheets.readonly—read-only access to your Google Sheets documents.

Game Tables does not request any Google Drive scope, so it cannot list or browse your files. The spreadsheets.readonly scope itself grants read-only access to Google Sheets; Game Tables uses this permission only to read the spreadsheets you specifically identify to it by URL or ID. It does not request access to Gmail, Contacts, Calendar, or any other Google service, and it cannot modify, create, or delete anything in your Google account.

Project files

Game Tables also imports data from CSV files that are part of your Unity project. It reads only the CSV assets you assign as a source.

How Game Tables accesses and uses your data

Game Tables runs inside the Unity Editor on your local machine. If you authorize access to Google Sheets, your machine communicates directly with Google’s APIs, both when you sign in and when you import. There is no Game Tables server; the plugin’s author never receives your spreadsheet data or your Google credentials.

Data read from your Google Sheets or CSV sources is used solely to populate Unity assets inside your Unity project. It is not used for any other purpose.

What is stored and where

When you sign in, Google’s OAuth library caches an access token and a refresh token on your local machine so that subsequent sessions do not require you to sign in again. These tokens are stored, unencrypted, in a JSON file under Unity’s persistent data path for the current Unity project:

  • macOS: ~/Library/Application Support/<Company>/<Project>/GameTables/AuthTokens/
  • Windows: %USERPROFILE%\AppData\LocalLow\<Company>\<Project>\GameTables\AuthTokens\
  • Linux: ~/.config/unity3d/<Company>/<Project>/GameTables/AuthTokens/

<Company> and <Project> are the Company Name and Product Name defined in your Unity project’s Player Settings. These are ordinary files, protected by your operating system’s file permissions. If you use Game Tables on a shared machine, be aware that anyone who can read that folder can use the cached token to read your spreadsheets. Tokens stay there until you sign out or revoke access.

Apart from this token cache, the only files Game Tables modifies are Unity asset files inside your Unity project.

What is shared

Nothing beyond the requests your machine makes directly to Google’s own APIs. Game Tables does not transmit any data—spreadsheet contents, local file contents, usage information, error reports, or anything else—to the plugin’s author or to any third party other than Google.

How your data is protected

All communication with Google’s APIs uses HTTPS. Sign-in happens through Google’s standard OAuth flow in your browser—this is why a browser window opens when you sign in—so Game Tables never sees or handles your Google password. To receive Google’s response, it briefly runs a listener on 127.0.0.1.

Because the requested scope is read-only, a leaked token cannot be used to change anything in your Google account. And because there is no Game Tables server, there is no central store of user data that could be breached—the only copy of your access and refresh tokens is the local cache described above, protected by your operating system’s file permissions.

Limited Use compliance

Game Tables’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Revoking Google access and deleting cached tokens

You can revoke Game Tables’ access to your Google account and delete the local token cache at any time.

  • From inside Unity: open Preferences → Game Tables, and under the Google Sheets section click:
    • Sign Out to delete the locally cached tokens. Your Google account will still list Game Tables as an authorized app until you also revoke access.
    • Sign Out and Revoke Access to ask Google to revoke the token and then delete the local cache.
  • From Google: visit myaccount.google.com/permissions and remove Game Tables from the list of connected apps.
  • On disk: delete the AuthTokens folder at the path listed above.

Because the plugin’s author holds none of your data, there is nothing further to delete.

Changes to this policy

If Game Tables’ handling of your data changes, this policy will be updated with a new “Last updated” date, and the change will be noted in the plugin’s release notes.

Contact

Questions about this policy or about Game Tables’ handling of your data can be sent to knyazev751@gmail.com or using the contact form on oleg-knyazev.com.