Security Policy

Shrim is built for organisations whose data can't be put at risk — including enterprise and government operations. Security is part of the platform by default, not an add-on.

Our approach

• Access control — role-based access, so each department, role, and user sees only what they need.
• Single sign-on — SSO / SAML support for organisations that manage identities centrally.
• Audit logs — a record of who did what, and when.
• Encryption — business data is encrypted to protect it from unauthorised access.
• Data residency — control over where your data is stored, including within India.

Specific security commitments for your organisation are set out in your agreement with us. To discuss your security or compliance requirements, contact bhavy@shrim.cloud.

Reporting a vulnerability

If you believe you've found a security issue in shrim.cloud or the Shrim platform, please email bhavy@shrim.cloud with the subject “Security report” and include enough detail for us to reproduce it.

When researching, please:

• Do not access, change, or delete data that isn't yours.
• Do not disrupt our services — no denial-of-service or automated high-volume testing.
• Give us reasonable time to fix the issue before sharing it publicly.

We will acknowledge your report, keep you updated, and will not take action against good-faith research that follows these guidelines.