Our Day is a private household organiser for one household: an Android app and a laptop web app. This page describes version 0.8. It does not describe any other product.
Last updated 29 September 2026.
Only the household’s members, signed in with their own accounts, can read the household’s data. This is enforced by the database and file storage rules on Google’s servers, not only by the app. Choosing “Sebastian” or “Ula” on a phone only changes what is emphasised; it grants no access. Naming a person, pet or vehicle on an entry never grants anyone access either.
New entries, trips, documents and profiles are shared with the household unless the person chooses “Only me”. “Only me” items and private backups are readable only by that person’s own account.
Connecting a Google account is optional and happens only on an Android phone. Our Day asks only for read-only permissions: https://www.googleapis.com/auth/calendar.readonly, and, separately, read-only access to Google Tasks. Declining Tasks does not remove calendar access. Our Day never asks for a Google password and never creates, edits or deletes anything in Google.
The phone reads the account address, the calendars that account can see, and the appointments on the calendars the person chooses to include: title, description, place, times, time zone, all-day dates, busy or free state, status, and Google’s identifiers for the event. It refreshes when the app opens, when someone asks, and periodically in the background while online. A failed refresh leaves the saved appointments in place.
The Google sign-in token is kept by Google Play services on that phone. It is never written into Our Day’s files, never uploaded, never given to the laptop web app or our server functions, and never shared with the other phone.
Google appointments stay on the phone unless a person turns on “Share with household” for one, or it belongs to a shared trip. Then a copy of Google’s values for that appointment (a snapshot) and Our Day’s own notes on it are stored with the household’s data, so the other member can see it without any Google access. Turning sharing off removes the snapshot’s content. The laptop web app never connects to Google Calendar; it only shows these shared snapshots and when each phone last refreshed.
Our Day keeps its working copy in the app’s private files on each phone: entries and notes, the Google cache and sync cursor, trips, profiles, places, documents and their files, and preferences such as language, theme and home time zone. Device-only settings (language, theme, notification switches, which Google calendars the phone imports) never leave the phone.
Shared items and private backups are stored in Firebase Cloud Firestore in Google’s europe-west2 (London) region, in the Firebase project our-day-mccluskey. That covers entries, trips, notes, profiles (people other than the two members, pets and vehicles, with only the details someone typed), special dates, records such as a fuel top-up, and document details. Each phone also records its platform, app version and when it last refreshed Google, so the other member can see how current things are.
Files such as booking confirmations, boarding passes and photos are stored in Firebase Cloud Storage in europe-west2. The storage is private: files can be read only by signed-in household members (or, for private files, by their owner) through the app. Our Day never creates public or shareable links to files. Originals are kept exactly as they were added. A saved boarding pass is a saved copy, not a live pass, and barcodes are never recreated from text.
Deleting something in Our Day leaves a marker with no content, so the other devices know it was deleted.
The web app at /app/ uses Sign in with Google through Firebase Authentication for identity only. It asks for no calendar or other Google permissions and stores no Google tokens. A signed-in account that is not a household member sees nothing but an explanation. The web app keeps a copy of the household data it has loaded in the browser’s storage so it can work offline; signing out and clearing the site’s data in the browser removes it.
Nothing is recorded or sent unless you start it. Voice and document reading only work once Our Day’s server functions are set up; until then the app says “Voice isn’t set up yet” and you fill things in by hand instead.
Voice. When you record in Our Day, the recording goes to Our Day’s own server function in europe-west2, which passes it to OpenAI for transcription and returns the text. You can correct it first. If you ask for a draft, the corrected words — plus, only if you choose to include it, the open entry’s details — and the names of the household’s profiles are sent to OpenAI to suggest a draft.
Reading a document. When you choose “Read details from this document” and confirm, that one file (a PDF or image) is sent the same way to OpenAI, which suggests the booking details it can see. Barcodes and QR codes are not read or copied.
Our household can instead choose Google’s Gemini API as the provider for these requests. Only one provider is used at a time; the same request is never sent to both. Nothing is saved, booked, sent or changed until you check the draft and save it yourself.
Only signed-in household members can use these functions. The provider key is held in Google Secret Manager on the server and never reaches the app or the web. Our server keeps no audio, transcripts, drafts or documents; it keeps a daily count of requests per person to enforce limits, and its logs hold only error codes, sizes and counts. The provider processes each request under its API terms, and we ask it not to store requests. On the phone, recordings are deleted after transcription or when you discard them, unless you turn on “Keep voice recordings on this phone”. Recordings and drafts in progress are never synced or backed up.
Tapping Call opens the phone’s own dialler with the number. Our Day does not place or record calls. A call recording is added only when someone chooses a file or shares one into Our Day; it stays in the app’s private files on that phone and is never synced. A dictated note is never shown as a call transcript.
Reminders are worked out on the phone for the person using it, only for things they can see and asked to be reminded about. They are shown as notifications on that phone only. Nothing about reminders is sent anywhere, and the reminder switches in Settings apply to that phone alone.
If someone opens a place in Maps, the place name or address is handed to Google Maps or the browser. Access notes such as a gate code stay in Our Day. Address suggestions from an online service are off unless someone turns them on.
Everything shared with the household can be seen in the app and in the laptop web app. In the web app, Settings → “Download export” saves a ZIP file with the household’s records and files and your own private ones, built in your browser from what you can already read. If you would like anything else we hold for you, email us and we will provide it as a file.
Disconnecting a Google account asks Google to revoke that sign-in and removes the account from the phone, with the cached appointments no other connected account can read. It does not delete anything in Google. You can also remove Our Day from your Google Account permissions at any time.
Leaving the household stops syncing; items already on the phone stay there. Uninstalling the app, or clearing its storage, removes its private files on that phone. To have the household’s data, files and accounts deleted from our Firebase project entirely, email us from a member’s address and we will delete them.
This page and the home page are static. They do not ask for an account, set a cookie, or collect messages. The web app at /app/ is described above.
Questions or requests about your data: causewaycleaning@gmail.com