Cookie Policy
NeuPortal · Beta testing edition of 03.11.2026 · Contact: [email protected]
Section 1. Use of cookies during beta testing
1.1. The NeuPortal Platform uses cookies (small text files placed on your device) and browser local storage to keep the AI-terminal interface working correctly, save user settings, sign users in to their account, protect against bots and debug the custom payment gateway.
Section 2. Which cookies are used
2.1. Technical (strictly necessary). They maintain the user's sign-in session and security when working with wallets and balances. Signing in to the account is impossible without them, so consent is not requested for them.
| Name | Purpose | Duration |
|---|---|---|
__neu_access | access token for the account session | up to 1 hour |
__neu_refresh | renewing the session without signing in again | up to 30 days or until sign-out |
__neu_mfa | intermediate step of a sign-in with two-factor authentication | up to 10 minutes |
__neu_resumed | protection against repeated automatic session renewal | 15 seconds |
NEXT_LOCALE | chosen site language | until the browser is closed |
2.2. Functional. They remember interface settings.
| Name | Purpose | Duration |
|---|---|---|
np_tz (cookie) | time zone for displaying times | 1 year |
np_nova_dock (cookie) | position of the "Nova" assistant panel | 1 year |
local storage: neuportal.cookie_consent, neuportal.ads_consent, "Nova" settings, account layout, amount hiding | your cookie choice and interface settings; kept only in your browser | until the browser data is cleared |
| session storage: form resubmission keys | protection against an operation being processed twice | until the tab is closed |
2.3. Bot protection cookies (Cloudflare). The site runs on the Cloudflare network. The registration and sign-in forms use Cloudflare Turnstile — a check that the action is performed by a human. Cloudflare may set its own technical cookies (for example __cf_bm, cf_clearance) under its own policy.
2.4. Functional cookies of the compliance provider Didit. Our site integrates the external Didit verification module, which opens in a Didit window or page. It uses its own secure cookies to recognise the user's session, prevent fraud and complete the KYC/AML procedures correctly. These cookies are processed in accordance with Didit's policy (didit.me/terms/cookies).
2.5. Advertising (public website pages only, after consent). The public pages of the website may use the Google Ads tag (gtag.js), which measures conversions (registration, going to the community) and may be used for remarketing. The tag is loaded only after the user has given separate consent to advertising cookies in the cookie banner; until then it is not loaded and nothing is sent to Google. Google may set its own cookies (for example _gcl_au) under its privacy policy. The user's choice is kept in local storage (neuportal.ads_consent). No advertising tags are ever used in the user account.
2.6. Analytics. No analytics cookies are currently used in the user account; site stability and load on the AI terminals are monitored on the server side, and error monitoring works without cookies. If analytics cookies are added, this Policy will be updated and, where the law requires, consent will be requested.
Section 3. Consent and managing cookies
3.1. A banner is shown on the first visit. Non-essential (advertising and analytics) cookies are used only to the extent permitted by applicable law and — where the law requires consent — after it is given. You can change your choice by clearing the site data in your browser: the banner will appear again.
3.2. The User may disable or delete cookies at any time in their browser settings; however, disabling strictly necessary cookies may cause the terminal interface to work incorrectly and make gateway transactions impossible.
Section 4. Changes and contact
The Policy is updated when the set of cookies changes; the current version is published on the site. For any questions about cookies, contact us at: [email protected].
