Privacy at Neural Critic
Neural Critic uses the minimum data needed to provide reader accounts, community features, newsletters, and consent-based publication analytics.
Effective: 7 September 2026
Reader accounts and Google Sign-In
If you choose Sign in with Google, Neural Critic uses Supabase Auth to receive the basic identity information needed to create or sign in to your Reader account. The requested Google scopes are limited to openid, email, and profile.
- Neural Critic may receive your Google account identifier, name, email address, and profile image.
- This data is used to authenticate you, identify your Reader account, and display your chosen reader identity in account/community features.
- Neural Critic does not request access to Gmail, Google Drive, Google Contacts, or other Google account content.
- Google Sign-In data is not sold and is not used by Neural Critic for advertising or ad personalization.
You may revoke Neural Critic's Google access from your Google Account settings. Revoking provider access does not automatically delete community content you previously submitted.
Community and account data
When you use Reader features, Neural Critic may process account/profile information, comments, reactions, follows, reports, and related timestamps so those features can work. Supabase provides the authentication and database infrastructure for these features.
Newsletter data
If you join the Neural Critic newsletter, the email address you submit and subscription status are stored through the publication's Supabase backend for newsletter operations. Neural Critic uses Resend to maintain the Weekly Drop delivery list and send newsletter emails. Newsletter signup analytics fire only after a successful signup. You can unsubscribe using the link included in newsletter emails, and provider opt-outs are reconciled back into Neural Critic's subscription records.
Optional analytics
Google Analytics loads only after a reader allows analytics. Measurement is used for publication-level signals such as page and article views, reading depth, searches, successful newsletter signups, shares, follows, likes, and outbound-link domains.
Neural Critic's analytics implementation is designed not to send email addresses, comment text, account names, or other reader-entered content to Google Analytics. Advertising storage and personalization signals remain disabled.
Local preferences
The site may store local browser preferences such as light/dark mode, analytics consent, and short-lived session state needed to prevent duplicate measurement or preserve reader experience.
Service providers
- Supabase supports Reader authentication, publishing, community features, and newsletter subscription records.
- Resend processes newsletter delivery, delivery-list membership, and unsubscribe suppression for the Neural Critic Weekly Drop.
- Google provides optional Google Sign-In and, only with reader analytics consent, Google Analytics measurement.
- GitHub Pages serves the public Neural Critic website and static assets.
- Cloudflare provides domain registration, DNS, and email-routing services for neuralcritic.net.
Your choices
You can change the analytics preference on this page at any time. You can sign out of your Reader account, revoke Google access from your Google Account, and unsubscribe from the newsletter using the unsubscribe link included in newsletter emails. For account or privacy questions, email [email protected].
Data retention and security
Neural Critic retains account, community, newsletter, and operational data for as long as reasonably needed to provide those features, protect the publication, resolve abuse or security issues, and meet applicable obligations. Reasonable technical safeguards are used, but no online service can guarantee absolute security.
Policy changes
This policy may be updated as Neural Critic's features or service providers change. Material updates will be reflected by changing the effective date on this page.
Use of Google user data is limited to the practices described in this policy and is intended to comply with the Google API Services User Data Policy.