Campfetti
← Back to comparison table

Privacy Policy

What this site collects, what it does not, and how to opt out.

Effective date: October 20, 2026

The short version

Campfetti has no accounts and no logins, and it does not ask for your name, your child’s name, or your contact details. If you save a camp, that shortlist stays on this device only. It is not an account, and the site does not ask for an email to keep it. Chip-in payments, if you choose to make one, happen on Stripe, and this site never sees the card or Apple Pay details. It uses a product analytics tool to count visits, see which features get used, and record where on the page people click, so that the site can be improved. It does not sell your information to anyone, and it never has.

The one thing worth knowing specifically: when you use the filters, the analytics event includes what you filtered by, including the age or grade you selected and the words you type in the search box. That information is not connected to your name, because the site never learns it.

The sections below are the precise version.

1. Who this is from

This site is operated by Molly Rempe. Questions, and any request about your information, go to hello@campfetti.com.

2. What the site does not collect

There are no user accounts, so the site does not collect names, email addresses, mailing addresses, phone numbers, or passwords. The Support page does not take a payment itself. If you choose to chip in, the button opens Stripe, and the card number and Apple Pay details stay with Stripe. This site never sees them. A Venmo button is not shown unless a Venmo link is configured for that deploy.

It also does not:

3. What is collected automatically

The site uses PostHog, a product analytics service, to understand how the comparison table is used. Data is processed on PostHog’s United States infrastructure.

Page and device information. When you visit a page, PostHog records that the visit happened, along with the page address, the site or search engine you arrived from, your browser, operating system, device type, and screen size.

Approximate location. PostHog derives an approximate location — roughly city and region level — from your IP address. This is used to understand how much of the audience is actually in Colorado, which is one of the few ways to tell whether the site is reaching the families it is for.

A visitor identifier. A randomly generated identifier is stored in a cookie and in your browser’s local storage so that returning visits can be recognized as the same browser. It is not linked to your identity and it does not follow you to other websites.

Specific interactions. These deliberate actions are recorded, each with a little context: applying a filter, changing the sort order, switching between table and card view, grouping by provider, showing or hiding past sessions, saving or unsaving a camp, opening a saved list, sharing that list, opening a list someone else shared, choosing a season from the season heading, choosing a region tab, clicking through to a camp’s official source, sharing or copying the page link, starting a correction or missing-camp email, opening the Support page, choosing a support amount, and choosing Apple Pay or card on that page. If a Venmo link is configured, choosing Venmo is recorded the same way.

Click positions, for heatmaps. Where you click on the page is recorded as a coordinate, along with your window size and scroll depth, so that it is possible to see which parts of the comparison table people actually use and how far down the page they get. This is genuinely useful — it is how the site learned that most clicks happen below the first screenful, which affects where important controls belong. What is recorded is the position of the click and nothing about what sits there: no element text, no field contents, no keystrokes. Heatmap data is not linked to your identity, and it is kept for 90 days.

Page performance. Standard web performance measurements — how quickly the page loaded and became usable, and how much the layout shifted while loading — are collected automatically for the page you are on. These describe the page and your connection speed, not you.

What the filter event contains. To be direct about this, because it is the least obvious item on the list: when you apply a filter, the recorded event includes the filter values you chose. That includes the age or grade you selected, the date range, maximum price, day length, duration, and the words in the search box. The search words are sent once, about half a second after you stop typing, not on every keystroke. Clearing the search box sends that event right away. It is not connected to any name or contact information, because the site does not have yours. On this directory, those filter values are also stored in the page address so a shared link opens the same comparison. The address can include a selected age or grade and the search words.

What clicking a camp link records. Following a listing to a provider’s site records which provider, session, listing id, and link you clicked, plus the hostname of that link and a snapshot of the filters that were active at the time (the same kinds of values as the filter event, including the search words when a search is active). A click from your saved list or from a shared shortlist also records that it came from the saved list. That is used to tell whether the site is actually helping people reach camps, and which destinations and filter combinations those clicks come from. The provider does not receive any information about you from this site.

What the Support page records. Opening Support records that the page was opened. Choosing $5, $15, $30, $50, or a custom amount records that dollar amount. Choosing Apple Pay or card records that method and the amount. If a Venmo link is configured and you choose it, that method is recorded the same way. It does not record a name, email, or payment details. The payment itself happens on Stripe, not on this site.

Saved camps, on this device. Choosing Save stores that listing’s id, name, provider, season, region, dates, price, category line, and official link in local storage on this device. The list is not an account, the site does not ask for an email to keep it, and it is not written to the camp database. Sharing builds a link that contains those listing ids. Saving, unsaving, opening your saved list, sharing it, and opening a shared link are recorded. Those events include the camp name, provider, season, region, listing id, and how many camps are on the list. Sharing also records whether the device share sheet or a copied link was used. Opening a shared link records how many camps were on it, whether this device already had a saved list, and how many of the shared camps were already saved. Those events are not tied to your name, because the site does not ask for one.

4. Camp data requests

The camp listings are loaded from this site’s own server, which holds the database credentials. Your browser never connects to the camp database directly, and no information about you is sent to it or stored in it.

5. When you email

The correction and missing-camp links open your own email program. If you send a message, Molly Rempe receives whatever you chose to include — typically your email address and the details of the correction — through Google’s Gmail service. That message is used to check and fix the listing, and to reply to you. It is not added to a mailing list, and there is no newsletter.

6. Hosting

The site is hosted on Netlify, which keeps standard server logs including IP addresses, as any web host does, for security and reliability purposes.

7. Advertising

If advertising is running on this site, it is supplied by Google AdSense. Google and its partners may use cookies and similar technologies to serve and measure ads, and may use information about your visit to this and other sites to show you ads. This is the one part of the site that involves tracking across websites, and it is worth understanding.

You can control this directly, and it does not require asking Molly Rempe:

Advertising never affects which camps appear on this site or how results are ordered, and no camp provider pays to be listed. See the Terms of Use for more on that.

8. Cookies and similar technologies

The site uses two kinds, and no others:

There are no marketing, social media, or cross-site tracking cookies beyond those. You can block or delete cookies in your browser settings; the comparison table works fine without them, and blocking them simply means visits are not counted.

A saved camp list is kept in local storage on this device, which is separate from the cookies above. Clearing this site’s stored data on this device removes the list. Blocking cookies does not remove a list that is already stored.

9. Children

This site is built for parents and caregivers, not for children, and it is not directed to children. It does not knowingly collect personal information from anyone under 13. The age and grade filters are numbers used to match camp sessions; they are not tied to a child’s name or any other identifying information, because the site never asks for it.

If you believe a child has sent personal information through the email links, contact hello@campfetti.com and it will be deleted.

10. How long information is kept

Analytics events are retained for 12 months, and heatmap click data for 90 days, after which they age out. Email correspondence is kept as long as it is useful for handling and verifying the correction it concerns.

11. Your choices

Whatever your state’s law requires, requests are honored here as a matter of practice:

Colorado residents have rights under the Colorado Privacy Act, including access, correction, deletion, and opting out of targeted advertising. This site is small enough that it very likely falls below the thresholds that make those obligations binding, but the requests above are honored regardless.

12. Security

The site stores no accounts and does not store payment or card details. A saved camp list stays on this device and is not stored on the server as an account. Optional support is handled by Stripe, not by this site. Database credentials are held server-side and are never sent to your browser. No method of transmission over the internet is completely secure, and no absolute guarantee can be made.

13. Changes

This policy will be updated when the site’s data practices change, and the effective date above will change with it. Material changes will be reflected here rather than announced individually, since there is no mailing list to announce them to.

14. Contact

hello@campfetti.com for anything on this page.