Privacy
The private workflow brief stays disconnected. Optional site analytics stay off unless you allow a small, first-party aggregate signal.
Your private-brief answers stay on that page
Your private workflow brief runs in your browser. Answers are held only in page memory. They aren’t submitted, sent to Cortex Partners, or written to browser storage. Clearing the brief, refreshing the page, or closing it removes them from the page.
Copy and print stay under your control
If you choose Copy brief, your browser handles the text through its clipboard. If you choose Print brief, your browser or operating system handles the print output. We don’t receive the copied or printed brief. If you’ve allowed optional analytics, the site may count only the fixed milestone label copy or print, never the brief or your selections.
Optional aggregate analytics
If you choose Allow, this site can count four event classes: a page view, an authored call-to-action click, an authored section being reached, and an answer-free workflow milestone. Events use fixed labels written into the site; they don’t copy page text or your selections.
Optional analytics remain off until you choose.
What we exclude from optional analytics
No workflow answer, answer label, generated brief, recommendation, clipboard or print content, free text, arbitrary page text, query, hash, referrer, contact information, visitor identifier, advertising identifier, browser fingerprint, session replay, or raw error is included.
How we handle your preference and privacy signals
The browser stores only allow or deny under one analytics-preference key. An unset or unreadable preference means no analytics request. Global Privacy Control and the legacy Do Not Track signal suppress optional analytics even after Allow.
How we aggregate and retain counts
Allowed events go only to a same-origin Cortex Partners function. Raw enum-only event records are targeted for deletion within two complete UTC days after they are rolled into daily counts. Daily aggregates are capped at about 400 complete UTC days. Protected reporting returns counts, not raw events or visitor histories.
Site delivery still uses request metadata
The hosting and content-delivery service can process request metadata needed to deliver and protect pages, assets, and the optional analytics function. That can include an IP address, browser or device information, the requested path, and request time. This ordinary host processing is separate from the fixed event content described above.
The contact form is a separate submission
If you choose to use the contact form, Netlify processes and stores the name, work email, optional organization, workflow note, and processing acknowledgment you submit so Cortex Partners can reply. The private workflow brief does not transfer into that form. Do not include passwords, credentials, regulated data, or client-sensitive material.
Keep sensitive material out
Do not use this site to share secrets, credentials, customer records, personal or regulated data, or proprietary process detail. The private brief doesn’t provide a free-text field or file upload.