Security & Compliance Policies

How Persiv Technology protects PersivX and the data customers put in it: who may access what, how data is protected and kept, how changes are made, and what happens when something goes wrong.

Policy ownerPersiv Technology
Approved byHarsh Jain and Ankit Kumar
Effective from1 November 2026
ReviewedAt least once a year, and after any significant change or incident. Next review: 1 November 2027

Purpose and Scope

These policies set the security rules for building, operating and supporting PersivX. They apply to:

  • the PersivX product: its code, its settings and its releases;
  • servers that Persiv Technology runs PersivX on, hosted on Oracle Cloud (OCI), AWS or Google Cloud, or on-premises;
  • everyone who works on PersivX or can reach those servers. Only Persiv Technology's employees do.

They are written to meet the expectations of a SOC 2 audit (the Security criteria) and of a penetration test (VAPT). Where a page describes what PersivX itself does, such as how long a session lasts, that is the product's actual behaviour and its default setting.

Shared Responsibility

PersivX can run on servers Persiv operates or on servers a customer operates. Who does what depends on that:

AreaPersiv TechnologyWhoever operates the server
Security of the product code, fixes and releasesYesInstalls releases
Secure default settingsYesKeeps them; records any change
Operating system, database, TLS certificates, firewallOn Persiv-run serversOn their own servers
Backups and restore testsOn Persiv-run serversOn their own servers
Users, licences and sharing inside PersivX—The customer's administrators
Which outside services receive data (AI, messaging)Lists them and makes each one switchableDecides which to switch on

The Policies

Governance

  • Ownership. Each policy has a named owner, shown at its top. The security programme is owned by Harsh Jain and Ankit Kumar.
  • Review. Every policy is reviewed at least once a year and after any significant incident, architecture change or audit finding. Changes are approved by Harsh Jain and Ankit Kumar, and the previous version is kept.
  • Acknowledgement. Everyone in scope reads and accepts these policies when they join and after each significant change.
  • Exceptions. An exception to any policy needs written approval from the policy owner, a reason, a compensating control where one exists, and an end date. Exceptions are listed in this policy document and reviewed at each policy review.
  • Breaches of policy are reported by email to support@persivx.com and handled from there.

Reporting a Security Issue

Anyone who finds a security weakness in PersivX can report it to support@persivx.com. Persiv acknowledges a report within 2 days, and handles it under the Vulnerability Management policy. Please don't test against servers you are not authorised to test, and don't access or change other people's data.