What runs where
Applane runs in three places. Two of them are yours.
| Place | What runs there | Who owns it |
|---|---|---|
| The employee’s Chrome | The extension: side panel, the agent loop, the sandbox preview, chat history and drafts in browser storage. | Your company (managed Chrome profiles). |
| Your Google | The OAuth client the employee signs in with. The Apps Script projects that are the apps. Vertex AI, which runs Gemini and bills to your project. Drive, Sheets and Docs, which the apps read and write as the viewer. | Your company (Workspace organisation and one GCP project). |
| Applane | The tenant record (your domain, your OAuth client id, your settings), the seat list, the licence signer, the admin console, billing. | Applane (Supabase in Frankfurt, Cloudflare, Stripe). |
What crosses the lines
Section titled “What crosses the lines”The extension calls your Google with the employee’s own OAuth token, minted by your OAuth client. That token reaches the Apps Script API, Vertex AI, Sheets, Drive and Docs, and Applane never sees it.
The extension sends Applane two things: your domain name, to find the tenant, and a Google ID token, to prove who is signing in. The ID token is discarded after the check. Applane sends back the tenant configuration and a signed licence.
The admin console sends Applane what an admin types into it, plus pass or fail results from the setup checker.
Nothing else crosses. No app source, no prompt, no sheet row, no Drive file. The full list is in Data flow.
For AI agents: llms.txt, llms-full.txt, or any page with a .md suffix.