VigyanLLM Support & Help
A real person reads every message sent to contact@vigyanllm.in. This page tells you how to reach us, what to include so we can help fast, and what you should never send.
Never send sensitive data to support
Do not include DNA or protein sequences, sample or patient information, passwords, API keys, or card numbers in an email or bug report. We never need them to answer a question or fix a problem.
Contact
Email contact@vigyanllm.in. That mailbox is also linked in the site footer on every page. There is no phone support and no separate support portal — email is the channel.
What to include in a report
- The page URL or tool you were using (for example /primer or /blast)
- Browser and device (for example Firefox 141 on Android)
- Date and time of the problem, with your timezone
- The exact error text or a screenshot of it
- What you expected to happen and what happened instead
This is usually enough to reproduce an issue on our side without needing anything from your input data.
Where to go for common tasks
| Task | Where |
|---|---|
| Email not verified / new verification mail | Sign-in screen → request a new verification email |
| Saved results, exports, plan usage | Dashboard → Usage & Billing (sign-in required) |
| Pricing questions | /pricing (limits and tiers are listed there before you pay) |
| Refund requests | /refund policy, then email with your Razorpay order ID |
| API keys and webhooks | /developer-keys, /developer-webhooks, /developer |
| Policies (privacy, terms, cookies, security) | /privacy, /terms, /cookies, /security |
| Account deletion | /account-deletion |
What support can and cannot answer
We can help with: accounts and verification, billing and subscriptions, product behaviour, documentation questions, and bugs.
We cannot: run analyses on your behalf, interpret results for clinical or diagnostic use (VigyanLLM outputs are research use only), recover data from a deleted account, or advise on sending sensitive data anywhere.
Response expectations
Every message to contact@vigyanllm.in is read by the team. Straightforward questions get straightforward answers; anything that needs investigation takes longer, which is why timestamps, URLs, and error text matter. We do not publish a fixed response-time guarantee — we would rather under-promise and answer properly.
Frequently asked questions
How do I report a bug or broken tool result?
Email contact@vigyanllm.in with the page URL, the tool you used, your browser and device, the date and time (with timezone), the exact error text or a screenshot, and what you expected to happen. That is enough for us to reproduce most problems without needing any of your input data.
What should I never send to support?
Never send DNA or protein sequences, sample or patient information, passwords, API keys, or card numbers. We do not need any of them to answer a question or fix a bug, and support conversations are not the right place for sensitive research or clinical data.
Can support run an analysis for me or give diagnostic advice?
No. VigyanLLM outputs are research-use-only in silico recommendations — see the Terms — and analyses must be run by you in the tools. Support helps with accounts, billing, product behaviour, and bugs, not with experimental design sign-off or clinical interpretation.
How do I verify my email or fix a sign-in problem?
On the sign-in screen you can request a new verification email. If sign-in still fails, email contact@vigyanllm.in from the address you registered with and describe the error you see — never include your password.
Where do I manage billing, invoices, and refunds?
Signed-in users manage their plan under Dashboard → Usage & Billing, and pricing details are on /pricing. Refund requests follow the Refund policy — email contact@vigyanllm.in with your Razorpay order ID (never card or UPI credentials).