Skip to content
Syntax

Privacy / launch readiness

Privacy Policy

This policy explains how Synthetix handles personal data for the public AI and software engineering blog. It reflects the current codebase and launch plan: newsletter, contact, security, error monitoring, hosting, database services, consent controls, GA4, AdSense, and Web Vitals are covered; a Google-certified CMP remains an external launch requirement where personalized ads require it.

Last updated: 2026-05-09Version 1.3
Controller
Synthetix is operated by Bruno Brizolara. Privacy requests go to hello@synthetix.ai.
Active public data
Newsletter email and consent, contact form fields, theme preference, technical logs, and error diagnostics.
Consent-gated data
GA4 and AdSense load only after visitor consent and production environment configuration. Personalized ads in the EEA, UK, and Switzerland still require a Google-certified CMP.
Review status
This is implementation copy, not a legal opinion or external compliance certification.

01 / Controller

Controller and privacy contact

Synthetix is an independent publication operated by Bruno Brizolara. Where privacy laws use terms such as controller, business, or controlador, Synthetix is the party that decides why the public site collects and uses the data described here.

Use hello@synthetix.ai for access, deletion, correction, portability, objection, opt-out, consent withdrawal, or other privacy requests. If a request depends on your jurisdiction, identity verification, or legal limits, we will handle it according to the applicable rule and the data we actually hold.

02 / Data

Data we collect

You can read the public content without creating an account. The public site collects data only when you submit a form, subscribe to the newsletter, choose a theme, trigger security checks, or when routine hosting and error-monitoring systems process technical request data.

Admin authentication is separate from ordinary readership. Supabase Auth cookies may be used on admin routes, but public readers are anonymous unless they submit a contact or newsletter form.

  • Newsletter: email address, locale, explicit consent, source label, confirmation token, unsubscribe token, subscription status, and timestamps.
  • Contact form: name, email, selected subject, message, locale, optional Cloudflare Turnstile token, and hashed IP/user-agent values for rate limiting and abuse prevention.
  • Preferences: the bb_theme cookie stores only light or dark theme preference for one year.
  • Diagnostics: Sentry may receive error events, stack traces, request URLs, device/runtime details, and breadcrumbs. The app disables default PII and strips sensitive headers in server and edge events.
  • Hosting/API logs: the active web host and Fly.io may process request metadata such as IP address, route, timestamp, user agent, and response status when the site is deployed.
  • Analytics and ads: Google Analytics 4 and Google AdSense are consent-gated and require production IDs before they load. Web Vitals are reported without setting cookies. A Google-certified CMP remains required before serving personalized Google ads to users in the EEA, UK, or Switzerland.

03 / Use

Why we use data

We use personal data to operate the site, send and manage newsletter subscriptions, respond to contact requests, prevent spam and abuse, keep admin access secure, diagnose errors, measure launch performance, and support monetization once ads and consent tooling are configured.

Where a legal basis is required, the likely bases are consent for newsletter signups, optional analytics, optional ad personalization, and non-essential cookies; legitimate interest for security, abuse prevention, error diagnostics, service reliability, and basic audience measurement; contract or pre-contract steps when responding to a request you send; and legal obligations where a law requires us to keep or disclose information.

04 / Cookies

Cookies, consent, analytics, and ads

Today, the public app uses the bb_theme cookie for theme preference and first-party browser storage for consent choices. Admin and authentication areas may use Supabase session cookies. GA4 and AdSense are not loaded until the visitor grants the relevant consent and production IDs are configured.

Before serving personalized Google ads to users in the EEA, UK, or Switzerland, the launch plan requires a Google-certified CMP integrated with the IAB Transparency and Consent Framework. Google publisher policies also require clear disclosure that Google and other ad technology providers may use cookies, web beacons, IP addresses, or other identifiers when ads are served.

If any non-Google ad network or additional Google ad technology provider is enabled, the production CMP or vendor list must identify that party and this policy should be updated before that provider serves ads.

The consent controls default Google Consent Mode v2 to denied for analytics storage, ad storage, ad user data, and ad personalization, then update those signals after the visitor chooses.

05 / Vendors

Vendors and international transfers

Synthetix relies on service providers to host the site, store data, send email, monitor errors, protect forms, and, after launch configuration, measure traffic and serve ads. These providers may process data in the United States or other regions.

We avoid promising a specific transfer mechanism unless it is confirmed for the vendor and account. The launch checklist should verify each production vendor's data-processing terms, region selection, sub-processors, and transfer safeguards before AdSense submission.

06 / Rights

Your privacy choices and rights

Depending on where you live, you may have rights to know what data is collected, access it, correct it, delete it, restrict or object to processing, withdraw consent, request portability, opt out of sale or sharing, limit certain sensitive-data uses, or complain to a privacy authority.

Newsletter emails include an unsubscribe path. Browser settings can block or delete cookies. If an ads/CMP layer is enabled, it must provide clear consent choices and revocation instructions for covered regions.

  • EU/UK-style rights include information, access, rectification, erasure, restriction, portability, objection, and valid consent withdrawal where consent is used.
  • LGPD-style rights include confirmation, access, correction, anonymization/blocking/deletion where applicable, portability, information about sharing, and consent revocation where consent is used.
  • California-style rights may include knowing, deletion, correction, opt-out of sale or sharing, limiting sensitive information use, and non-discrimination for exercising rights.

07 / Retention

Retention and deletion

We keep personal data only as long as needed for the purpose collected, security, abuse prevention, legal obligations, dispute resolution, or a valid operational need. The current implementation does not support the older fixed retention claims that appeared in this page.

Newsletter confirmation links expire in app logic after seven days. Subscription records are kept while the status and unsubscribe token are needed to manage consent, delivery, and suppression. Contact messages and diagnostic records should be deleted or anonymized when they are no longer needed or after a valid deletion request unless an exception applies.

08 / Children

Children's privacy

Synthetix is a general technical publication for developers and builders. It is not directed to children, and we do not knowingly collect personal data from children. If you believe a child provided personal data, contact hello@synthetix.ai so we can review and delete it where appropriate.

09 / Updates

Changes

We may update this policy when site features, vendors, legal requirements, or launch configuration changes. The page will keep an updated date and version so readers can see when the policy changed.

Data categories and retention

Data categories and retention
CategoryDetailsLikely basisRetention
NewsletterEmail, locale, consent, source, confirmation token, unsubscribe token, status, and timestamps.Consent and service operation.Kept while subscription status, unsubscribe, suppression, or legal records are needed; deleted on valid request where possible.
ContactName, email, subject, message, locale, hashed IP/user-agent for rate limits, optional Turnstile token, and timestamps.Responding to your request, abuse prevention, and security.Kept while the request, moderation, abuse prevention, or legal need remains; deleted or anonymized on valid request where possible.
Preferences and sessionsbb_theme stores light/dark preference. Admin areas may use Supabase Auth cookies.Site functionality and admin security.Theme cookie lasts one year unless cleared. Admin sessions follow Supabase/Auth configuration.
Diagnostics and logsError events, request URLs, device/runtime details, route metadata, status codes, and hosting logs.Security, reliability, debugging, and abuse prevention.Kept according to production provider settings and removed when no longer needed for those purposes.
Analytics and adsGA4, AdSense, ad identifiers, consent records, and CMP signals once launch configuration enables them.Consent where legally required; legitimate interest for limited, non-personalized measurement where allowed.Will follow the configured Google/CMP retention settings and user consent choices.

Vendor status

Vendor status
VendorRoleStatusData involved
SupabasePostgres database, storage, and admin authentication.Active in the app architecture.Newsletter records, contact messages, generated content data, storage objects, and admin session data.
ResendTransactional newsletter and contact email delivery.Active when email sending is configured.Recipient email, locale, confirmation and unsubscribe URLs, and contact acknowledgement data.
SentryWeb and API error monitoring.Active only when SENTRY_DSN or NEXT_PUBLIC_SENTRY_DSN is configured; there is no fallback DSN in this checkout.Error details, stack traces, URLs, device/runtime information, breadcrumbs, and stripped request headers.
NetlifyNext.js web hosting for the public site.Launch infrastructure, not proven as deployed in this checkout.Request logs, IP-derived location, deployment telemetry, and edge/network metadata when deployed.
Fly.ioPlanned NestJS API hosting.Launch infrastructure, not proven as deployed in this checkout.API request logs, IP address, route metadata, runtime logs, and app hosting metadata when deployed.
Cloudflare TurnstileOptional contact-form anti-abuse challenge.Only loaded when a Turnstile site key exists and the contact form receives focus.Challenge token and technical browser signals used to verify the form submission.
GoogleSearch Console, GA4, AdSense, and Google-certified CMP support.GA4 and AdSense are implemented as consent-gated public code. Search Console remains external account setup. Certified CMP setup remains external for covered ad regions.Search performance data, analytics events, ad identifiers, cookies/local storage, consent signals, and ad-serving data once configured.