Your Data

Last updated August 2026

What we collect

If you create an account, we store your email address and authentication data through Supabase, our auth and database provider. If you upload workflows, proofs, or datasets, that content is stored via Vercel Blob and associated with your account. We don't require an account to browse guides, tools, or the model library.

Newsletter

If you sign up for NeuralDrift Weekly, your email address is processed by Kit, our newsletter provider, for newsletter delivery and to create and manage your subscription. We don't send anything else about you to Kit beyond the page you signed up from. Every issue includes an unsubscribe link, and unsubscribing removes you from future sends.

Analytics

We use Vercel Analytics to understand aggregate traffic (page views, referrers, rough device/location data). It doesn't use cookies and doesn't track you across other sites. If a Google Analytics measurement ID is configured, NeuralDrift also sends the event names and non-identifying context described in this policy to Google Analytics. The measurement ID is disabled by default. Newsletter signup attempts and completions are tracked as events (which page they happened on), but your email address is never included.

Third-party services

Some tools on this site call out to external APIs to do their job — for example, Hugging Face for model/dataset metadata, and Google's Gemini API for auto-captioning in the training tool. Data you submit to those tools (like uploaded images for captioning) is sent to the relevant provider to generate a result and is not stored by us beyond your session unless you explicitly save it.

What we don't do

We don't sell your data, and we don't run behavioral ad targeting on this site.

Your controls

You can delete your account and associated uploads at any time from the dashboard, or by emailing us. Deleting your account removes your stored profile data; content you've shared publicly (like a published workflow) may need to be removed separately — ask and we'll take it down.

Contact

Questions about this policy or a data request? Reach out via the GitHub repo.