Skip to content
TrustOS

Example scenarios

How teams put TrustOS to work.

Three illustrative scenarios drawn from situations we see often, in lending, diagnostics and online retail.

Book a demo

Scenarios on this pageIllustrative

Lending

A lender with three apps and one customer

A mid sized NBFC offers two wheeler loans, gold loans and a credit line, each through its own app. The same customer can appear in all three, plus the collections system and a call centre tool run by a vendor.

A businessman in office attire reading through files with a yellow folder at his desk

  1. The inventory links the three apps, the loan management system, the collections vendor and the data warehouse to one customer record.

  2. Notices for each product are rewritten in plain language, published in English, Hindi and Gujarati, and versioned.

  3. A consent withdrawal for marketing reaches the campaign tool and the vendor's dialler, while loan servicing messages continue because the loan agreement requires them.

  4. Erasure requests are checked against the lender's legal record keeping duties first, so data the lender must keep is restricted and kept, and the customer is told why.

What changesThe privacy lead can answer, for any customer, what they agreed to, what was done and when, without asking three product teams.

Healthcare

A diagnostics chain answering patient requests

A chain of thirty collection centres across Gujarat and Maharashtra sends reports by WhatsApp and email. Patients ask for copies, corrections to names and ages, and sometimes for their data to be deleted.

Two doctors reviewing X-ray images on a laptop

  1. Requests from the front desk, the call centre and the Privacy Centre land in one queue, each with a due date and an owner.

  2. Identity is checked against the booking record before anything is shared, and the check is recorded.

  3. Corrections are made in the lab system through a connector, and the patient gets a confirmation with the corrected report.

  4. Deletion requests are weighed against medical record retention rules, with the reasoning recorded for each case.

What changesRequests stop living in the front desk's personal WhatsApp, and the operations head sees overdue items before patients have to chase.

E-commerce

An online brand rehearsing its first breach

A D2C brand with a Shopify store, a WhatsApp order line, a third party logistics partner and a marketing agency has never had a breach, and has no plan for one.

Warehouse workers carrying boxes between shelves

  1. Each vendor that touches customer data is recorded, with what they hold and the contract terms that apply.

  2. A breach runbook is set up in TrustOS: who decides, who informs customers, who informs the Data Protection Board, and the 72 hour clock for the detailed report.

  3. A tabletop exercise runs a simulated leak from the logistics partner end to end, and the gaps found are assigned as tasks.

  4. Templates for customer and Board intimation are drafted and approved in advance.

What changesIf an incident happens, the team starts from a rehearsed plan with owners and drafts ready.

See 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.

Book a demoTake the gap assessment
Or get a rollout proposal in two minutes
  1. Step 1A 30 minute demo on Google MeetWith someone who knows the Act and the product.
  2. Step 2Your systems and purposesWe walk one product's personal data through TrustOS.
  3. Step 3A first phase you can planModules, owners and effort, written down for you to keep.