Cookie
Cookie policy
Devhook Pulse uses only technical cookies, strictly necessary to keep you signed in, to protect the Service from abuse and to remember your language. It sets no analytics, profiling or advertising cookies. Technical cookies need no consent (Article 122 of the Italian Privacy Code and the Garante’s cookie guidelines of 10 June 2021), so the Service shows no cookie banner.
1. Cookies on the Devhook Pulse domain
| Cookie | Purpose | Duration |
|---|---|---|
| __Host-pulse_session | Keeps you signed in. HttpOnly, Secure and SameSite=Strict: scripts cannot read it, and it is never sent from other sites. | Up to 12 hours |
| pulse_google_nonce | Ties a Google sign-in to this browser, so a sign-in token stolen elsewhere is refused. Set when the sign-in page opens, and used only for Google sign-in. | 10 minutes |
| NEXT_LOCALE | Remembers the site language: your browser’s on the first visit, then the one you choose. | Until you close the browser |
| g_state | Set by Google’s sign-in script on the Devhook Pulse domain when the sign-in page opens: it remembers the state of Google’s sign-in prompt, for example that you closed it. Devhook does not read it. | Up to 6 months (set by Google) |
| cf_clearance | Set by Cloudflare, which shields the Service from automated traffic and attacks: it remembers that this browser passed its bot checks. Devhook does not read it. | Up to 1 year (set by Cloudflare) |
2. Statistics without cookies
Visits to the website are counted without cookies and without storing anything on your device, as the privacy policy describes. The console keeps a single technical entry in the browser’s local storage, pulse.onboarding.dismissed, so the getting-started guide stays closed once you close it; it remains until you clear it in your browser’s settings.
3. Third-party services
The sign-in and sign-up pages show the Sign in with Google button, loaded from Google’s servers. Google may read or set its own cookies on its own domains, under Google’s policies, for example if you already have a Google session; its script also sets the g_state cookie on the Devhook Pulse domain (see the table). Payments take place on Stripe’s pages, which set their own technical cookies under Stripe’s cookie policy.
4. Managing cookies
You can delete or block cookies in your browser’s settings. Without the session cookie you cannot sign in; without the language cookie the site uses your browser’s language.
5. Changes to this policy
Devhook updates this policy when the cookies it uses change. The date at the top of this page shows the current version.