Your Telegram stays yours.
The short version: your data lives on your own instance and nowhere else. We never sell it, never pool it, never read it beyond the features you press. Signing in creates a normal Telegram device session you can revoke from your phone at any time, and a single click inside the app deletes everything we hold. The only data that ever leaves your instance is a short chat excerpt sent to an AI provider when you use an AI feature.
01Who we are
telegrime is a Telegram BD cockpit built by Yashvini Shukla and Adrian Elson. Contact: yashvinishukla@gmail.com (Yashvini), aelson389@gmail.com (Adrian), or @spacevii on Telegram. Until incorporation completes, the founders are jointly the data controller for the services described here.
02This website (telegrime.com)
- The only personal data collected here is the email address you submit to the waitlist, stored with our forms provider (Netlify) and used solely to contact you about telegrime.
- No analytics scripts, no advertising trackers, no cookies.
- Want your email removed? One message to the contacts above and it's gone.
03The public demo (demo.telegrime.com)
- The demo runs entirely on fictional sample data. Every person, group and message in it is invented.
- There is no login and we collect no personal data from you there, with one exception: if you use the feedback form, we store what you type. The demo resets itself periodically.
04Hosted instances (beta.telegrime.com and per-tester instances)
Each beta tester gets a dedicated instance: their own server process and their own storage, gated by an access code. Instances are not shared and their data is never pooled.
- Telegram sign-in: logging in creates a standard Telegram device session, exactly like signing into Telegram Desktop on a new laptop. You can see it, and revoke it, at any time in Telegram → Settings → Devices. If you use two-step verification, your cloud password passes straight through to Telegram's servers and is never stored, logged or seen by us.
- What your instance stores: the session credential, an index of your chats (names, unread counts, last-message snippets), the contacts, notes, tags, pipeline stages, lists, templates, campaigns and events you create in the app, cached profile photos, and any feedback you send.
- Where it lives: on your instance's private storage volume, hosted on Railway's cloud infrastructure. Nowhere else.
- AI features: when you press an AI feature (summaries, reply drafts, scans, auto-tag), a short excerpt of the relevant chat is sent to the AI provider (Anthropic, or OpenAI if configured) to generate the output. That is the only data that ever leaves your instance, it happens only when you trigger a feature, and per those providers' API terms it is not used to train their models.
- Messages you send: replies and broadcasts go out through your own Telegram account. You are responsible for using them in line with Telegram's terms of service; bulk messaging people who haven't consented can get your Telegram account limited by Telegram.
- Cookies: one signed cookie that remembers you passed the access gate. No tracking or analytics cookies.
- Retention and deletion: your data stays until you remove it. Settings → Delete all my data wipes your instance's database, files and session, and revokes the Telegram device session server-side, in one click, no need to ask us. Revoking the session from Telegram → Settings → Devices also cuts the app's access instantly.
05What we never do
- Sell or rent your data. To anyone. Ever.
- Pool or cross-reference data between users' instances.
- Read your chats for any purpose other than the feature you invoked.
- Run advertising or third-party analytics on any telegrime surface.
06Your rights
Wherever you are, we treat GDPR as the baseline: you can access, export or erase your data. Deletion is self-serve inside the app; for anything else, or for questions, write to yashvinishukla@gmail.com and we'll respond within 30 days. If you're in the EU/UK you also have the right to complain to your data-protection authority.
07Changes
If this policy changes materially we'll note it here with a new effective date, and tell beta testers directly. Continued use after a change means acceptance.