OOrbitAction
Back to registration
Pre-release document. Final operator identity, privacy contact, jurisdiction-specific disclosures and retention schedule require legal review before commercial launch.

Data Protection

OrbitAction Pre-Release Privacy Notice

Version: portal-preview-2026-09-22

This notice explains the information used for preview account access and security testing.

1. Information Collected

  • Name, email address, password hash and legal-document acceptance.
  • Security records such as hashed session tokens, hashed IP identifiers and audit events.
  • Account-recovery and deletion records needed to complete or protect those requests.

2. How Information Is Used

Information is used to create and protect accounts, verify email ownership, prevent abuse, recover access, investigate security events and improve the pre-release service.

3. Security Design

Passwords are stored as hardened hashes. One-time identity tokens and session credentials are stored as hashes. Saved Binance credentials use authenticated encryption and API secrets are never returned to the customer interface.

4. Service Providers

Infrastructure and transactional-email providers may process the minimum information needed to host the service and deliver account-security messages. OrbitAction does not use preview registration data for advertising.

5. Account Deletion

A confirmed deletion removes active credentials, devices, workers and sessions when no open position remains, then closes and pseudonymizes the account. Security, audit or legal records may require limited retention.