Privacy Policy
Effective 30 August 2026.
What this covers
This policy explains what Sarathi · सारथी collects when you use the web app at sarathi.sivaram.dev, the Telegram bot, and the per-user webhook, and what we do with it. Sarathi is operated from India by the operator of Sarathi, referred to here as "we" or "Sarathi".
Sarathi is a demo-stage product. It does not show ads, does not sell your data, and does not run advertising trackers.
Data we collect
Account. When you sign up, Clerk handles the login and gives us your name, email address and a Clerk user id. We store the name and the Clerk id. Your email lives with Clerk; we read it when we need to send you a Stripe receipt or answer a request from you. We also generate two random tokens for you: one for your webhook URL and one for linking Telegram.
Telegram. If you link the bot, we store your Telegram chat id so order cards can be sent to you and your taps can be matched back to your account. We do not store your Telegram contacts, phone number, or any message that is not a bot interaction.
Alerts and orders. Every alert TradingView posts to your webhook is stored as a signal: the raw body, symbol, side, quantity, stop, target, price hint, strategy label, and time received. When you confirm or skip, we record the decision, the size multiplier, the time, and whether it came from Telegram or the web. If the paper broker fills it, we store the fill price, quantity, status, and a broker order id.
Journal. The journal is the signals, decisions and fills above, shown in one place. It is not a separate copy.
Studio chats and strategies. Chats you have in the Strategy Studio are stored with their title, chosen model, and every message. Strategies you save are stored with their name, every version of the Pine Script source, an alert template, any tester results you paste in, and notes.
Billing. We keep a wallet balance and a ledger of every credit purchase, usage debit, delivery charge, adjustment and refund. Stripe sends us an event for each checkout, and we store that event record. It includes the amount, currency, the pack you bought, and the email Stripe used. It never includes your card number. We also record model usage events from OpenRouter: model name, token counts, and cost in US dollars, tied to the chat that caused them.
Broker credentials. If you connect Dhan or Zerodha, you give us an API key, an API secret, and optionally a client id. They are encrypted before they are written to the database. See Security.
Newsletter. The email form on the landing page stores your email address and which page you signed up from. Nothing else.
Technical logs. Our server writes structured request logs: route, timing, outcome, and identifiers such as your user id or a hashed key. These are used to debug and to spot abuse. Cloudflare and Railway keep their own infrastructure logs, which include your IP address and user agent.
How we use it
- To run the service: receive your alerts, render order cards, place the order you confirm, and keep your journal.
- To run the Studio: send your prompts to a model and return the answer.
- To bill you: meter model usage and card deliveries, apply credits, and settle refunds.
- To keep the service safe: rate limiting, dedupe, abuse detection, and debugging.
- To contact you about your account, a purchase, or a change to these documents.
We do not use your data to train models. We do not profile you for marketing.
Third parties we rely on
| Service | What it does | What it sees |
|---|---|---|
| Clerk | Sign-in, sessions, account records | Name, email, login events, session cookies |
| Telegram | Delivers order cards and your taps | Your chat id, the card text, your button presses |
| Stripe | Takes payment for credit packs | Email, amount, card details (Stripe only, never us) |
| OpenRouter and the model providers behind it | Runs Studio chats and generates Pine Script | Your prompts, chat history, and any strategy source in the conversation |
| Cloudflare | Serves the web app from its edge network | IP address, request logs |
| Railway | Hosts the API server and the Postgres database in Singapore | Everything stored in the database, at rest on their infrastructure |
| TradingView | Sends alerts to your webhook | Nothing from us. TradingView is the source of your alerts, not a processor of your data |
When you use the Studio, your prompt leaves our servers and goes to OpenRouter, which routes it to a model provider. Each provider has its own data policy. Do not put broker credentials, passwords, or anything you would not want a model provider to read into a chat.
Where data lives
The database and the API server run on Railway in Singapore. The web app is served by Cloudflare Workers, so static files and page responses may be cached at Cloudflare locations close to you. Clerk, Stripe, Telegram and OpenRouter store data in their own regions under their own terms.
Retention
- Account, signals, journal, chats, strategies and wallet data are kept while your account exists.
- Broker credentials are marked revoked when you disconnect a broker and are then unused. Ask us if you want the encrypted rows deleted outright.
- Stripe event records and the ledger are kept for as long as Indian tax and accounting rules require, even after account deletion.
- Newsletter emails are kept until you unsubscribe or ask to be removed.
- Server logs are short-lived and rotate with the hosting provider's defaults.
Security
- Broker credentials and per-user model API keys are envelope-encrypted with AES-GCM. Each secret gets its own data key, which is wrapped by a server-held master key. The server decrypts a broker credential only at the moment it sends an order. The master key can be rotated.
- All traffic between your browser, Telegram, TradingView, and our server uses TLS.
- The web app never talks to the database. Only the API server can read or write it, and only after checking your Clerk session.
- Your webhook URL is a secret. You can rotate it from Settings, and the old URL stops working immediately.
- We never see or store card numbers. Stripe handles the checkout page.
No system is perfectly secure. If we learn of a breach affecting your data, we will tell you by email.
Your rights
Under India's Digital Personal Data Protection Act, 2023, and as a matter of how we want to run the service, you can:
- Ask for a copy of the personal data we hold about you.
- Ask us to correct anything that is wrong.
- Ask us to delete your account and the data tied to it, subject to the accounting records noted under Retention.
- Ask for an export of your journal and strategies in a machine-readable form.
- Withdraw consent for anything optional, such as the newsletter or the Telegram link, at any time. Unlinking Telegram and unsubscribing are self-serve. Account deletion is by request for now.
Write to hello@sarathi.sivaram.dev from the email on your account. We will reply within 30 days. If you are not satisfied, you may raise a complaint with the Data Protection Board of India once it is operating.
Cookies
- Clerk sets session cookies so you stay signed in. They are required for the dashboard to work.
- Your theme choice, the Studio model you last picked, and whether the setup card is open are stored in your browser's local storage, not in cookies, and never leave your device.
- We do not set advertising or cross-site tracking cookies.
- We run a self-hosted analytics script (varam-analytics.sivaramp.com) that records page views and basic browser details to see which pages are read; it is not an advertising tracker.
Children
Sarathi is for adults. You must be 18 or older to create an account. We do not knowingly collect data from anyone under 18. If you believe a minor has an account, tell us and we will remove it.
Changes
We will update this policy as the product changes, for example when a live broker route ships. The effective date at the top moves when we do. For material changes we will email account holders before the change takes effect.
Contact
Operator: the operator of Sarathi, India. Email: hello@sarathi.sivaram.dev