Privacy policy

How HomeFrame handles your data. Last updated October 2026.

HomeFrame is a product of Home Grid LLC ("we"), which is responsible for the data described here.

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

HomeFrame asks for two calendar permissions, and uses each for one thing.

With calendar.readonly it 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.

With calendar.events it writes an event to Google only when you add one yourself, on the wall display or in the app, and only to the single calendar you have nominated in Settings. If you nominate no calendar, HomeFrame writes nothing at all. It edits or deletes only events it created this way, identified by a record it keeps of them; it never edits or deletes an event it did not create, and it never adds anything to your calendars on its own.

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.

Microsoft accounts and Outlook calendars

You may also sign in with a Microsoft account, or connect an Outlook / Microsoft 365 calendar (personal or work). HomeFrame then receives, through Microsoft Graph, the same categories of data it receives from Google: your email address, name and account identifier for sign-in, and for a connected calendar the list of your calendars and the events in them (title, preview text, location, start and end, all-day flag, cancellation status and link). It writes an event to Outlook only when you add one in HomeFrame, to the single calendar you nominate. Refresh tokens are encrypted at rest exactly as Google's are, and disconnecting the account in Settings deletes them. A work or school tenant may require its administrator to approve HomeFrame first; HomeFrame never sees anything the administrator has not allowed.

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.

Payments

Purchases are handled by Stripe. Your card details go to Stripe and never reach HomeFrame. We keep only what we need to know what your household has bought: a Stripe customer reference, whether HomeFrame has been purchased and when, and the status of any AI companion subscription.

How HomeFrame protects your data

Google user data — your calendars, their events, and the profile information returned when you sign in — is protected by the following measures.

How long HomeFrame keeps your data, and how to remove it

What HomeFrame does not do

HomeFrame's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used solely to provide and improve the user-facing features described on this page, and for no other purpose.

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.

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

Home Grid LLC · support@home-frame.com