What we collect
- Account: your email address and a password (stored hashed by our authentication provider — we never see it).
- Your data in the app: watchlist entries and the acknowledgements you sign (which document, which version, when).
- Operational logs: standard server logs (requests, timestamps, IP addresses) kept for security and debugging.
That is the list. We do not collect browsing profiles, analytics identities, advertising identifiers, or your trades.
Cookies
tg sets essential cookies only — the session cookie that keeps you logged in. No tracking cookies, no ads, no third-party cookies.
What we use it for
Running the service: signing you in, storing your watchlists, feeding your watchlisted tickers into the nightly sweep, keeping a record of the acknowledgements you signed, and keeping the service secure. We do not sell or rent your data, and we do not use it for advertising.
Where it lives
Data is processed by our infrastructure providers: Supabase (database and authentication) and Railway (application hosting). When you connect an AI client over MCP, your client's requests are authorized through the same account; we don't receive your conversations — only the tool calls your client makes to tg.
Retention and your rights
Account data is kept while your account exists. You can see your watchlists in the app, and you may request access to or deletion of your account and its data by contacting the operator through the site; deletion removes your account data, with operational logs expiring on their normal short schedule.
Changes
Material changes to this statement will be posted here with a new version date.