資料處理原則

SquirrelDeck 用於使用者自訂的網頁自動化、提醒、介面與媒體工作。Google Drive 同步和 GitHub 雲端擷取都是選用功能，只會在使用者主動連接帳號並啟用後執行。

本機資料

腳本程式碼、腳本名稱、網址規則、跨網域允許清單、常駐／獨立 UI、鬧鐘、排程、媒體任務、執行記錄與介面設定，預設儲存在瀏覽器擴充功能的本機儲存空間。背景高畫質、前景視窗與桌面截圖／錄影模式在本機 Chrome 處理。

網頁內容與媒體檔案

只有在使用者主動開始截圖／錄影，或明確建立並啟用媒體排程後，SquirrelDeck 才會處理指定頁面或桌面內容。畫面可能包含網址、網站內容、帳號資訊或個人通訊。

本機模式產生的 PNG、JPEG 或 WebM 會由 Chrome 下載或依使用者選擇存入本機截圖剪貼簿。Google Drive 設定同步不包含截圖與錄影媒體檔案。

GitHub 選用雲端截圖與錄影

使用者選擇 GitHub 雲端模式並完成授權後，SquirrelDeck 會把目標網址、預定執行時間與擷取設定直接傳送到使用者自己的私人 GitHub Repository 與 GitHub Actions。SquirrelDeck 不提供共用 Repository、共用 Runner 或共用 Actions 額度；運算時間與 Artifact 暫存空間計入 Repository 所有者自己的 GitHub 帳號。

GitHub Actions 會在全新的 Playwright／Chromium 瀏覽器中開啟目標網址，不會帶入本機 Chrome Cookie、擴充功能或登入工作階段。結果短期保存為使用者帳號中的私人 GitHub Actions Artifact，Workflow 設定的保留期為一天；SquirrelDeck 成功下載或匯入後會請求刪除該 Artifact。媒體不經過 Cloudflare，也不會傳送到 SquirrelDeck 開發者伺服器。

GitHub OAuth 憑證保管

GitHub 登入使用官方 Device Flow，SquirrelDeck 不要求使用者建立或貼上 Personal Access Token。取得的 GitHub OAuth access token 會先以 AES-GCM 加密；加密後的 ciphertext／IV 與非機密 metadata 儲存在使用者自己的 Google Drive 隱藏 appDataFolder，解密金鑰只保存在目前 Chrome 裝置的擴充功能本機儲存空間。解密後的 token 只在需要 GitHub API 呼叫時保留於瀏覽器工作階段。

若移除擴充功能、清除擴充功能本機資料或更換裝置，本機解密金鑰可能遺失，此時使用者需要重新連接 GitHub。解除 GitHub 雲端連線時，SquirrelDeck 會嘗試刪除 Drive 中的加密授權資料並清除本機金鑰；使用者 GitHub 帳號中的私人 Repository 不會自動刪除。

Google Drive 選用同步與帳號選擇

只有在使用者明確同意並連結 Google 帳號後，SquirrelDeck 才會使用 Google Drive。一般設定同步可選擇隱藏 appDataFolder 或由 SquirrelDeck 建立的可見 SquirrelDeck Backup 資料夾，內容可包含腳本、網址規則、排程、媒體任務、鬧鐘、常駐／獨立 UI 與介面參數。

連線時，SquirrelDeck 使用 Firebase Authentication 僅開啟 Google 官方帳號選擇流程並取得基礎帳號識別資料（Google 帳號識別碼、電子郵件地址與顯示名稱）。首次透過 Google 聯合登入時，Firebase Authentication 可能在 SquirrelDeck 的 Firebase 專案中建立並保留對應的 Authentication 使用者記錄；SquirrelDeck 不會把腳本、設定或 Google Drive 備份內容傳送或儲存在 Firebase。完成帳號選擇後會立即結束 Firebase 登入工作階段；使用者選定帳號後的實際 Drive 存取仍由 Chrome Identity 與 Google Drive API 直接處理。

為跨裝置辨識備份位置，SquirrelDeck 可能在隱藏應用資料空間保存小型位置 marker。GitHub 雲端模式另外使用同一隱藏應用資料空間保存「加密後」的 GitHub OAuth 憑證資料。截圖與錄影媒體檔案不會上傳到 Google Drive。

腳本參數與本機憑證保險庫

使用者可將網址、數字、開關與選單等一般腳本設定整理為可編輯參數。帳號、密碼、Secret、Token 與 API Key 等驗證資料不會保存為一般腳本參數；只有在使用者閱讀說明並明確同意後，才會建立本機憑證保險庫。

憑證保險庫使用 PBKDF2-SHA-256（250,000 iterations）從使用者主密碼衍生 AES-256-GCM 金鑰後，加密保存於擴充功能本機儲存空間。主密碼不會被儲存，解鎖金鑰只存在於 Chrome 擴充功能工作階段，瀏覽器或擴充功能重新啟動後會重新鎖定。

只有使用者明確綁定的 USER_SCRIPT 能在執行時取得對應憑證；MAIN 網頁環境不能讀取憑證 API。本機憑證保險庫不會同步到 Google Drive、GitHub 或 SquirrelDeck 伺服器。使用者可隨時鎖定或清除保險庫；若忘記主密碼，SquirrelDeck 無法復原其中資料。

使用者腳本與第三方服務

使用者腳本由使用者自行建立或匯入，可能讀取或修改獲授權網頁，並在使用者明確允許時向第三方 API 發出請求。GitHub 雲端模式只在使用者主動啟用時直接與 GitHub 通訊。第三方網站及 API 的資料處理由其各自條款與隱私政策規範；請勿執行來源不明的腳本。

腳本宣告的 @require、@resource、@updateURL 與 @downloadURL 會從腳本作者指定的網址下載並保存在本機快取；有完整性雜湊時會先驗證。遠端 JavaScript 只會透過 Chrome userScripts API 作為使用者提供的腳本執行，不會更新擴充功能本身。GM Cookie 與系統通知只在腳本明確宣告對應 @grant、Chrome 已授予選用權限，且網址規則允許時使用。

權限用途

• storage：保存本機腳本、任務、介面設定及 GitHub 憑證保管庫的本機 AES 金鑰。
• userScripts、alarms：執行使用者提供的腳本、提醒與排程。
• activeTab、tabs、scripting、webNavigation：處理使用者授權分頁、等待條件及自動化／媒體流程。
• downloads、clipboardWrite：儲存使用者要求的輸出，或在使用者明確選擇時將截圖、圖片、文字等內容寫入系統剪貼簿。
• offscreen、tabCapture、desktopCapture、system.display、debugger：建立、處理與儲存使用者要求的截圖／錄影。
• 選用 identity 與 Google Drive API：僅在 Google Drive 同步或 GitHub 加密憑證保管需要 Google OAuth 時使用。
• 選用 cookies、notifications 與網站存取權限：只有使用者設定的腳本、提醒、跨網域請求或特定登入流程需要時才會請求／使用。

資料分享與出售

SquirrelDeck 不出售使用者資料，也不會用於廣告、信用評估或與核心功能無關的目的。資料只會依使用者的明確設定傳送到其選擇的服務，例如 Google Drive、GitHub，或使用者腳本指定的第三方 API。

資料保存與刪除

本機資料由使用者透過 SquirrelDeck 或 Chrome 擴充功能管理機制控制。Google Drive 資料由使用者自己的 Google 帳號控制。GitHub 雲端結果是私人 Actions Artifact，設定最長保留一天並在成功取回後請求刪除。解除 GitHub 連線不會自動刪除使用者帳號中的私人 Repository。

聯絡方式

如對本隱私權政策或 SquirrelDeck 的資料處理方式有疑問，請使用 SquirrelDeck Chrome Web Store 商品頁所列的開發者聯絡管道。

Data processing principles

SquirrelDeck supports user-configured web automation, reminders, interfaces, and media tasks. Google Drive synchronization and GitHub cloud capture are optional and run only after the user explicitly connects the relevant account and enables the feature.

Local data

Script code, names, URL rules, cross-domain allowlists, resident/independent UI definitions, reminders, schedules, media tasks, execution records, and interface settings are stored locally by default. Background high-quality, foreground-window, and desktop screenshot/recording modes are processed in local Chrome.

Web content and media files

SquirrelDeck processes a specified page or desktop content only after the user starts a screenshot/recording action or explicitly enables a media schedule. Captured content may contain URLs, website content, account information, or personal communications.

Local-mode PNG, JPEG, or WebM output is downloaded through Chrome or stored in the local screenshot clipboard as selected by the user. Screenshot and recording media files are not included in Google Drive settings synchronization.

Optional GitHub cloud screenshots and recordings

After the user selects GitHub cloud mode and completes authorization, SquirrelDeck sends the target URL, scheduled execution time, and capture settings directly to the user's own private GitHub repository and GitHub Actions. SquirrelDeck provides no shared repository, runner, or Actions quota; compute time and artifact storage count against the repository owner's own GitHub account.

GitHub Actions opens the target URL in a fresh Playwright/Chromium browser and does not inherit local Chrome cookies, extensions, or signed-in sessions. Results are stored briefly as private GitHub Actions artifacts in the user's account with workflow retention set to one day. After successful download/import, SquirrelDeck requests deletion of the artifact. Media does not pass through Cloudflare or SquirrelDeck developer servers.

GitHub OAuth credential storage

GitHub sign-in uses the official Device Flow; SquirrelDeck does not ask the user to create or paste a Personal Access Token. The GitHub OAuth access token is encrypted with AES-GCM. Ciphertext/IV and non-secret metadata are stored in the user's own hidden Google Drive appDataFolder, while the decryption key remains only in extension-local storage on the current Chrome device. The decrypted token is kept only for the browser session when GitHub API calls are required.

If the extension is removed, local extension data is cleared, or the user moves to another device, the local decryption key may be lost and GitHub must be reconnected. Disconnecting GitHub cloud mode attempts to delete the encrypted authorization data from Drive and clears the local key; the private repository in the user's GitHub account is not deleted automatically.

Optional Google Drive synchronization and account selection

Google Drive is used only after the user explicitly consents and connects a Google account. General settings sync can use the hidden appDataFolder or a visible SquirrelDeck Backup folder created by SquirrelDeck. Synced settings can include scripts, URL rules, schedules, media tasks, reminders, resident/independent UI definitions, and interface settings.

During connection, SquirrelDeck uses Firebase Authentication only to open Google's official account chooser and obtain basic account identity data (Google account identifier, email address, and display name). The first federated Google sign-in may create and retain a corresponding Authentication user record in SquirrelDeck's Firebase project; SquirrelDeck does not send or store scripts, settings, or Google Drive backup content in Firebase. The Firebase sign-in session ends immediately after account selection. Actual Drive access for the selected account remains direct through Chrome Identity and the Google Drive API.

SquirrelDeck may store a small backup-location marker in hidden app data for cross-device backup-location discovery. GitHub cloud mode also uses the hidden app-data space for encrypted GitHub OAuth credential data. Screenshot and recording media files are not uploaded to Google Drive.

Script parameters and local credential vault

Users can organize ordinary script settings such as URLs, numbers, switches, and menu choices as editable parameters. Authentication data such as usernames, passwords, secrets, tokens, and API keys is not stored as ordinary script parameters. A local credential vault is created only after the user reads the disclosure and explicitly agrees.

The credential vault uses PBKDF2-SHA-256 (250,000 iterations) to derive an AES-256-GCM key from the user's master password and stores only encrypted credential data in extension-local storage. The master password is not stored, and the unlocked key exists only for the Chrome extension session; the vault locks again after the browser or extension restarts.

Only USER_SCRIPT entries explicitly bound by the user can obtain the corresponding credential at runtime; the MAIN webpage environment cannot read the credential API. The local credential vault is not synchronized to Google Drive, GitHub, or SquirrelDeck servers. Users can lock or clear the vault at any time; SquirrelDeck cannot recover vault data if the master password is forgotten.

User scripts and third-party services

User scripts are created or imported by the user and may read or modify authorized webpages or contact third-party APIs explicitly allowed by the user. GitHub cloud mode communicates directly with GitHub only when enabled by the user. Third-party sites and APIs are governed by their own terms and privacy policies; users should not run scripts from untrusted sources.

Resources declared with @require, @resource, @updateURL, and @downloadURL are downloaded from URLs selected by the script author and stored in a local cache; integrity hashes are verified when provided. Remote JavaScript runs only through Chrome's userScripts API as user-provided script code and cannot update the extension itself. GM Cookie and system notifications are available only when the script declares the corresponding @grant, Chrome has granted the optional permission, and URL rules allow the operation.

Permissions

• storage: stores local scripts, tasks, interface settings, and the local AES key for the GitHub credential vault.
• userScripts and alarms: run user-provided scripts, reminders, and schedules.
• activeTab, tabs, scripting, and webNavigation: operate on user-authorized tabs and support wait conditions and automation/media flows.
• downloads and clipboardWrite: save user-requested output or write screenshots, images, text, and other workflow output to the system clipboard only when the user explicitly chooses that action.
• offscreen, tabCapture, desktopCapture, system.display, and debugger: create, process, and save user-requested screenshots/recordings.
• Optional identity and Google Drive APIs: used only when Google OAuth is needed for Drive sync or the encrypted GitHub credential vault.
• Optional cookies, notifications, and website access: requested/used only when needed for user-configured scripts, reminders, cross-origin requests, or specific sign-in flows.

Sharing and sale of data

SquirrelDeck does not sell user data and does not use it for advertising, credit assessment, or unrelated purposes. Data is sent only according to the user's explicit configuration, such as to Google Drive, GitHub, or a third-party API selected by a user script.

Retention and deletion

Local data is controlled through SquirrelDeck or Chrome extension management. Google Drive data is controlled by the user's Google account. GitHub cloud results are private Actions artifacts configured for at most one day of retention and are requested for deletion after successful retrieval. Disconnecting GitHub does not automatically delete the private repository in the user's account.

Contact

For questions about this privacy policy or SquirrelDeck's data handling, use the developer contact channel listed on the SquirrelDeck Chrome Web Store listing.