最終更新： May 2026 · VisionAI Workspace ベータ
あなたのOrbitコンテンツはGoogle Driveに保存され、これが主要な記録となります。VisionAI Workspaceはプラットフォームをご利用中にそこへの読み書きを行い、短期キャッシュ（24時間以内に自動削除）とサービス運営に必要なアカウント・利用データのみを保持します。実際のコンテンツはあなたのDriveに残り、あなたの管理下にあります。
VisionAI Workspaceはあなたがデータを所有できるように設計されています。サービス提供に必要な最小限の情報のみを収集します：
収集したデータはVisionAI Workspaceプラットフォームの運営のみに使用します：
サインイン時、VisionAI Workspaceはあなたに代わってGoogle Sheets、Google Drive（ファイル作成のみ）、Google Docsへのアクセスに関するOAuth許可を要求します。このアクセスは専ら以下のために使用されます：
重要：VisionAI WorkspaceのGoogle Driveアクセスをいつでも取り消すことができますが、その場合プラットフォームはワークスペースにアクセスできなくなり、アクセスが復元されるまで機能しなくなります。Google Drive内のデータはあなたのものであり、影響を受けません。
VisionAI Workspaceは時間とともに拡張するよう設計されたマルチプロバイダーAIアーキテクチャを使用しています。タスクを送信すると、プロンプトコンテンツは以下のAIプロバイダーのいずれかによって一時的に処理され、レスポンスが生成されます — どのプロバイダーが使われるかはリクエストごとに異なります：
VisionAI WorkspaceはGoogle Sheet以外にプロンプトやAI出力のコピーを保持しません。ただし、各サードパーティAIプロバイダーは独自のプライバシーポリシーに従って入力を一時的にログまたは処理する場合があります。データの取り扱いについて懸念がある場合は、各プロバイダーのプライバシーポリシーを確認することをお勧めします。
トランザクションおよびアカウントメール（ウェイトリストの確認、通知、招待など）を送信するため、VisionAI Workspaceはサードパーティのメール配信プロバイダーであるBrevoを使用します。メールを送信する際、お客様のメールアドレスとメッセージ内容は、そのメールを配信する目的でのみBrevoによって処理されます。Brevoはこのデータを自社のプライバシーポリシーに従って処理します。当社はBrevoを広告目的で使用しません。
How it is protected. All traffic between your browser, this platform and Google's APIs runs over HTTPS/TLS. Your Google OAuth tokens are stored in our Supabase Postgres database, encrypted at rest, and are read only by server-side code — they are never sent to your browser and never appear in client-side JavaScript. Account records are protected by row-level security so one account cannot read another's, and the elevated key used for server-side work exists only in server environment variables, never in the app bundle.
The narrowest scopes that work. Drive access is drive.file, which reaches only files this application itself created for you — not the rest of your Drive. Calendar access is calendar.app.created, which reaches only a secondary calendar this application itself created; it cannot see your primary calendar or any event this app did not write. Either can be revoked at any time from your Google Account settings.
Limited Use. VisionAI Workspace's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
We do not train models on your data. We do not use Google user data — raw, aggregated, anonymized or derived — to create, train, or improve any machine learning or artificial intelligence model of our own, and we never sell it or transfer it for advertising.
One open question, stated plainly rather than left out. Content is processed by third-party AI providers to carry out your requests, and those providers set their own terms. Google's Gemini API states that on its free tier, submitted content may be used to improve Google's products and models. We have asked Google directly whether routing content that originated in your Google Sheet through their own Gemini API falls within the Limited Use requirements, and we will update this policy with their answer. If it does not, we will either move that integration to a paid tier — where Google states it does not use submitted content to improve its products — or remove it.
Which AI services see your content, and when. Content is sent to an AI provider only to carry out something you asked for — running a worker on a task, generating an image, summarizing or drafting an email — and only for as long as that request takes. The providers currently used are Groq, Google Gemini, Mistral AI, OpenRouter (a gateway that routes to other providers), Cloudflare Workers AI and Hugging Face. We do not operate self-hosted or offline models; each of these is reached over an API.
Gmail (development only). The Gmail integration is presently limited to the platform owner's own account — a server-side check runs before any request reaches Google, so no other user can trigger it or see its consent screen. It requests gmail.modify (reading messages and most write actions — marking read, archiving — but not permanently deleting), https://mail.google.com/ (Gmail's broadest scope, requested solely because permanent delete has no narrower scope available; everything else this integration does works under gmail.modify alone), and gmail.compose (creating, editing and deleting drafts this app itself created — no code path sends mail beyond that). Message bodies are read live from Google and are not copied to our database. An email you explicitly attach to an orbit or a task is copied into your own Google Sheet — the same file that already stores the rest of your workspace — not to our servers. Two AI-generated artifacts derived from a message you asked to summarize or suggest a task from — the summary and the suggestion — are stored in our database per message so they don't have to be regenerated on every visit; nothing else about a message's content is retained.
認証はGoogle OAuthを通じて処理され、認証インフラプロバイダーであるSupabaseによって管理されます。SupabaseはOAuthトークンを安全に保存してセッションの継続性を維持します。VisionAI WorkspaceはGoogleパスワードや、ワークスペース運営に必要なOAuthトークン以外の認証情報にアクセスできません。セッションはプラットフォームの積極的な使用に紐付けられています。
Cookie： VisionAI Workspaceは必須セッションCookieのみを使用します。これらのCookieは認証とセッション中のログイン維持に必要です。広告Cookie、トラッキングピクセル、サードパーティ分析Cookieは使用しません。必須Cookieはコアプラットフォーム機能を損なうことなく無効にすることはできません。
現在のVisionAI Workspaceベータ版は無料で使用でき、支払い情報は必要ありません。有料Pro機能が導入された際、すべての請求は安全なサードパーティ決済プロセッサーが処理します。VisionAI Workspaceはクレジットカード番号、銀行詳細、支払い認証情報を直接保存することはありません。決済プロセッサーの詳細は有料機能のリリース時に開示されます。
ワークスペースデータはあなた自身のGoogle Driveに存在するため、あなたが保持を選択する限り持続します。アカウント情報（名前、メール、Supabase経由のOAuthトークン）に加えて、プラットフォームの運営に必要な運用データも保持します — 利用状況・信頼性ログ、スケジューリングおよび通知記録、パック購入の支払い履歴、そしてワークスペースコンテンツの短期パフォーマンスキャッシュ（24時間以内に自動削除）です。アカウント削除をリクエストした場合、これらのデータをSupabaseから削除します。あなたのGoogle SheetおよびDrive内のファイルはあなたのものであり、あなた自身が直接削除する必要があります。
あなたには以下の権利があります：
VisionAI Workspaceは成人を対象としており、18歳未満の方を対象としていません。18歳未満の方から個人情報を故意に収集することはありません。18歳未満の方が個人データを提供したと思われる場合は、お問い合わせいただければ削除のための措置を講じます。
VisionAI Workspaceがベータを超えて成長するにつれ、このプライバシーポリシーは新機能、プロバイダー、法的要件を反映するように更新されます。重要な変更についてはメールまたはアプリ内通知でアクティブユーザーに通知します。変更後のプラットフォームの継続使用は更新されたポリシーへの同意を構成します。
Whose Drive shared content is written to. A workspace can have more than one person in it: an owner, and the crew they invite. The owner’s Google Drive is the system of record for the whole workspace. When a crew member uploads a file or an image to a conversation, or an AI worker produces an artifact for one of the workspace’s orbits, that content is written to the owner’s Drive under the owner’s Google account — never to the crew member’s own Drive. One consequence is worth stating plainly rather than leaving to be discovered: because attachments are stored in the owner’s Drive, a workspace owner may be able to see a file that was attached to a conversation they are not a member of, even though the conversation itself is not readable by them.
What we store for messaging. Conversation membership, message text, attachment references, emoji reactions, read state and your per-conversation notification preference are stored in our Supabase Postgres database rather than in Google Drive. Row-level security restricts reads to the members of a conversation. Typing indicators and who is currently viewing a conversation are broadcast live between connected clients and are not stored at all.
Who can see a message. An orbit’s crew room is readable by everyone the owner has granted that orbit to, and its membership is kept in step with that grant automatically. A direct message is readable only by its participants, and can only be started between people who share at least one orbit — with the exception of the workspace owner, who is reachable by anyone in their workspace and may group any of their crew together.
Notifications carry part of the message. When a message needs to reach somebody who is not looking at the app, the notification contains the sender’s name, the orbit’s name or an indication that it is a direct message, and the first 90 characters of the message body. Depending on your settings that is delivered in-app, by email through Brevo, and as a web push notification through your browser or operating system’s push service. If you would rather message content did not leave the app that way, set a conversation to Quiet or Muted using the bell in its header.
Messages are not sent to AI providers. Conversations between people in a workspace are not routed to any AI model. Content reaches an AI provider only when somebody explicitly runs a worker on a task, as described in Section 4.
Deleting, and leaving a workspace. Deleting a message clears its text and its attachment references from our database; the underlying file already written to the workspace owner’s Drive is not removed by that action and has to be deleted from Drive by its owner. If an owner withdraws your access to the last orbit you hold in their workspace — including by archiving that orbit — your membership ends and you lose access to that workspace’s orbits, rooms and message history. Messages you sent and files you uploaded stay with the workspace. Deleting your own VisionAI Workspace account removes your account data from our systems; it does not retract content you contributed to somebody else’s workspace.