Legal
Cookie Policy
Everything QuantGrid's websites store on your device, named individually. It is a short list: strictly necessary storage, your appearance preference, and two analytics tools on the public website that load only if you allow them. No advertising and no cross-site tracking on either property, and no analytics at all in the dashboard.
- Last updated
- 8 October 2026
- Applies to
- quantgrid.in and the QuantGrid platform
1. What this covers
This policy explains what Tristack Technologies LLP, trading as QuantGrid, stores on your device and why. It covers two properties:
- quantgrid.in, the public website you are reading now.
- app.quantgrid.in, the dashboard you sign in to once you register.
It covers cookies and also browser local storage, 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 collect on our servers and your rights under the Digital Personal Data Protection Act, 2023, is in the Privacy Policy.
It does not cover QuantGrid AlgoTrader, the trading software you install on your own computer. That app keeps its own files on the computer it runs on, and its own pages, which the app serves on that computer, keep their cookies and browser storage there too. The Privacy Policy says what the app keeps on your computer and what it shares with us.
2. Our position, in short
That is a smaller list than most sites publish, and it is deliberate. The two analytics tools measure pages on the public website only, and only for visitors who allow them, and nothing in the dashboard, where your trading is, is measured at all.
3. On the website
The marketing site at quantgrid.in is statically rendered and sets no cookies of its own. You can read every page, including the prices and every policy document, with every cookie blocked.
The two analytics tools listed in section 5, Google Analytics and Microsoft Clarity, are loaded by Google Tag Manager, and none of the three loads until you allow analytics. On your first visit the website asks, at the bottom of the page. If you decline, or make no choice, nothing of Google's or Microsoft's is loaded, no analytics cookie is set, and the website works exactly the same. If you allow them, they set their own cookies on our domain, and Clarity also sets its own on Microsoft's domains, as section 6 says. Section 8 says how your choice is kept and how to change it. The contact form posts what you type in it and nothing more: it sets no cookie, and it does not remember you between visits.
4. In the dashboard
The dashboard at app.quantgrid.in does not use a session cookie. When you sign in, it keeps your access token in browser local storage and sends it with each call it makes to our API. The practical differences worth knowing:
- Signing out, or clearing site data for that domain, removes the token and ends the session on that device.
- The token is scoped to your own account and is the only thing that identifies you to the application.
- It is stored per browser and per device, so signing in on a laptop does not sign you in on a phone.
The dashboard also remembers the appearance you selected, in the same local storage. That is the complete list. Your broker access tokens are never stored in your browser: they are held encrypted on our servers, as described on the security page.
5. The complete inventory
Every item stored on your device by us, or set on our domains by the analytics tools on the public website, what it does and how you remove it. If you find something on our domains that is not on this list, tell us at privacy@quantgrid.in and we will explain it or remove it.
| What | Where it is stored | Purpose | Type | Control |
|---|---|---|---|---|
| Sign-in token | Browser local storage, on the dashboard domain | Keeps you signed in to the dashboard between page loads once you have authenticated. Not a cookie: it is held in local storage and sent by the application when it calls our API. | Strictly necessary | Sign out, or clear site data for the dashboard domain. Clearing it signs you out. |
| Appearance preference | Browser local storage, on this website and on the dashboard domain | Remembers the appearance you selected (light, dark or your system's setting), so it is not reset on every visit. | Preference | Clear site data for the domain and it returns to the default. |
| Analytics choice | Browser local storage, on this website | Remembers whether you allowed or declined analytics on this website, and when, so the two tools below load only if you allowed them and the website does not ask again on every page. Not a cookie. | Strictly necessary | Change it in section 8 at any time. Clear site data for this website and it is forgotten, and the website asks again. |
| Google Analytics (_ga, _ga_*) | Cookie, set on our domain, loaded through Google Tag Manager only after you allow analytics | Counts visits and which pages are read, so we can tell what is useful and what nobody opens. Property G-6T56MSKN21. It measures pages, not people: we do not send it your name, your email or anything about your trading. | Analytics | Decline analytics, or withdraw an earlier Allow in section 8, and it stops loading and these cookies are deleted. Blocking cookies for our domain also stops it. |
| Microsoft Clarity (_clck, _clsk) | Cookie, set on our domain, loaded through Google Tag Manager only after you allow analytics | Records how pages are used, including clicks, scrolling and navigation, and can replay a session as a diagram of those interactions. We use it to find layouts that confuse people. Project xyupuaiht6. Clarity masks text input by default, so what you type is not captured. | Analytics | Decline analytics, or withdraw an earlier Allow in section 8, and it stops loading and these cookies are deleted. Clarity also honours a Do Not Track signal. |
Nothing in that table has a marketing purpose, and none of it is shared with anyone for one.
6. Third parties
The third parties below can set cookies, or have cookies set on our domain on their behalf, while you use our service. Each one is there to do a specific job, and each one is governed by its own policies rather than by this one.
| Who | When they are involved | What they do |
|---|---|---|
| Only if you choose Sign in with Google | Sign-in happens on Google pages, which set Google cookies on Google domains under Google policies. We receive the confirmation that you signed in, your Google account identifier and your email address. Use email and password instead and nothing Google-related is involved. | |
| Razorpay | Only during a payment | Razorpay 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 Razorpay directly and never reach our servers. |
| Google (Tag Manager and Analytics) | Only if you allow analytics on the public website | Google Tag Manager loads our measurement tags, and Google Analytics 4 counts visits and page views under property G-6T56MSKN21. It receives the page you requested, a randomly generated visitor identifier and your approximate location derived from your IP address. It is not given your name, your email or anything about your trading. |
| Microsoft (Clarity) | Only if you allow analytics on the public website | Microsoft Clarity records interactions with the page, including clicks, scrolling and navigation, so we can see where a layout is confusing. Project xyupuaiht6. Text you type into a field is masked by Clarity before it leaves your browser. Clarity also sets its own cookies on Microsoft's domains, such as clarity.ms, under Microsoft's privacy statement. Declining stops them being set; withdrawing an earlier Allow cannot delete those already set, so clear them in your browser settings. |
None of them is an advertising integration, none of them is given your trading data, and nothing collected is sold or shared with an ad network. Who processes 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 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 in the dashboard. The measurement described in section 5 runs on the public website only, so nothing you do with a broker account or a live order is measured.
- No trading data in any analytics tool. Google and Microsoft receive pages and interactions, never an order, a position, a balance or a broker account.
- No sale of cookie or browsing data, to anyone, ever.
This list used to open by denying any analytics at all. That stopped being true when we added Google Analytics and Microsoft Clarity to the public website, and the denial stood here longer than it should have. Both are listed in full in section 5, and this page is the record of what runs rather than of what we would like to be able to say.
8. Your analytics choice
The two analytics items in section 5 are not strictly necessary. The website works identically without them, they exist so we can see which pages are useful and where a layout confuses people, and that is the kind of thing a visitor should be asked about rather than told about. So they run only if you allow them:
- Off until you choose. Until you choose Allow, neither tool is loaded: no Google Tag Manager, no Google Analytics, no Microsoft Clarity, and none of their cookies. With JavaScript switched off, they never load at all.
- Remembered in this browser. Your choice is kept in this browser's local storage, as the analytics choice in section 5, so the website does not ask on every page. A choice made in one browser does not carry over to another, and clearing site data for this website forgets it, so the website asks again.
- A Global Privacy Control signal counts as declining. If your browser sends one and you have not chosen, we treat it as Decline and do not ask. You can still allow analytics below.
- Without your consent, no analytics cookie stays. Until you allow analytics, our pages delete any Google Analytics or Microsoft Clarity cookie left on our domain, an earlier visit's included.
- Change it at any time, here. If you withdraw an earlier Allow, both tools stop loading, their cookies on our domain are deleted from your browser, and every page of this website open in this browser where they were running reloads once, so nothing already running carries on. Clarity's own cookies on Microsoft's domains cannot be deleted from here: clear them in your browser settings.
Your analytics choice
Reading the choice saved in this browser.
Before this control existed, the two tools loaded on every visit, and this section said so and pointed to the browser controls in section 9 as the only way to stop them. Those controls still work, and nothing about the service degrades if you decline, because nothing about the service depends on analytics.
9. Your controls
You are in control of all of it, from your own browser:
- Allow or decline analytics with the choice in section 8, at any time.
- Clear or block cookies for our domains in your browser settings. Every browser offers this per site.
- Clear site data for the dashboard domain to remove the sign-in token and the appearance preference. You will be signed out and the appearance returns to the default.
- Use a private window for the marketing site. Nothing of ours persists after you close it.
What blocking costs you: block storage on the dashboard domain and you cannot stay signed in, so the application will not work. Nothing on the marketing site is affected: every page, price and policy stays fully readable with all storage blocked.
We set nothing that follows you between sites. A Global Privacy Control signal counts as declining analytics, as section 8 says, and Clarity also honours a Do Not Track signal. Cookies set by Google during Sign in with Google, by Razorpay during a payment, or by Microsoft Clarity on Microsoft's own domains once you allow analytics, are set on their own domains and controlled through their settings and policies. The Google Analytics cookies and Clarity's _clck and _clsk are set on our domain, so declining analytics, or blocking cookies for our domain, stops them, and declining also stops Clarity setting its cookies on Microsoft's domains.
10. Changes and contact
We may revise this policy, for instance if we change an analytics tool 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 8 October 2026.
Questions about a specific item, or a request to see what we hold about you, go to privacy@quantgrid.in. We respond within 30 days. For a formal complaint, the Grievance Officer is Devansh Dalmia, at grievance@quantgrid.in. Your rights over your personal data, and how to exercise them, are set out in the Privacy Policy.
Questions about this document
Write to legal@quantgrid.in, or reach the Grievance Officer, Devansh Dalmia, at grievance@quantgrid.in or by phone: call us. Every policy on this site is published by Tristack Technologies LLP, which operates QuantGrid 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.