Version 2026.05 · Last updated 2026-05-12
Cookie policy
PULSE uses a small number of cookies. None of them sell your data and none of them are required to give you a marketing experience. You can change your choices at any time using the cookie preferences link.
Cookie categories
Strictly necessary
Required for PULSE to function: your authenticated session, the CSRF token that protects forms, and the cookie that remembers your cookie choice itself. These cannot be turned off.
session— your signed-in session (httponly, samesite=Lax).csrf_token— protects forms from cross-site request forgery.pulse_consent— remembers which cookies you accepted (no PII; just the policy version + accepted categories).
Analytics (off by default)
If you opt in we collect aggregate page-view counts and feature-usage metrics so we can see which pages are confusing and which features nobody uses. We do this with first-party logs only — no third-party analytics SDK runs in your browser unless you opt in.
Marketing (off by default)
If you opt in we may set a first-party identifier so that, when you come back through a campaign link, we can attribute your sign-up to the right channel. We do not run third-party ad pixels.
How to change your mind
Open the cookie preferences panel at any time. Authenticated users can also manage everything from Account › Privacy & data.
How we enforce your choice
Non-essential analytics and marketing scripts are not loaded into the page until the matching purpose is granted. Technically, every such script is delivered as <script type="text/plain" data-consent-purpose="..."> and only promoted to an executable script after consent — so a "Reject all" choice means nothing fires, end of story.
Contact
Privacy questions: [email protected].