Local-First Architecture & Privacy
TickMint runs on your computer. A local gateway process talks to Rithmic, stores your data in a local database (tickmint.db), and serves the workstation UI. There is no TickMint account, and no TickMint server sits between you and your broker:
- The workstation UI talks to the gateway over loopback (
127.0.0.1) only, using a per-launch session token. - The gateway talks to Rithmic directly over a TLS WebSocket.
- Other outbound connections are limited to the ones listed below.
What TickMint connects to
| Destination | When | Why |
|---|---|---|
Rithmic (wss://rprotocol.rithmic.com:443 and the plants it assigns) |
While a connection is active | Login, market data, orders, accounts and history. Your Rithmic username and password go only here. |
| Economic calendar provider | Only when the news indicator or the journal’s day view needs it; cached for 2 hours | Economic calendar events (a standard web request) |
downloads.tickmint.net |
When the app checks for or downloads an update | App updates. The request includes the app version and platform. Our hosting provider (Google Cloud: Cloud Storage and Cloud CDN) may keep request logs, including IP addresses. |
| Discord, Slack, Telegram, email or your webhook URL | Only if you configure alert channels | Alert delivery |
TickMint has no telemetry, analytics or crash reporting, and does not require a TickMint account. Google Analytics is used on the tickmint.net website only, never in the app. Fonts are bundled with the app. Your credentials, trades, sizes, P&L and scripts stay on your machine, except credentials sent to Rithmic to log in and anything you send through an alert channel.
Where your data lives
The desktop app keeps everything in its data folder (Electron’s standard per-user app data location):
| OS | Data folder |
|---|---|
| macOS | ~/Library/Application Support/TickMint |
| Windows | %APPDATA%\TickMint |
| Linux | ~/.config/TickMint |
| File or folder | Contents |
|---|---|
tickmint.db (plus -wal and -shm files) |
Connections, encrypted credentials, fills, journal, copier groups and settings, alert channels |
.secret.key.enc |
The encryption key, protected by your OS keychain |
scripts/ |
Your MintScript files |
journal/attachments/ |
Journal screenshots |
forexfactory_cache.json |
Cached economic calendar |
window-state.json, editor-window-state.json, journal-window-state-v3.json |
Window sizes and positions |
Workstation preferences (settings, chart layouts, indicators, drawings, themes, alert preferences and SIM-1 history) are kept in the app’s local storage, also on your machine.
Credential encryption
Rithmic passwords and alert-channel secrets (webhook URLs, bot tokens, SMTP passwords, HMAC secrets) are encrypted before they are written to the database.
- Cipher: AES-256-GCM with a random 12-byte IV per value.
- Key: a random key stored in
.secret.key.enc, protected by the OS keychain (macOS Keychain, Windows DPAPI or the Linux secret service). If no keychain is available, the key is stored in.secret.keywith owner-only permissions (0600). - Override: set the
TICKMINT_ENCRYPTION_KEYenvironment variable to supply your own key.
Saved secrets are never sent back to the UI. Forms show Stored with a lock icon instead.
Local gateway security
The gateway listens on 127.0.0.1 only, so other devices on your network can’t reach it.
- Session token: each desktop launch generates a random 256-bit token (64 hex characters) in memory. A standalone gateway uses a 192-bit token (48 hex characters). The token is never written to disk.
- Every API call except
/api/healthmust send the token in theX-Session-Tokenheader, or it is rejected with HTTP 401. - WebSocket clients must send the token in their first message. A wrong token closes the socket with code 4001.
- Requests must use a loopback
Hostheader, which blocks DNS-rebinding attacks from web pages. Browser connections must also come from an allowed origin. - The packaged app lets the OS choose a free port each launch and loads the UI from
app://tickmint.
App sandboxing
- All windows run with context isolation and the Chromium sandbox.
- The Content Security Policy only allows scripts bundled with the app (
script-src 'self'). - MintScript indicators run in a sandboxed worker with no network access (
default-src 'none').