Effective November 13, 2026

Privacy

The short version: essential infrastructure keeps the site secure and running; analytics and advertising measure how it is used unless you choose essential only; and signups go to the tools that deliver what you requested. This page covers those site flows, account access for our products, separately chosen newsletters, and the choices you have. We do not sell personal information.

Who we are

Torta Studios, LLC. For anything privacy related, write to [email protected].

Hosting and essential security

Cloudflare sits at the edge of this site for caching, traffic delivery, bot detection, and abuse protection, and DigitalOcean hosts the application and its database. Those providers process connection data such as your IP address, user-agent, requested URL, and request headers as needed to deliver and secure the site. Cloudflare may set the essential, HttpOnly __cf_bm cookie for about 30 minutes to carry encrypted bot-management signals. It is site-specific and remains active regardless of the optional analytics choice. Sentry receives application errors and performance traces for operational monitoring whether or not optional analytics is enabled. Its SDK collection disables cookies, query strings, request and response bodies, authorization, attribution, reader access codes, IP/user fields, and local variables; error and trace payloads are scrubbed again before send, and browser tunnel requests omit ambient cookies and referrers.

Crawler measurement

We record visits from search and AI crawlers, and from agents that sign their requests, in PostHog to understand whether public pages are discoverable. Records contain the crawler name, vendor, verification result, verified signer, public route (or “other”), and HTTP status. IP addresses and signature headers are used only on the server for verification; no IPs, cookies, request headers, query strings, reader codes, or personal identifiers are sent. Each crawler uses one fixed agent identity and creates no person profile. This machine traffic measurement runs independently of optional visitor consent. Requests served or blocked by the edge are absent.

Analytics

Unless you choose essential only, we use PostHog and Google Analytics to understand pages viewed, buttons clicked, browser exceptions, and session recordings (all form and keyboard input is masked in PostHog recordings). Google Analytics traffic is routed through a Google Cloud measurement server we operate.

Our PostHog transport passes your IP address to PostHog so it can look up your approximate location (city, region, and country). PostHog keeps that location and discards the IP address; it is not stored with your events.

PostHog keys a signup person profile with a deterministic SHA-256 hash of the lowercased, trimmed email. For a guide signup, that profile also receives the submitted name and email, a random guide reader code, and guide-reader status; the event may include an email-provider category, guide, referral code, and stored ad click IDs. When Beehiiv tells us a subscription to The Proofing Room was created, by any route, PostHog records it under that same email hash with the Beehiiv subscription ID and Beehiiv's source labels (acquisition channel, UTM source, medium, and campaign). A field-guide signup made after you chose essential only here, and any signup through our MCP server, are the exceptions: PostHog gets nothing about those subscriptions. Subscriptions made on Beehiiv's own pages are always recorded. Confirmation, status, and deletion events are not copied into PostHog.

The Proofing Room's pages, run by Beehiiv, also load PostHog through our Google Tag Manager container, and The Proofing Room shows no consent banner. There PostHog records pages viewed and clicks, with no session recordings; your browser sends it to PostHog directly, and PostHog treats your IP address the same way as above. It reads the same PostHog browser identifier as this site, a first-party cookie for tortastudios.com and its subdomains, so a visitor to both sites counts once. Choosing essential only here deletes that cookie on this site; it does not change what The Proofing Room records.

Links in The Proofing Room's emails carry an opaque subscriber ID, Beehiiv's ID for your subscription, in a tsid parameter. Any site an issue links to can see it, including sites we don't run. When such a link opens this site or The Proofing Room's pages, the page removes the ID from the address bar right away. Unless you chose essential only here, our server then asks Beehiiv which subscription the ID belongs to and tells PostHog to join this browser's PostHog identifier to that subscriber's email-hash profile described above, so your visits count toward your subscription. Your browser never receives the email or its hash, and a browser already joined to one profile is never moved to another. The Proofing Room shows no banner, so there this happens unless you chose essential only on this site in the same browser. If you forward an issue, visits from its links may be joined to your profile. Each such visit is also counted, with only which of our two sites it reached and whether it joined, in PostHog under one shared label with no profile and in our database for our weekly internal summary.

Advertising

Unless you choose essential only, tags from Google, LinkedIn, Meta, and OpenAI may collect usage data to measure ad performance and build advertising audiences. For a field-guide conversion, OpenAI may receive your normalized email as a deterministic SHA-256 hash together with your IP address, browser user-agent, its __obref click-reference cookie when present, and the signup page URL. The deterministic email hashes used here and for PostHog are pseudonymous and matchable, not anonymous: SHA-256 does not reveal the email directly, but someone who knows or guesses it can hash it the same way and match it. It is not irreversible anonymization. We do not send OpenAI your plain email address. Choosing essential only blocks these ad conversion and audience signals.

When you sign up or book

This site has no newsletter signup form; The Proofing Room's own pages, run by Beehiiv, handle subscriptions. Our links to those pages pass through tortastudios.com/newsletter, which adds UTM labels: where the link sits on our site (the footer or the contact page) and, when attribution is allowed, the source, medium, and campaign of your first visit (see below), or otherwise tortastudios.com / website. Beehiiv records them if you subscribe there. A field-guide signup sends your name and email to our DigitalOcean-hosted database, Attio (CRM), Beehiiv, and Loops (contact and guide delivery); our D.B. Fresh service also sends those details to our internal Slack workspace, with whether they came through the form, an agent using the form as a WebMCP tool, or our MCP server. As the form says, a field-guide signup also subscribes you to The Proofing Room, our newsletter, without a confirmation email when you submit it in your browser yourself; when an agent or an automated browser submits it, Beehiiv asks you to confirm by email first, and so does signing up on The Proofing Room's own pages. Beehiiv delivers the newsletter and manages confirmation, active status, unsubscribes, and deletion; if your address unsubscribed from The Proofing Room before, a field-guide signup leaves it unsubscribed. The signup also tells Beehiiv the page you signed up on and which form you used, and records which kind of client submitted it (a browser, an automated browser, a declared or verified agent, an agent using the form as a WebMCP tool in your browser, or an agent using our MCP server), decided on our server without storing your IP address, browser user-agent, or request headers. It also tells Beehiiv whether you allowed optional tracking here (all or essential), so an essential-only signup stays out of PostHog. These delivery flows run even with essential-only consent because they perform the request you submitted.

When anyone joins The Proofing Room, through our field-guide form or any other route, Beehiiv notifies our site and we post the new subscriber's email, signup source labels (UTM source, medium, and campaign, Beehiiv's acquisition channel, the signup form and page, and the kind of client), and whether the subscription is active or waiting for email confirmation to our internal Slack workspace, update that post when you confirm, and record the subscription in PostHog as described under Analytics. We keep those labels and the subscription status without the email, along with confirmation, unsubscribe and spam-report events, in our database to post a weekly summary to the same channel.

When optional tracking is allowed, PostHog receives the profile data described above, and Beehiiv also receives where your first visit came from: the UTM source, medium, campaign, term, and content saved from it, or, without UTMs, a source and medium we derive from the site that sent you (for example google / organic, linkedin / social, chatgpt / ai, or direct / none), plus that site's address without any page or search. Guide links contain a random reader code used for access and share attribution; it identifies the link, never your identity, to other readers. The link in your guide email also carries a key that opens the guide in any browser you use; the address bar drops it on arrival, so links you copy or share never contain it. Our contact page loads an embedded Calendly scheduler once it is on screen or you touch it, even under an essential-only choice; Calendly receives connection data and any scheduling details you enter to provide the booking flow. Our separate PostHog and advertising events about that booking remain optional-gated.

When an agent acts for you

AI agents can use tortastudios.com's own tools: our MCP server at tortastudios.com/mcp, and the field-guide form, which Chrome can offer to an agent in your browser as a WebMCP tool. Reading and searching our content through them needs no personal details. An agent should ask for the field guide or The Proofing Room only when you asked it to, with your own name and email.

A field-guide request from our MCP server sends the name and email the agent gives to the same places as the form (our database, Attio, Beehiiv, Loops, and our internal Slack through D.B. Fresh) and answers the agent with the guide's PDF link. No consent cookie reaches the MCP server, so these requests send nothing about you to PostHog or the ad platforms and record no first visit. A Proofing Room request from the MCP server sends only the email, and the name if given, to Beehiiv. Either way, Beehiiv emails you a confirmation link and you join only if you click it.

Every agent signup is labeled as one. Beehiiv records the kind of client and the agent's name: for our MCP server, the name the agent's software reports for itself (for example “Claude Code”), or the product name in its user-agent when it reports none; for an assistant that identifies itself to our form, such as ChatGPT or Claude, that assistant. Both appear in the Slack post about the new subscriber. We do not store the agent's IP address or request headers.

The confirmation email then opens with one sentence saying who asked: “Your assistant, Claude Code, asked us to sign you up.” when we have a plain name, “An AI assistant asked us to sign you up.” when we don't, and “This signup came from an automated tool, not a person.” for a script or automated browser. Beehiiv keeps that sentence with your subscription as the signup_note field. A signup you make yourself in your browser has no such sentence.

We count every call an agent makes to these tools, in PostHog under one shared label with no profile and in our database for our weekly internal summary. A count records the tool, whether it worked and how long it took, the name and version the agent's software reports for itself (or the product name in its user-agent), and the MCP protocol version. For a search it also records the search words, lowercased and cut to 100 characters, with anything that looks like an email address or phone number removed, and how many results came back; for a read, the path of the page asked for. For the field-guide form in your browser, we count only that an agent filled it in, cancelled, or submitted it, and whether that worked. A count never includes the name or email given for the field guide or The Proofing Room, an IP address, cookies, or request headers, and because it identifies no one it is kept whatever your consent choice. Our database keeps only the tool, the outcome, and the agent's name.

Torta Studios products and The Proofing Room

Torta Studios products, including ChatGPT apps where offered, may use an identity provider you authorize for account access. We receive account identifiers and, when provided, your email address and its verification status to operate your account. Signing in, using a product, or accepting this privacy policy does not give us newsletter consent.

If you separately choose to receive The Proofing Room and your provider has verified your email, we automatically send that address to Beehiiv to enroll you. Beehiiv manages confirmation, delivery, and unsubscribes. For ChatGPT plugin enrollments, Beehiiv receives the chatgpt-plugin-user tag to identify where the enrollment came from. New subscriptions also include signup source labels.

The Proofing Room shares editorial material about building products, media, and AI, along with related Torta Studios product updates and offers. We do not use unrelated chats, recordings, transcripts, or other uploaded media for newsletter enrollment or marketing.

You can unsubscribe through the link in any newsletter email. Unsubscribing does not affect your account access. Necessary security, service, and support communications are separate from the optional newsletter. We keep suppression information to honor your opt-out and do not enroll you again just because you sign in later.

Consent, cookies, and attribution

The first-party torta_consent cookie has three states. Your first visit, from any region, sets the default state implicit for 90 days: PostHog, Google Tag Manager with Google Analytics and the Google, LinkedIn, Meta, and OpenAI ad tags, and first-visit attribution run from that first page, and the consent banner stays open so you can decline. Choosing accept all stores all; choosing essential only stores essential and turns all of them off. Either explicit choice lasts 180 days, and the default never replaces it. If the default expires before you choose, the next page sets it again. A missing or unrecognized value counts as no choice. We do not use your timezone or location to set it. A small essential localStorage notification containing only the consent transition and a random nonce wakes other open tabs; those tabs re-read the cookie rather than trusting the notification.

An HttpOnly first-party ts_attribution cookie keeps your first visit from outside our sites recorded while attribution is allowed, for 90 days: Google, Microsoft, or Meta click IDs; UTM source, medium, campaign, term, and content; the address of the external site that sent you, without any page or search on it (none for a direct visit); landing path; capture time; and inferred platform. Arriving from one of our own sites does not count as a first visit. We use it to connect a later signup, here or on The Proofing Room through our links, to the campaign or site that first brought you. Guide signups may copy the snapshot into the lead record, and PostHog signup events may receive its click IDs. Later visits and campaigns never overwrite the first touch. Choosing essential only in any tab updates every open tab and deletes this attribution cookie, exact PostHog tracking persistence, and the PostHog reader email-hash cookie while preserving consent, guide access, unrelated state, and PostHog's identifier-free opt-out marker. It stops future optional collection; it does not erase data already sent, which you can ask us to delete below.

A first-party guide reader cookie lasts up to one year so the requested guide remains accessible. On this site PostHog runs only when consent allows it, through an app-owned consent-checking transport, and its browser identifier cookie is set for tortastudios.com and its subdomains, so The Proofing Room reads the same one; advertising tags follow the same optional gate. Cloudflare's essential __cf_bm cookie is the security exception described above.

Retention and deletion

Lead records are kept until you ask us to remove them. Newsletter lifecycle records are managed in Beehiiv. Unsubscribing stops the newsletter; suppression information is kept to honor opt-outs. Session recordings and analytics follow the retention settings of PostHog and Google Analytics. Email [email protected] to access or delete anything we hold about you; deletion requests are forwarded to the services above.

Your choices

You can also opt out per platform through Google, LinkedIn, Meta, and OpenAI ad settings, or email us and we will handle it.

Changes

When the stack changes, this page changes in the same release. The effective date above always reflects the latest revision.