Privacy Policy

1. Who operates Futurysk

Futurysk is currently operated under the Futurysk name. References to “Futurysk,” “we,” “us,” or “our” mean the operator of the Futurysk platform.

Questions or requests concerning personal information must be sent to [email protected].

2. Scope

This Privacy Policy applies to personal information processed through Futurysk websites, accounts, subscriptions, support communications, Binance account connections, Testnet and Mainnet trading environments, and related operational systems.

It does not govern information processed independently by Binance, Binance Pay, an email provider, a hosting provider, your browser, or another third party under that party’s own terms and privacy practices.

3. Information we collect

Depending on the features you use, Futurysk may process the following categories.

3.1 Account information

• email address;
• email verification state;
• password hash;
• account identifier and status;
• account creation, update, and deletion timestamps.

Futurysk does not store your password in readable form.

3.2 Authentication and security information

• session identifiers stored as hashes;
• session creation, expiry, revocation, and last-seen information;
• user-agent and pseudonymized or hashed network information where configured;
• MFA enrollment state;
• encrypted TOTP material;
• hashed recovery codes;
• authentication and security event records;
• step-up authentication state;
• rate-limit and abuse-prevention signals.

3.3 Subscription and payment information

• selected plan and access period;
• displayed amount, unique amount, currency, and price version;
• payment reference and transaction reference;
• payment status and review decision;
• subscription start, expiry, grace, and revocation information;
• payment evidence uploaded by the user;
• file metadata and cryptographic file hash;
• internal review records.

Do not upload unrelated sensitive documents as payment evidence.

3.4 Binance connection information

• account labels and internal identifiers;
• Binance environment;
• encrypted API credentials;
• credential validation and connection state;
• exchange account information returned through authorized API access;
• symbol, margin, balance, position, order, fill, and reconciliation information needed to provide the Service.

3.5 Trading and operational information

• symbols and market selections;
• Entry, Stop Loss, Take Profit, side, and order type;
• risk policies and position-sizing inputs;
• normalized price and quantity;
• previews, order records, idempotency records, and execution stages;
• Binance order identifiers and final status;
• position, protection, close, flatten, and reconciliation activity;
• Testnet and Mainnet environment information;
• TradingView source and signal information where enabled;
• operational and audit events.

3.6 Support information

• messages sent to [email protected];
• information and attachments you choose to provide;
• troubleshooting details;
• incident, billing, privacy, and complaint correspondence.

Never send a password, raw API secret, MFA code, recovery code, or private key to support.

3.7 Technical and browser information

• application and security logs;
• request timestamps and error codes;
• browser and device information where needed for security;
• essential session cookie data;
• local preferences such as chart timezone;
• temporary browser-session trading draft state.

4. How information is obtained

Information may be obtained:

• directly from you during registration, payment, support, or account configuration;
• from your browser or device when you use the Service;
• from Binance through API access you authorize;
• from Binance Pay references or payment evidence you provide;
• from operational, authentication, security, and reconciliation processes; and
• from a signal source or integration you configure.

5. How information is used

Futurysk may use information to:

• create, verify, authenticate, and secure accounts;
• provide Testnet and Mainnet environments;
• calculate risk and position size;
• validate and route user instructions;
• place, monitor, protect, and reconcile orders and positions;
• maintain idempotency and investigate uncertain operations;
• process subscriptions and review payment evidence;
• provide support and respond to incidents;
• detect fraud, abuse, credential compromise, and unauthorized access;
• maintain logs, backups, and audit records;
• debug, monitor, and improve reliability;
• enforce the Terms and incorporated policies; and
• establish, investigate, or respond to claims and disputes.

Futurysk does not currently use personal information for marketing newsletters or advertising-cookie profiling.

6. Binance API credentials

Binance API credentials are intended to be transmitted over an encrypted connection, processed server-side, and stored within an encrypted credential boundary.

Raw credentials must not be returned to the browser after storage. Access is intended to be restricted to the operations and systems that require it.

A connected Binance key must not include withdrawal permission. Futurysk may refuse unsafe credentials.

Credentials are retained only while the corresponding connection remains active. They are deleted when the connection is removed or account deletion is finalized, subject to the technical deletion process. Historical audit records should not retain the raw secret.

You can revoke credentials directly from Binance at any time.

7. Browser storage

Futurysk uses essential browser storage for authentication, security, preferences, session continuity, and temporary interface behavior.

The current Service does not use advertising cookies. The current Service does not intentionally deploy third-party analytics trackers. If these practices change, the Cookie and Browser Storage Notice will be updated.

8. Service providers and disclosure

Information may be processed by providers required to operate the Service, including providers for:

• infrastructure and hosting;
• database and storage;
• transactional email;
• domain and network delivery;
• payment processing or payment verification;
• backup and recovery; and
• support tooling, if adopted.

The final hosting provider may change as the Service develops. Infrastructure and database hosting are intended to be located in the United States.

Futurysk may also disclose information:

• when necessary to investigate account compromise, abuse, fraud, or payment disputes;
• to protect users, connected exchange accounts, Futurysk systems, or third parties;
• in connection with a reorganization or transfer of the Service; or
• when the operator determines disclosure is necessary to respond to a valid official request.

Futurysk does not sell personal information as a business model.

9. International processing

Futurysk is intended for worldwide users. Information may be transmitted to and processed in the United States or another location used by a service provider.

By using Futurysk, you understand that privacy rules and protections may differ from those in your country of residence.

10. Security measures

Futurysk uses measures intended to reduce unauthorized access, including password hashing, server-side credential handling, encrypted credential storage, HTTPS, secure session cookies in production, strict same-site session behavior, MFA, recovery-code hashing, access boundaries, rate limits, audit records, and reconciliation controls.

No system is completely secure. Futurysk cannot guarantee that unauthorized access, loss, misuse, or disruption will never occur.

11. Retention

Information is retained according to the Data Retention and Deletion Policy. Data may be deleted earlier when it is no longer required.

Retention may be temporarily extended for an active security investigation, payment dispute, fraud review, unresolved reconciliation issue, or account-deletion dependency.

12. Account export, correction, and deletion

Authenticated users may use available account tools to request an export or deletion.

Exports may include available profile, payment, and security-event information in supported formats. Export scope may evolve as the Service develops.

Account deletion uses a seven-day waiting period during which the request may be canceled. Finalization may be delayed while a connected trading account remains active or requires risk-reducing action.

After finalization, active credentials are deleted, sessions are revoked, entitlement is revoked, account identifiers are removed or pseudonymized, and selected security metadata is removed. Certain operational, Mainnet, payment, security, and deletion records may remain until their applicable retention periods expire.

Requests may also be sent to [email protected]. Futurysk may require verification before processing a request.

13. Users under 18

Futurysk is not intended for anyone under 18 years old. Futurysk does not knowingly permit a person under 18 to create an account.

14. Changes to this Policy

Futurysk may update this Privacy Policy at any time. The revised version becomes effective when published with a new effective date.

Advance notice and renewed consent are not required. Continued use after publication constitutes acceptance of the revised policy.

15. Contact

All privacy questions and requests must be submitted to:

[email protected]