Compliance
Compliance Information
Our current compliance posture and the data-protection frameworks PawOS operates under.
Last updated: 31 August 2026
1. Current certification status
PawOS does not currently hold formal security or compliance certifications such as SOC 2 or ISO 27001. We state that plainly rather than imply a certification that doesn't exist. Our actual security practices — encrypted credential storage, row-level data isolation, audit logging, and Confirmation Gates — are documented in full in our Security Policy regardless of certification status.
2. Data protection frameworks
Depending on where you're located, one or more of the following frameworks may apply to how we handle your personal data: India's Digital Personal Data Protection Act, 2023; the GDPR for users in the EU/EEA (including Finland); the Privacy Act 1988 for users in Australia; and state-level privacy laws in the United States. Our Privacy Policy describes, region by region, what we actually do today and where our current practice has gaps — including that we have not appointed an EU representative under Article 27 GDPR and have not executed Standard Contractual Clauses with every sub-processor. This page does not claim compliance beyond what's described there.
3. Payment processing
Payments are processed by Razorpay, which advertises PCI-DSS compliance for its own systems. We do not store your full card or bank account details ourselves.
4. Roadmap
We do not hold a formal security certification today and have no committed date for one. If that changes, we will update this page with real, verifiable status rather than a projected timeline.
5. Contact
General questions about this document: legal@revantaai.com. Privacy and data-protection requests: privacy@revantaai.com. Security reports: security@revantaai.com, following our Vulnerability Disclosure Policy. See also our Grievance Officer contact above where this document includes one.
6. Changes to this document
We may revise this document as PawOS's features or applicable law change. The date at the top of this page reflects the version currently in effect. Where a change is material, we will note it in our Changelog and, where required by law, notify affected users directly (for example, by email or an in-app notice) before the change takes effect. Continuing to use PawOS after a revised document takes effect constitutes acceptance of it.