Privacy Policy

About this policy

KidCampConnect is a small side project run by two parents. We're building a directory of summer camps, classes, and enrichment activities for parents in Madison, Evanston, and Tampa. The service is currently in private early access — visible only to people who have entered a shared access code.

This policy describes what personal information we collect, why, and what we do with it. We've written it to reflect what we actually do today, not generic boilerplate. If anything is unclear, email us at hello@kidcampconnect.com.

What we collect

We collect information from a small number of well-defined places:

1. Waitlist signup. When you fill out the waitlist form on our marketing landing page, we collect the email address and city you provide. The submission is handled by Formspree, which delivers it to our inbox.
2. “List your camp” provider submissions. When you submit a camp listing through the public “List your camp” form, we collect whatever you choose to share — typically a name, a URL, contact information, and program details. The submission is handled by Formspree, which delivers it to our inbox.
3. “Add a program” planner imports. When you use our planner's “Add a program” feature to import a camp from a URL, an email, or pasted text, the URL or text content you provided is sent to our server for parsing. The result of that parsing is logged in a private GitHub issue tracker so we can triage and add the program to the public directory. If you choose “Save to my plan” only (without “Submit to us”) and use manual entry — meaning you didn't use a URL or paste flow — your input stays in your browser and is not sent to us.
4. Feedback you send us. When you use the “Send feedback” button, your message is sent to us along with some context about your visit (the page you were on, your browser's user agent, your viewport size). Your email is included only if you choose to provide one. The form has two opt-in attachments:
   • Screenshot of the page you were on — captured locally in your browser and sent with your feedback to help us see what you saw. Default off. Check the box to include it. If you do, the screenshot may include any text and images visible on the page at the time of capture, including a child's first name if it appears in the planner.
   • Plan snapshot in the feedback form (opt-in, default off). If you check the box to attach your saved plan, your kids' first names are replaced with “Kid 1”, “Kid 2”, etc., the notes you've written on saved programs are removed, and any friends you've added to saved programs are removed — all before the snapshot leaves your device. Ages and saved programs are preserved so we can see the plan's structure, but children's identities and your own free-text notes are never transmitted.
5. Site access cookie. While the service is in private access, we set an HTTP-only signed cookie (kcc_access) when you successfully enter the access code. This cookie does not contain any personal information — it's a cryptographic token that records that you entered the correct code. It expires after 30 days.
6. Browser-local planner state. When you save a camp, build a summer plan, or set up a kid profile in the planner, that information is stored only in your browser's localStorage (under keys beginning with kcc.). This includes any first names and ages you enter for your children. The planner is designed to keep this information only on your device — we don't purposefully collect or store it on our servers. Clearing your browser data clears it.
7. Your precise location, only if you grant it. When you click “Use my location” on the directory's distance filter or in onboarding, your browser asks your permission to share your location with the site. If you grant permission, your latitude and longitude are sent to our server in the body of the search request, where we use them to compute distance from each camp and sort by nearest. We do not store latitude and longitude on our servers. Your approximate location (latitude, longitude, and nearest ZIP code) is also saved on your device in browser localStorage under your saved plan, so the distance filter applies across visits without re-prompting. You can use the distance filter by typing a ZIP code instead, in which case precise location is never requested or transmitted.
8. Analytics and product-experience tools. We use third-party services to understand how the site is used and where the planner is hard to use. They see things like page views, navigation patterns, click activity, and (for session-replay tools) the visual structure of the pages you see — but they do not see the contents of any input or textarea you type into, and any area we have specifically marked as private is excluded from recording. Tools we currently use: Google Analytics (page-view analytics) and PostHog (session replay). Each is governed by its provider's privacy policy.

We don't collect anything else from you actively. We don't ask for phone numbers, mailing addresses, or payment information.

Important: if you include personal information about your child in a free-text field of a submission form (for example, mentioning their name or age in a question), that information will reach us through the form. Please share only what's necessary.

Why we collect it

• Waitlist email and city: to notify you when we launch in your area, and to gauge demand by city.
• Submissions: to add programs to the directory, and to follow up with you if we have questions.
• Access cookie: to keep you signed in during the private-access phase, without making you re-enter the code on every page.
• Planner localStorage: so your saved plans persist across visits — without us holding the data.
• Precise location: to compute distance from camps you're considering, both for filtering by radius and sorting nearest-first. We use it for the request and discard it; we don't store it on our servers.
• Analytics: to understand how the product is actually used so we can improve it.

Third parties we share data with

KidCampConnect is hosted in the United States. If you access the service from outside the U.S., your information is transferred to and stored in the U.S. We use the following third-party services. Each has its own privacy policy:

• Vercel — our hosting provider. Vercel may process network data incidental to delivering pages.
• Formspree — receives and forwards form submissions (the waitlist signup and the “list your camp” provider form).
• GitHub — when you use the planner's “Add a program” feature with URL, paste, or submit-to-us flows, the submission is logged in a private GitHub issue tracker for our team to triage. Parent feedback submissions are also filed there as issues, and any screenshot you opt to attach is uploaded to a dedicated feedback-screenshots branch in the same repository.
• Analytics and product-experience tools — services we use to understand product usage and improve the planner. Currently:
  • Google Analytics — page-view analytics. See https://policies.google.com/privacy
  • PostHog — session replay. See https://posthog.com/privacy
  All currently store data on US infrastructure.
• Google Maps Platform — we use the Google Maps API to provide location lookup, geocoding, and embedded map views. Your use of these map features is also subject to the Google Privacy Policy.

We do not sell personal information. We do not share waitlist emails or submissions with any third party beyond the processors named above. We may disclose information if required by law (subpoena, court order, or lawful request).

Children's privacy

KidCampConnect is parent-directed. The service is intended for use by parents and guardians, not children. We do not knowingly collect personal information directly from children under 13.

The planner lets parents enter children's first names and ages so they can plan around their kids' schedules. This information is stored on your device, in your browser's localStorage. We do not save it on our servers, and our planner does not transmit it. Clearing your browser data clears it.

Three things on the site can carry visual information off your device, and we've made specific choices for each so children's identities don't travel with it:

• Session replay (PostHog). Replay records what happens visually on the page during your visit. We have configured replay to mask every screen and component that displays a child's first name — names appear as same-size blocks in any recording, never as readable text — and to mask the contents of every input and textarea. The planner's “Add a program” modal, where you may paste a registration confirmation email, is excluded from recording entirely.
• Plan snapshot in the feedback form (opt-in, default off). If you check the box to attach your saved plan, your kids' first names are replaced with “Kid 1”, “Kid 2”, etc., the notes you've written on saved programs are removed, and any friends you've added to saved programs are removed — all before the snapshot leaves your device. Ages and saved programs are preserved so we can see the plan's structure, but children's identities and your own free-text notes are never transmitted.
• Screenshot in the feedback form (opt-in, default off). If you check the box to attach a screenshot, your browser captures whatever is visible on the page as image bytes and sends it with your feedback. If a child's first name is on screen at the time of capture — for example, a “Place for Peter” label in the planner — that name will appear in the screenshot. The masking we apply to session replay does not extend to screenshots; if you'd rather not include it, leave the box unchecked.

If you find a case where a child's name appears un-masked in session replay (where it should be masked), please tell us at hello@kidcampconnect.com and we will fix it. If you believe we have inadvertently collected information directly from a child under 13, contact us at the same address and we will delete it.

If something goes wrong

If we become aware of a security incident that exposes information you've given us, we will notify affected users without unreasonable delay. Depending on the kind of data involved and where you live, applicable state law may also require us to notify you in a particular way and within a particular timeframe; we will follow those requirements when they apply.

Your choices

• Access, correction, or deletion of waitlist or submission data: email hello@kidcampconnect.com and we will respond within a reasonable time.
• Browser-local planner state: clearable by clearing browser data on your device.
• Precise location: opt in per-session by clicking “Use my location” and granting browser permission. Revoke via your browser's site permissions. Your saved approximate location lives in browser localStorage; clearing browser data removes it. You can also type a ZIP code manually — that path never requests or transmits precise location.
• Access cookie: clearable via your browser's cookie settings.
• Analytics and replay: opt out via your browser's privacy controls (Do Not Track or Global Privacy Control), an ad blocker or privacy extension that blocks requests to analytics providers, or any opt-out tool a specific provider offers. If you'd like us to exclude your sessions from collection directly, email hello@kidcampconnect.com.
• Feedback attachments: the screenshot and plan-snapshot checkboxes in the feedback form are opt-in per-submission. Uncheck them before sending if you don't want to attach.

Data retention

• Waitlist email: kept until you ask to be removed or until the service launches publicly in your area, whichever comes first.
• Submissions: kept indefinitely as part of the directory, or as reference for follow-up.
• Access cookie: 30 days, then expires automatically.
• Browser localStorage: kept until you clear it.
• Precise location: processed in the request and not stored server-side. Your saved approximate location (latitude, longitude, and nearest ZIP) lives in browser localStorage on your device until you clear it.
• Analytics and replay: retained per each provider's stated retention period (currently up to 14 months for Google Analytics events; up to 30 days for PostHog session replays). When we add or change providers, we update this list.
• Feedback submissions: kept indefinitely as GitHub issues in our private repository, including any screenshots or anonymized plan snapshots you chose to attach. Retained for product-improvement reference.

Security

We're a two-person side project hosted on a major platform (Vercel). We follow standard practices: no passwords stored, an HTTP-only and signed access cookie, HTTPS everywhere. We can't promise perfect security; if we become aware of a breach involving your personal information, we will notify affected users in accordance with applicable state laws.

Changes

We will update this page when our practices change in any material way. The “last updated” date at the top reflects the most recent change. If a change materially affects how we handle data you have already provided, we will reach out to let you know.

Contact us

Email: hello@kidcampconnect.com