What we keep
- Your account: your email address, so you can sign in with a code.
- Your family: first names and roles (parent, teen, kid, guest). Kids under 13 are profiles a parent makes: a first name, no email, no sign-in.
- Your plan: events, rides, dinners, recipes, grocery list, meeting notes, check-in answers and survey answers you type in.
- Who changed what: each edit records who made it and when, so the family can see it and undo it.
- App opens: one line per person per day that they opened the app, to see whether the app is helping during the test.
- Notifications: if you turn them on, your phone’s push address, so we can send reminders.
Who can see it
Only the people in your household. The database itself enforces this: one family can’t read or change another family’s data, and we test that on the live system. The team running the test can see a count-only scorecard across families (meetings held, app opens, survey answers and notes you send through the feedback button) to judge whether the app works.
Google Calendar
Connecting a calendar is optional, and only adults can connect one, and only their own.
- What we ask for: read-only access to your calendars (
calendar.readonly), plus your email address to label the connection. Family Fifteen never creates, changes or deletes anything in your Google Calendar. - What we read: events in the calendars you pick, for the next two weeks or so: title, date and time, and location. Nothing older, nothing from calendars you didn’t pick.
- What we do with it: put your events on the family’s week so everyone knows who’s where and who needs a ride. You decide what the family sees: show an event, fold it into a plain “work line”, or hide it.
- The weekly AI draft: to suggest dinners and spot rides that need a driver, the draft sees event times and who’s involved. It sees event titles while “Let Claude read my event titles” is ticked (Family → Calendars; it starts ticked). Untick it and your events go as busy times only. It never gets locations, emails or ages.
- How it’s stored: the access key Google gives us is kept in a part of the database the app can’t reach; only our server uses it, to refresh your events.
- Turning it off: Family → Calendars → Disconnect. That tells Google to cancel our access and deletes every event we imported. You can also remove Family Fifteen at myaccount.google.com/permissions.
Family Fifteen’s use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. We don’t sell calendar data, use it for ads, let people read it except as described here, or use it to train AI models.
The AI draft
Once a week, and when a parent taps “Draft now”, Family Fifteen sends a summary of the coming week to Claude, an AI model made by Anthropic, and gets back suggested dinners, breakfasts, lunches and drivers. The summary holds first names and roles, the family’s recipes and diet needs, events (titles only as allowed above), and check-in answers. Under Anthropic’s commercial terms, data sent through its API isn’t used to train its models. Photos you take of a recipe card are sent the same way, only to read the recipe.
Who else handles it
- Supabase stores the database and sends sign-in emails.
- Netlify hosts the app.
- Anthropic runs the AI draft (above).
- Apple, Google or your browser’s push service delivers notifications you turn on.
Deleting your data
A parent can remove people and disconnect calendars any time in the app. To delete your whole household, write to info@familyfifteen.com. We delete it, with everything in it, within 7 days and confirm when it’s done.
Kids
Kids under 13 never get an account or a sign-in; a parent manages their profile. A parent can make a read-only link for a kid to see their own week, and turn it off at any time. Teens 13 to 17 can sign in only after a parent invites them.
Questions
Write to info@familyfifteen.com. If this policy changes in a way that matters, we’ll tell you in the app before it takes effect.