Privacy Policy

This policy explains at a high level how information may be handled when you visit the public website or use the TradeRigor closed-beta application. It does not claim compliance or certification under a particular privacy regime.

Depending on the features you use, TradeRigor may handle:

• account identity information, including email address, display name, verification and account status;
• authentication information, including password hashes, session records, access status, and authorization context;
• organization, membership, platform-account, capability, and subscription-status metadata;
• trading configurations, exchange-binding details, non-secret credential metadata, research inputs, saved analytical state, and generated evidence;
• exchange API credential material that an authorized user deliberately submits for an enabled integration, stored in encrypted form; and
• technical, operational, security, audit, error, and service-usage records generated while the platform runs.

TradeRigor is not designed to take custody of funds or financial assets. Do not submit sensitive personal information that a requested feature does not require.

Information may come directly from you or an authorized organization administrator, from your use of the service, from systems that operate and secure the service, and from third-party services you choose to connect, such as an enabled exchange integration.

Information may be used to authenticate users; enforce organization and capability boundaries; provide research, analysis, monitoring, and configured integration features; retain evidence and operational state; protect, diagnose, and maintain the service; respond to beta feedback; and meet applicable legal obligations.

TradeRigor does not use application data to promise or guarantee a trading result.

The current application uses browser sessionStorage for a bearer session token, the selected organization, and session-only research-builder or filter state. Session storage is scoped to a browser tab session and is not a cookie.

The current TradeRigor application code does not set first-party analytics or advertising cookies, use localStorage, load advertising trackers, or install tracking pixels. A separate cookie policy is therefore not provided at this stage. Hosting or network providers may still process ordinary technical request data needed to deliver and protect the service.

When an authorized exchange integration is enabled, submitted API credential material is processed for that connection and stored using the platform’s encrypted credential controls. Application views use credential metadata and do not return stored secret values.

You should grant only the permissions required for an intended integration, follow the environment restrictions shown in the product, and revoke credentials you no longer use.

Information may be processed by infrastructure and operational service providers acting to host, deliver, secure, or support TradeRigor. Data is sent to a connected exchange only when needed for functionality an authorized user has configured. Optional notification integrations may process the content necessary to send the configured notice.

Information may also be disclosed where reasonably necessary to comply with law, protect rights or safety, investigate abuse, or support a business reorganization subject to appropriate safeguards. TradeRigor does not describe account data as being sold for advertising.

Information is retained for as long as reasonably needed to provide and secure the service, preserve required research or audit evidence, resolve disputes, and satisfy applicable obligations. Different records may require different periods. Exact retention schedules have not yet been adopted for commercial launch and require legal and operational review.

You may update information made editable through the service and may stop using the service. Depending on applicable law, you may have rights to request access, correction, deletion, restriction, objection, or portability, and to complain to an appropriate authority.

Requests may require identity verification and may be limited where retention is required for security, evidence integrity, legal obligations, or another lawful reason. A verified public privacy-request channel must be established before commercial launch; beta participants should use their invitation channel in the interim.

TradeRigor uses technical and organizational controls intended to protect information, including authenticated access, authorization boundaries, secret redaction, and encrypted credential storage. No transmission, storage, or security control is guaranteed to be completely secure. Keep your device, password, session, and connected-service credentials protected.

This policy may change as the beta service, infrastructure, data practices, or legal requirements develop. The latest revision date will appear at the top of this page, and material changes will be communicated where required.

The responsible legal entity and formal privacy contact are not yet established for commercial launch and must be completed after legal and business review. Until then, beta participants should use the channel through which access was arranged.