← Back to app

Privacy Policy

Last updated: August 25, 2026

The short version: We collect only what's needed to help you plan your kids' activities. We don't sell your data, we don't show ads, and we don't share your information with third parties except the infrastructure providers that run the app (Google/Firebase, Anthropic, Postmark, Apple). You can delete your data at any time.
Who else can see your family, in one paragraph Your co-parent sees everything. Anyone you invite to your Family Circle — a grandparent, a caregiver — sees only what you scope to them, read-only, and loses access the moment you remove them. If you join your child's class, the teacher's class emails become events on your calendar, and the teacher is shown a count of enrolled families and nothing else — not your name, not your email, not your child's name. Other parents in the class cannot see you either. Nobody outside these people sees your family's information.
What Google sign-in and calendar access actually do Signing in with your Google account lets us identify you (your email and display name). Separately, if you choose to connect Google Calendar, we ask for permission to view and edit events on your calendars. We use it for exactly two things: (1) we read your upcoming calendar events (roughly a 30-day window) so they appear alongside your school and camp schedule in the app and on your kitchen display, and (2) we add school, camp, and community events to your calendar when you tap to sync them. That's the full extent of it. We do not read your Gmail, your contacts, or your files. You can revoke our access at any time at myaccount.google.com/permissions.

If Google shows an "unverified app" warning during sign-in, it is because our calendar feature is completing Google's review process. It is safe to continue.
Google user data — Limited Use
One Little City's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically, the Google Calendar data we access is used only to provide and improve the calendar features you turn on. We do not sell or transfer it to third parties except the infrastructure providers that operate the app; we do not use it for advertising; and we do not use it to develop, improve, or train generalized artificial-intelligence or machine-learning models. No human reads your calendar data except with your explicit consent, where necessary for security, or to comply with applicable law.

1. Who we are

One Little City is a community app built for families in Falls Church City, Virginia. It helps parents manage school calendars, summer camps, and local events. The app is operated by One Little City LLC.

2. What we collect

We collect only the data you provide directly:

We do not collect:

3. How we use your data

4. Forwarded email parsing

Each family gets a personal forwarding address like yourname_family@inbox.onelittlecity.com. Any email you forward there is parsed and the extracted events/actions appear on your agenda only. Key points:

Gmail connection — admin only. The district admin (one designated person per district) may optionally grant One Little City Gmail read access to automatically pick up community-wide school emails (like FCCPS newsletters) and publish only the schoolwide items to the shared community agenda. This is an admin-only feature — regular users never see a "Connect Gmail" prompt. The admin's raw email content is processed by AI for event extraction, never shared with other users, and never used to train AI models.

5. AI features

We use Claude by Anthropic for three things: (1) parsing forwarded school emails, (2) the AI Camp Planner and Camp Concierge, and (3) photo flyer extraction when you choose to snap one. When you use these features:

6. Where your data is stored

All data is stored in Google Firebase (Firestore) in Google Cloud's US data centers. Firebase provides:

We do not store data on personal servers or outside of Google Cloud infrastructure. Inbound email is routed through Postmark, which passes the webhook payload to our Cloud Functions; it is not retained by Postmark after delivery.

7. Who can see your data

About class email: a class has one email address, held by the teacher and intended for her class mailing list. Anything sent to that address is read by our AI and turned into events and to-dos on the calendar of every family enrolled in that class. We do not show that address to parents. Because a class message reaches many families, our AI is instructed not to extract personal or medical details about any child, and to skip anything that is about one named child rather than the class.

8. Data retention

9. Your rights

You can at any time:

10. Children's privacy (COPPA)

One Little City is designed for use by parents and guardians, not by children directly. We do not knowingly collect personal information from children under 13. All data about children is entered and managed by their parent or guardian, and is intentionally minimized: we collect a first name and grade (or age) only. We do not ask for last names, dates of birth (full birthdays stay on your device for camp age-eligibility only), school IDs, medical or health information, or any other identifier that could be used to contact a child outside the app.

This holds for classes too. A teacher never uploads or types a class roster, and never tells us who is in her class. Each parent joins on their own, using a code, and enters their own child — so every piece of information about a child still comes from that child's own parent or guardian, exactly as above. The teacher is shown a count of enrolled families and is never given a name, an email address, or a child. When a class email is sent to our AI to pull out dates, no child's name or details are attached to it.

11. Security

We take security seriously:

12. Changes to this policy

We may update this policy as the app evolves. Significant changes will be communicated via the app or email digest. The "last updated" date at the top reflects the most recent revision.

13. Contact

Questions about your data or this policy? Contact us: