Privacy Policy
This product keeps browsing password-free and account-free, guest planning browser-local, account planner import explicit, and optional email signup narrow. These disclosures describe the current parent-facing data flows.
Minimal parent-facing collection
This page reflects the current implementation and product guardrails. It is not legal advice.
What we collect
For optional email updates, the current product stores only the parent email address provided, the surface where it was submitted, and the page path tied to that request. For update reports, the product stores the report message, the page path, optional provider or program references, and an optional reply email. For basic product analytics, the browser may keep an anonymous identifier so repeated visits can be counted without requiring an account.
Saved and planning data in this browser
Saved programs, narrowed options for closer review, likely week choices, held weeks, and recent fit filters such as age, broad area, camp type, day format, and registration timing are stored in this browser's local storage. They are used to keep realistic options, likely registration targets, and open-week search links visible on this device. Guest planning does not require sign-in and does not store child profiles on the server.
Optional account planner import
If a parent signs in and explicitly imports this browser's planner, the account planner stores the parent email, optional display name from the auth provider, stable external auth subject, selected program references, compare/planned flags, and optional planned published session references. The import does not store child names, exact birthdates, schools, addresses, medical details, payment information, free-form child notes, or provider-visible preference data.
What we do not collect
Browsing listings does not require a password or account. The current optional email update, correction, and local planning flows do not ask for child names, medical details, payment information, or other unnecessary child data.
How we use it
Email update requests are stored only so the directory can follow up about launch updates, registration-timing follow-up, or broader timing coverage. Correction reports are stored only so listing details can be reviewed against source pages and fixed when needed.
Current limits
Automatic timing emails are not live yet. During parent testing, stored email update and correction records are reviewed at least monthly and parent email addresses should be deleted or anonymized within 12 months unless an active follow-up still requires them. Browser-local planner data stays on the device until the browser clears it or the parent clears site storage. Account planner selections stay on the account until the parent replaces or deletes them from the account tools.
Deletion and unsubscribe requests
The dedicated privacy/deletion form is not live in this parent test yet. Right now, browser-local saved and planning data can be cleared on this device by clearing this site's stored browser data, and email follow-up can be stopped by replying stop or unsubscribe in the same outreach or observation thread. Signed-in parents can still delete account planner selections from the account page when account sync is enabled; that clears saved planner selections but does not delete the auth provider identity row. The dedicated privacy request path will handle email update deletion, correction-contact removal, and broader account identity removal only after dedicated privacy-request support is enabled and verified. Do not include child details in bug or correction forms while that path is paused.
What is available now, and what still waits
The dedicated privacy/deletion request form is still paused until dedicated privacy-request support is enabled and verified. The current parent test still has a few immediate cleanup and follow-up paths.
Available now
Clear this browser's local site storage if you want saved and planning data removed from this device right now.
Reply stop or unsubscribe in the same outreach or observation thread if you do not want email follow-up.
Use bug or correction reports only for product or listing issues, not for identity or deletion requests.
Still paused
Use the dedicated privacy/deletion form only after dedicated privacy-request support is enabled, verified, and the paused state is removed.
Until then, treat this page as support context for the current parent test rather than as a completed identity-removal workflow.
Start by browsing, then use trust pages as support.
If you landed here before opening the directory, start with browse. Narrow to realistic options first, then compare or check timing only when a few camps still matter.
Browse first, confirm details on the provider source page, then come back here if the privacy or trust copy still conflicts with current product behavior.