Homebase · last updated 14 October 2026
Homebase is a private application used by one household. It is not offered to the public and there is no sign-up: no member of the public can obtain an account. It is used by the two people who run the household it was built for.
This policy describes what Homebase holds, which services process it, and what it does with information from Google. Where a capability is planned but not yet in use, this policy says so rather than describing it as though it were already true.
This is held in a database the household controls and in the local storage of the devices they sign in on.
Each person signs in with their own account. Records are shared with the household by default: what either of them writes can be read, and corrected, by the other. That is deliberate, because the application exists to run a household jointly, and one person marking a task done has to land on the record the other is looking at.
A record can be made private to the person who wrote it. A private record can be read and changed only by its owner. This is enforced by the database itself rather than by what the screen chooses to show, and a shared record belonging to one person cannot be made private by the other.
Homebase is assembled from a small number of services. These are the ones in use today:
| Service | What it does for Homebase |
|---|---|
| Supabase | Stores the household's records and handles signing in |
| Cloudflare | Hosts the application and runs its server-side component; also controls who can reach it |
| Google Cloud | Hosts a service the household operates that prepares their daily financial summary, and stores the credentials it uses |
| Google Calendar | Read, with permission, so appointments can be displayed |
| Google Drive | Read, so Homebase can collect the daily financial summary file that service produces |
| Open-Meteo | Weather. The browser sends an approximate location, rounded to about 11km, so a town rather than an address. As with any request from a browser, the service also sees the network address it came from. No account and no name is sent |
The financial summary is produced by a service the household runs themselves, which obtains account information from their financial institutions through Plaid, under credentials they control that are held in Google Secret Manager. Homebase itself does not connect to any bank, does not hold banking credentials, never contacts Plaid, and reads only the summary file that service writes.
Configured, and not yet connected. The permissions below are what Homebase is set up to request. At the date on this page no Google account has been connected to it, and no Google user data has been received. This section describes what will happen when a connection is made.
With the household's permission, Homebase reads their Google Calendar. The permissions requested for reading are:
calendar.events.readonly — to show eventscalendar.calendarlist.readonly — to know which calendars existHomebase also reads a single file from the household's Google Drive, the daily financial summary described above.
Google user data is used for one purpose: showing the household their own information inside Homebase. Specifically:
Google Calendar remains the record of appointments. Homebase does not maintain a duplicate calendar.
The token that permits Homebase to read Google information is held server-side only. It is not sent to the browser, is not included in any export or backup the household makes of their own data, and cannot be retrieved through the application.
The household can withdraw Homebase's access to their Google account at any time at myaccount.google.com/permissions. Withdrawing access stops Homebase reading their Google information. Daily snapshots already saved are the household's own records and remain until they delete them. Records the household entered themselves remain theirs, and can be exported or deleted from inside the application.
Calendar information and the financial summary are fetched while the application is open and held in memory as it runs. Neither is written to the device's storage as calendar or financial records, and the server-side component stores neither.
One exception, stated because it is true. Homebase saves a daily snapshot of what it showed on the day's summary screen, so the household can look back at a past day. The snapshot is a copy of that page as displayed, so where the page showed an appointment, the snapshot contains it. Snapshots are kept on the device and are designed to be copied to the household's own Google Drive so they survive the device being replaced. They are the household's own records and are deleted with them.
The server-side component records operational errors, noting that a request failed and on which path. These do not contain calendar contents, financial figures, or anything the household wrote. Responses from the application's own interface are never stored in the browser's offline cache.
When the household deletes a record it stops appearing and is marked deleted rather than removed immediately. This is so their other devices can learn that it was deleted; a row that has simply vanished cannot tell another device anything. The household controls the database and can remove records from it permanently.
The export the application offers is a copy of what is held on that device. It deliberately excludes sign-in tokens.
Homebase is actively being built, and this policy will be updated as its handling of information changes. The date at the top of the page shows when it was last revised.
Questions about this policy can be sent to homebase@captivatingandco.com.