Where your apps and data live

Your team builds in Applane and uses the finished tools in your company’s Google environment. Applane does not receive your app data, code or prompts.

Solid arrows carry your Google token; it never leaves your Google. The dashed arrow carries a domain name and an ID token one way and a licence the other way.

Place	What lives there
Your browser	The builder, sample-data preview, chat history and drafts.
Your company’s Google environment	The apps and their source in Apps Script and Drive; business data in your Google sources; AI requests through your company’s Vertex AI project.
Applane’s services	Company configuration, admin and builder accounts, licences, billing and service records.

What this means for your team

• People use internal apps with their work accounts and their existing data permissions.
• Your company owns what you build. Published apps can keep running after you cancel Applane, as long as their Google accounts, data and services remain available.
• Clearing the builder’s browser data removes local chat history and drafts. It does not delete published apps from Drive.

For IT and security reviewers

The browser calls Google directly with the user’s Google access token. Applane receives a separate ID token to verify sign-in and issue a licence, then discards that ID token. It also receives account configuration and service requests, including hosting request logs.

Account records are hosted on Supabase in Ireland (eu-west-1). For retention, website analytics and other providers, see data storage and sub-processors. Google processing and cache locations depend on your model configuration; see model cost and caching.