Privacy

Last updated 7 September 2026

Home is a shared organiser for one household. It is operated by Curiosity. This page describes exactly what it stores, who else touches it, and how to get rid of it. If anything here is unclear, email justin@flitter.co.nz.

What it stores

Your name, email address and profile photo, taken from the Google account you sign in with. The tasks, lists, events, recipes, people, maintenance jobs, messages and forwarded emails that you and the other people in your household create, including any photos you attach to them. Push notification subscriptions for each device you turn notifications on for.

Google account data

Signing in asks only for your name, email address and profile picture. Connecting a Google Calendar is separate and optional; only then does Home ask for these permissions, and it uses them only as described:

• calendar.readonly

  To show your calendars and events inside the app.

• calendar.events

  To create, edit and delete events you make in the app on the calendar you chose.

• openid, email

  To know which account was connected, so it can be shown in Settings and reconnected when a token expires.

Calendar events are copied into Home so the app can show one merged view and keep working offline. They are visible only to people in your household. Access and refresh tokens are stored in a table no browser session can read; they are used only by the server, to sync the calendars you chose.

Limited Use

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

Google Workspace APIs are not used to develop, improve, or train non-personalized AI and/or ML models.

Google user data is never used for advertising of any kind, never sold, never given to data brokers or information resellers, never used to assess credit-worthiness or for lending, and never transferred to anyone else except as needed to run the features you asked for. Nobody at Curiosity reads it, other than where you ask for support and give explicit permission at the time.

Microsoft account data

If you connect an Outlook or Microsoft 365 calendar instead, the same applies. The app asks to read and write calendars, copies events in so it can show them, stores the tokens the same way, and uses them for nothing else.

Forwarded email

If your household uses the shared inbox, emails you forward to its address are stored so everyone in the household can see them, along with any attachments. Mail from an address that is not a member of that household is dropped without being stored.

Who can see it

Only people in your household, and only while they are members of it. Nobody outside your household can read your data, including other Home households. This is enforced in the database itself rather than only in the app, so a request for someone else’s data returns nothing rather than relying on the screen to hide it.

Who else processes it

These companies handle household data on our behalf, and only to do the job listed:

• Supabase

  Database, file storage and sign-in. All household data lives here.

• Netlify

  Hosts and serves the app itself.

• Cloudflare

  Routes mail sent to your household address into the shared inbox.

• Stripe

  Takes payment. Card details go straight to Stripe and never reach us.

• Apple and Google push services

  Deliver push notifications to your devices. They carry the notification text, nothing else.

Google and Microsoft appear in this list only if you choose to connect a calendar, and only for that calendar.

How it is protected

Everything travels over HTTPS. Each row of household data carries the household it belongs to, and the database refuses to return a row to anyone outside it. Photos, voice notes and email attachments sit in private storage that is never publicly addressable; the app fetches short-lived links that expire. Calendar tokens live in a table with no client-readable policy at all, so they can only ever be used by the server. Card numbers never reach us.

How long it is kept

Household data is kept while your household exists, because that is the point of it: last year’s shopping is what makes buy-again useful, and an old recipe is still a recipe. Calendar events are refreshed from the source and removed when you disconnect that calendar. Push subscriptions are removed when you turn notifications off on that device. Deleting removes data from the live database straight away; short-term backups held by our hosting provider for disaster recovery may still contain it briefly before they roll off.

Deleting it

Disconnecting a calendar in Settings deletes its stored tokens and its events, and you can do that yourself at any time. You can also revoke Home’s access to your Google account at myaccount.google.com/permissions, which stops calendar sync immediately.

Deleting the whole household is by request rather than a button, for now: email justin@flitter.co.nz and it will be done within 30 days. When it is, everything belonging to that household goes with it in one step — tasks, lists, recipes, people, maintenance jobs, messages, forwarded email, and every photo and attachment.

Changes

If this policy changes materially you will be told in the app before the change takes effect, and the date at the top of this page will change.

Contact

Curiosity, justin@flitter.co.nz. This policy is also linked from the home page and sits alongside the terms.