What this site does today
NasdaqistanIntel is a personal trading toolkit designed and maintained by Lukas Baranovic. The current files run entirely in the browser. There is no application server receiving journal entries, daily plans, risk results, or passphrases.
Demo access data
Registration stores a codename and a lightly obscured passphrase in browser localStorage. Login stores the active codename as a local session value. This is convenience gating, not secure authentication: anyone with access to the browser profile or developer tools may be able to inspect or change those values.
Do not use a real or reused password. A production account system would require server-side authentication, secure password hashing, session protection, and a materially different privacy notice.
Plans, journal, checklist, and risk guard
The daily plan, key levels, journal entries, checklist state, and daily risk results are saved to localStorage and associated with the active codename. They remain on that browser and device unless the user exports the journal, clears site data, or removes individual entries through the interface.
The market-structure reader processes pasted candle data in memory. It does not upload those candles. Reloading the page clears the chart input unless the browser itself restores form state.
Cookies, analytics, and fonts
This build does not include analytics, advertising trackers, third-party cookies, or remotely hosted web fonts. It uses system fonts and static local files. The browser may still create ordinary localStorage entries for the features described above.
News sources and external calendars
The News Wire contains links to third-party publishers and economic calendars. Opening one of those links leaves NasdaqistanIntel; the destination’s privacy policy, cookies, analytics, and terms then apply. The current site does not control those services.
How to remove local data
Individual trades and daily risk results can be removed from the dashboard. To remove all NasdaqistanIntel data, clear the site’s storage in browser settings. Because there is no remote database in this build, there is no server-side profile to delete.
If the architecture changes
Adding a real backend, live data provider, hosting analytics, contact form, payment service, or cloud sync changes what data is processed and where it goes. This brief must be updated before those features are presented as covered.
Owner and contact
Site owner: Lukas Baranovic. No public contact channel was supplied in the project files. Add a real contact method before public launch if applicable law or the final service requires one.