Where is my data stored?

This page separates the data your team works with from the account records Applane needs to run the service.

In your Google

Data	Where
App source and every version	An Apps Script project per app, a Drive file owned by the builder. Google’s own revision history.
Deployed apps	Apps Script web-app deployments on script.google.com.
The data apps read and write	Your Sheets, Docs, Drive, BigQuery, Firestore. Apps read them as the viewer.
Model calls	Vertex AI in your project. Request logging follows your project’s settings; the default logs no content.
Presence (who has an app open)	The coordination sheet, if you set one.
Usage telemetry (Enterprise)	A BigQuery dataset in your own project.
Audit of Google actions	Cloud Audit Logs, the Apps Script dashboard, the Drive audit log, the Admin console.

In the builder’s browser

Chat history, drafts, the cached tenant configuration and the licence token, in the browser’s IndexedDB store for app.applane.dev. No Google token is written to storage; access tokens live in memory for the life of the tab. Clearing the site’s data removes local history, drafts and cached settings. Published apps stay in Drive, and you will need to sign in again.

In Applane

Data	Retention	Personal data?
Company name, verified domains, plan	Life of the contract plus 30 days	No
Tenant configuration: OAuth client id, GCP project id, group and bot addresses, feature flags, allowlists	Same	Group and bot addresses only
Admin emails and roles	Same	Yes
Builder emails, first and last seen, client version	Same; reclaimed seats kept 12 months for invoice disputes	Yes
Seat events and admin actions (the audit log)	12 months	Actor emails
Billing records	7 years (Dutch bookkeeping law)	Billing contact, held by the payment provider
Server logs: request id, path, status, IP address	30 days	IP address

Not stored: Google tokens, app source, prompts, transcripts, sheet or document contents, app viewers, an inventory of your apps. See Data flow.

The marketing website also uses analytics and collects contact-form submissions. See the privacy notice for those records and their retention.

Deletion

• Closing the company deletes every tenant row within 30 days. Billing records stay for the legal period.
• A builder’s rows are deleted on the admin’s request within 30 days.
• A subject access request: the admin exports the builder’s rows (seat, events) from the console; the company handles its employee.

Backups

The database is backed up daily by the hosting provider, in the same EU region.