Privacy

Forms and email

We store the information you submit, along with submission time, source, review status and your event email preferences where applicable. We use a salted IP hash and browser user agent to limit abuse. Supabase stores these records; Resend processes the email content to send confirmations and notify the organizer. Travis Johnson reviews host and speaker submissions.

Joining the event update list gives local hosts permission to send event updates for your chosen metros. Repeating signup adds a metro to your preferences. Choosing All Southern California includes every metro. It does not subscribe you to a separate weekly digest. Host and speaker applications do not subscribe you to marketing email.

Submissions are saved before email delivery is attempted. A confirmation can be delayed. Event emails include an unsubscribe link: opening it shows a confirmation page, and confirming stops event updates to that email address across all metros.

Pageviews and ambassador attention

We measure which pages are useful with a first-party endpoint. It records the page path without its query string, the referring website’s origin, a coarse screen-width category, and sanitized campaign source, medium and name when supplied. A daily pseudonymous identifier helps limit repeated traffic. We do not store an IP hash or user agent in pageview records, and this measurement does not use cookies or browser storage. Pseudonymous data is not the same as anonymous data.

We also count visits to named ambassador profiles, profile cards visible for at least one second, and clicks on ambassador names, social links, websites, Luma profiles and listed events. These are separate measures. Records include the public ambassador identifier, link category and the local event path when applicable; they do not contain external destination URLs or link text. We honor browser Do Not Track and Global Privacy Control signals.

Optional product analytics

PostHog analytics are off until you choose Accept analytics. Declining does not affect event links, email signup or other site features. If you accept, our server sends sanitized pageviews, marked registration button clicks, other event and community link clicks, signup form starts, categorized signup failures and successful event-email signup requests to PostHog in the United States. Events include the local page path, referring website origin, sanitized campaign labels, coarse screen-width category where available, and public event details such as event ID and metro.

Acceptance creates a random browser ID in the first-party cs_analytics_id cookie for up to 90 days. We use local storage under cs_analytics_attribution_v1 to retain the first consenting arrival and the most recent tagged or externally referred arrival, including source, medium, campaign, local landing-page path and referring website origin, for measurement during that ID’s lifetime. Local-storage records are cleared or replaced on the next site visit after expiry; they may remain on the device until then or until you clear browser data. This helps connect repeat visits on the same browser to event clicks and email signup requests. Direct or internal navigation does not overwrite the last known campaign. Different browsers, cleared storage and renewed IDs are not joined. These identifiers are pseudonymous, not anonymous.

The cs_analytics_consent cookie remembers your accept or decline choice for up to 180 days. Use Analytics choices in the footer to change your choice. Declining after acceptance removes the browser ID and locally stored attribution and stops future PostHog collection; it does not automatically erase events already received by PostHog. Do Not Track and Global Privacy Control keep this optional analytics off and remove the local analytics ID and attribution when the site checks those signals.

We do not send form contents, email addresses, raw visitor IP addresses or browser user agents to PostHog, create person profiles, or record your screen. A saved signup request may be a repeat or preference change; it does not prove a new subscriber or email delivery. A registration click does not prove event registration. PostHog retains received analytics under the project’s retention settings. The 90-day browser-storage limit and the first-party cleanup below do not delete PostHog’s records. Contact us to ask about data removal.

Registration attribution and operational monitoring

Registration links identify Claude Community SoCal and the event or link placement with campaign labels. If you accept optional analytics, Luma links can also carry the last known campaign source, medium and campaign name. We do not put your browser ID or form answers in these links. Luma processes registrations under its own privacy practices. We reconcile aggregate registration status and campaign counts separately from link clicks; attendee names, email addresses and answers are not sent to PostHog.

To detect site failures, we retain limited operational records such as failure category, timestamp, mail-worker health and hashed delivery-event identifiers. Signed Resend delivery notifications are checked, but their recipient addresses and message content are not retained in these monitoring records. Operational records are removed after 30 days. Synthetic health probes are labeled separately from visitor analytics.

Retention and choices

Pageview and ambassador interaction records and form security metadata are removed after 30 days by scheduled maintenance. Successful email jobs are retained for 30 days and submission receipts for 90 days. Unresolved delivery records may remain while an issue is investigated. Applications and signup records remain until removal is requested; consent and opt-out records may be retained to honor your preferences.

To ask about, correct or remove your information, email travis@claudesocal.com. We do not sell attendee lists or share them with sponsors.

Hosting and external links