The short version. Our Life uses a single shared "family code" instead of accounts — there's no email, no password, and no name required to start. The data your family creates inside the app (appointments, lists, meals, recipes, photos) is stored in our database tied to that code. We don't sell it. We don't share it with advertisers. You can export or delete it at any time.
1. Information we collect
Our Life is designed to work without traditional user accounts. We collect:
Information you put into the app
- Family content: appointments, lists, meal plans, recipes, family-member names and roles, notes, photos you attach, saved places, and any other content you create or upload.
- Family code: a 6-character random code generated when you create a family. It's the only identifier we use to associate data with your household.
- Member details: names, emoji, color, role (parent / child), and optionally avatar photos you choose to add. There is no requirement to use real names.
Information we collect automatically
- Local device preferences: theme, palette, kid-view mode, and other UI settings are stored in your browser's localStorage and never sent to us.
- Anonymous crash reports: if you encounter a crash, we may receive an anonymized error report via Sentry that includes the device type, browser, and stack trace. We do not collect IP addresses or content from your family doc in those reports.
- Server logs: our servers keep short-lived request logs containing IP address, timestamp, and the endpoint called. These are used to operate the service and are deleted on a rolling basis.
What we do not collect: we do not require an email address, phone number, real name, date of birth, government ID, payment information at signup, location at the device level, contacts, calendar imports from other accounts (unless you choose to subscribe to an ICS feed), or any cross-site browsing data.
2. How we use information
- To operate the app — sync your family's data across devices in real time, send reminders you've configured, generate calendar feeds you've enabled.
- To provide the AI features (meal plans, recipe import, natural-language appointment entry) when you actively use them.
- To fix bugs and improve reliability, using anonymized crash reports.
- To enforce our Terms — for example, preventing abuse of share links.
We do not use your information for advertising, profiling, or any kind of behavioral analysis. We do not sell your information.
3. Sharing and third parties
We share data with a small set of service providers strictly to operate the app:
- MongoDB Atlas — our hosted database where your family doc is stored.
- Anthropic — when you use an AI feature, the relevant text (e.g. "Soccer Tuesday at 4pm", or the recipe URL you want imported) is sent to Anthropic's Claude API to generate a response. Anthropic does not train models on this data.
- Google Maps Platform — when you search for a location or request driving directions, the query is sent to Google.
- Sentry — anonymized crash reports if enabled.
- App Store / Play Store — if you install Our Life from a store, your relationship with that store is governed by the store's own privacy policy. Apple and Google may share aggregate install metrics with us; we never receive your store account email.
We do not share with advertisers, data brokers, social networks, or analytics platforms that profile users.
4. How AI features work
AI features (meal planning, recipe import, natural-language quick add) are opt-in — you only invoke them by tapping the feature. When you do, the relevant input you provided is sent to Anthropic's Claude API, processed, and the result is returned to your device. We do not include your entire family doc in those requests; only the specific text or URL needed for the task.
Anthropic states they do not train their models on API inputs. We do not retain a separate copy of the AI request beyond what's necessary to operate the feature and respond to bug reports.
5. Where your data lives
Your family doc is stored in MongoDB Atlas in the United States. Photos you attach are stored as compressed JPEG data inside the family doc — they are not uploaded to a separate image host. Sync between devices happens via real-time Server-Sent Events streamed over HTTPS.
Some data is also stored locally on your device — your last-known family snapshot, theme preferences, and the kid-view toggle live in your browser's localStorage so the app works offline. Clearing your browser's storage will remove this local copy but will not affect the copy stored on our servers.
6. Share links and the babysitter view
You can choose to mint public share links — for example, to give a babysitter a read-only view of tonight's schedule, or to share a single list with a relative. Anyone who has the link can view the data the link is scoped to. Links are unguessable random tokens, but they are not authenticated; if you share them broadly, the data they reveal is publicly accessible.
You can rotate or revoke any share link from the Share Manager screen at any time. Rotation invalidates the previous link immediately.
7. Children's information
Our Life is designed to be used by families that include children, but the app is intended to be set up and operated by a parent or guardian. The parent decides what information about their children appears in the app. We do not collect any information from children directly — children using Kid View interact only with content their parent has entered.
If you believe we have inadvertently collected information from a child without parental consent, please contact us and we will delete it.
8. Your rights
Because we don't require an email at signup, the family code is what proves ownership. As long as you have the code, you can:
- Access all data in your family doc directly inside the app — there is nothing hidden.
- Export your family's data to JSON from Settings → About → Export.
- Correct any field by editing it in the app.
- Delete any record at any time. To delete the entire family, remove all members and the doc will be purged on next cleanup.
- Rotate share links to revoke prior access.
- Disable AI features by simply not using them.
If you are in a jurisdiction with specific data-protection rights (such as the EU's GDPR, the UK's UK-GDPR, or California's CCPA), you also have the right to request human review of any data we hold. Email support@ourlifeapp.ai with your family code and we will respond within 30 days.
9. Data retention
Your family doc is retained for as long as the family is in use. Families that have not synced for 18 months may be archived and eventually deleted, after which the family code becomes available for reuse. Anonymized crash reports are retained for up to 90 days. Server logs are retained for up to 14 days.
10. Security
All traffic between your device and our servers is encrypted in transit via HTTPS / TLS. Database access is restricted to authorized backend processes only. We do not at this time offer end-to-end encryption of family data — meaning our infrastructure can technically read your family doc to operate the service. We are evaluating an opt-in e2e mode for a future release.
No system is perfectly secure. If you have reason to believe your family code has been shared with someone you didn't intend, you can rotate to a new code from Settings.
11. Changes to this policy
We may update this policy from time to time. The effective date at the top of this page tells you the most recent version. Material changes will be announced inside the app before they take effect.
12. Contact us
Questions, concerns, or data requests? Email support@ourlifeapp.ai. Please include your family code so we can locate the right data.