1. Scope and responsibility
This notice explains how BOTIFY handles personal data through this website, customer accounts, purchases, account balance, support, licensing, downloads, VIP access, and security operations. BOTIFY controls the information it collects directly for those services. A payment processor, fiat-to-crypto provider, card network, wallet service, email provider, identity provider, hosting provider, broker, and MetaTrader operator may separately control information under their own notices and terms.
This notice does not identify a physical office or corporate registration that has not been established on the website. Questions and privacy requests may be submitted through authenticated BOTIFY customer support.
2. Information BOTIFY stores
Account records may include username, email address, password hash or external sign-in identifier, verification and account status, session records, device-bound identifiers or hashes, and security timestamps. BOTIFY does not store your plaintext password.
Order, balance, license, and delivery records may include product and plan, official price, payment channel, invoice and payment references, currencies, settlement status, ledger entries, refund or review state, broker name and server, MetaTrader login, account type, leverage and lot configuration, license scope and expiry, device binding, file checksum, download state, and audit events. BOTIFY never needs your broker trading password.
Botify Cloud records may include an independent subscription state, cTrader authorization-token ciphertext, masked or hashed trading-account references, deployment and configuration versions, short-lived signed leases, heartbeat times, open-position counts, safety permissions, provider status, alerts, and operational events. BOTIFY does not collect or store a cTrader, broker, trading-account, or email password. Provider tokens are encrypted at rest and limited to authorized service roles.
Transactional-email records may include the message type, customer and source-record reference, verified-email revision, fixed template and sender version, non-secret deposit or order facts, delivery-attempt timestamps and status, and the email provider's message identifier. A purchase receipt PDF uses the customer name and email captured on the paid order together with its product, Cloud, payment-method, price, and paid-time facts. The outbox does not contain a card number, wallet secret, crypto address, provider payment secret, license secret, or product binary.
Authenticated BOTIFY support records may include messages, attachments, delivery and read state, automated-support classifications, and account or order references. Likely secrets are filtered where supported, but you must not submit passwords, one-time codes, private keys, recovery phrases, card details, or identity documents.
When public Thunderbolt chat is enabled, the Spaceship service is not loaded until you choose to continue. The messages and details you enter are then handled through Thunderbolt and made available to BOTIFY in that service. BOTIFY does not automatically attach your BOTIFY username, email, account, order, balance, payment, license, broker, or device records to Thunderbolt.
3. Card and payment-provider data
BOTIFY stores the minimum payment metadata needed to match a payment to an order or balance deposit, validate signed status notifications, prevent replay or duplicate credit, support refunds and disputes, and preserve financial and security records. This can include the provider invoice or payment identifier, requested and received amount, currency, channel, status, timestamps, and provider message.
BOTIFY does not collect or store a card number, CVV, card PIN, or the phone number, photo ID, selfie, or other identity documents requested by a third-party fiat-to-crypto provider. When you choose card payment, you are redirected to that provider. It determines eligibility, countries, available methods, conversion, fees, identity checks, retention, and its own data-sharing practices. Review the provider’s separately presented privacy notice and terms before submitting information.
A return to BOTIFY is not proof of payment. BOTIFY relies on the provider’s signed server notification and server-side settlement checks before crediting balance or granting access.
4. How information is used
BOTIFY uses information to create and secure accounts; prevent simultaneous or unauthorized access; calculate prices; create and reconcile orders and balance entries; bind Demo, Live, and VIP rights; generate and deliver protected files; enforce expiry and device limits; answer support requests; investigate fraud, refunds, security events, and technical failures; maintain service reliability; and comply with applicable legal obligations.
BOTIFY also uses the current verified account address to send operational messages after account verification, a processed balance deposit, or a paid order. Messages waiting for verification are held. An event pinned to an earlier email revision is cancelled rather than retargeted to a changed address.
BOTIFY does not use card or provider identity documents because it does not receive them. BOTIFY does not sell those documents or use customer support content to request wallet or trading secrets.
5. Service providers and disclosure
Information is shared only as needed with services that operate the application, database, email, authentication, payment, fiat-to-crypto conversion, file delivery, public chat, and security functions, or where disclosure is required by applicable law, a valid legal request, fraud prevention, or protection of customers and the service. Provider access is limited to the role each provider performs, but each independent provider also applies its own terms and privacy practices.
For operational email, Resend receives the verified destination address, fixed message content, and any purchase-receipt PDF needed to deliver that message. BOTIFY requires provider-level open and click tracking to remain disabled for this transactional stream. BOTIFY records the provider message identifier and delivery-processing state. Provider acceptance means Resend accepted the request for processing; it does not prove inbox delivery. BOTIFY does not send Resend payment-provider secrets, crypto addresses, product binaries, or license secrets.
If you deliberately open Thunderbolt, Spaceship processes the conversation and any contact, lead, or scheduling details you choose to enter so that the chat and human handoff can operate. Review Spaceship’s privacy policy before continuing. Providers may process information in another country. Available safeguards and rights depend on the applicable law and provider arrangement.
6. Retention and security
BOTIFY keeps account, order, payment, balance-ledger, licensing, download, authenticated-support, transactional-email, and security records for as long as reasonably necessary to provide the service, preserve entitlement and audit integrity, resolve disputes and refunds, prevent duplicate delivery or abuse, and meet applicable accounting or legal duties. The durable email outbox and provider message identifier form an append-only operational audit trail; recipient addresses are resolved from the protected account record rather than duplicated in the outbox. Purchase-order name and email snapshots used on a receipt remain part of the financial order record. Some append-only payment, ledger, email, licensing, and security records cannot be selectively erased without undermining those duties; access can still be restricted where appropriate. Thunderbolt conversations are also subject to Spaceship’s separate service controls and retention practices.
BOTIFY uses server-side authorization, encrypted transport, password hashing, restricted secrets, signed payment notifications, device and session controls, append-only financial records, and access checks. No system can guarantee absolute security. Contact authenticated BOTIFY support promptly if you believe your account or payment reference has been exposed.
7. Your choices and rights
Depending on applicable law, you may request access, correction, deletion, restriction, objection, or portability of personal data and may complain to a competent privacy authority. BOTIFY may need to verify your identity through the authenticated account before acting. A request may be limited where records must be retained for payment reconciliation, fraud prevention, license enforcement, legal obligations, claims, or another lawful reason.
You can decline to load Thunderbolt and use the public help center or authenticated BOTIFY support instead. You can avoid card-provider processing by choosing another available payment method. If you already submitted information to Thunderbolt, a payment provider, or an identity provider, requests concerning that provider’s copy must also be directed to the provider under its own privacy notice.
8. Updates and contact
This notice may be updated prospectively when the service, providers, security controls, or applicable requirements change. The version and effective date are shown on this page. Open BOTIFY customer support for a privacy question or authenticated rights request. Do not include a password, card detail, broker password, wallet secret, or provider identity document.