logo-navbar

ulse

Cookie Policy

Last Updated: September 8, 2025

This Cookie Policy explains how Pulse uses cookies and similar technologies on the platform (the “Service”).

1. Scope

This Cookie Policy explains how we use cookies and similar technologies (local storage, session storage, lightweight analytics beacons) on the Pulse platform.

2. What We Use

We keep usage minimal. We do NOT store private keys.

Categories

  • Essential: session/auth token reference, feature flags, UI state (theme, last viewed metric, dialogs dismissed).
  • Performance / Analytics (if enabled): page views, load timing (aggregated).
  • Functional: username cache, chart preferences.
  • Security / Anti-abuse: rate limiting tokens, anomaly flags.
  • Optional: referral attribution parameters (e.g. ?ref=CODE).

3. Technologies

  • Cookies (small HTTP text tokens)
  • Local Storage / Session Storage (persistent UI & state)
  • In-memory runtime flags
  • Optional third‑party scripts (analytics/performance, only if enabled)

4. Third Parties (Examples)

Remove or adjust if unused.

  • Analytics: Plausible / Google Analytics (anonymized or pseudonymized usage data)
  • CDN / Hosting: static asset delivery (may log IP + user agent transiently)
  • Image / Storage (profile images): S3 / Cloud storage provider

5. Why We Use Them

PurposeExamplesLegal Basis (EU/UK)
Core operationAuth state, wallet session continuityLegitimate interest / Contract
UX preferencesTheme, metric selectionLegitimate interest
Analytics (if active)Aggregate usage trendsConsent (where required)
SecurityAbuse detection, throttlingLegitimate interest

6. Consent (EU/UK/EEA)

Essential items load immediately. Non‑essential (analytics/marketing) load only after consent (banner or settings panel). You may withdraw consent at any time.

7. Managing / Blocking

  • Browser settings: clear or block cookies/local storage.
  • Use “Private / Incognito” windows for session isolation.
  • Adjust in‑app cookie/settings panel (if implemented).
  • Blocking essential items may break functionality.

8. Retention

  • Essential/local prefs: until cleared or invalidated by app changes.
  • Analytics identifiers: provider rotation (typ. 6–24 months).
  • Security tokens: short rolling windows.

9. Do Not Track

Currently not acted upon due to lack of industry standardization. You may use browser-based blocking tools.

10. Changes

We may update this policy; the revised date indicates the latest version. Material changes may be announced in‑app.

11. Contact

Cookie or data questions: pulsesolofficial@gmail.com
General support: pulsesolofficial@gmail.com or Discord.