Privacy, in plain language.
This starter page explains the current site behavior. Jared should review and complete it before launch.
Information you send
The contact form asks for your name, email address, and a description of your inquiry. Company, project type, budget, and timing are optional. The form also records the page from which it was sent. Do not include passwords, confidential credentials, or sensitive personal information.
How information is used
Inquiry information is used to understand and respond to your message. The website includes Vercel Analytics and Speed Insights to measure website usage and performance. Vercel Analytics also counts public service and inquiry link clicks, scheduling handoffs, inquiry form starts, and accepted submissions. These events contain public page paths and fixed destination labels, without form contents, email addresses, query strings, or fragments. They honor Do Not Track, Global Privacy Control, and the studio browser opt-out. A scheduling handoff does not confirm a booked meeting.
Site usage insights
The studio also keeps a private, first-party traffic dashboard. It counts page views and recognizes a returning browser with a one-year cookie. Firestore stores a random browser identifier in hashed form, first and most recent visit dates, page-view totals, broad country and first-level region, a broad device category, grouped traffic sources, referrer hostnames, email template and campaign labels, and article share channel labels. Email and article share links include those labels but no recipient identifier; product links pass through our site for an approximate aggregate count before redirecting. It does not store visitor IP addresses, cities, precise coordinates, full referrer URLs, URL query strings, or a long-term per-person browsing history. Your IP address is checked transiently to exclude studio traffic and limit abuse. Browsers sending Do Not Track or Global Privacy Control are excluded. Counts may be approximate if cookies are cleared or blocked.
How you found us
So the studio can tell which pages lead to project conversations, your browser remembers the first page you opened on this site, the referring site's hostname and any campaign labels in the link for 30 days, in local browser storage. This stays in your browser unless you submit an inquiry, in which case it is saved with that inquiry. It is not recorded when your browser sends Do Not Track or Global Privacy Control.
Optional chat contact details
After your first message, Codey asks whether you would like to share your name and email directly in chat. You can decline and continue chatting. When you explicitly share these details, they are saved as a private inquiry lead in Firestore with the project summary collected during your conversation. This lead is separate from the temporary chat history and does not subscribe you to marketing or send an inquiry email automatically.
Client project chat
Signed-in clients can ask Codey about their own organization's project progress, deliverables, and billing. The server checks membership for every request. These responses are assembled from client-visible portal records and Stripe invoices without sending private project or billing records to an AI provider. Client questions and responses are stored in temporary Firestore chat sessions with a 24-hour expiry, bound to the authenticated account. The client chat uses a separate essential conversation cookie. Private chat is not saved in browser local storage; signing out clears the displayed conversation. Payments and approvals require explicit action in the portal or Stripe.
Storage and access
Submitted inquiries are sent through Mailgun to the studio's configured inbox. When Firebase is configured, inquiries are also stored in Cloud Firestore. Access to these lead records is restricted to server-side operations and authenticated administrators whose Firebase user IDs are explicitly allowlisted. The server may temporarily use request network metadata for per-instance spam throttling; it is not added to the lead record. Mailgun and Firebase regions, accounts, and applicable provider terms must be confirmed by the studio before launch.
AI studio assistant
When enabled, the assistant sends your message, limited recent conversation context, and your collected project needs to Anthropic to generate a response. If Anthropic cannot provide a usable response and a fallback is configured, the same information may be sent through OpenRouter to a free model provider. Those providers may have different data handling practices. The assistant uses public studio information to explain services and collect a project brief. Do not send passwords, credentials, confidential documents, or sensitive personal details. AI responses can be mistaken; the team reviews your scope before discussing a quote.
A private Firestore conversation and project brief expire 24 hours after the conversation starts. Expired conversations are no longer used. Background deletion uses Firestore's configured expiration policies and is not immediate. Network addresses are processed for abuse protection; private usage records store a secret-based identifier instead of the raw address. Request quotas expire after their usage window. Providers handle information under their own terms and retention practices.
The assistant does not automatically send an inquiry or add you to an email list. You choose whether to review, edit, and submit a project inquiry. Submitted inquiries follow the storage and retention practices described on this page. Booking opens the configured scheduling provider, which has its own privacy practices; the assistant cannot confirm a booking.
Email lists and preferences
The studio's private admin tools can store contact lists, names, companies, contact sources, and records of marketing permission in Firestore. Submitting an inquiry does not automatically subscribe you to marketing. Marketing emails are sent through Mailgun with a visible unsubscribe link. An opt-out applies across all studio marketing lists and is preserved if your address is imported again. Delivery receipts, failures, complaints, and opt-outs may be recorded. Campaign emails use Mailgun tracking pixels to measure opens, and may use tracked HTML links to measure clicks once secure link tracking is configured. These events can be associated with the recipient and message. Mailgun may process network, device, and approximate location information for those events. Our private campaign records retain open/click counts, separating activity Mailgun flags as automated; our aggregate dashboard does not identify recipients. Opens and clicks do not prove that a person read an email. Our site also counts visits from tagged email links and approximate product link requests. Unsubscribe links remain direct, and inquiry notifications, operational alerts, and portal invitations have tracking disabled.
Live site activity
While a public page is visible, it also sends an anonymous activity heartbeat every 30 seconds. A private live dashboard shows browsers active in the last two minutes, their current public page, the public pages visited during that visit, broad country/region, and device category. This temporary list stores up to 500 unique public page paths without query strings or fragments. A new visit starts after 30 minutes without activity, and the previous visit's page list is replaced. These separate presence records carry an expiration field 30 minutes after the last heartbeat; automatic deletion is asynchronous after the studio enables the expiration policy.
Retention and requests
The studio has not yet chosen a retention period for inquiries and email-list records. Before launch, set a retention and deletion process. Historical analytics records carry a 400-day expiration field; the studio must enable Firestore's automatic expiration policy for those collections. You may use the contact page to ask about a submitted inquiry or email-list record and request that it be corrected or removed, subject to applicable legal requirements. A minimal opt-out record may be retained to prevent future marketing messages.
Cookies and third parties
Your selected color theme is saved in local browser storage; until you choose a theme, the site follows your device preference. The site-usage dashboard uses a first-party, HTTP-only cookie for returning visitor counts. The assistant uses a separate short-lived essential cookie to connect your browser to its private conversation. Chat messages and inquiry details are not stored in local browser storage; the first-visit details described above are. Cloudflare Turnstile verifies assistant requests in production and processes verification information. Firebase Authentication may use browser storage when an administrator signs in. External links are opened on services with their own privacy practices.
Contact
Use the contact page for privacy questions. A named privacy contact and final policy date should be added before launch.

