Cookies & storage

Version 2026-10-20-v4

Bicks, operated by Dan Bickels as an individual based in Israel. Contact: support@bicksjournal.com.

Storage that makes Bicks work

Bicks uses browser storage for your signed-in session, journal recovery, drafts and preferences. Sign-in details are stored in IndexedDB, separately from journal caches in local storage. These records can remain until you clear site data. Cloudflare access and security features may use cookies to verify access and protect the service. Google sign-in uses Google’s own authentication services.

Optional broker connection

Connecting Tradovate uses a necessary Secure, HttpOnly, host-only cookie with a ten-minute lifetime to bind the authorization flow to your browser and protect against forged requests. It contains a random state value, not your broker password or access token. Your current Bicks identity is verified again before the connection is attached to your account.

Site performance measurement

The live site includes Cloudflare Web Analytics / real-user performance measurement through a browser beacon. It measures site visits and performance separately from server-side AI cost metering. Cloudflare describes this as privacy-first measurement rather than advertising tracking. Its collection documentation explains the beacon and reporting endpoints. Bicks does not configure it to collect journal-entry content. The Bicks application does not include advertising pixels.

Your controls

You can manage cookies and site storage in your browser. Blocking essential storage can prevent sign-in or journal recovery. Clearing it can remove unsynced local work, so export or confirm cloud saving first. Signing out alone does not clear all journal data from the device.