neurodance Cookie Policy

1. What this policy covers

This Cookie Policy explains the cookies and similar local storage that neurodance ("we," "us," "our") uses when you visit neurodance.ai or use the neurodance app, and the choices available to you. It supplements our Privacy Policy.

A cookie is a small text file a website or an embedded third-party service stores in your browser. We also use browser local storage, which behaves similarly but is not sent to a server automatically with every request.

2. We use cookies only where they are necessary

Apart from the advertising measurement described in section 3, neurodance does not set other advertising, retargeting, cross-site tracking, or third-party analytics cookies. Our own product-reliability telemetry (AWS CloudWatch RUM) is configured to run without setting any cookie at all. Your signed-in session is kept in your browser's local storage, not a cookie.

The cookies below are set only where they are needed to keep the service secure, prevent fraud and abuse, or complete a connection you asked for. Some are set by the third-party providers we use for those specific functions, on their own domains.

3. Cookies we use

Bot and fraud protection (Cloudflare Turnstile) — set by challenges.cloudflare.com when neurodance needs to confirm a request (such as sign-up or a form submission) is coming from a real person rather than a bot. Session-length, first- or third-party depending on your browser's settings.

Payment fraud prevention (Stripe) — set by js.stripe.com and api.stripe.com on checkout and billing pages, so our payment processor can screen a card payment for fraud before it is charged. Typically expires within a year if not renewed by a further visit to a Stripe-hosted page.

Connected-platform sign-in (neurodance) — a short-lived, first-party cookie set on our own domain only while you are connecting a social or storage account (for example Instagram, Meta, YouTube, Google Drive, or Dropbox). It binds the authorization callback to your browser session and is not used for any other purpose. It is marked HttpOnly, so it cannot be read by page scripts.

Advertising measurement — OpenAI Ads scripts from bzrcdn.openai.com are loaded only if you allow Marketing cookies. Meta scripts from connect.facebook.net measure page views and funnel events through the first completed purchase, even if you have not allowed Marketing cookies. Matching page-view, lead, sign-up, and checkout-start events are also sent server-to-server through Meta's Conversions API with the page URL, a shared event ID for deduplication, Meta browser/click identifiers where available, and the request IP address and browser user-agent. After an account becomes a paid subscriber, Meta scripts and events are enabled only if you allow Marketing cookies. The first completed purchase is also sent server-to-server through Meta's Conversions API with transaction amount, currency, purchase type, and hashed email or account identifier where available. These integrations do not receive prompts, uploaded content, or payment-card details.

Third-party sign-in and connection providers — when you sign in with Google, or connect Instagram, Meta, YouTube, TikTok, X, Google Drive, or Dropbox, that provider's own site (for example accounts.google.com) may set cookies under its own policies while you authenticate. neurodance does not control these and they are not shared with us beyond the authorization result.

4. Your choices

Most browsers let you view, delete, and block cookies in their settings, and offer a private or incognito mode that discards cookies when you close the window. Blocking cookies from challenges.cloudflare.com or the Stripe domains may prevent you from completing sign-up, sign-in, or a purchase, since those cookies are required for the security checks on those specific pages to run. Blocking cookies does not sign you out of neurodance, because your session lives in local storage rather than a cookie.

You can also clear neurodance's local storage at any time from your browser's site data settings; doing so signs you out and clears locally cached preferences.

The cookie notice shown in the app lets you Accept All or Manage Cookies to choose Analytics and Marketing preferences individually. Marketing controls OpenAI Ads and continued Meta measurement after you become a paid subscriber; it does not stop Meta funnel measurement before a first purchase. Analytics controls the visitor ID described in section 5. Your choice is stored in your browser and shared across our sites, and you will not be asked again unless you clear neurodance's site data.

5. Usage data (not a cookie)

Separately from cookies, neurodance records first-party usage events when you use the site or app, as metadata (IDs, counts, timestamps), never the content of your prompts, uploads, or imports. These include pages viewed, actions taken, time spent, errors, things you create or connect, billing and subscription events, and whether emails we send you are delivered, opened, or clicked. While you browse, a random session ID is kept in your browser's session storage and cleared when you close the tab. If you allow Analytics cookies, we also set a random visitor ID cookie (neurodance-visitor, up to 400 days) so we can tell returning visitors from new ones; it is deleted if you turn Analytics off. Detailed click and page-timing records are deleted after 90 days; we keep daily activity totals. When you sign up, the campaign details you arrived with (such as UTM tags) are saved to your account. This isn't covered by the cookie categories above; it's described in our Privacy Policy under Self-Service and Enterprise Data.

6. Changes to this policy

We may update this policy if the cookies we use change, for example if we add an analytics or advertising integration in the future. We will post the revised policy here and update the effective date. You can revisit your choices through your browser's neurodance site-data controls.

7. Contact

Questions about this policy: email support@neurodance.ai.