What we store, and why

Your email address (or mobile number)

The one you sign in with. It is how a code reaches you and how your account is recovered. It is not sold, rented, shared with any other company, or used for a newsletter.

Sign-in records

Each session stores a device identifier your browser generates, the IP address the request came from, and the browser’s user-agent string. They exist so a session can be revoked and so a sign-in from somewhere unexpected can be recognised.

What you tell the product about your trading

The capital you declare for position sizing, your risk settings, the positions and exits you log, and your journal entries. This is the data the product exists to work on, and none of it leaves it.

Broker credentials, only if you enable automated execution

Your Kite API key, secret, TOTP seed and password, encrypted with a key held by a key-management service. Exactly one database role can read that table, and the API that writes them holds no permission to read them back — so no endpoint can return them, by construction rather than by care.

An audit trail

Security-relevant actions — a sign-in, a credential stored, automated execution switched on — are recorded with a timestamp and a correlation identifier. It exists so a question about what happened to an account has an answer.

There are no third-party analytics, advertising or tracking scripts on this site. Nothing is loaded from an ad network. No behavioural profile is built and no data is sold or shared for marketing.

Sessions are held in your browser’s local storage rather than in cookies, so the site sets no tracking cookie. Product usage is measured only from data already in the database — accounts, sessions, positions — and never from a third-party pixel.

Database

A managed Postgres database hosted by Neon in AWS ap-southeast-1 (Singapore). Encrypted at rest by the provider; every connection is TLS.

Application server

A virtual server that runs the API, the web app and the scheduled jobs. It holds no user database of its own.

Email delivery

Sign-in codes are sent through Resend. They receive the address the code is going to and the code’s text, and nothing else about you.

Market data

Prices and index data come from public NSE sources. They describe the market, not you, and they are stored separately from anything of yours.

Demo accounts

Deleted automatically 24 hours after they are created, along with everything seeded into them. A demo account is a scratch pad, not a record.

Your account

Kept while the account exists, because a trading journal whose history is trimmed is not a journal.

Broker credentials

Deleted when you disconnect the broker or switch automated execution off. Disconnecting removes the encrypted rows; it does not merely hide them.

Sign-in codes

Stored hashed, expire in minutes, and are useless after they are used.

Email support@tradeorskip.com from the address you signed up with and ask for deletion. Your account, positions, journal, sessions and any stored broker credentials are removed.

There is no self-serve delete button yet. That is a gap and it is stated here rather than left for you to discover: until it exists, deletion is a request a person acts on.

Broker secrets are encrypted with a managed key, database access is separated by role so the application cannot read what it only needs to write, and every request carries a correlation identifier so an incident can be traced. The security page has the detail, including what to do if you find a problem.

Questions, corrections, and requests about your data: support@tradeorskip.com. A person reads it. Who that is, and how to escalate.

This page describes what the software does. It is not a legal opinion and makes no claim about compliance with any particular statute; that assessment belongs to counsel, and the description here is written to be checkable against the system rather than to satisfy a template.