Security
How Nityasha protects your data and how to report a vulnerability.
Security
Last updated: 12 October 2026
Your data and your trust matter to us. This page summarises how Nityasha is secured and how to report a problem.
How we protect your data
- Encryption in transit: all traffic between your devices and Nityasha runs over TLS.
- Encryption at rest: stored credentials, API tokens, and OAuth tokens are encrypted with AES-256.
- Tokenised agent access: connected agents authenticate with hashed tokens and scoped permissions (read / propose / edit); you can revoke a token at any time from settings.
- Database row-level security: user data is isolated per account at the database layer, not only in the application.
- No training on your content: your private data is never used to train general-purpose AI models. See the AI & Data Usage Policy.
- Payments: handled by PCI-DSS compliant processors (Razorpay, Stripe). We never store full card numbers.
Reporting a vulnerability
If you believe you have found a security issue, please report it privately. Do not open a public issue for vulnerabilities.
Email [email protected] with:
- a description of the issue
- the smallest reproduction that demonstrates it
- the impact you believe it has
- whether you intend to publish it eventually
We will acknowledge your report and work with you on a fix and a sensible disclosure timeline. Good-faith research that follows this process will not face legal action from us.
Account security tips
- Use a strong, unique password and do not share your credentials.
- Review connected agents and integrations in settings, and revoke anything you no longer use.
- Report any suspected unauthorised access to your account immediately at [email protected].
Contact
- Security reports: [email protected]
- Privacy requests: [email protected]

