Privacy policy

How HomeFrame handles your data. Last updated September 2026.

HomeFrame is a family wall calendar. It shows your Google Calendar events, your household's chores and meal plan, and a slideshow of photos you choose, on a tablet in your home. This page describes exactly what it collects and what it does with it.

What HomeFrame stores about you

Google Calendar data

With the calendar.readonly permission, HomeFrame reads your calendars so it can show them on the wall. It stores, for the calendars you switch on: the calendar's name, colour and identifier, and for each event its title, description, location, start and end times, all-day flag, status and Google link.

HomeFrame only keeps a window around today — roughly two months back and thirteen months forward — and rewrites it on each sync. It never writes to, creates, or deletes anything in your Google Calendar. The permission it requests is read-only, so it could not do so even if it tried.

Google Drive data

HomeFrame requests no Google Drive permission at all. The slideshow reads a folder that you have chosen to share in Drive as "Anyone with the link", which HomeFrame fetches the same way any visitor holding that link would. It has no access to the rest of your Drive, and connecting a Google account to HomeFrame never asks for one.

Because such a folder is readable by anyone who has its link, use a folder created for this purpose rather than one holding anything private.

For the photos you choose, it stores the file identifier, name and pixel dimensions. Photo images themselves are fetched from Drive when the slideshow displays them and passed straight to your screen; they are not copied into HomeFrame's database.

Google sign-in

If you sign in with Google, HomeFrame receives your email address, name, profile picture and a Google account identifier, and uses them only to create and recognise your account.

Access tokens

To keep your calendar current without asking you to sign in every time, HomeFrame stores a Google refresh token. It is encrypted at rest with AES-256-GCM. Disconnecting the account in Settings deletes it, and you can revoke HomeFrame's access at any time at myaccount.google.com/permissions.

What HomeFrame does not do

HomeFrame's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Who else is involved

Households are separate

Every piece of data in HomeFrame belongs to exactly one household, and every request is checked against the household of the person making it. Members of one household cannot read or change another household's calendars, photos or anything else.

Deleting your data

Disconnecting a Google account in Settings removes its token, calendars and synced events. To delete your account and your household's data entirely, email support@home-frame.com and it will be removed.

Children

HomeFrame is meant for a household to run together, and a family's chore chart may well name children. Only an adult account holder can connect a Google account or change settings. HomeFrame does not knowingly collect data directly from children.

Changes

If this policy changes in a way that affects how your data is handled, the date at the top will change and the notice will appear in the app.

Contact

support@home-frame.com