Privacy policy

Jon Budish Newsletter · Updated October 15, 2026

Reading and reader accounts

Articles are publicly readable. Reader accounts use an email address and password managed by Supabase Authentication. We store your first and last name, optional profile photo, comments, replies, and article reactions to provide account and discussion features. Your name appears with your participation. Signing up does not automatically subscribe you to newsletter emails.

Newsletter recipients

Jon and the site administrators maintain newsletter recipient email addresses and available contact names. Recipient lists are not public. Multiple addresses supplied for one recipient may be stored separately. Contact Jon to request removal from the mailing list.

Newsletter email preferences

Creating a website account does not subscribe you to newsletter emails. Signed-in readers can separately subscribe or stop delivery for their verified account email under Newsletter emails. Existing newsletter subscriptions remain in place until changed. Reply notification preferences are separate.

Google and Gmail connection

The author Gmail connection requests the connected account’s email identity and permission to send email on its behalf. It does not request permission to read the inbox or Google contacts. This connection is restricted by the website to Jon’s sending account. Google authorization credentials are encrypted in storage and used by server-side features; they are not displayed to readers.

Google user data is used to identify the connected sender and support author-authorized newsletter sending. It is not sold, used for advertising, or used to train artificial intelligence models. The use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Services and cookies

Vercel hosts the website. Supabase provides authentication, database, and photo storage. Resend delivers account-related emails. Google provides the optional author Gmail connection. These services process the information needed to perform their functions. Authentication cookies keep you signed in; browser storage remembers text size, reading-theme and author/reader-view preferences.

Readership analytics

A first-party browser identifier, stored for up to 30 days, estimates article readership. When a published article opens, the site records the article, UTC date, browser identifier and, for signed-in readers, account identifier. A separate flag records ten seconds of visible reading. Repeat views of the same article on the same browser and day are counted once. Administrators see aggregate readership and account statistics; these estimates do not identify anonymous people. Clearing cookies or switching browsers can change unique-reader estimates. No IP address is stored in the readership table. Site-wide analytics also record page paths without query strings, page-view identifiers, the same anonymous browser identifier, and estimated active seconds. Time pauses when the page is hidden or unfocused, or after one minute without interaction. Administrators see aggregate visitor counts and time estimates, not the identity of anonymous visitors. IP addresses, email addresses, URL query strings, and referrer URLs are not stored in the site-visit table.

Access and deletion

Authorized authors and administrators can manage the publication and recipient information. Data is retained to operate the publication until removed or no longer needed. You may request account, profile, comment, recipient, or connected-Google-data deletion by contacting jbudish1@gmail.com. Jon can disconnect Gmail in Author’s desk or revoke access through his Google Account permissions.

Contact

For privacy questions or data requests, email jbudish1@gmail.com.