Bicks Journal Back to workspace ↗
BICKS · EARLY ACCESS

Privacy Policy

Version 2026-10-20-v4

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

This policy explains how Bicks handles information when you use bicksjournal.com (formerly bicks.app) and the optional Bicks Journal Chrome extension. The operator identified above determines how Bicks uses your information. Questions and privacy requests can be sent to the contact above or through Support.

1. Information you provide

We process your account identifier, email and sign-in profile to create and authenticate your account. If you choose Google sign-in, Google supplies the account information needed for that sign-in. We record the versions of the Terms and Privacy Policy you accept and the time of acceptance.

Your journal may contain trades, instruments, dates, prices, profit and loss, account labels, notes, psychology entries, screenshots, strategy models, custom fields, preferences and unfinished drafts. We process the information you enter or import to store and display your journal, calculate statistics and reports, and synchronise supported records between your devices. You decide what journal content to provide. Avoid including account passwords, broker API secrets, identification documents, or unnecessary information about other people.

2. Why we use information and your choices

We use account and journal information to provide the features you request, maintain your account, respond to support requests, diagnose problems, secure the service and prevent abuse. Technical usage records also help us manage AI allowances, capacity and computing costs. If you contact Support, we use your message and contact details to investigate and respond.

You are not required by Bicks to provide information by law. Providing it is your choice, but account information is necessary for cloud access, and a feature cannot operate without the information it needs. You may leave optional journal fields empty. Voice and AI processing are optional; manual trade entry remains available without sending a recording for AI processing.

3. Cloud storage and information on your device

Supabase provides authentication and cloud database storage. Journal data, preferences and session information are also stored in your browser so the workspace can function. Signing out does not automatically erase all locally saved journal data. On a shared device, preserve any unsynced work you need, sign out, and clear the site’s stored data after use. Clearing browser storage can remove unsynced work.

Account access controls separate users’ cloud journals. Authorised administration or support may require access to cloud records for the purposes described in this policy; access is not limited exclusively to you. Information you export or share outside Bicks is then subject to your handling and the recipient’s practices.

Optional Tradovate connection and broker imports

If you choose to connect Tradovate, you sign in on Tradovate’s own website and approve the registered read-only permissions. Bicks does not ask for or store your Tradovate password. Tradovate supplies a limited-duration authorization token, accessible account identifiers and names, and permitted execution, order, position and contract information. These permissions do not permit Bicks to place or cancel trades, transfer money or change account risk settings.

We store encrypted authorization tokens on the server, separately from your journal and with owner/environment binding, plus your selected accounts, connection label, history selection, earliest imported trade date, synchronization status and imported closed-trade summaries. Server-side synchronization checks for updates approximately every minute while authorization remains valid, including when your browser is closed. An open, visible journal checks saved imports approximately every 15 seconds. Provider delays, request limits or failures can delay updates. Tokens can expire or be revoked and may require you to reconnect. Only the accounts you select are imported. Data available through the API can be incomplete: historical coverage and provider permissions vary. The current connection imports complete closed trades reconstructed from recent executions returned by Tradovate. It does not import archived trading history from past sessions. An empty response does not establish that an account has never traded. Existing date filters remain until you confirm a new account selection. These checks do not guarantee lifetime history, and unavailable commissions are labelled as unknown; displayed P&L may be gross.

You can disconnect Tradovate in the account-management screen. This removes the stored tokens and pending authorization state for both Live and Demo and stops new synchronization. It does not revoke an already issued token at Tradovate or erase saved journal entries; you can also revoke Bicks through Tradovate and delete journal entries separately. Deleting a trade removes its stored broker summary and keeps a minimal deletion identifier to prevent re-import. Superseded summary content is discarded when reconciled, while minimal inactive identifiers can remain to remove obsolete copies from devices. Account deletion removes active broker connection and import records; provider backups follow their own retention schedules. Pending authorization records expire after ten minutes. They contain a random-state hash and may temporarily contain an encrypted grant while the returning browser proves it is signed in to the same Bicks user. They contain no raw authorization code or plaintext access token and are removed on completion, replacement, disconnection or account deletion.

Your Bicks account cannot use these features to retrieve another Bicks user’s connected accounts. Authorized infrastructure administrators retain operational access to server secrets and databases; this is not end-to-end encryption against the operator. Broker data is used for journaling and synchronization and is not automatically sent for AI extraction. Tradovate independently processes authentication and broker account data under its privacy policy.

4. Optional recordings and AI extraction

When you choose Extract, the audio or text you submit is sent through Bicks to Cloudflare Workers AI. Whisper transcribes recordings and Qwen extracts trade fields from text. The request can also include relevant trading-model names, vocabulary, enabled choices and custom-field definitions from your account so the result fits your journal. Bicks does not send your entire journal for this extraction. Review the transcript and proposed fields before saving: transcription and extraction can omit or misunderstand what you said.

Bicks does not save raw recordings in its application database or offer a recording archive after extraction. Audio is held temporarily for recording and processing. Temporary AI recovery results can contain the transcript and extracted fields. Cloudflare’s handling of inference content, operational metadata and limited legal or security exceptions is described in its Workers AI data-usage policy. Bicks does not use your journal content to train its own AI models.

5. Chrome extension

The optional extension is linked to your account using a one-use pairing code. New drafts are stored separately for the account identity verified by Bicks; a different connected account cannot open that draft. Older drafts without a verified owner are not loaded or submitted and can be explicitly deleted in the extension. It stores an account-specific access token and unfinished form content in Chrome extension storage, retrieves the model information needed for its forms, and sends entries you choose to save to Bicks. If you use voice capture, Chrome requests microphone access. Audio is sent for processing when you choose Extract trade; recordings are discarded when the panel closes, while extracted fields may remain as an unfinished draft.

The extension’s website access is limited to bicksjournal.com and bicks.app. It does not read the contents of the trading website beside it, monitor your browsing history, or place orders. Disconnect it in the extension or revoke paired extensions in Bicks Settings to stop future access. In extension version 0.5.14 and later, Sign out stops access and clears the current account’s local draft and recording after confirmation. Older extension versions may retain an account-bound local draft until expiry or deletion. Entries already saved to your journal are not deleted by disconnecting.

6. Technical records and browser storage

Our hosting, authentication and security services process connection and request information, which can include IP addresses, browser or device information, timestamps, request paths and error information. Bicks uses IP-based rate limiting to protect authentication and other endpoints. AI metering records include account and request identifiers, recording duration, model identifiers, token counts, processing time and estimated cost; those metering records do not contain the recording or full prompt.

Bicks uses browser storage for sign-in sessions, journal caching, preferences and drafts. The live site also includes Cloudflare Web Analytics / real-user performance measurement in the browser, using a Cloudflare beacon to measure site visits and performance. This measurement is separate from AI cost metering. See Cloudflare’s collection documentation; Bicks does not configure this beacon to collect journal-entry content. Blocking or clearing necessary storage can prevent sign-in or remove local work. Bicks does not sell or rent your personal information, use journal content for advertising, or treat acceptance of this policy as permission to send marketing emails.

7. Providers and disclosures

We use Supabase for authentication and data storage, Cloudflare for hosting, security and optional AI processing, and Google if you choose Google sign-in. Support correspondence is handled through our support email provider. These providers receive the information necessary for their role and may process it outside your country. This is not a promise that information remains in Israel or any other single country.

We may disclose information when required by applicable law or a valid legal request, or when reasonably necessary to investigate abuse, protect people’s safety, or defend legal rights. We limit such disclosures to what is appropriate for that purpose. Links to other services do not make their privacy practices part of Bicks’ own practices.

8. Retention and deletion

You can delete supported journal records in the application. Deletion removes the corresponding active journal and extension-source records. Minimal account-bound identifiers marking deleted trades, drafts or model names are retained to prevent an older tab or retry from restoring them; they do not retain the deleted recording, notes or photos. Deleted model names remain reserved; choose a different name for a new model so an older offline tab cannot restore content under the reused name. Linked trade/section Notebook notes and psychology review signatures are removed with the trade. Independent day notes, shared option libraries and other separate journal records are not deleted merely by removing a trade or model. Another device may still display an older local copy until it reloads or its storage is cleared. You can permanently delete your cloud account in Settings → Journal data → Delete account by pressing and holding the delete button. This removes the active account, saved journal data, AI usage records and paired extension access. You can also contact Support for account deletion or removal of other account information; we may verify ownership before acting. We will explain any applicable legal reason for retaining information. Local browser and extension copies may need to be cleared separately.

9. Access, correction and privacy requests

You can review and edit journal entries and use the export options in Settings. The current export covers trades, notebook notes and report settings; it is not a complete export of all account information. Contact Support to request access to other personal information, correction of inaccurate information, deletion, or to raise a privacy concern. We will handle requests and any additional rights under the law that applies to you, subject to appropriate identity checks and lawful exceptions. You may also contact the privacy regulator in your jurisdiction.

10. Security, adults and policy updates

We use authentication, access controls and encrypted HTTPS connections to help protect information. No online service is completely secure. Keep your account credentials private, revoke extension access you no longer need, and notify Support if you suspect unauthorised access.

Bicks is intended for people aged 18 and over. If you believe a child has supplied personal information, contact Support. Material changes to this policy will be presented for renewed acknowledgement before continued workspace access. The version shown above identifies this policy.