Privacy policy

Written from the actual schema rather than from a template. Every table and cookie named here exists; nothing is listed that we do not hold.

Last updated 10 August 2026

The short version. Your trading journal never reaches our servers — it lives in your browser. We hold your email (through Clerk), your payment records (through Razorpay), and the watchlists, screens and backtests you create. We do not sell anything to anyone, and there is no advertising or cross-site tracking on this platform.

Who is responsible

Tiruvi Desk operates this platform and decides what is collected and why — the Data Fiduciary, in the language of India's Digital Personal Data Protection Act, 2023. Contact details are in the Terms of Service.

What we store, and where

Three places, with different properties. Knowing which is which is most of understanding this policy.

Your browser only: The trading journal — every imported fill, every round trip, every note. Stored in localStorage under tiruvidesk.journal.v1. It is never uploaded, never backed up by us, and we cannot recover it. Pattern scan results live here too, under tiruvidesk.scans.v1.
Our database (Neon, Postgres): Watchlist entries, saved screens and their rules, option structures, backtest runs and their trades, your subscription and payment records, and — if you connect a broker — an encrypted broker session token. All keyed to your account.
Third parties: Clerk holds your identity. Razorpay holds your payment instrument. Neither passes us more than we list below.

The journal, specifically

This is the one place your own money appears, and it is deliberately the one thing we do not have. It is read from your browser, computed in your browser, and rendered in your browser.

The single exceptionis the AI assistant. If you ask it a question about your journal, the relevant trades are sent with that request so it has something to answer from. They are used for the length of that one request and are not written to any database of ours. They do reach Google's Gemini API as part of the request — see the third-party list below.

Clearing your browser storage deletes the journal permanently. Export it first if you want a copy; the export re-imports cleanly.

Account and identity

Identity is handled by Clerk. We never see or store your password. From Clerk we read your user id, email address, name if you provided one, and account creation and last-active timestamps — used to sign you in, attribute your data, and show the operator a subscriber list.

Payments

Payments are processed by Razorpay. Card numbers, UPI IDs, CVVs and bank credentials never touch our servers— they are entered in Razorpay's own checkout and stay with them.

What Razorpay reports back to us, and what we keep:

Payment and order identifiers, so a payout can be traced to a plan
Amount, currency, status, and the method used (card, UPI, netbanking)
The email address and contact number you gave at checkout
An error description, when a payment fails

These are financial records. We keep them after an account closes, because tax and accounting obligations require it — see retention below.

Your broker connection

Connecting ICICI Direct Breeze is optional and gives this platform read-only market data access. It cannot place orders, read your holdings, read your funds, or see your positions — the client has no methods for any of that and a runtime allowlist blocks those endpoints.

The session token is encrypted with AES-256-GCM before it is stored, using a key held in our environment rather than in the database, so a database dump contains ciphertext. It is scoped to your account alone, expires at midnight IST with the broker session itself, and Disconnect deletes it immediately.

Cookies

There are no advertising cookies, no analytics cookies and no cross-site trackers on this platform. Every cookie set here is functional, and all of them are httpOnly — meaning no script in your browser can read them.

Clerk session cookies: Keep you signed in. Set and managed by Clerk.
bz_st, bz_meta, bz_login_state: Your encrypted broker session, its issue and expiry timestamps, and a short-lived nonce proving the broker login started here. Expire at midnight IST.
td_admin: Operator access only. Never set for a normal account.

Who else sees your data

Each of these receives only what its function requires.

Clerk: Identity and authentication. Holds your email, name and sessions. Their privacy policy.
Razorpay: Payment processing. Holds your payment instrument and contact details. Their privacy policy.
Neon: Database hosting. Holds everything in the middle column above, encrypted at rest. Their privacy policy.
Vercel: Application hosting. Processes requests and keeps operational logs. Their privacy policy.
Google (Gemini): Only when you use an AI feature. Receives your request text, and — for a journal question — the trades sent with it, or for a chart scan, the image. Images are not stored by us. Their privacy policy.
ICICI Direct (Breeze): Only if you connect a broker. Sees the market-data requests made with your session. Their privacy policy.

Market data providers — Yahoo Finance for fundamentals, publisher RSS feeds for news — are fetched by our servers on a schedule for the whole platform. Those requests carry nothing about you.

What we do not do

We do not sell or rent personal data to anyone.
We do not run advertising or share data with ad networks.
We do not build profiles for any purpose other than running the product.
We do not use your journal, screens or backtests to train any model, ours or anyone else's.

How long we keep things

Account data: Until you delete your account, then removed within 30 days.
Watchlists, screens, backtests: Until you delete them, or until your account is deleted.
Broker session tokens: Until midnight IST the day they were issued, or until you disconnect.
Payment records: Kept after account deletion, as tax and accounting law requires. Retained no longer than those obligations demand.
Operational logs: Held by Vercel on their retention schedule, typically weeks rather than months.

Your rights

Under the DPDP Act 2023 you may ask for a summary of the personal data we hold, ask for it to be corrected or completed, ask for it to be erased, and nominate someone to exercise these rights if you cannot.

Being straight with you: self-service export and deletion are not built yet. Until they are, these requests are handled manually — write to us and we will action them within the statutory period. Building the automated path is on the roadmap, and we would rather say so than imply a button exists.

Security

Broker tokens are encrypted at rest. Payments are verified by HMAC signature before anything is recorded. Every entitlement is checked on the server, on each request, rather than trusted from the browser. Traffic is HTTPS-only and the application sends a content security policy, HSTS, and framing and referrer restrictions.

No system is perfectly secure. If you find a vulnerability, please report it before disclosing it publicly — see the Terms.

Age

This platform is not intended for anyone under 18, and we do not knowingly collect data from children. Trading in Indian securities requires a demat account, which requires majority in any case.

Changes to this policy

The date at the top is the authority on when this last changed. A change that materially affects what we collect or who receives it will be notified in the application before it takes effect.