Privacy Policy

1. Who we are

MarktMakrs is operated by APPJS Technologies Private Limited ("we", "us", "our"), a company incorporated in India. This policy explains what personal data we handle when you use the MarktMakrs web application, why we handle it, and what choices you have.

For any privacy question, write to us at support@marktmakrs.in.

2. How you sign in

Signing in with Google is the only way into MarktMakrs. There is no separate registration form, and no password for us to hold or lose: Google authenticates you and tells us who you are. We may restrict or withdraw access to the application at any time.

3. What data we collect

We keep the amount of personal data we handle deliberately small:

• Google account details: when you sign in, Google gives us a signed identity token from which we read your verified email address and your display name. We use these to identify you and to show who is signed in. We do not receive or store your Google password.
• Session data: after a successful sign-in we issue a signed session token that contains your email address and display name. Your browser stores it in local storage and sends it with each request so you stay signed in.
• Your account record: the first time you sign in we create an account for you, holding your email address, your display name, the account identifier Google gives us, the date you joined, the date you last signed in, and whether your access is currently enabled. That is the whole record — we store no password, and nothing about what you look at in the dashboard.
• Technical logs: like any website, our servers may record ordinary request information such as IP address, browser user-agent, timestamps, and the URLs requested. These are used for security and debugging.
• Payment records, if you subscribe: the transaction identifier, the amount, the plan, the status and the date, linked to your account. That is the whole of it.

We do not collect or store payment details. Payments are processed by PhonePe: you enter your card, UPI or bank details on their page, those details go to them and never reach our servers, and what comes back to us is a confirmation — which transaction, how much, whether it succeeded. We could not charge your card ourselves even if we wanted to.

We do not collect government identifiers, contact lists, location data, or your brokerage login credentials. We do not ask you to connect your own broker account in order to use the dashboard.

4. What we do not do

• We do not sell, rent, or trade personal data.
• We do not show ads to you inside the application, and we do not sell advertising space on it. We do run Google's advertising tag, which is described below — it measures our own advertising, it does not put adverts in front of you here.
• We do not build behavioural profiles of you ourselves, and we do not use your data to train machine-learning models. We can't speak for what Google does with what its advertising tag collects — that is covered by Google's own policy.
• We do not send marketing email — we have no mailing list.

5. Why we handle it

We handle the data above only to run the service: to verify that you are permitted to sign in, to keep you signed in, to show the dashboard and its scans, and to keep the application secure and working. We rely on our legitimate interest in operating and securing the application, and on performing the service you have signed in to use.

6. Cookies and local storage

Google's advertising tag sets cookies in your browser to measure our advertising, as described under “Third parties we rely on” below. Apart from those:

• Local storage: your session token, and nothing else. It stays in your browser, is sent back to us with each request so you stay signed in, and clearing your browser data removes it.
• One short-lived, http-only cookie is set only during the administrator flow that links our own market-data connection. It lasts a few minutes, exists purely to secure that redirect, and is never set for ordinary users.

7. Third parties we rely on

• Google (Google Identity Services) handles sign-in. Google's own privacy policy governs what Google does with your Google account and the sign-in itself.
• Zerodha Kite Connect supplies the market data the dashboard displays. This connection is made with our own credentials, held on our server; your personal data is not sent to it.
• PhonePe processes payments if you subscribe. Your card, UPI and bank details are collected and held by them under their own privacy policy (https://www.phonepe.com/privacy-policy/), not by us. We pass them the amount and an order reference, and they tell us whether the payment succeeded.
• Our hosting and infrastructure providers process data on our behalf in order to run the servers.
• Google Fonts serves the typeface this site is set in. Your browser fetches it directly from Google, which means Google receives your IP address and browser details. This happens on every page — including this one, and the home page — whether or not you are signed in, and whether or not you have an account. It sets no cookies.
• Google Ads (the gtag.js tag) measures how well our advertising works — for example, whether someone who clicked one of our adverts went on to sign in. It loads on every page, including this one and the home page, before and whether or not you sign in, and it sets cookies in your browser. It tells Google that a page of ours was viewed, along with your IP address and browser details; Google may also use it to show you our adverts elsewhere. What Google does with that is governed by Google's own privacy policy, and you can limit it through Google's Ads Settings or your browser's cookie controls.

Market data — prices, volumes, indices, and the indicators and signals computed from them — is information about instruments, not about you, and is not personal data.

8. How long we keep it

We keep your account record for as long as your account exists, so that you can sign back in and be recognised. We keep no history of what you did while signed in. Your session token is stateless and expires on its own (by default after seven days), after which you sign in again; signing out removes it from your browser immediately. Server logs are kept only as long as needed for security and troubleshooting.

Payment and transaction records are the exception: tax and accounting law requires us to keep them for a set period, so they survive a deletion request and the closure of your account. We keep only what that obligation needs — the transaction identifier, amount, plan, status and date — and nothing about what you looked at.

9. How we protect it

Traffic is served over HTTPS. Session tokens are cryptographically signed, so they cannot be altered or forged, and every request is verified against that signature before anything is returned. Our market-data access token is held only on the server and is never sent to the browser. No system is perfectly secure, but we limit risk by holding as little personal data as possible.

10. Your rights

You can ask us what data we hold about you, ask us to correct it, or ask us to delete it. Since your account record is short — email address, display name, and when you joined and last signed in — a deletion request means we delete that record and discard server logs that mention you, after which nothing of yours remains. You can also ask us to disable your access without deleting the account. Write to support@marktmakrs.in and we will respond within a reasonable period, and you may stop using the service at any time simply by signing out.

11. Children

MarktMakrs is not intended for anyone under 18, and we do not knowingly handle the data of children.

12. Changes to this policy

If we change how we handle data, we will update this page and the date at the top of it. Continuing to use the application after a change means you accept the updated policy.

13. Contact and governing law

Questions, requests, or complaints about privacy: support@marktmakrs.in. This policy is governed by the laws of India.

If a complaint is not resolved to your satisfaction, you can escalate it: write to support@marktmakrs.in and mark it for the attention of our Grievance Officer. Our contact details are on the Contact page.