BackLegal
Legal

Cookies Policy

Neo Native uses a deliberately small number of cookies of its own. On the free plan, Google shows ads on some pages and may set advertising cookies, under the choice you make in Google's consent message; Starter and Pro have no ads. This page lists every cookie we set, the ones Google can set, everything the app keeps in your browser, what each is for, and how to control it.

Last updated · October 2, 2026
Short version: one login-session cookie; three affiliate cookies, only if you arrive through a partner's referral link; and one product-analytics cookie, only if you accept it. None of ours track you across the web. On the free plan, Google's advertising cookies come with the ads, and Google asks first where the law requires it (section 4).

01What are cookies?

Cookies are small pieces of data that a website asks your browser to store, then sends back on later visits. They're how the web remembers you between page loads — including for essential things like "keep me signed in" and "use dark mode."

Some cookies are strictly necessary — the Service literally cannot work without them. Others are functional — they make the experience nicer but aren't required. One is analytics, and it is set only with your consent. We set no advertising or cross-site tracking cookies of our own, and we don't share cookie-derived data with third parties for marketing. On the free plan, the pages that carry ads load Google AdSense, and Google can set its own advertising cookies there — see section 4.

02What we use

Here is every cookie Neo Native sets, and why:

sessionStrictly necessary. A signed JWT identifying your signed-in account — signed, not encrypted: the signature stops anyone altering it, but whoever holds the cookie can read the fields inside (your account id, email, display name and plan). HTTP-only, Secure, SameSite=Lax. Expires when you log out, and otherwise 7 days after it was issued — browsing does not extend it on its own. Without this you cannot stay signed in.
nper_refAffiliate attribution. Set only when you arrive through a partner's referral link — never otherwise. Holds that partner's code so that, if you sign up, the referral is credited to them. HTTP-only, Secure, SameSite=Lax. Lasts 180 days, and is deleted as soon as it has been used at signup.
nper_vidAffiliate attribution. Set together with nper_ref, under the same condition. A random identifier with nothing personal in it, used only so that opening the same referral link twice counts as one click. HTTP-only, Secure, SameSite=Lax. Lasts 180 days.
nper_clickAffiliate attribution. Set together with nper_ref, on the redirect that follows a partner's link. It holds no identifier — only the fact that the redirect happened — so that the page you land on can count the click. HTTP-only, Secure, SameSite=Lax. Lasts 2 minutes.
ph_…_posthogProduct analytics — only with your consent. When analytics is switched on, a banner asks first. Until you accept, PostHog is not started in your browser at all: this cookie is never set and nothing is sent to PostHog. If you accept, PostHog (listed in our Privacy Policy) stores a random identifier here and in localStorage under the same name, linked to your account once you sign in. The cookie lasts 365 days. Your answer to the banner is kept in nper:analytics-consent (section 3), and you can change it at any time in Settings.
nper_analytics_consentProduct analytics — only with your consent. Set only when you accept analytics, and deleted as soon as you decline or withdraw. It holds the single word granted and nothing that identifies you: it tells our server that it may send the events it records itself (sign-up, login, subscription) to PostHog. Secure, SameSite=Lax. Lasts 365 days.

03What the app stores in your browser

Beyond those cookies, the app keeps data in your browser's localStorage. It is not a cookie in the strict HTTP sense, but some privacy laws cover both. Part of it is also saved to your account, so it comes back when you sign in — on this browser after signing out, or on another device: your portfolio, watchlists, dashboard layout, chart drawings, screener presets, saved articles and the symbol on each Favorite Chart tile. The list below is generated from the app's own code, so it cannot fall out of step with what is actually stored.

Your content. Clearing site data deletes these from this browser. The ones marked "also saved to your account" return the next time you sign in; the others are deleted permanently, because we hold no copy.

vol_portfolio_v2Your portfolio: every position, quantity and entry price. Also saved on your account, so it comes back after you sign out and appears on your other devices. Also saved to your account.
vol_portfolioThe older single-portfolio format, kept so an existing book still opens.
vol_portfolio_equity_v1The daily value of your portfolio over time, used to draw its performance curve.
vol_watchlists_v1Your watchlists and the symbols on them. Also saved to your account.
vol_watchlistThe older single-watchlist format, kept for the same reason.
nper:dashboard:layout:v2How you arranged your dashboard: which widgets, in which order and size. Also saved to your account.
nper:dashboard:layout:v1The previous dashboard arrangement format.
nper:dashboard:favorite-chart…The symbol you pinned to each chart tile on the dashboard. Also saved to your account.
nper:dashboard:migrated:pulse-mapA marker recording that your dashboard was migrated to a newer widget, so it is not migrated twice.
nper:chart:drawings:v1…Trend lines, levels and other drawings you placed on a chart, one entry per symbol. Also saved to your account.
nper.markets.screener.presets.v1Screener filters you saved as a preset. Also saved to your account.
nper:news:savedArticles you saved to read later: for each one its headline, link, publisher, date, picture, related tickers and a short summary (up to 200 articles), so a story stays in Saved after it leaves the news feed. Also saved to your account.
nper:docsync:v1…Bookkeeping for the items that are also saved to your account: which account they belong to, which edits made in this browser are still waiting to be sent, and which version of each item this browser last received.
nper:chat:seenWhich chat messages you have already read, so unread counts are right.
nper:nav:seen:v1Which sections you have already visited, so "new" badges clear.
nper:cmdk:recent-tickersThe last few symbols you searched or charted, to offer them first next time.
nper:menu:visits:v1Which pages you open most, to show your four most visited pages at the top of the Menu. Kept only in this browser.
nper:corr:prefs:v1The correlation window and methods you picked on the Correlation Map, so the map opens the way you left it. Kept only in this browser.
nper:chart:prefs:v1The chart defaults you saved with «Save as default»: the kind of series, which indicators are on and their parameters, volume and the log scale. Kept only in this browser.
nper:ads:bar-dismissedWhen you last closed the "Terminal Pro" bar at the bottom of the free plan, so it stays hidden for three days. Only the time is stored.
nper:dashboard:floating:v1The dashboard tiles you detached into floating windows: which widgets, where on the screen, how big, and which are minimised — so they are where you left them after a reload. Kept only in this browser.
nper:dashboard:settings:v1Your dashboard settings: whether tiles can be detached into floating windows (free) or stay in the grid (fixed), and how the board is laid out on a phone. Kept only in this browser.
nper:dashboard:boards:v1The boards you saved under a name from «Presets» on the dashboard — which widgets, their sizes and settings — so you can open them again; as many as your plan allows. Kept only in this browser.

Preferences for this browser. These describe the device, not you — none of them says who you are or what you own.

nper:color-schemeYour light or dark preference, so the app does not flash the wrong theme on reload.
nper:sidebar:collapsedWhether you collapsed the sidebar.
nper:sidebar:collapsedSecs:v2Which sidebar sections you folded away.
nper:box:…Which collapsible panels you left open, one entry per panel.
nper:view:…Which view you picked for a panel that offers more than one, such as the equity curve and the ticker breakdown in the trade journal.
nper:cmdk:quickWhich four shortcuts you chose for the quick-access boxes at the top of the menu.
nper:analytics-consentYour answer to the analytics consent prompt, so you are not asked again on this browser.
nper:storage-ownerWhich account the stored data above belongs to, so it can be cleared when someone else signs in on this browser.
nper:bootedA marker that the loading screen already ran in this tab. Cleared when the tab closes. Stored per tab, not permanently.

04Third-party cookies

Some third-party services can set cookies, each only in one place:

StripePayments happen on Stripe's own pages — Checkout and the billing portal — which you reach from the pricing page and the billing screen. We load no Stripe script on our pages; Stripe may set cookies on its own for payment-fraud detection, governed by Stripe's cookie policy.
Google AdSenseAdvertising — free plan only. On the free plan, the Markets, News, Dashboard and Watchlist pages carry ads served by Google AdSense. Starter, Pro and the Pro trial never load it, nor does the iOS app, and there are no ads in chat, your portfolio, settings, billing or these legal pages. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the Internet. Google can set cookies on this site's address — for example __gads, __gpi and __eoi — and on its own domains, such as doubleclick.net and google.com. In the EEA, the UK and Switzerland, Google's own consent message (a Google-certified consent platform using the IAB Transparency & Consent Framework) asks before ads are personalised; if you refuse, Google may still show non-personalised or limited ads. Pages with ads carry a Google link to reopen that choice. You can opt out of personalised advertising at Ads Settings or at www.aboutads.info. How Google uses this data: How Google uses information from sites or apps that use our services.
VercelOur host may set anonymous performance cookies on rare error pages to assist with debugging. These do not identify you.
YouTubeLive TV plays streams in YouTube's privacy-enhanced player (youtube-nocookie.com). YouTube stores nothing on your device until a stream plays; once it does — when you open a channel — it may, under Google's privacy policy.
News TerminalThe Live TV page embeds the News Terminal, a separate service loaded from its own address. It may use its own cookies and storage.

We run one performance measurement, Vercel Speed Insights, which records how quickly pages load and respond. It sets no cookie and no identifier, and reports nothing about who you are — which is why it runs without a consent prompt.

Beyond these — Google AdSense on the free plan, and the consent-based analytics cookies in section 2 — we embed no other advertising tags, no social-media buttons, and nothing else that drops cross-site tracking cookies.

05How to control cookies

You can clear cookies and localStorage at any time from your browser settings. Doing so signs you out of the Terminal and resets your preferences for this browser.

Your portfolio, watchlists, dashboard arrangement, saved articles and chart drawings are also saved on your account, so they come back the next time you sign in. Anything under "Your content" in section 3 that is not marked as saved to your account is lost for good.

Blocking the strictly-necessary session cookie will prevent you from signing in.

Of our own cookies, the only one that waits for your consent is the analytics one: when analytics is switched on, a banner offers Accept and Decline, and either answer is remembered on this browser. Google's advertising cookies on the free plan are covered by Google's own consent message instead (section 4), which is separate from our banner. A visitor who simply arrives is given no cookie at all; the login cookie follows an action you took, and the three affiliate cookies are set only when you arrive through a partner's link. Whether those three require prior consent is a question we are taking advice on, and we will follow that advice rather than our own reading. Any future cookie for marketing or experimentation will ask first in the same way.

06Changes to this page

When the cookie inventory changes, we update the "Last updated" date at the top. Material changes — for example, enabling an analytics service — are also announced inside the Service so you can make an informed choice.

Contact
Questions about this document?
Neo Native — privacy@neonativeterminal.com