Privacy Policy
Version 2026-09-22-v1
Bicks, operated by Dan Bickels. Contact: bicksupport@gmail.com.
What we collect and why
We process your account identifier, email and sign-in profile to authenticate you; trades, notes, psychology entries, images, models and drafts to provide your journal; and technical usage records to operate the pilot, prevent abuse and estimate computing costs. Providing journal content is voluntary. Account information is needed for cloud access. We also record the document versions and time of your acceptance.
Cloud and device storage
Supabase provides authentication and database storage. Journal data, preferences and session information are also stored in your browser. Signing out does not automatically erase all locally saved journal data. On shared devices, export any unsynced work and clear the site's stored data after use. Authorised administration and support may require access to cloud records; access is not limited exclusively to you.
Chrome journal extension
If you use the optional Bicks extension, a one-use code links it to your account. It stores an account-specific access token and any unfinished trade form in Chrome extension storage. It retrieves your Bicks model names and fade reason options, and sends entries that you choose to save to your Bicks journal. If you choose voice capture, Chrome requests microphone access. The audio remains in the extension until you choose Extract trade, when it is sent to Bicks for the optional processing described below. Recordings are discarded when the panel closes; extracted form fields may be kept as an unfinished draft. It has access only to bicks.app; it does not read the contents of the trading website, monitor your browsing history, or place trades. Disconnect the browser in the extension or revoke all paired extensions from Bicks Settings to stop future access.
Optional voice and AI processing
When you submit a recording, Cloudflare Workers AI processes audio with Whisper and text with Qwen to prepare trade fields. Review the result before saving. The application does not save raw audio in its database. Temporary recovery results may contain transcripts and extracted fields. Their cleanup target is approximately 24 hours, subject to the scheduled cleanup running; removal can be delayed by operational failures. Processing-job records are scheduled for removal after 30 days.
Usage measurement and retention
Usage records include account and request identifiers, timestamps, audio duration, model identifiers, token counts and estimated costs. The metering record does not include the recording or full prompt. Journal records, acceptance history and usage metrics are retained while your account is active and until deletion is handled. Provider logs and backups may persist under provider retention schedules; deletion is not an immediate wipe of every backup.
Providers and international processing
We use Supabase for accounts and data, Cloudflare for hosting, access protection and optional AI, and Google if you choose Google sign-in. Processing may occur outside your country. Bicks does not sell your journal content or use it for advertising. Cloudflare describes its AI data handling in its Workers AI data-usage policy.
Your choices and requests
You can enter trades manually instead of using voice, edit journal entries, and export from Settings. Contact Support to request access, correction or deletion of cloud account information, or raise a privacy concern. We may verify account ownership before acting. Legal obligations may require limited retention, which we will explain where applicable. Reading this policy does not grant marketing permission.
Security and updates
We use authentication and access controls, but no online service can guarantee absolute security. Do not upload credentials or unnecessary sensitive information. Material policy changes will be presented in the workspace. Bicks is intended for adults aged 18 and over.