Legal
Cookie Policy
Everything triStack AlgoTrader stores on your device, named individually. It is a short list, and it is short on purpose: one appearance preference, and whatever our network provider needs to serve you the page.
- Last updated
- 23 August 2026
- Last reviewed
- 23 August 2026
- Applies to
- trade.quantgrid.in and the triStack AlgoTrader service
1. What this covers
This policy explains what Tristack Technologies LLP, which operates triStack AlgoTrader, stores on your device and why. It covers two properties, and they are separate deployments on separate hosts:
- trade.quantgrid.in, the public website you are reading now.
- trade.quantgrid.in, the application. Each customer has their own instance served there, on their own database.
It covers cookies and browser local storage alike, because both are data kept on your own device and the practical question is the same one: what is stored, why, and how do you get rid of it. The wider picture, including what we hold on our servers and your rights under the Digital Personal Data Protection Act, 2023, is in the Privacy Policy.
2. Our position, in short
That is a shorter list than most sites publish, and it is deliberate. A company that sells isolated infrastructure to people who care about isolation has no business building a profile of which pages they read before they got in touch. The honest position is to collect nothing rather than to collect it and promise restraint.
It is also a position that has to stay true. The copy in this section is written against the analytics setting in our own configuration rather than typed as a claim: if a measurement tag is ever configured, this page says so instead of continuing to deny it.
3. On this website
trade.quantgrid.in is statically rendered and sets no cookies of its own. Every page, including this one and every other policy document, can be read from start to finish with nothing of ours written to your device except the appearance preference, and that is written only if you use the appearance control.
The network that serves the site may set its own operational cookie as traffic passes through it, described in section 5. The contact form posts what you type in it and nothing more: it sets no cookie and does not remember you between visits.
We do not measure you. There is no page-view counter, no visitor identifier and no heatmap. What our infrastructure necessarily logs in order to serve a request, and how long it is kept, is set out in the Privacy Policy.
4. On your instance
Your instance at trade.quantgrid.in is a different deployment, on your own database, and it keeps you signed in between page loads. That storage belongs to the application and to your browser, and this website can neither read it nor write to it: they are different origins.
Signing out, or clearing site data for that hostname, ends the session on that device. The session is scoped to your own instance, and it is stored per browser and per device, so signing in on a laptop does not sign you in on a phone.
Your broker credentials are never stored in your browser. They are held on your instance, encrypted at rest, as described in the Privacy Policy and on the security page.
5. The complete inventory
Every item stored on your device by us or by our network provider, what it does, and how you remove it. If you find something on our domains that is not on this list, tell us at [email protected] and we will explain it or remove it.
| What | Where it is stored | Purpose | Type | Control |
|---|---|---|---|---|
| Appearance preference | Browser local storage, on trade.quantgrid.in, under the key "tsat-theme" | Remembers whether you chose the light rendering, the dark rendering, or to follow your system setting, so the choice is not reset on every visit. It is written only when you use the appearance control, holds one of three words, and is read by nobody but the page you are reading. | Preference | Clear site data for this domain and it returns to following your system setting. Nothing else changes. |
| Network and bot-protection cookie | Cookie, potentially set by our edge network on this domain | The network in front of this site may set an operational cookie to tell automated traffic from human traffic and keep the site reachable. It carries no advertising or cross-site tracking function, and we do not read it for any purpose of our own. | Strictly necessary | Expires on its own shortly after your last request. Blocking it can stop the site loading. |
| Sign-in session on your instance | Set by the application on trade.quantgrid.in, not by this website | Your instance keeps you signed in between page loads. That is a different hostname, a different deployment and your own database. Nothing about it is shared with this website, and this website cannot read it. | Strictly necessary, on the application | Sign out of the instance, or clear site data for that hostname. Doing so signs you out. |
Nothing in that table has a marketing purpose, and none of it is shared with anyone for one. Three rows is the whole of it.
6. Third parties
Two third parties can set a cookie while you deal with us, and only one of them is involved in reading this website. Each is governed by its own policies rather than by this one.
| Who | When they are involved | What they do |
|---|---|---|
| Our edge network and DNS provider | On every visit to this site | Resolves the hostname, terminates TLS and serves the page, and may set the operational cookie described in section 5 while doing it. It carries traffic; it is not given anything about you beyond the request itself. |
| Payment gateway | Only during a payment | Where an invoice is paid online, the gateway's own checkout runs the payment and sets its own cookies on its own domain, for fraud prevention and to carry the transaction through. Card and bank details go to the gateway directly and never reach our servers. No payment flow runs on this marketing site. |
Neither is an advertising integration, neither is given anything about your trading, and nothing collected is sold or shared with an ad network. Which processors handle what on our behalf, and where, is set out in the Privacy Policy.
7. What we do not use
Stated as a list, because a specific denial is worth more than a general assurance:
- No analytics of any kind on this website. No page-view counting, no visitor identifier, no funnel measurement.
- No session recording, no heatmaps and no scroll tracking.
- No advertising cookies, no conversion pixels, no retargeting tags and no ad-network integrations.
- No social-media widgets, share buttons or embedded players that would set third-party cookies.
- No cross-site or cross-device tracking, no device fingerprinting and no data brokers.
- No analytics inside the application. Nothing you do with a broker account, a strategy or a live order is measured by a third party.
- No sale of cookie or browsing data, to anyone, ever.
If any of that changes, this list is the first thing that has to change with it, and the tag has to appear in section 5 in the same edit. A denial that outlives the fact it describes is worse than the measurement it was denying.
8. Why there is no cookie banner
There is nothing here to consent to. The appearance preference is set only when you press the appearance control, it holds one word, and it is a record of something you asked for. The network cookie is strictly necessary to serve you the page. Neither is used to profile you, and neither leaves your device for anyone’s purpose but serving the request.
Interrupting every reader with a dialogue asking permission for storage that does nothing to them would be theatre, and it would train people to click through the ones that matter. If we ever add an optional cookie or a third-party script, we will ask for your consent before it runs, and this section will be replaced with the control rather than with an apology.
9. Your controls
You are in control of all of it, from your own browser:
- Clear or block cookies for our domains in your browser settings. Every browser offers this per site.
- Clear site data for this domain to remove the appearance preference, or for the application hostname to remove the sign-in session.
- Use a private window for this site. Nothing of ours persists after you close it.
What blocking costs you: block the network cookie and our provider may challenge or refuse your requests before they reach us. Block storage on the application hostname and you cannot stay signed in, so your instance will not be usable in that browser. Nothing else is affected: every page and every policy on this website stays fully readable with all storage blocked, and the appearance simply follows your system setting.
We set nothing that follows you between sites, so a Do Not Track or Global Privacy Control signal has nothing of ours to switch off. Cookies set by a payment gateway are controlled through its own settings, since they are set on its domain and not on ours.
10. Changes and contact
We may revise this policy, for instance if we change network provider or add a payment method. The version in force is the one published on this page, and the date at the top is the date it took effect. This version is effective 23 August 2026.
Questions about a specific item, or a request to see what we hold about you, go to [email protected]. We respond within 30 days. For a formal complaint, the Grievance Officer is Ashutosh Mishra, at [email protected]. Your rights over your personal data, and how to exercise them, are set out in the Privacy Policy.
Questions about this document
Write to [email protected], or reach the Grievance Officer, Ashutosh Mishra, at [email protected]. Every policy on this site is published by Tristack Technologies LLP, which operates triStack AlgoTrader and is the entity you contract with.
Registered office: B-35, Vinoba Kunj Apartments, Sector 9, Rohini, Delhi 110085, India · LLPIN ACP-3743 · GSTIN 07AAYFT2516N1ZFSee also Terms, Privacy, Cookies, Refunds, Service delivery, Disclaimer and Risk disclosure.