Google user data
Domicile can import past and upcoming trips from Google Calendar, so you do not have to type them in. It does not access Gmail. This page sets out exactly what that involves.
Draft for legal review · version 2026-10-18
Limited Use
Domicile's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What we ask for
| Permission | Why |
|---|---|
Sign-in: your name, email address and Google account ID (openid, email, profile) | To create and sign in to your Domicile account if you choose Sign in with Google |
Read-only Google Calendar (calendar.readonly) | To find trips you have put in your calendar |
Calendar access is asked for only when you choose to import. Domicile never adds, changes or deletes your events. Domicile does not ask for Gmail access: booking emails reach Domicile only if you forward them to your private Domicile address (see Forwarded emails). Gmail access granted to an earlier version of Domicile is revoked by our server.
How it is used
Within the period you choose (three months to ten years), Domicile reads your calendar events and extracts the travel details of events that look like flights. You review every suggestion before it becomes part of your record. The data is used only to provide this import to you. It is not used for advertising, not used to build or train AI or machine-learning models, not sold, and not used to decide credit or for any purpose unrelated to the import.
On Android, events are read on your phone with a short-lived permission and never pass through our servers. On iPhone and the web, our server reads them on your behalf using a permission you grant, stored encrypted.
What is stored
- The travel details found: the flight number, airports, departure date and booking reference, plus an internal reference so the same trip is not suggested twice. These are kept in your account until you dismiss them, delete them or delete your account.
- Event text is not stored.
- On iPhone and web, Google's refresh token is stored encrypted on our server until you disconnect or delete your account.
Sharing
Google user data is not shared with anyone except the processors that host our database and server (Supabase and Cloudflare), and only as needed to store and serve your own record. It is never sent to the planning assistant or to OpenAI. No person at Domicile reads your Google data unless you ask us to for support and agree, it is needed to investigate abuse or a security incident, or the law requires it.
Stopping and deleting
- Disconnect Google Calendar in Domicile's Profile to stop further imports.
- Remove Domicile's access entirely at myaccount.google.com/permissions.
- Delete imported suggestions in the app, or delete your account; account deletion also revokes any Google permission held by our server.
- Questions: support@domicile.live.