Energy and utilities
Bring plant documents, incident records and asset data into the investigation.
Investigate incidentsPrivate AI, built around your business.
Prisov's core product is the foundation for company-specific AI applications, which our forward-deployed engineers develop, deploy and maintain alongside your team.
DPDP Rules 2025 readinessApprovedExportReview 13 itemsApprove
Approved by a named person, exported as the Word record.
Items13
Met8
Partly met2
Not met3
| # | Requirement |
|---|---|
| 1 | Rule 3(b)The notice gives an itemised description of the per… |
| 2 | Rule 3(c)(i)The notice describes how the Data Principal can… |
| 3 | Rule 3(c)(iii)The notice describes how the Data Principal ca… |
| 4 | Rule 6(1)(a)Personal data is secured through encryption, obf… |
| 5 | Rule 6(1)(b)Access to the computer resources that process pe… |
| 6 | Rule 6(1)(c)Access to personal data is visible through logs,… |
| 7 | Rule 6(1)(d)Processing can continue if personal data is comp… |
| 8 | Rule 6(1)(e)Logs and personal data are retained for one year. |
| 9 | Rule 6(1)(f)Contracts with Data Processors provide for reaso… |
ExportMarkdownWord
DPDP Rules 2025 readiness
Prepared on 24 Sep 2026 by Arjun Mehta
Approved on 24 Sep 2026 by Priya Nair
1. Register
| # | Requirement | Status | Reviewer |
|---|---|---|---|
| 1 | Rule 3(b) | Met | Priya Nair |
| 2 | Rule 3(c)(i) | Met | Priya Nair |
| 3 | Rule 3(c)(iii) | Not met | Priya Nair |
| 4 | Rule 6(1)(a) | Met | Priya Nair |
| 5 | Rule 6(1)(b) | Met | Priya Nair |
| 6 | Rule 6(1)(c) | Met | Priya Nair |
| 7 | Rule 6(1)(d) | Met | Priya Nair |
| 8 | Rule 6(1)(e) | Not met | Priya Nair |
| 9 | Rule 6(1)(f) | Partly met | Priya Nair |
| 10 | Rule 7(1) | Partly met | Priya Nair |
| 11 | Rule 7(2)(b) | Not met | Priya Nair |
| 12 | Rule 9 | Met | Priya Nair |
| 13 | Rule 14(3) | Met | Priya Nair |
Runs within the infrastructure you approve
- On-premises
- Private cloud
- Air-gapped
- Hybrid
Inside the core product.
Five connected layers that run within your approved infrastructure, from the records your teams trust to applications people can review.
Connectors
Connectors
Start with the sources your team trusts.
Connect approved sources with their access context.
Responsibilities
- Select the relevant systems and source owners.
- Agree read access, service identities and connection limits.
- Define how updates and removals are detected.
- Agree together
- Which sources are authoritative for this workflow?
Ingestion & processing
Ingestion & processing
Make information usable and traceable.
Prepare usable content without losing its source context.
Responsibilities
- Parse documents and normalize relevant records.
- Retain source references, versions and access rules.
- Identify processing failures and propagate source changes.
- Agree together
- How fresh must the information be?
Knowledge & data
Knowledge & data
Find the evidence the request needs.
Retrieve relevant enterprise context for the authorized user.
Responsibilities
- Organize approved content for the chosen workflow.
- Retrieve relevant information within user permissions.
- Check freshness, relevance and gaps in the evidence.
- Agree together
- What makes a retrieval result complete and useful?
Model gateway
Model gateway
Choose models without rebuilding the workflow.
Route each request under the agreed model and connection policy.
Responsibilities
- Select approved models for the task and environment.
- Apply request, data-boundary and connection policies.
- Compare model changes against agreed evaluation examples.
- Agree together
- Which model fits the quality, licensing and compute needs?
Enterprise AI
Enterprise AI
Put the result into the team’s workflow.
Turn evidence into useful answers or reviewable actions.
Responsibilities
- Present source references and missing evidence.
- Require review or approval where the workflow calls for it.
- Evaluate real examples with the people who own the work.
- Agree together
- Where must a person review or authorize the result?
Built for your industry.
The core product supports company-specific AI applications across industries, shaped around document-intensive reviews, reports and assessments.
Pharma and life sciences
Review site records against applicable GMP requirements, identify gaps and link findings to supporting evidence.
Assess GMP gapsHealthcare
Work with records, claims and clinical documentation available to authorized teams.
Handle recordsFinancial services
Interpret regulatory amendments, identify affected internal documents and assess what needs to change.
Assess regulatory changePublic sector and government
Search approved internal sources within staff permissions.
Search institutional knowledgeProfessional services
Build on engagement knowledge and approved documents within client access boundaries.
Research from firm knowledgeOutputs your reviewers can verify.
Applications connect requirements or changes, source passages, proposed findings and unresolved questions, and are designed to surface missing evidence and uncertainty. Final judgments stay with your authorized professionals.
Within what time must we give the Board detailed information about a personal data breach?
PrisovFrom sources
How this was answered · 49 s
- Updated and detailed information about the breach must reach the Board within seventy-two hours of becoming aware of it.1
- A description of the breach must be sent to the Board without delay.1
- IR-SOP-07 notifies the Board only after the investigation is closed, within 14 days.2
3 citations from 12 passages · in force on 13 May 2027
DPDP Rules 2025 readinessChecking 4 of 13Export
Items13
Met2
Partly met0
Not met1
| # | Requirement | Status | Evidence |
|---|---|---|---|
| 1 | Rule 3(b)The notice gives an itemised description of the per… | Met | 1 claim, 1 citation |
| 2 | Rule 3(c)(i)The notice describes how the Data Principal can… | Met | 1 claim, 1 citation |
| 3 | Rule 3(c)(iii)The notice describes how the Data Principal ca… | Not met | 1 claim, 2 citations |
| 4 | Rule 6(1)(a)Personal data is secured through encryption, obf… | Checking | — |
Claim
Detailed information about a personal data breach is given to the Board within seventy-two hours of becoming aware.
Judge
Supported by its quotesEvidence
The Data Protection Officer notifies the Data Protection Board of India after the investigation is closed, and in any case within 14 days of the breach being confirmed.
IR-SOP-07, version 3, page 1within seventy-two hours of becoming aware of the breach
DPDP Rules, 2025, page 3Review
AcceptEditReject
Ledger entries1,284
Chain integrityVerifiedEvery entry hashes the one before it
On this page7
Refused here1
Ledger
| Entry | When | Action | By | For | Outcome | Hash |
|---|---|---|---|---|---|---|
| #1284 | 24 Sep 2026, 17:42 | Output approved | Priya Nair | DPDP Rules 2025 readiness | Done | 9f2c41e0b7a3 |
| #1283 | 24 Sep 2026, 17:41 | Output approved | Arjun Mehta | DPDP Rules 2025 readiness | Refused | 4be07d19c2f5 |
| #1282 | 24 Sep 2026, 17:39 | Claim reviewed | Arjun Mehta | Requirement 11 of 13 | Done | c81d3a6f0e92 |
| #1281 | 24 Sep 2026, 17:31 | Check started | Arjun Mehta | DPDP Rules 2025 readiness | Done | 07aa5e3b9d14 |
| #1280 | 24 Sep 2026, 17:30 | Run prepared | Arjun Mehta | DPDP Rules 2025 readiness | Done | e3f94c26ab71 |
Confirm that we are fully compliant with every rule.
PrisovFrom sources
No answer from the evidence.
The documents in force on 13 May 2027 do not establish that every requirement is met, so this cannot be confirmed from the evidence.
Each finding is designed to link to the source passage behind it.
Practical value for your teams
Applications designed to reduce manual preparation and review effort while keeping experts in control.
For business teams
Less manual preparation and review, with experts in control.
- Structured reportsPrepared from internal knowledge, in the structure your team uses.
- Document-heavy reviewsFindings linked to their source passages, with missing evidence surfaced.
- Operational and regulatory changesAffected documents identified, with what needs to change.
For IT teams
Less to build and maintain in-house.
- A maintained core productOne shared foundation for every application, in your approved infrastructure.
- Your choice of modelsCompatible open-source or commercial models, based on your requirements.
- Engineering supportOur engineers develop, deploy and maintain your applications.
Start with one document-intensive task.
Discuss one business task with us to define the intended output, data-handling requirements and evaluation scope.