Legal

Security

Python Analytics · Effective 15 November 2026

How we protect the data you trust us with: hosting in India, encryption, access controls, audit logs, breach notification, and how to report a vulnerability.

1. Our commitment

A compliance product holds sensitive information about your business, so we build security into the platform from the start. This page describes the measures we apply today and what is on our roadmap. We aim to be accurate here rather than impressive.

2. Hosting in India

Complisarthi is hosted on Amazon Web Services in the Asia Pacific (Mumbai) region, ap-south-1. Customer workspace data is stored there. Each customer’s data lives in its own database schema, separate from every other customer’s, and the database is not exposed to the public internet.

3. Encryption

  • In transit: traffic between your browser and Complisarthi is encrypted with TLS.
  • At rest: data stored on our AWS infrastructure is encrypted at rest.
  • Passwords are never stored; we keep only a salted bcrypt hash.
  • Enterprise customers who bring their own AI provider keys have those keys encrypted with AES-256-GCM before storage.
  • Password-reset and email-verification tokens are stored only as one-way hashes, are single-use and expire quickly.

4. Access controls

  • Role-based access control with defined roles, from Company Admin to Viewer, and checks in both the web layer and the server layer.
  • Strict tenant isolation: every query for customer data is pinned to that customer’s own schema.
  • Sessions can be revoked instantly on sign-out, password reset or account suspension.
  • Rate limiting on sign-in, sign-up and password reset to resist guessing and abuse.
  • Payment webhooks are signature-verified, and card details never touch our servers.
  • Access by our own staff to production systems is limited to those who need it and is logged.

5. Audit logs

Security-relevant actions, such as sign-up, profile changes, audit completion and administrative actions, are recorded in a per-workspace audit log with who did it and when. Consent events captured by the Consent Manager are kept in a tamper-evident log. Logs are retained as described in our privacy policy.

6. AI and your data

AI requests go through a gateway we control. We record only metadata about usage (feature, model, token counts), not prompts or outputs. Every AI feature has a non-AI fallback. Enterprise customers can route AI calls with their own provider keys.

7. Breach notification

If a personal data breach affects your data, we will tell you without undue delay after we confirm it, describing what happened, the data involved, what we are doing and what you can do. Where the DPDP Act and Rules require it, we will notify the Data Protection Board of India, and we will give you the information you need to meet your own notification duties, including the 72-hour detailed report.

8. Vulnerability disclosure

If you believe you have found a security vulnerability in Complisarthi, please report it to pi@piai.online with the subject “Security report”.

  • Include what you found, where, and steps to reproduce it.
  • Give us reasonable time to fix the issue before you disclose it publicly.
  • Do not access, change or delete data that is not yours, do not disrupt the service, and do not use social engineering or physical attacks.
  • We will acknowledge your report within three business days, keep you updated, and credit you if you wish once the issue is fixed.
  • We will not pursue legal action against researchers who act in good faith and follow these guidelines.

9. Compliance roadmap

ISO/IEC 27001 certification is planned. It is not yet achieved, and we will not claim it until an accredited auditor has certified us. We will update this page when that changes.

10. Contact

Security questions and reports: pi@piai.online. This version is effective from 15 November 2026.

This page is general information, not legal advice. Complisarthi is software, not a law firm.