YOUR WORKSPACE. CLEAR TERMS.
Privacy notice
How information moves through your BotFabricForex workspace.
01 · Operator and contact
BotFabricForex is provided under the Fixio business brand, the name on the current Stripe merchant account. Contact support@botfabricforex.com about this notice, the operator or a data request.
Business details
Trade name: Fixio
Business address: Dekemastate 7, 7608 XH Almelo
Dutch Chamber of Commerce (KvK): 97151343
Published business details at Fixio
02 · Your account and workspace
When Google sign-in is available, Supabase authenticates your account. The app records a user identifier, provided name and email, account creation and last-seen times. It stores the strategies, journal entries, uploaded research candles, settings, immutable simulation evidence and observation rules that you save. Subscription records include Stripe customer/subscription identifiers, billing status and access periods; card details are entered into Stripe’s payment pages.
If you personally connect a crypto exchange, the service stores the connection name, exchange and market type, permission-verification state and application-encrypted API credentials. A separate server-only encryption key is used; credentials are not returned to your browser or AI chat. Supported reads can retrieve balances, positions and timestamps from the selected exchange. Existing AI connections with approved read access can receive these account results, never the credentials. Public exchange market data does not require connecting a private account. Trial activation stores its start/end, policy version and request identifier; it does not store a payment card or cause an automatic charge. Revoke an exchange connection in the platform to remove its stored credentials; deleting the local copy does not revoke a key at the exchange, where you can revoke it separately.
Account email stores your verified recipient address, template language, optional preferences and deduplication/delivery records. Queued plaintext/HTML may contain your display name and requested account-event information, but never passwords, API keys or card details. Important account/trial/membership messages concern requested service events; optional account, connection and practice-status updates default off. A personally requested preview goes only to the verified signed-in address. SMTP acceptance is not proof of mailbox delivery. The configured SMTP provider processes recipients and message content to send these messages.
03 · Read-only MetaTrader connection
Pairing your own terminal allows its bridge to send account identity and currency, balance/equity/margin, open-position context, quotes and completed candles to your private workspace. These can reveal trading activity and financial information. Terminal pairing is optional. The server stores a hash of its device credential, not a readable copy. The bridge has no order-execution function, and the platform does not ask you to upload a broker password.
Real MT5 execution is a different, personally enabled pairing with a separate credential. It records an account fingerprint, approved limits and expiring authority, durable order intent/attempt state, and reported order/deal evidence. Its local worker keeps private execution/recovery state on your own computer and needs the matching already signed-in hedging account. Existing read-only bridge credentials do not gain execution rights. No broker password is requested by the hosted service.
04 · AI hosts, permissions and notices
An MCP connection shares the account data requested by the AI host within your approved permissions. Read permission can expose private workspace and terminal context; write permission can save supported workspace changes. Connecting ChatGPT (OpenAI) or Claude (Anthropic) is your choice and requires a separate consent flow. BotFabricForex does not automatically send all workspace data to both hosts. Host conversation storage and use follow that host’s own settings and terms. The platform records your personal research-notice acknowledgement: notice version and text hash, requested/effective language, translation source and acceptance time. This is distinct from MCP consent, acceptance of service terms and consent to a brokerage order.
Accepting the ordinary service terms creates a separate receipt bound to your account. We store the terms version and text hash, the server-recorded acceptance time, the requested and displayed language, the translation source, and a snapshot of the original public terms you accepted. The original receipt is retained unchanged and can be downloaded from your account. It is separate from the research-risk acknowledgement and MCP permission, and does not waive statutory rights. No personal user-agent is stored in this acceptance receipt.
An additional, personally selected AI trading permission is separate from ordinary read/write access and never added to an old grant automatically. Real-money authority is created personally in the account screen and stores its consent version, account/connection, exact market, reviewed strategy revision where chosen, limits, expiry and revocation. Requested live tools can return own order/position information to the connected AI provider and can request orders only within supported approved authority. Separate exchange execution credentials are encrypted with the dedicated execution key; neither the browser nor AI chat receives saved secret values. Live orders, attempt/recovery evidence and broker/exchange responses needed to reconcile actual status are private account records. No withdrawal or transfer authority is included.
External TradingView or Make alerts are optional and require a separate personal connection and activation. We store the connector and its binding to your bot, account connection, exact market, fixed amount, strategy revision and expiring authority; received action, symbol, event identifier, timestamps and processing/result receipts are private account records. Only a hash of the dedicated receiver secret is stored by BotFabricForex. You provide the selected TradingView or Make service with the receiver template or credential; it does not contain your broker password or exchange API key. An HTTP 202 receipt records acceptance for processing and is not execution or a confirmed fill. Revocation stops new dispatch but does not erase past receipts or cancel orders already in flight; this feature has no new automatic log-deletion schedule.
Website AI inference is off by default. Customers normally use their own ChatGPT or Claude account through their MCP connection; BotFabricForex does not automatically share the whole workspace. Only if embedded Strategy Chat is separately enabled does it send the current conversation and research context you explicitly select through Vercel AI Gateway to the chosen OpenAI or Anthropic model. It does not automatically attach balances, positions, orders, journal entries or credentials. This optional conversation stays in open-page memory, not a saved BotFabricForex transcript, and is cleared on leaving or refreshing. The gateway and model provider process enabled requests under their own policies. Account-scoped counters and conservative usage reservations limit abuse and service costs. Bot events are private operational history; public crypto trend snapshots are descriptive caches and own MT5 radar snapshots remain account scoped.
When you select “Send this chart”, the chosen provider also receives the exact completed-candle chart snapshot and selected fixed indicators. The server holds up to four account-scoped chart snapshots; a snapshot can be used for analysis for ten minutes. AI chart changes are limited to supported market, interval and indicator settings. A strategy proposal is an unsaved concept until you choose to review and save it.
05 · Why information is used
Account and workspace information supports the service you request; payment records support subscriptions and accounting; permission, acknowledgement and support records support security, troubleshooting and administration. Where applicable, these purposes rely on contract performance, legal obligations or legitimate interests in operating and protecting the service. Optional sharing with an AI host is controlled through your connection approval.
06 · Providers and support access
Supabase provides authentication/database infrastructure; Vercel hosts the application; Stripe handles payments; Google handles Google sign-in. The app’s embedded TradingView chart connects your browser to TradingView and can expose network/browser information to that provider. OpenAI and Anthropic receive data when you connect and request their tools. The current support portal shows authorised administrators account name/email, subscription status, support notes, aggregate record counts and support audit events. It has no customer impersonation, payment override or order controls. Infrastructure operations may require access to stored data; this notice does not claim that staff can never access it.
07 · Location and international processing
The current application database project is in eu-west-1. That regional database location is not a promise that all processing stays in the EU: hosting, identity, payments, charts and connected AI providers operate internationally. Applicable processing and transfer arrangements depend on the provider and service configuration. Ask the contact above for the applicable arrangement. The provider notices below describe their own processing; no blanket EU-only or regulatory-compliance claim is made.
08 · Browser storage and retention
The app persists its Supabase sign-in session in browser storage and remembers the interface language. Temporary session storage supports the OAuth/MCP consent flow. Signing out and revoking a connection are different actions. The published legal pages use only a language preference and load no analytics or advertising tracker of their own. Third-party app embeds can have their own storage. Saved research evidence has no user edit/overwrite endpoint. The current service has no automated account-deletion screen or documented automatic record-expiry schedule. Request deletion by email; any necessary accounting, security or legal retention and provider-backup handling must be explained when the request is reviewed.
09 · Your choices and rights
You can disconnect an AI connection, revoke a paired terminal or sign out. Depending on applicable law, you may request access, correction, deletion, restriction, portability or object to processing; you may withdraw consent and complain to a data-protection authority. Contact the email above. Identity verification may be needed. See the European Commission’s explanation of data rights.
The public marketing website counts page views and clicks on trial or workspace links in anonymous aggregates. It sends only a fixed event name and an approved public page path, without query strings or fragments. It does not store analytics cookies, session IDs, IP addresses, referrers, browser fingerprints, emails or account identifiers. Do Not Track and Global Privacy Control opt-outs prevent collection. Counters cover a rolling 31-day UTC window; expired buckets are removed on the next observation or administrator refresh. Recent activity uses only the current and previous 5-minute counts. These counts are not unique people, completed registrations or sales. Authorized administrators can view these totals. Hosting and security services may independently process network logs under their policies; this counter does not add them to analytics.
10 · Changes and publication status
Version: 2026-10-20-1. Updated: 20 October 2026. Material changes to processing should be reflected here before they are introduced. English, Spanish and Dutch versions are provided. Custom workspace translations generated through AI may contain errors and are not independently reviewed legal translations.