Privacy Policy

Last updated: August 8, 2026

Spaghetti Labs, LLC, a California limited liability company (“we,” “our,” or “us”), operates stumblapp.com — a free, public calendar of family-friendly events across the San Francisco Bay Area — and the Stumbl iOS app. This policy explains what information each of those collects, why, how long we keep it, and what you can do about it.

Most people reading this are here for the website. Sections 1–9 cover the website. Section 10 covers the iOS app, which works differently because it has accounts. Sections 11 onward apply to both.

1. Who we are and what this covers

Spaghetti Labs, LLC is the controller of the personal information described here. We are a small, independent operation based in California.

This policy covers two things:

• The website at stumblapp.com — a free, public events calendar. No account exists for it and none is offered.
• The Stumbl iOS app — a separate product with phone-number accounts, friends, check-ins, and an optional subscription. It collects considerably more information, all of it described in Section 10.

If you have only ever visited the website, nothing in Section 10 applies to you.

2. Browsing the website

You do not need an account to use this website. There is no sign-up, no sign-in, no paywall, and no trial. Every event listing, city page, category page, guide and search result is public and free.

We do not ask for your name, your email address, your location, or anything else in order to show you events. The only place on the site that asks you for anything at all is the optional newsletter box (Section 6). The only place that leads to a payment form is the optional support link, and that form belongs to Stripe and lives on Stripe’s own page (Section 8.2). Nothing here is unlocked by paying, so there is nothing to buy.

Pages are rendered on our servers and delivered to you as plain HTML. Every script the site runs is served from stumblapp.com itself — no JavaScript is ever loaded from a third-party server, and no third party can observe you through code on this site. (Some of that self-hosted code is open-source software we did not write, such as the MapLibre library that draws the events map; it runs from our servers like everything else and phones nobody.) JavaScript, when you have it enabled, only adds conveniences — filtering, saving an event, sharing a link, the interactive map — and every page remains fully readable and navigable with JavaScript turned off.

The events map deserves one specific promise. Map imagery and geography load from our own servers, not from a mapping provider, so looking at the map tells no one where you are looking. If you tap the map’s locate button, your browser will ask permission and then position the map using your device’s location; that location is used entirely inside your browser and is never transmitted to us or anyone else.

3. What the website stores in your browser

The site stores two small things in your browser’s localStorage:

Neither is a cookie, so neither is attached automatically to requests, and neither is associated with an account or any identifier for you — you do not have one.

Your theme preference never leaves your device at all; it is read only by the page itself.

Your saved events stay on your device too, with one exception we want to be plain about: when you open the Saved page, your browser sends that list of event IDs to our server so we can look up those events and show them back to you. Like any other request, that URL appears in our server logs (Section 4). The list is a set of public event IDs — it is not tied to an account, we do not store it, and we do not build a profile from it. If you never open the Saved page, the list is never sent.

Practical consequences worth knowing:

• Clearing your browser’s site data, or using private browsing, erases your saved events. There is no backup and we cannot restore them.
• Saved events do not sync between your phone and your laptop. The list lives in one browser, and we never store a copy of it.
• If we ever store other small interface preferences of the same kind, they follow the same rule: they stay in your browser.

4. Server logs

The website runs on Firebase Hosting and Cloud Functions, both operated by Google Cloud. Like essentially every web server, these record technical metadata about each request:

• The IP address the request came from
• The user agent string your browser or crawler sends (browser and operating system family)
• The URL requested, including any query parameters such as a search term or filter
• The date and time, response status code and response size
• The referring URL, when your browser chooses to send one

We use these logs for three purposes and no others: security (detecting and blocking attacks), abuse prevention (rate limiting, identifying automated bulk extraction), and operations (fixing errors, understanding load, keeping the site fast). The same logging covers the site’s own internal JSON endpoint, which on-page filtering calls back to.

We do not use server logs to build a profile of you, we do not attempt to identify individual visitors from them, we do not combine them with the newsletter list, and we never sell them or hand them to advertisers.

Retention. Request logs are retained for approximately 30 days under Google Cloud’s default logging retention, after which they are deleted automatically. We do not extend that period. The exceptions are narrow: we may preserve specific entries longer where we are actively investigating a security incident or abuse, or where we are legally required to. Aggregate counts derived from logs — for example, how many times a page was viewed in a month — may be kept longer in a form that does not identify anyone.

5. Cookies, analytics and tracking

We do not set any cookies on this website. There is no cookie banner because there is nothing to consent to.

We also do not use:

• Third-party analytics scripts (no Google Analytics, no Firebase Analytics on the web, no product-analytics SDK)
• Advertising pixels, conversion tags or retargeting scripts
• Cross-site or cross-app tracking of any kind
• Browser fingerprinting
• Data brokers, identity-resolution services or audience-matching services

Two honest caveats, because your browser does make requests to servers other than ours:

• Fonts. Our pages load the Nunito typeface from Google’s font servers (fonts.googleapis.com and fonts.gstatic.com). As part of that request, Google receives your IP address and user agent, exactly as happens on any site that uses Google Fonts. We receive nothing back from Google about you.
• Event photos. When a listing includes a photo, your browser loads that image directly from the organizer’s own web server, which therefore sees your IP address and user agent. Likewise, when you click through to a source listing, you are on that organization’s site and their privacy policy applies, not ours.

Do Not Track and Global Privacy Control. Because we do not sell or share personal information and do not track anyone across sites, there is nothing for these signals to switch off. We nevertheless treat a Global Privacy Control signal as a valid opt-out request.

6. The email newsletter

The newsletter is entirely optional. You can use every part of the website without it.

6.1 What we collect

• Your email address.
• The page you signed up from — so we know which parts of the site people find useful.
• The date and time of the signup, which is also our record of your consent.
• A coarse IP address for the signup request, truncated so that it identifies a network rather than a device. We keep this only to detect and block bulk fake signups.

We do not ask for your name, your children’s ages, your neighborhood, or anything else.

6.2 What we use it for

Two things only: a weekly digest of Bay Area family events, and occasional short notes about the site itself (a new feature, a new city, a change to this policy). That is the whole list.

We do not need to know whether you opened an email, and we do not currently measure opens or clicks. If that ever changes, we will describe it here first.

6.3 What we will never do with it

We do not sell, rent, trade, or otherwise disclose your email address to anyone for their own use. We do not send third-party offers, we do not send advertising on behalf of others, and we do not add you to any list you did not ask for. Your address is used to send you the Stumbl newsletter and for nothing else.

6.4 How to unsubscribe

Every single email we send contains a one-click unsubscribe link at the bottom. One click removes you — no login, no confirmation form, no “are you sure.”

You can also email contactstumblapp@gmail.com with the word “unsubscribe” and we will remove you by hand.

We honour removals promptly: normally immediately, and in every case within 10 business days. After removal we keep only a minimal suppression record so that the address is not accidentally re-added later. If you would rather we erase that too, say so and we will.

6.5 Where the list is stored

Newsletter signups are stored in our Firestore database on Google Cloud in the United States, and delivery is handled by a third-party email service provider acting as our processor under its own security and privacy terms. If you want to know which provider currently handles delivery, email contactstumblapp@gmail.com and we will tell you.

7. Where event listings come from

Every event on this site is aggregated from a calendar that its organizer has already published publicly. Our sources are libraries, parks and recreation departments, regional park districts, museums, city governments, farmers’ market operators and similar community organizations across the Bay Area. Each source is named on our Sources page.

What we take from those pages is descriptive, factual information about a public event: the title, a short description, the date and time, the venue and address, any age guidance, the cost, and a link back to the original listing. Every event page on this site links to its original source, named and clickable, so you can always check the organizer’s own page.

We do not collect or publish personal information about people who attend events. There are no RSVPs, no attendee lists, no guest counts and no check-ins anywhere on the website.

Occasionally an organizer’s own public listing names a staff member — “Storytime with Ms. Rivera,” for example. That is information the organization chose to publish, and we reproduce it only as it appears in their listing. If you are named in a listing and would rather not be, email contactstumblapp@gmail.com and we will remove your name.

Organizers who want a listing corrected or taken down should see the corrections and removals section of our Terms of Service.

8. Advertising and how the site is funded

8.1 Advertising

This site runs no advertising today. There is no ad network, no ad server, no sponsored-content system, no affiliate tracking, and no sponsor pixel anywhere on it. Nothing about you is sold, shared or made available to advertisers, because there are no advertisers.

An honest word about the future, since the site is free and does cost money to run. If we ever introduce advertising or sponsorship, we will:

• update this policy and change the “Last updated” date at the top before any ad code is deployed, not after;
• describe plainly what the ad system collects and who operates it; and
• provide an opt-out wherever the law requires one.

Until you see that change reflected on this page, you can safely assume there is no advertising on the site — because there is not. What we will not do, in any scenario, is fund the site by selling your personal information.

8.2 Voluntary support

The site is free and stays free, but it isn’t free to run, so there’s an optional tip jar. If you want to help with the hosting bill, the domain and the time that goes into keeping the listings current, you can. It buys nothing. The site, the listings and every feature are the same for someone who contributes and someone who never does. The Terms of Service spell out what a contribution is and isn’t; this section is only about your privacy.

• The link takes you to Stripe. It’s an ordinary outbound link to a payment page hosted by Stripe, Inc. on a stripe.com address. There is no payment form, no checkout widget, no iframe and no Stripe JavaScript on stumblapp.com. Keeping the payment off-site is exactly what lets the commitments in Section 5 stand: no third-party script runs on this site, and adding a tip jar didn’t change that.
• Stripe runs the transaction under its own policy. Once you’re on Stripe’s page you’re dealing with Stripe. Whatever you type there goes to Stripe, not to us, and Stripe is the party responsible for it — the controller and processor of that payment — under Stripe’s privacy policy. We don’t send Stripe anything about you.
• We never receive or store card details. Not the card number, not the expiration date, not the security code. They never reach our servers, because there is no payment code on our servers to reach.
• What we can see. Our Stripe dashboard shows us whatever a payer chose to give Stripe — typically a name, an email address, the amount, and the last four digits of the card. That’s Stripe’s record of the payment, shown to us as the account holder, not something we collected here. We use it for two things: reconciling what came in, and answering a refund request.
• Contributing is not a signup. We don’t add contributors to the newsletter, to a supporter list, or to any other list. If you want the newsletter, use the newsletter box.
• We store nothing about contributions in our own database. There’s no contributions collection in Firestore and no flag on anything. The site cannot tell whether you’ve ever contributed, because it has no idea.
• No cookie, no localStorage entry. Clicking the link sets nothing on stumblapp.com. It’s an <a href> and nothing else. Anything Stripe sets, it sets on its own domain under its own policy.

If you contributed and want it back, email contactstumblapp@gmail.com and we’ll refund it. You don’t have to explain why.

9. Children’s privacy

Stumbl is a site about things to do with kids, made for the adults planning those outings — parents, grandparents, caregivers, nannies, teachers. It is not directed to children under 13, and children are not its audience.

On the website, there are no accounts, no profiles, no comments, no messaging, and no way for anyone to submit personal information except the optional newsletter box, which is intended for adults. We do not knowingly collect personal information from children under 13, and we do not use age, school, or child-directed targeting of any kind. Consistent with the Children’s Online Privacy Protection Act (COPPA), if we learn that a child under 13 has given us personal information — for example, by typing an email address into the newsletter box — we will delete it promptly.

In the iOS app, accounts are for adults 18 and over. Children do not have their own accounts or profiles and cannot create one. Family member first names and ages are entered voluntarily by the parent or guardian, stored as metadata on the parent’s own profile, and visible only to that parent’s confirmed friends. Children do not interact with the app directly.

If you believe a child has provided us with personal information, contact contactstumblapp@gmail.com (or contactstumblapp@gmail.com for the app) and we will delete it.

10. If you use the Stumbl iOS app

This section applies only to the Stumbl iOS app. The app is a friends-and-check-ins product: it helps parents coordinate spontaneous meetups with people they know. It requires an account and collects more information than the website does. Nothing here applies to website visitors.

10.1 Information you provide

10.2 Information collected automatically

10.3 Device permissions

You can change any of these permissions at any time in your device’s Settings app.

10.4 Location, in more detail

• Check-in location: when you create a check-in, its location is stored with the check-in and shared with your friends (or selected friend groups) for the duration of that check-in. Coordinates written to our database are truncated to roughly 111 meters of precision.
• Background location: if you grant “Always” permission, the app periodically updates your approximate location using iOS significant-change monitoring. This is used solely to work out whether a friend’s check-in falls inside your notification radius. It is not shared with other users and not visible to friends. Only one value is stored at a time — we do not build a location history.
• Arrival and departure detection: while you have an active check-in, the app watches your distance from the check-in location so it can prompt you to update your status. This is processed on your device and is not stored or shared.
• No location without consent: every location feature requires your explicit permission, revocable at any time in Settings. The app remains usable without it, with reduced check-in and notification features.

10.5 Subscriptions and payments

We do not collect, store, or have access to your payment information. All Stumbl+ subscription payments are processed entirely by Apple through the App Store. We receive only your subscription status and plan type.

We store the following subscription data in Firestore, associated with your account, purely to determine which features are available to you: subscription status (trial, active, or expired), plan type (monthly or annual), trial start date, and expiration date.

The events calendar on this website is free for everyone and is not part of any subscription.

10.6 Deleting your app account

You can delete your account at any time from the Profile tab in the app. Deletion is permanent and removes your profile, profile photo, friends, check-ins, favorite locations, feedback, friend requests, pending invites and subscription records from our servers. You can also request deletion by emailing contactstumblapp@gmail.com.

11. How we share information

We do not sell your personal information. We never have. We share information only in these limited ways:

• Service providers. The companies listed in Section 15 process data on our behalf, under their own privacy terms, to make the site and app work.
• With your friends (app only). Your display name, profile photo, check-in location, activity notes and attending family members are visible to people you have mutually added as friends. You choose whether a check-in goes to all friends or to selected friend groups.
• Through shared groups (app only). When you join a shared group, your profile information (display name, profile photo, and phone number) is shared with existing group members, and theirs with you, through the mutual friendships the group creates. Group admins see your display name and photo when you request to join. Your display name may appear as the inviter’s name on a group invite preview.
• Legal requirements. We may disclose information where required by law, regulation, legal process or governmental request, or to protect the rights, safety or property of Spaghetti Labs, LLC, our users, or the public.
• Business transfers. If Spaghetti Labs, LLC is acquired, merged, or sells assets, information may transfer as part of that transaction. We will note any such change here and describe any choices you have.

We do not share personal information with advertisers, and we do not track you across other apps or websites.

12. How long we keep information

13. Security

• All connections use HTTPS/TLS. The site and app make no plain-HTTP requests.
• Data at rest is encrypted using Google Cloud’s built-in encryption.
• The website reads Firestore only through the server-side Admin SDK inside our Cloud Function. The public site never connects to Firestore from your browser, and our database security rules remain closed to unauthenticated clients.
• Access to app data is restricted by server-side Firestore security rules that enforce per-user authorization; push notification tokens are accessible only to the account owner.
• Phone number authentication uses standard SMS verification with rate limiting.
• Profile photos are stored in Firebase Cloud Storage with access controlled by authenticated URLs.

No method of transmission or storage is completely secure. We take reasonable measures, but we cannot guarantee absolute security.

14. Your privacy rights

Everyone, everywhere, can do the following without asking us: browse the site without identifying yourself, clear your browser storage, unsubscribe from the newsletter with one click, and delete an app account from the Profile tab. The rest of this section covers formal legal rights.

14.1 California residents (CCPA/CPRA)

In the past 12 months we have collected these categories of personal information:

As a California resident you have the right to know what personal information we have collected about you, the sources, the business purposes and the categories of recipients; the right to delete it; the right to correct inaccurate information; the right to data portability; the right to limit the use of sensitive personal information; the right to opt out of the sale or sharing of personal information; and the right not to be discriminated against for exercising any of them.

We do not sell personal information, and we do not share personal information for cross-context behavioral advertising, as those terms are defined by the CCPA and CPRA. We have not done so in the preceding 12 months, and we have never done so. There is therefore no opt-out link on this site, because there is nothing to opt out of.

The only sensitive personal information we handle is precise geolocation in the iOS app, used solely to deliver the check-in and nearby-notification features you asked for — never to infer characteristics about you. You can withdraw it at any time in your device Settings.

You may use an authorized agent to submit a request on your behalf; we will ask for proof of their authority and verify your identity before acting.

14.2 EEA and UK residents (GDPR / UK GDPR)

Stumbl is aimed at people living in or visiting the San Francisco Bay Area, and we do not target the EEA or the UK. If you are nevertheless visiting from there, the following applies. Spaghetti Labs, LLC is the data controller, and our lawful bases are:

You have the right to access, rectify, erase, restrict and port your data, to object to processing based on legitimate interests, and to withdraw consent at any time — for the newsletter, by clicking unsubscribe in any email; for app permissions, in your device Settings. Withdrawing consent does not affect processing already carried out.

Our processing takes place in the United States. Where personal data is transferred out of the EEA or UK, our providers (principally Google) rely on the European Commission’s Standard Contractual Clauses and the UK Addendum. You also have the right to lodge a complaint with your local supervisory authority, or with the UK Information Commissioner’s Office.

14.3 Making a request

Email contactstumblapp@gmail.com and tell us what you want. For app accounts, deletion is faster in the app itself (Profile tab).

We will verify your identity in proportion to the sensitivity of the request — for a newsletter request, that usually just means replying from the address in question. We respond within 45 days for CCPA requests and within one month for GDPR requests, extending only where the law allows and telling you if we do. There is no charge, unless a request is manifestly unfounded or repetitive.

15. Service providers and where data lives

All Firebase and Google Cloud services are provided by Google LLC under Google’s data processing terms; see Firebase’s privacy page. Apple’s policy is at apple.com/legal/privacy. Our data is stored in the United States.

Stripe is the odd one out on that list, and worth a sentence of its own. It is not processing site data for us: it hosts its own payment page, on its own domain, and handles anything typed there as its own controller under its privacy policy. We send Stripe nothing about you, and no Stripe code runs on stumblapp.com. All we do is link to it, and read the resulting payment record in our dashboard (Section 8.2).

16. Changes to this policy

We update this policy when what we do changes. When we make a material change — particularly anything that widens what we collect or who receives it — we will change the “Last updated” date at the top of this page before the change takes effect, and we will describe it in the newsletter if you subscribe to it.

Continued use of the website or app after an update means you accept the revised policy. If you disagree, stop using the site, unsubscribe from the newsletter, and delete your app account if you have one.

17. Contact us