Cookie Policy
Last updated: 12 July 2026 · Effective: 12 July 2026
This Cookie Policy explains what cookies and similar technologies CreatorPulse (“we”, “us”, “our”) uses when you visit www.getcreatorpulse.com(“Site”) or use our platform (“Service”), why we use them, and what choices you have.
This policy should be read alongside our Privacy Policy and Terms of Service.
1. What Are Cookies?
Cookies are small text files placed on your device (computer, tablet, or mobile) by a website when you visit it. They are widely used to make websites work efficiently, to remember your preferences, and to provide information to website owners.
Cookies may be session cookies (deleted when you close your browser) or persistent cookies(remaining on your device for a set period or until you delete them). They may be set by us (“first-party cookies”) or by third-party services we use (“third-party cookies”).
2. Cookies We Use
CreatorPulse uses only strictly necessary cookies. We do not use advertising, tracking, or analytics cookies.
| Cookie Name | Type | Purpose | Duration | Party |
|---|---|---|---|---|
next-auth.session-token | Strictly Necessary | Authenticates your signed-in session. Contains an encrypted session reference — no personal data is stored in the cookie itself. | 30 days | First-party |
__Secure-next-auth.session-token | Strictly Necessary | Secure variant of the session token used on HTTPS connections in production. | 30 days | First-party |
next-auth.csrf-token | Strictly Necessary | Cross-Site Request Forgery (CSRF) protection. Prevents unauthorised form submissions on your behalf. | Session | First-party |
__Host-next-auth.csrf-token | Strictly Necessary | Secure host-bound CSRF token used in production. | Session | First-party |
next-auth.callback-url | Strictly Necessary | Stores the URL to redirect you to after a successful sign-in (e.g. the page you were trying to access before login). | Session | First-party |
next-auth.pkce.code_verifier | Strictly Necessary | PKCE (Proof Key for Code Exchange) verifier used during OAuth 2.0 flows to prevent authorisation code interception attacks. | Session | First-party |
3. Third-Party Technologies
We use the following third-party technologies on our Site that may set cookies or use similar storage mechanisms:
| Service | Purpose | Privacy Policy |
|---|---|---|
| Tawk.to | Live chat widget on the marketing site. Tawk.to may set cookies to identify returning visitors to the chat widget. | tawk.to/privacy-policy |
We do not use cookies or SDKs from:
- Google Analytics, Google Ads, or any Google advertising products
- Meta Pixel or any Meta advertising products
- Hotjar, Mixpanel, Amplitude, or any behavioural analytics tools
- Any advertising networks or data brokers
4. Local Storage and Session Storage
In addition to cookies, we may use browser localStorage or sessionStorage to store small amounts of data on your device (such as UI preferences). This data does not leave your device and is not transmitted to our servers.
5. Legal Basis for Cookies (EEA and UK)
If you are located in the EEA or United Kingdom:
- Strictly necessary cookies (all cookies in our table above) are used on the basis of our legitimate interest and strict necessity to provide the Service. Under applicable law, these do not require your consent.
- We do not currently set any cookies that require consent under the ePrivacy Directive or UK PECR. If we add such cookies in the future, we will implement a consent mechanism before doing so.
6. Managing and Disabling Cookies
Because we use only strictly necessary cookies, disabling them will affect your ability to use the Service. Specifically, clearing or blocking our session cookies will sign you out of CreatorPulse.
You can manage cookies through your browser settings:
- Chrome: Settings → Privacy and security → Cookies and other site data
- Safari: Preferences → Privacy → Manage Website Data
- Firefox: Options → Privacy & Security → Cookies and Site Data
- Edge: Settings → Cookies and site permissions
You can also use browser extensions such as uBlock Origin or Privacy Badger to control third-party cookies (e.g. from Tawk.to).
7. Do Not Track
Some browsers transmit a “Do Not Track” (DNT) signal. Because we do not engage in cross-site tracking or behavioural advertising, our Service behaves the same regardless of whether a DNT signal is received.
8. Changes to This Policy
We may update this Cookie Policy from time to time to reflect changes in the cookies we use or for legal, regulatory, or operational reasons. We will notify you of material changes by posting a notice on the Site or by email. The “Last updated” date at the top of this page indicates when the policy was last revised.
9. Contact
If you have questions about our use of cookies, please contact us:
CreatorPulse
Email: hello@creatorpulse.io