Legal

Cookie policy

1. Where we stand today

This website sets no advertising cookies, no analytics cookies, no attribution pixels and embeds no third-party media that sets cookies. That is not a promise about the future — it is a description of the current build, and the whole runtime dependency list is Next.js, React, the Supabase client libraries and the Sentry SDK described in section 5.

2. Essential cookies and storage

Essential cookies or browser storage may be used to keep you signed in, complete an account export or deletion, support secure authentication and recovery, and remember strictly necessary page state.

Two named preferences, so the list is complete rather than approximately complete: the beta pageremembers the language you chose, and the join page keeps your chosen language in the address bar so it survives signing in. Both are conveniences, neither is analytics, and neither leaves your browser.

3. The waitlist

The waitlist form uses no marketing cookies. It records your email address and consent metadata on the server, sends a confirmation email, and keeps only confirmed addresses. Unconfirmed entries are purged after 30 days.

4. Why there is no cookie banner

Because there is nothing to consent to. A banner asking permission for cookies that do not exist trains people to dismiss banners, and it would be the only dishonest thing on this site. The rule we hold ourselves to is the plain one: build the consent mechanism before adding the technology that needs it, not after.

5. Sentry, stated precisely

The website runs Sentry on the server only. It records our own errors: no browser SDK is loaded, nothing is set in your browser, and no identifier follows you anywhere. This is enforced by the build rather than by intention — the key is read from a server-only environment variable, so it is not possible to start reporting from a visitor's browser by mistake. Query strings, request bodies, headers, cookies and user data are dropped before an event is sent.

Before any browser-side Sentry is added, three things happen together: a consent mechanism, a change to this page, and a change to our own content-security policy — which currently blocks it.

6. Before we ever add anything non-essential

• A consent banner, with "reject all" exactly as easy as accept.
• Settings to change your mind later.
• Non-essential scripts blocked until consent is given.
• The consent version and timestamp recorded.
• This page, the subprocessor list, the privacy policy and the app-store disclosures all updated in the same change.

7. The app is separate

The mobile app has its own consent mechanism for optional SDKs. Crash reporting is off by default and asked for once, in plain words, at the end of onboarding — including for people who joined their household on this website rather than in the app. Analytics is not active. Consent is recorded with its policy version, and the gate stays closed until the answer is known, so a failure to read it can never mean sending.

8. Contact

privacy@visibleneeds.site

Version 21 August 2026. Written against the running system rather than from a template — section 1 is checkable against the site's dependency list, and section 5 against a single environment variable name. If something here does not match what the product does, the page is wrong and we want to know: get in touch.