NuxGrid Privacy

Privacy

Data controller

The data processing described here is carried out by the NuxGrid publisher to provide, secure and administer the service. For any request concerning your data, use the Support feature available from your NuxGrid account. You can also write to contact@nuxgrid.com without signing in to your account.

Data used

NuxGrid uses the login identifier, password hash, account role, account status, and creation and last-login dates.

To create a standard account, the form currently requests only a username and password. NuxGrid does not require an identity document, postal address, telephone number or email address.

For connector operation, the server retains the following metadata: the name chosen by the user, public key, status, version, synchronization activity and desired strategy configuration. The machine hostname is not used.

The desired configuration may describe the trading strategy (market, amount, spacing, profit target and associated options), but does not contain exchange secret keys, available capital or executed orders.

For login attempts recorded by the application, the IP address is replaced with a technical fingerprint to limit abuse. Security logs may be retained for as long as needed for their purpose.

Orders, capital and trading data

The connector’s local database is the source of truth for orders, executions, balances, available capital, metrics and trading events. This data is not stored permanently in NuxGrid server operational tables.

To display the dashboard, the server may relay a snapshot requested by the browser. This snapshot may contain the orders, metrics and capital needed for display, but the technical relay record is deleted after consumption and is not used as a server-side history.

The browser may locally retain the latest snapshot in IndexedDB to display the dashboard when the connector is temporarily unavailable. This storage remains under the user’s control and can be deleted through the browser’s site data.

Exchange security and secrets

Exchange keys are encrypted in the browser before transmission. The server never receives the values in plaintext; the encrypted envelope may be temporarily relayed to the connector and its contents are erased after validation or revocation.

After validation, usable keys are installed locally on the connector. They are not included in metric or order synchronizations.

Account passwords are stored as hashes and are not kept in plaintext.

Purposes and legal bases

Account management, authentication, connector synchronization, console display, purchase processing, support and requested notifications are based on performing the requested service.

Service security and abuse prevention are based on the legitimate interest in protecting NuxGrid and its users. Retention of records required by regulations is based on applicable legal obligations.

Recipients and third-party services

Data is accessible only to people authorized to administer NuxGrid and providers needed for its operation, notably the IONOS host.

When the user configures a connector or an exchange, strictly necessary data may be transmitted to the explicitly configured device and, for real orders, to the exchange selected by the user. No public or advertising-related sharing is planned.

Sharing between accounts is optional and limited to the active positions needed for the shared view. It does not turn the server into an archive of orders or balances.

Cookies and trackers

The application uses a session cookie strictly necessary for authentication and session maintenance. It is deleted when the session closes or expires.

NuxGrid currently uses no advertising cookie, profiling tool or audience measurement tool requiring consent.

A language preference cookie remembers your selected language for one year.

The browser may also remember display preferences and a copy of the latest dashboard state. You can delete this information in your browser settings; some preferences and display data will then be lost.

Retention and requests

Accounts, connector metadata, configurations and associated data are retained for as long as necessary to operate the service, ensure security and comply with applicable obligations. Trading orders, balances and metrics remain in the connector’s local storage and, where applicable, the browser’s local storage.

Dashboard snapshots relayed by the server are temporary transport data. They are deleted after reading; expired requests and old results are cleaned up when new requests are made. They do not constitute a durable server-side history.

Login attempts older than two days are purged when a new attempt is recorded. Security logs, support tickets and payment references currently have no automatic purge; retention serves follow-up, security and applicable legal obligations.

Completed or failed private backtests become eligible for deletion after the configured period, 48 hours by default, measured from completion or creation when no completion date is available. Cleanup occurs when the backtest area is accessed. Published backtests are exempt from this purge.

Connector backup exports pass through a temporary server file, deleted when request processing finishes. The downloaded copy remains on your device, where you control its retention. Telegram association codes are valid for 15 minutes. Expired or used codes are cleaned up when a new code is created. Data retained by Stripe, Telegram, your exchange and your own connector is also subject to their rules and your settings.

The retention periods selected for general contact enquiries unrelated to a purchase or dispute are one year after the enquiry is closed, and 90 days from creation for operational backups of the NuxGrid server. This backup period does not apply to copies kept on your device or to your own connector.

Commercial correspondence has a selected retention period of five years from the last exchange; invoices and accounting evidence have a period of ten years from the end of the relevant financial year. Documents needed for a dispute may be retained for the time required to handle it and meet applicable obligations.

For a request for access, rectification, erasure, restriction or objection, use the Support feature from your NuxGrid account. You can also write to contact@nuxgrid.com without signing in to your account.

Your rights

Under the conditions provided by applicable regulations, you may request access, rectification, erasure or restriction of processing, object to certain processing and recover your data where the right to portability applies.

To exercise your rights, use the Support feature in your NuxGrid account. You may also lodge a complaint with the Commission nationale de l’informatique et des libertés (CNIL). You can also write to contact@nuxgrid.com without signing in to your account.

Stripe payments

Extension purchases are processed by Stripe on its payment page. Stripe collects the information needed for payment, which may include your email address and billing information.

NuxGrid sends Stripe a reference linked to your account and selected extension. NuxGrid retains the references needed to confirm payment and activate the extension. Your full payment card details are not stored in the NuxGrid database.

Stripe may process data outside the European Union, including in the United States. Its privacy policy describes international transfers and the protection mechanisms it applies.

Stripe privacy policy

Telegram notifications

If you link Telegram to your account, NuxGrid retains the conversation identifier, your Telegram username when available, the linking date and your notification preferences.

Enabled notifications may send Telegram information about your purchases, sales, conversions and connector incidents. They may include trading amounts, prices and results. You can disable delivery in your preferences.

Telegram is a third-party service established outside the European Economic Area. Sent messages are also subject to its privacy policy and its processing and retention terms.

Telegram privacy policy

Support and correspondence

When you contact the built-in support or contact@nuxgrid.com, your messages, any contact details you provide and the technical diagnostics collected for your request are used to handle it.

Do not include passwords, exchange secret keys or recovery phrases in these messages.

NuxGrid © 2026
Contact