FUTURYSK / LEGAL
Data Retention and Deletion Policy
Futurysk uses an aggressive early-stage retention schedule intended to limit storage growth and reduce unnecessary personal-data retention. Active credentials are removed when a connection is removed or account deletion is finalized. Mainnet operational records are retained longer than routine logs because they may be needed for reconciliation and incident investigation.
1. Retention principles
Futurysk intends to retain information only as long as needed for active service operation, account security, reconciliation, payment review, fraud prevention, incident investigation, and the retention periods described below.
Information may be deleted earlier when no longer required.
Retention may be temporarily extended for an active security investigation, payment dispute, fraud review, unresolved reconciliation issue, or account-deletion dependency.
2. Normal retention schedule
| Data category | Normal retention period |
|---|---|
| Unverified or abandoned account | Up to 7 days |
| Expired email-verification and password-recovery token records | Up to 7 days after expiry |
| Expired or revoked sessions | Up to 30 days |
| IP hash and user-agent security metadata | Up to 30 days |
| Security and authentication events | Up to 90 days |
| Trading drafts | Up to 30 days after the latest update |
| Completed idempotency records | Up to 30 days |
| Completed reconciliation jobs | Up to 30 days |
| Reconciliation-run history | Up to 90 days |
| TradingView signal and job history | Up to 90 days |
| General operational audit events | Up to 90 days |
| Testnet trading and order history | Up to 90 days |
| Mainnet order, operation, and reconciliation history | Up to 180 days |
| Daily-loss ledger records | Up to 180 days |
| Billing and payment metadata | Up to 12 months |
| Approved payment-proof files | Up to 90 days after final approval |
| Rejected payment-proof files | Up to 30 days after final rejection |
| Payment-proof hash and reference metadata | Up to 12 months |
| Subscription and entitlement history | Up to 12 months after expiry or revocation |
| Support correspondence | Up to 90 days after the matter is closed |
| General application logs | Normally up to 14 days |
| Security error logs | Up to 30 days |
| Database backups | Rolling cycle of up to 14 days |
| Finalized account-deletion record | Up to 90 days after finalization |
| Minimal fraud-prevention tombstone | Up to 180 days |
| Active encrypted API credential | Until connection removal or finalized account deletion |
| MFA secret and unused recovery-code hashes | Until MFA removal or finalized account deletion |
3. Payment-proof minimization
Payment-proof files may contain more information than Futurysk needs after review.
Approved proof files are normally removed within 90 days after final approval. Rejected proof files are normally removed within 30 days after final rejection.
Limited metadata may remain for up to 12 months, including payment reference, transaction reference, amount, currency, decision, timestamps, and cryptographic file hash.
4. API credential deletion
An encrypted Binance API credential is retained only while the associated connection remains active.
The credential is intended to be deleted promptly when:
- the user removes the connection;
- the relevant trading account is deleted; or
- account deletion is finalized.
Historical order, security, and audit records must not retain the raw API secret.
Revoking a key at Binance remains the fastest way for a user to stop its exchange access.
5. Account deletion process
An authenticated account-deletion request enters a seven-day waiting period. The user may cancel during that period.
Finalization may be delayed while a connected trading account remains active, has open exposure, requires reconciliation, or requires available risk-reducing action.
When deletion is finalized, Futurysk intends to:
- delete active encrypted exchange credentials;
- revoke active sessions;
- revoke active or pending entitlement;
- replace or remove direct account identifiers;
- disable authentication;
- remove selected IP and user-agent metadata;
- remove MFA secrets and unused recovery-code hashes; and
- mark the account as deleted.
6. Deleted-account Mainnet history
After account deletion is finalized, direct user identity is removed or pseudonymized from retained Mainnet operational history where technically feasible.
Pseudonymous Mainnet order, operation, reconciliation, and related risk records may remain for the balance of their normal retention period, up to a maximum of 180 days.
These records are retained only for operational reconstruction, reconciliation, security investigation, dispute review, and system-integrity purposes.
7. Export
Authenticated users may request an available account export in a supported format.
The current export may include profile, payment, and security-event information. Export scope may change as the product develops.
Sensitive values, including password hashes, raw API credentials, MFA secrets, recovery-code hashes, internal encryption material, and protected security fields, are excluded or redacted.
8. Backups
Database backups are normally kept on a rolling cycle of up to 14 days.
Information removed from the live system may remain in an encrypted or access-controlled backup until that backup expires. Futurysk does not normally restore an individual deleted record from backup unless required for full-system recovery.
9. Retention implementation
Deletion may be performed in scheduled batches to protect database integrity and respect dependencies among orders, risk records, reconciliation records, audit events, payment records, and account records.
Expiry of a stated period means the data becomes eligible for deletion; it does not guarantee deletion at an exact second.
10. Contact
Retention, export, and deletion questions must be sent to [email protected].