Platform
Ten modules. One record of who did what, and when.
Every module works from the same inventory of personal data, systems and owners. Start with what you need first and add the rest in phases.
In short
What does the TrustOS platform do?
TrustOS runs DPDP Act compliance as everyday work, in ten modules: data inventory, purposes and notices, consent, the Privacy Centre, rights and grievances, retention and erasure, connectors and actions, breach response, processors and assessments, and evidence and audit. Each duty becomes a task with an owner, a due date and a record, and every module works from one inventory of personal data, systems and owners.
4 modules
Map and prepare
Know what personal data you hold, why you hold it, and tell people in plain language.
- Data inventoryData inventory records each system that holds personal data, the fields it keeps, the purposes it serves and the vendors who can reach it. Every other module in TrustOS reads from it, so a notice, an erasure task or a breach assessment starts from the same facts.
- Purposes and noticesPurposes and notices keeps a register of every reason you process personal data, with its ground, data categories and retention period. Notices are built from that register, approved by legal, versioned and published in the languages your customers read.
- ConsentConsent keeps one record per person, purpose and notice version, from every channel where you ask. When someone withdraws, TrustOS tells each system that relies on that consent and records which ones confirmed.
- Privacy CentreThe Privacy Centre is the part of TrustOS your customers, patients or students use. They read your privacy information, change their consents, raise requests and grievances, nominate someone, and see where each request stands.
4 modules
Respond and act
Take every request, withdrawal, erasure and incident to closure, inside the systems that hold the data.
- Rights and grievancesRights and grievances brings requests from the Privacy Centre, email, branches and support tools into one queue. Each request is verified, assigned, worked across systems and closed with a reply and the evidence behind it.
- Retention and erasureSet a retention period for each purpose, with the law or business reason behind it, and let TrustOS raise erasure work when that period ends. Legal holds, tax records and other exceptions are recorded, so nothing is deleted that should stay and nothing stays that should go.
- Connectors and actionsConnectors link TrustOS to the systems that hold personal data, within permissions you set. They search for a person's records, carry out approved actions such as erasure or correction, and confirm the result, including the cases that only partly worked.
- Breach responseOpen an incident the moment personal data may be affected, record when you became aware, and work through scoping, containment and notices with every step timed. TrustOS keeps the intimation to affected people and the Board, and the detailed report due within 72 hours, in one record.
2 modules
Govern and prove
Keep vendors, assessments and evidence in order, so an auditor's question is answered in minutes.
- Processors and assessmentsKeep a register of every processor, what data it receives and the contract terms that govern it, with reviews on a schedule. Run impact assessments for risky processing, including the yearly assessment a Significant Data Fiduciary owes, and track the fixes they lead to.
- Evidence and auditEvery task in TrustOS ends with evidence attached, so proof is gathered as the work happens. When an auditor, the board or the Data Protection Board asks, you assemble an evidence pack for a period or a question, and it can be verified cryptographically.
A data map, growing
From systems, to the data in them, to why you hold it
The map is built in three passes: the systems that hold personal data, the categories of data in each, and the purposes each category serves, with an owner for every purpose, shown for an NBFC.
How the data inventory worksA tour of the modules
Scroll through the platform
Five of the ten modules, each on a sample screen. Every one works from the same inventory of data, systems and owners.
Data inventory
A working record of what personal data you hold, where it sits and who touches it.
Data inventory records each system that holds personal data, the fields it keeps, the purposes it serves and the vendors who can reach it. Every other module in TrustOS reads from it, so a notice, an erasure task or a breach assessment starts from the same facts.
TrustOSCollections diallerAKCollections dialler
- Business owner
- Sneha Iyer, Collections, Pune
- Hosted by
- Vendor, Mumbai data centre
- Data categories
- Name, mobile, loan ID, overdue amount, call recordings
- Linked purposes
- Loan recovery, quality monitoring
- Receives data from
- Loan management system, nightly file
- Open issue
- Recordings have no retention period set
- Entry created, 11 Mar 2026
- Owner confirmed, 02 Jun 2026
- Retention period agreed with legal
- Six month reconfirmation due
Representative screen with sample data. Client screens stay private. Purposes and notices
Decide why you process each kind of data, then tell people in their own language.
Purposes and notices keeps a register of every reason you process personal data, with its ground, data categories and retention period. Notices are built from that register, approved by legal, versioned and published in the languages your customers read.
TrustOSPurpose: Share reports with the referring doctorAKPurpose: Share reports with the referring doctor
- Ground
- Consent, asked at registration
- Data categories
- Name, UHID, lab results, discharge summary
- Systems
- Hospital information system, Patient app
- Retention
- Until consent is withdrawn or the referral closes
- Appears in
- Patient app notice v4, OPD desk notice v2
- Approved by
- Dr Meera Nair, Privacy lead, 18 Sep 2026
- Proposed by Clinical operations
- Ground recorded by legal
- Added to Patient app notice v4
- Gujarati and Hindi versions approved
Representative screen with sample data. Client screens stay private. Consent
Record each consent against the notice shown, and act on withdrawal in every system.
Consent keeps one record per person, purpose and notice version, from every channel where you ask. When someone withdraws, TrustOS tells each system that relies on that consent and records which ones confirmed.
TrustOSWithdrawals awaiting confirmationAKRepresentative screen with sample data. Client screens stay private. Privacy Centre
One page where your customers manage consent, make requests and track them.
The Privacy Centre is the part of TrustOS your customers, patients or students use. They read your privacy information, change their consents, raise requests and grievances, nominate someone, and see where each request stands.
TrustOSPrivacy Centre, September 2026AKPrivacy Centre, September 2026
Visitors signed in
6,412
Consent changes
1,128
Requests raised
214
Grievances raised
37
- English61
- Hindi22
- Gujarati8
- Marathi6
- Tamil3
Representative screen with sample data. Client screens stay private. Rights and grievances
Every request and complaint in one queue, with owners, due dates and a reply on file.
Rights and grievances brings requests from the Privacy Centre, email, branches and support tools into one queue. Each request is verified, assigned, worked across systems and closed with a reply and the evidence behind it.
TrustOSRQ-2026-04417 CorrectionAKRQ-2026-04417 Correction
- Requester
- Lakshmi Reddy, Bengaluru
- Received
- Patient app, 06 Oct 2026
- Change asked
- Date of birth 14 Feb 1986, not 14 Feb 1968
- Verified by
- OTP and Aadhaar masked copy, front desk
- Systems
- Hospital information system, Lab system, Freshdesk
- Due
- 20 Oct 2026, 10 days left
- Request logged and merged with 2 duplicates
- Identity verified
- Hospital information system updated
- Lab system update by Arvind Kulkarni
- Reply sent to patient
Representative screen with sample data. Client screens stay private.
Erasure, everywhere it lives
One request out, a confirmation back from each system
The erasure plan comes from the data inventory. Connectors act where they can, processors confirm, people close manual tasks, and anything kept under a legal duty is recorded with its reason.
How retention and erasure workUnder every module
The same four steps, every time
- Step 1RequirementThe duty, written down and linked to the data and systems it affects.
- Step 2ResponsibilityA named owner, a due date and the steps to follow.
- Step 3ActionDone in the systems that hold the data, by connector or by a person.
- Step 4EvidenceA time stamped record of each step, kept as the work happens.
Built in
What every module shares
Roles and access
Each team sees and edits only what it is responsible for. Every change is attributed to a person.
Due dates and reminders
Clocks start when work arrives, and owners are reminded before anything goes overdue.
One audit trail
Actions across modules land in one trail you can filter by person, system, request or period.
Reports for management
Open work, overdue items and trends, summarised for the board pack or the DPO's monthly review.
Works with your systems
Connectors act on data where it lives. Systems without a connector get a task for a named person.
Deploy where you choose
Your own infrastructure with source code handover, or hosted by us in India.
Go further
The two surfaces, the proof, and the alternatives
For your customers
The Privacy Centre
The page people use to see their choices, raise requests and track them, under your name and in their language.
Learn moreFor reviewers
The evidence TrustOS keeps
What is recorded for each duty, and how an audit, a partner review or a Board inquiry is answered.
Learn moreFair comparisons
TrustOS or something else
When spreadsheets, a consent tool or an in-house build is enough, and where each one strains.
Learn moreSee it with your data
Show us where your personal data lives. We will show you TrustOS running on it.
A 30 minute walkthrough on Google Meet with someone who knows the Act and the product. You leave with a view of your first phase, the owners and the effort.
Or get a rollout proposal in two minutes- Step 1A 30 minute demo on Google MeetWith someone who knows the Act and the product.
- Step 2Your systems and purposesWe walk one product's personal data through TrustOS.
- Step 3A first phase you can planModules, owners and effort, written down for you to keep.