Privacy Policy
This page describes how BLOQ expects to handle data during account access. It is not legal advice and should be reviewed before commercial launch.
Who we are
BLOQ is a risk-first market intelligence and account-gated desktop app platform for disciplined traders. Contact: support@bloqtrading.com.
What data we collect
We may collect account identity, authentication, role, plan, account access, preferences, referral, support, diagnostics, license, device and download data needed to operate BLOQ.
Account and OAuth data
Google OAuth may provide email, name, avatar and a stable Google subject. BLOQ uses the Google subject as identity where available and uses email as a contact field.
Billing data
Plan access is managed through the BLOQ account layer. Card details and payment-provider secrets must not be stored in BLOQ frontend code.
License and device data
The backend may store masked license identifiers, masked device identifiers, platform, app version, account access status and download events. Raw license keys should not be exposed in public UI.
Referral data
Referral codes, signup attribution, discount intent and manual commission status may be linked to accounts. Self-referrals, abuse or fraud may invalidate referral activity.
Legal acceptance records
When a user accepts BLOQ terms or risk disclosures, BLOQ may store evidence including document type, title, version, document hash, acceptance time, account email/name snapshot, acceptance method, hashed IP, user agent and device label. Raw IP addresses, tokens, broker secrets and payment secrets should not be stored in these records.
Marketing preferences
Marketing consent is optional and can be withdrawn. We do not sell personal data. Optional product, account access, changelog, referral and marketing emails are controlled through account preferences.
SMS preferences
SMS preferences remain explicit and user-controlled when SMS communication is enabled for an account.
Support requests
Support requests may include category, subject, message, contact email and safe diagnostics. Do not send broker secrets, passwords, private keys, seed phrases or card data through support.
Technical diagnostics
Diagnostics should mask account ids, email and device identifiers. Diagnostics must not include access tokens, database URLs, API secrets, broker keys, full journal content or full trade details.
Cookies and local storage
The web portal may use local storage for account session state, referral code and UI state. See the cookie and storage notice for more detail.
How we use data
We use data to authenticate accounts, enforce backend roles and feature gates, manage account access, provide downloads, handle support, track referrals and maintain system security.
Processors
Processors include backend/database hosting, Google OAuth for sign-in, account billing infrastructure, email delivery, monitoring and uptime/status providers where required.
Trading journal and cloud sync
Unless a future cloud sync feature is explicitly enabled, private trading journal content should remain local/private. Do not submit full private trade journals through website support.
Retention
Account access data may be retained while the account, support request, audit need or legal/security reason exists. Legal acceptance evidence may need longer retention for compliance, dispute handling or legal defense.
User rights
For data export or deletion requests, contact support@bloqtrading.com from the email address connected to your BLOQ account.
Security
BLOQ uses backend-authored access control. Production secrets belong in backend environment variables and provider systems, never in frontend code.
Contact
Privacy questions: support@bloqtrading.com.